From: Tom Rymes <trymes@rymes.com>
To: development@lists.ipfire.org
Subject: Re: [PATCH 1/2] File modified : html/cgi-bin/vpnmain.cgi
Date: Tue, 10 Jul 2018 14:11:47 -0400 [thread overview]
Message-ID: <06b43974-8e19-8194-b376-03ebc0f797b5@rymes.com> (raw)
In-Reply-To: <CAP6ncskL8qFApLXavVfseB_mv=7m6Z9kUyfrri4_dZKa4AqPWQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1927 bytes --]
If I may ask, why IKEv1? Modern iOS and Android both support IKEv2,
don't they?
Tom
On 07/10/2018 2:07 PM, Julien Blais wrote:
> Hi Michael,
>
>
> For it to work, you simply need to generate a Roadwarrior connection per
> certificate. Then, change what is red, either replace cert by
> xauthrsasiget put ikev1 instead of ikev2.
>
> [root(a)ipfire ~]# cat /var/ipfire/vpn/config
> 2,on,Xiaomi,Xiaomi,host,xauthrsasig,,off,,192.168.10.0/255.255.255.0,,,10.0.10.0/29,off,,,off,3,1,aes256,sha2_512,1024|768,aes256,sha2_512,1024|768|none,on,,,clear,on
> <http://192.168.10.0/255.255.255.0,,,10.0.10.0/29,off,,,off,3,1,aes256,sha2_512,1024%7C768,aes256,sha2_512,1024%7C768%7Cnone,on,,,clear,on>,ikev1,120,30,off,start,900
>
> Here is the result in the file :
>
> conn Xiaomi
> left=vpn.jbsky.fr <http://vpn.jbsky.fr>
> leftsubnet=192.168.0.0/24 <http://192.168.0.0/24>
> leftfirewall=yes
> lefthostaccess=yes
> right=%any
> leftcert=/var/ipfire/certs/hostcert.pem
> rightcert=/var/ipfire/certs/Xiaomicert.pem
> ike=aes256-sha2_512-modp1024,aes256-sha2_512-modp768!
>
> esp=aes256-sha2_512-modp1024,aes256-sha2_512-modp768,aes256-sha2_512!
> keyexchange=ikev1
> ikelifetime=3h
> keylife=1h
> dpdaction=clear
> dpddelay=30
> dpdtimeout=120
> authby=xauthrsasig
> xauth=server
> auto=add
> rightsourceip=10.0.10.0/29 <http://10.0.10.0/29>
> fragmentation=yes
>
> Why this patch? it allows to have a functional visual on VPN connections
> in the vpnmain.cgi page. Everything that is IOS or Android works with
> Xauth, you do not support this type of device.
next parent reply other threads:[~2018-07-10 18:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAP6ncskL8qFApLXavVfseB_mv=7m6Z9kUyfrri4_dZKa4AqPWQ@mail.gmail.com>
2018-07-10 18:11 ` Tom Rymes [this message]
[not found] <CAP6ncsnpm30AVsfVE2ywCYQsWu-qjuqASC64Y2eZ+Nq7++V6Dg@mail.gmail.com>
2018-07-12 9:30 ` Michael Tremer
2018-07-09 20:07 jbsky
2018-07-10 17:42 ` Michael Tremer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=06b43974-8e19-8194-b376-03ebc0f797b5@rymes.com \
--to=trymes@rymes.com \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox