Vpn gate openvpn same public ip3/19/2024 ![]() ![]() Pinging the openvpn public IP (lets say it's 200.1.1.1) from internet.I feel it's very close to being 100% so I will just keep asking until I get there. Thanks a lot I removed the rule under Openvpn tab and that took care of the most pressing and frustrating issue for sure. It's a HP360 server, no switch ports as far as I know. What hardware is this? If it's something with switch ports make sure the WAN2 interface isn't set to reflect the WAN1 port state. ![]() Note: This rule is probably coming from the openvpn Server I also have running and therefore potentially unrelated. The (apparently default) config under Openvpn tab (of Firewall rules): I'm attaching some screenshots here for clarity and will test again when I get back to the fw physically. Since you talk of OpenVPN tab (which I didn't notice before), there is an allow all rule there, you mean that could be interfering here? The inbound pass rule for allowing ping is on the VPN interface OPENVPN_PUB1. I think that's what I've done if I'm understanding you correctly. Make sure you don't have a rule on the OpenVPN tab passing that, it must be passed on the assigned interface tab. You would need to do that for inbound traffic so that replys go back over the VPN. Thanks When setting up Gateway group for wan failover I had not changed the default gateway of Pfsense itself to the gateway group (System -> said in OpenVPN client with public IP, don't receive inbound traffic on failover WAN: Removed all rules since they break "reply-to" tags. Firewall -> Rules -> OpenVPN tab: Had an allow-all rule from openvpn server wizard (unrelated to this guide).Strange, right?Īny ideas on what might be going on here?Īlso, I assigned an interface to the vpn client tun/tap device and then allow the ping in through an inbound rule on that interface's IP. It doesn't work until I reconnect WAN cable. ![]() I've tried playing around with the VPN settings and I realized that even though I select WAN2 (not failover group) as interface for the VPN client. I have a ping running toward the public IP and it stops working when the WAN fails over to WAN2. The inbound doesn't work without WAN connected and I can't figure out why. I got to a poiint where the VPN reconnects when I disconnect WAN and on outbound traffic it's coming from the public IP of my VPN. Now, I want to maintain my public IP regardless of active WAN connection so I got a VPN with a public IP. I have pfsense with WAN failover set up and working (WAN, WAN2) ![]()
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |