"
I did a capture on the ovpnc1 interface while pinging 8.8.8.8 from my test machine and the source address is 192.168.1.6. Now, that interface, ovpnc1, its subnet is 10.8.8.0/24 with IP 10.8.8.60 and gateway 10.8.8.1. That would mean the issue is with NAT, am I right in thinking that?
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Pages1
#1
18.7 Legacy Series / Re: Issue when OpenVPN client is running (suspecting NAT issue)
September 21, 2018, 08:25:02 PM #2
18.7 Legacy Series / Issue when OpenVPN client is running
September 20, 2018, 06:32:26 AM
Hi,
I'm new to OPNsense and I'm trying to set it up as an OpenVPN client for my home network. I got that part and the routing working when OpenVPN isn't running.
OPNsense 18.7.3 is running in VMWare with 2 interfaces for WAN and LAN (192.168.1.2 and 192.168.1.3 respectively) and connected to my home router. On my test machine I set its IP statically with 192.168.1.3 as its gateway. For testing purposes, I have rules on all interfaces (WAN, LAN, NordVPN) to pass all.
As I've said above, when before I setup OpenVPN (or when I stop it) all work fine however when connected all packets on my test machine will timeout; this is seen by simply pinging 8.8.8.8. If I ssh to OPN I don't have any issues there and the vpn is working correctly; this was tested with curl ipinfo.io/ip.
OpenVPN (I think) adds the following route: 0.0.0.0/1 --> 10.8.8.1. If I delete it my test machine will be able to ping 8.8.8.8 again but is obviously not on the VPN. Also, pfctl -sn outputs is empty, I was expecting to see a rule similar to what I'd see when forwarding in iptables but I'm not familiar with pf or FreeBSD in general so if something could shed some light on how packets are forwarded from lan to wan would be nice.
I'm not sure what I did wrong so I'm not sure what additional info to provide, just let me know.
I'm new to OPNsense and I'm trying to set it up as an OpenVPN client for my home network. I got that part and the routing working when OpenVPN isn't running.
OPNsense 18.7.3 is running in VMWare with 2 interfaces for WAN and LAN (192.168.1.2 and 192.168.1.3 respectively) and connected to my home router. On my test machine I set its IP statically with 192.168.1.3 as its gateway. For testing purposes, I have rules on all interfaces (WAN, LAN, NordVPN) to pass all.
As I've said above, when before I setup OpenVPN (or when I stop it) all work fine however when connected all packets on my test machine will timeout; this is seen by simply pinging 8.8.8.8. If I ssh to OPN I don't have any issues there and the vpn is working correctly; this was tested with curl ipinfo.io/ip.
OpenVPN (I think) adds the following route: 0.0.0.0/1 --> 10.8.8.1. If I delete it my test machine will be able to ping 8.8.8.8 again but is obviously not on the VPN. Also, pfctl -sn outputs is empty, I was expecting to see a rule similar to what I'd see when forwarding in iptables but I'm not familiar with pf or FreeBSD in general so if something could shed some light on how packets are forwarded from lan to wan would be nice.
I'm not sure what I did wrong so I'm not sure what additional info to provide, just let me know.
Pages1
