I've added
rightsubnet=0.0.0.0/0
leftsubnet=0.0.0.0/0
to ipsec.conf and now get
connection 'myvpn' established successfully
still no ip addess for the connection (just keep-alives), but that's next I
suppose (need username/password probably)
From: Users on
I think you got the proto's backwards which explain the "no acceptable traffic
selectors found".
conn myvpn
type=transport
authby=secret
pfs=no
rekey=no
keyingtries=1
left=%defaultroute
leftprotoport=udp/l2tp
right=
rightprotoport=udp/%any
auto=add
ike=3des-sha1-modp1536!
Thanks a lot Noel. The connection is up and stable. Very helpful.
One more thing, the remote client is able to ping my private IP, but i am
unable to ping his private IP address. I have checked and my routes seem
OK. What do you suggest?
Below is my status:
*sudo ipsec statusall*
Status of IKE
Thanks a lot Noel. The connection is up and stable. Very helpful.
One more thing, the remote client is able to ping my private IP, but i am
unable to ping his private IP address. I have checked and my routes seem
OK. What do you suggest?
Kind regards,
Moses K
On Thu, Apr 4, 2019 at 9:50 PM Noel
Ok, I have enabled all the logs to level 4. Here is what I get around the
error. Is this any more helpful? Perhaps, I need to set left/rightsubmask? Is
the problem that it used my public ip rather than router internal? I don't
think there is anything else missing from config (I don't have
