No Traffic inbound
-
Hi Guys, wondering if someone can help as I'm struggling to get traffic inbound from my OpenVPN connection with IPVanish. I've successfully configured pfsense as an OpenVPN server and have also set it up as a client for connection to IPVanish, this seems to be working but for some reason I can't route traffic from my torrent server through it. I've followed a few guides and changed all manner of settings but no matter what I've tried when I enable the LAN rule for my torrent server to go through the IPVanish gateway everything just stops. It also seems as though there's packets leaving but none incoming.
I can't see where I've gone wrong with the rules but I suspect it has to be this, unless there's another setting somewhere I'm missing?
Thanks.
-
Deactivate both of those rules on IPVANISH and OpenVPN unless you are looking for connections INBOUND from IPVANISH.
If you are looking for connections INBOUND then IPVANISH has to forward a port to you if you are getting an RFC1918 address from them.
Need to see your rules on LAN. Those are the rules that actually steer your traffic out the VPN.
-
It's currently disabled here as when I do enable it all traffic from my torrent client stops, I lose internet connectivity from the torrentserver etc.
-
How do you expect traffic to route with the rule disabled? And that rule is TCP-only are you sure that's what you want?
-
Also it's my understanding I'd need inbound also for the torrent tracker to see me? Would changing the port forward rule here from WAN to IPVanish be what you mean or is this something at their end?
-
How do you expect traffic to route with the rule disabled? And that rule is TCP-only are you sure that's what you want?
I only disabled it to get it working for the time being on my WAN until I can figure this out.
-
To accept INBOUND connections IPVANISH needs to forward a port to you and you need to forward that port on the IPVANISH interface to your torrent node.
-
To accept INBOUND connections IPVANISH needs to forward a port to you and you need to forward that port on the IPVANISH interface to your torrent node.
OK thanks. I've also tried disabling those IPVanish/OpenVPN rules and also changed the protocal to TCP/UDP but still no joy with outbound.
-
What do you mean by "no joy". What isn't working? Can you not ping? Not resolve names? what? It could be 1000 different things. "no joy" tells us nothing.
-
What do you mean by "no joy". What isn't working? Can you not ping? Not resolve names? what? It could be 1000 different things. "no joy" tells us nothing.
I can ping the virtual IP address provided by IPVanish and I can resolve names, I just can't route any traffic through the tunnel. As soon as I switch the Gateway from my WAN connection I lose internet connectivity.
-
WHAT DO YOU MEAN "LOSE INTERNET CONNECTIVITY" ?
What stops working when you switch the gateway?
-
WHAT DO YOU MEAN "LOSE INTERNET CONNECTIVITY" ?
What stops working when you switch the gateway?
I can't access any web pages, I get the "This webpage is not available" message and my torrent client stops seeding/downloading. I can however ping addresses such as Google.com for example. It just seems I have outbound communication but nothing inbound is working.
-
Does traceroute -n 8.8.8.8 go out the VPN or the WAN?
What does dig @8.8.8.8 www.google.com do?
If you are stuck in a Windows world and don't have reasonable troubleshooting tools, sorry.
-
Finally got this working, I've attached the config that is working but it seems my main issue was the advanced config in the client section. One thing that isn't working though is the port forwarding on the IPVanish interface but I know this is because they don't support it so I'll likely be changing to AirVPN shortly.
One other thing I didn't expect to see was the WAN traffic graph mirroring the IPVanish one. I know for sure that the traffic is leaving the correct interface and just presume this is normal?
-
OpenVPN traffic is going out WAN, comrade.
