2 WAN interfaces
-
Hi,
I have one pfSense with 2 WAN and 1 LAN interface. WAN and OPT1 interfaces get IP through DHCP and have the same gataway. Gateway check is ok for WAN but for OPT1 gateway GW_OPT1 is in state gathering data. After sometime I see in log messages "kernel: arpresolve: can't allocate llinfo for WAN GWIP" (WAN GW IP = GW_OPT1 IP) and then WAN interface stops responding externally, OpenVPN connection gets dropped and so on.
I just did basic setup of interfaces, is there anything else I need to setup?
Thanks!
-
Hi,
Some additional info, I am using pfSense 2.0.3.
Now I have quite a lot and quite often messegeskernel: arpresolve: can't allocate llinfo for WANGWIP
I am running pfSense in ESXi 5.0 with vmware tools installed. This is hosted server. What can be the reason for
kernel: arpresolve: can't allocate llinfo for WANGWIP
??
Thanks
-
What are the monitor IPs for both interfaces? You cannot use the same monitor IP for both interfaces - this might be something to look at.
-
I have one pfSense with 2 WAN and 1 LAN interface. WAN and OPT1 interfaces get IP through DHCP and have the same gataway.
Your WAN interfaces need to have different gateways in order for dual-WAN to work.
-
I have one pfSense with 2 WAN and 1 LAN interface. WAN and OPT1 interfaces get IP through DHCP and have the same gataway.
Your WAN interfaces need to have different gateways in order for dual-WAN to work.
What do you exactly mean by this? Both my wan interfaces have the same gateway IP because they both use the same ISP backbone however they are getting dialed through separate PPPoE interfaces. Will this cause issues?
-
What do you exactly mean by this? Both my wan interfaces have the same gateway IP because they both use the same ISP backbone however they are getting dialed through separate PPPoE interfaces. Will this cause issues?
When you have two WAN interfaces using the same gateway, pfSense has no way to differentiate the routes. They both have the same gateway. Usually pfSense will pick the first route and ignore the second–again because it uses the gateway to differentiate the routes.
-
What are the monitor IPs for both interfaces? You cannot use the same monitor IP for both interfaces - this might be something to look at.
I disabled monitor for both interfaces (first disabled one but then nothing changed) since gateway is always up. But this did not help. System log is flooded/poisoned with messages "kernel: arpresolve: can't allocate llinfo for WANGW_IP".
Both WAN interfaces have the same gateway (WANGW_IP) which is assigned by DHCP, I can't change that.
Is there anything else to check?
-
You can't use the same gateway on two WAN connections. It won't work. You would need to ask your ISP for a different gateways in order to have to unique routes. Otherwise traffic will only go out the default gateway through one WAN connection.
-
But ingress traffic is routed well I think. Right?
Except asking server hosting company to change their policy is there anything else I can do to solve this problem?
-
Try use a router on one of your one of your wan before connecting to PFsense, so that both wans wont use same gateway. It works for me. use external IP to monitor the wan with router.
-
Support for two PPPoE WAN interfaces with the same gateway got added in 2.01, I've had it working (until I upgraded to 2.03 just now…). This may be a regression.
-
I think the confusion is a person can use the same gateway for dual wan, but you need to use "two different monitoring IP's". That is what i did to make my setup not show "Gathering Data State"
-
I think the confusion is a person can use the same gateway for dual wan, but you need to use "two different monitoring IP's". That is what i did to make my setup not show "Gathering Data State"
You can have the same gateway for dual WAN, I am using one such setup now. I think since version 2.0 or maybe 2.0.1 you can have the same gateway for multiple interfaces via PPPoE.
Like this poster said, you need two different monitoring IPs. Really anything will do, but I liked to use my ISP's recommended DNS.I was slamming my head against a wall with this too.
Change it, it should work.