Messages

Hi there.

Got it working for me. Very helpful was this post from schnipp:

https://forum.opnsense.org/index.php?topic=9478.msg43057#msg43057

The NAT-Rule was missing.
Still all the traffic goes through the firewall...but better than nothing. ;)

Thx.

Hi khodaeifard.

Did you get this work at least?

We are facing the same problem. Until yesterday our workaround was to route all the traffic through the tunnel, even the internet traffic. Although we did not really want this. Now yesterday we updated our opnsense from an really old release - 16.x i think - to the actual stable version 18.7. and at the moment we aren't even able to provide internet access during up ipsec tunnel. we need to get a solution for this, we have to do both: work remotely in the office lan and have internet access.

Are there any ideas to get this work? any help is appreciated. Thx. Lutz.

hi there.

struggling around with the same configuration (l2tp/ipsec) for the last three days now. didn't get it working al least with any other interface than the WAN. but want to use an ip of the lan respectively an virtual ip assigned to it. for my understanding this should make the internal communication easier.
the binding to the virtual configured interface seems to work, the l2tp log is:

Code Select Expand


l2tps: L2TP: waiting for connection on 10.128.10.240 1701


but the nativ osx-client ist saying:

Code Select Expand


...
L2TP sent SCCRQ
L2TP cannot connect to the server


there are no corresponding entries in the log of the firewall.

the virtual ip is assigned to the lan interface. however even if i take an existing ip of the lan interface this does not succeed.

opnsense is up to date, 16.7.8

any help is appreciated.

best regards,
lutz.