Hi all,

After a few hours fiddling with both TomatoVPN & OpenVPN into pfSense, I got it all working now... this is my first working OpenVPN connection by the way, so I am quite happy here :)

The tunnel is working fine, rebooting the TomatoVPN (on a wrt54) just connects back to my pfSense cheerfully. I just changed everything from UDP to TCP - and this seems to do the trick, and have added a custom configuration (into TomatoVPN) : route 192.168.10.0 255.255.255.0 (192.168.10.0 being the main office)

Added a route into the TomatoVPN, and it works great.


But - a bit "too" great... the tunnel is open for everyone that are sitting behind the TomatoVPN router... and this is not what I had in mind... (being used to IPSEC tunnels, I was somewhat surprised that tun's and taps are being (by default) allowed all traffic...

Reading on, I read that I should disable all the auto-added VPN rules, and add the tun-interface, so I could fiddle with the rules back there... now being already using about 12 IPSEC tunnels, I am a bit worried in doing this, will it affect the already existant IPSEC VPN rules ??

Or is this only for the next IPSEC VPN's that from now on, I need to add additional rules for them... if this is the case, then I don't need to worry (it'll be even more secure this way, no ?)


This is not a 100% crystal clear for me, reading the book at chapter 12.3


Kind regards,
Michel

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Commercial support available - https://portal.pfsense.org

Reply via email to