Help on load balancing arplookup 210.213.215.254 failed: host is not on local ne

cheeky · Feb 4, 2007, 2:56 AM

I've updated to the latest snapshot (2-02-2007) and the following error logs appears for my load balancing. 210.213.215.254 is the gateway of WAN.
Cannot surf using the WAN gateway, but ok using the WAN2 gateway.

WAN - PPPoE
OPT1 (wan2) - static IP

Help please.

Feb 4 10:43:07 kernel: arpresolve: can't allocate route for 210.213.215.254
Feb 4 10:43:07 kernel: arplookup 210.213.215.254 failed: host is not on local network
Feb 4 10:43:07 kernel: arpresolve: can't allocate route for 210.213.215.254
Feb 4 10:43:07 kernel: arplookup 210.213.215.254 failed: host is not on local network
Feb 4 10:43:01 kernel: arpresolve: can't allocate route for 210.213.215.254
Feb 4 10:43:01 kernel: arplookup 210.213.215.254 failed: host is not on local network
Feb 4 10:42:58 kernel: arpresolve: can't allocate route for 210.213.215.254
Feb 4 10:42:58 kernel: arplookup 210.213.215.254 failed: host is not on local network
Feb 4 10:42:57 kernel: arpresolve: can't allocate route for 210.213.215.254
Feb 4 10:42:57 kernel: arplookup 210.213.215.254 failed: host is not on local network
Feb 4 10:42:57 kernel: arpresolve: can't allocate route for 210.213.215.254
Feb 4 10:42:57 kernel: arplookup 210.213.215.254 failed: host is not on local network
Feb 4 10:42:54 kernel: arpresolve: can't allocate route for 210.213.215.254

sullrich · Feb 4, 2007, 2:56 AM

Double check the subnet masks on all interfaces.

hoba · Feb 4, 2007, 3:11 AM

I guess you are the first one to try loadbalancing with PPPoE. For PPPoE the gateway is the same IP as the interface has itself. Subnetmaks is /32. Guess that causes some problems with the current loadbalancing code.

sullrich · Feb 4, 2007, 3:12 AM

@hoba:

I guess you are the first one to try loadbalancing with PPPoE. For PPPoE the gateway is the same IP as the interface has itself. Subnetmaks is /32. Guess that causes some problems with the current loadbalancing code.

Heh. Yeah, that will cause a problem I suspect.

cheeky · Feb 4, 2007, 3:29 AM

But i've been using the load balancing feature since release 1.0 up to initial 1.0.1, no problem using PPPoE on WAN.
After updating to snapshots with failover capability, i encountered this problem.
Any workaround on this, please. Thanks.

hoba · Feb 4, 2007, 3:35 AM

So this is an updated system? You need to recreate the pools due to the changes in poolcreation. Edit the pools and delete all the poolmembers. Then add them back with the new gui code. Does that fix it?

cheeky · Feb 4, 2007, 4:22 AM

Actually i have reinstalled the whole system using the latest snapshot ISO, reconfigure from scratch and created new pools for load balancing. I want the failover feature in the latest snapshots. ;D

Now, i've reformatted again my pfsense using the orig 1.0.1 installer, load balancing works perfectly.

hoba · Feb 4, 2007, 10:33 AM

So to get this right: Using the latest snapshot doesn't work with a PPPoE WAN as poolmember but using original 1.0.1 release does work?

cheeky · Feb 4, 2007, 11:42 AM

Yes, hoba. WAN via PPPoE causes problems for load balancing pools using latest snapshots but it is functional using the original 1.0.1.
This must be the cause of my sleepless nights trying to use the latest snapshots in order for my pfsense to have failover capability. ???

hoba · Feb 4, 2007, 3:01 PM

What do you manually assign as gateway when using 1.0.1 releaseversion for the pppoe link?

cheeky · Feb 6, 2007, 8:30 AM

The gateway that i assign for the WAN poolmember is the gateway that i see from the status\interfaces of WAN (assigned automatically by my ISP via PPPoE).

hoba · Feb 6, 2007, 8:31 AM

I guess gateway and interface IP is the same and it is a /32, right?

cheeky · Feb 6, 2007, 8:51 AM

WAN IP is 210.213.171.2xx subnet 255.255.255.255
Gateway IP 210.213.170.x

hoba · Feb 6, 2007, 9:08 AM

Ok, I guess the code is too smart to accept a /32 and a gateway outside this subnet atm. Time to revisit it ;)

cheeky · Feb 9, 2007, 5:13 AM

Any update on this problem? Have this been resolved by the new snapshots?
Thank you very much.

databeestje · Feb 19, 2007, 7:23 PM

please give me the output from the routing table from Diag -> Routes.

I also require the relevant rules from your rules.debug.
using the command page execute the following.
grep route-to /tmp/rules.debug

I do not have a working pppoe test rig so I'm working in the dark here.
Are you willing to provide me access to the box?
I also commited another load balancer fix this evening. Check if that one outputs any messages.

cheeky · Feb 20, 2007, 3:21 PM

I'll try loading the new snapshot later, i'm currently using now the original 1.0.1 iso. So far no problem on my load balancer using PPPoe on WAN but no failover.
I'll post my results immediately.
Yes, i'm willing to open my pfsense firewall for you to debug inside.
Thanks.

dotdash · Feb 21, 2007, 4:48 PM

I am also having this problem. If it helps any, here is some data on my setup:
lan=fxp0
wan=fxp1 (pppoe)
opt1=fxp2 (WAN2 static IP)

wan 100.200.200.110
subnet mask 255.255.255.255
gateway 100.200.200.254

1.0.1 release
worked fine, but ISP turned off ICMP on the next-hop router.
Started monitoring the dns server, but it frequently timed-out and went offline.

Updated using
pfSense-Full-Update-1.0.1-SNAPSHOT-02-14-2007.tgz
Deleted and re-configured balancer.
Started getting messages in system log and no traffic was going out WAN
kernel: arpresolve: can't allocate route for 100.200.200.254
kernel: arplookup 100.200.200.254 failed: host is not on local network

updated to
pfSense-Full-Update-1.0.1-SNAPSHOT-02-18-2007.tgz
Slightly diffferent messages in log

kernel: arpresolve: can't allocate route for 100.200.200.254
kernel: arplookup 100.200.200.254 failed: could not allocate llinfo
kernel: arpresolve: can't allocate route for 192.0.2.113
kernel: arplookup 192.0.2.113 failed: host is not on local network

For now, I have pulled the WAN from the balancer pool
(only has opt1)
The default gateway for my LAN is still the balancer.
I CAN however, create a rule for a specific IP pointing to gateway default
and send that machine out the WAN.

Here is a partial dump of the current routing table
Destination Gateway Flags Refs Use Mtu Netif Expire
default 100.200.200.254 UGS 0 45115 1492 ng0
100.200.200.110 lo0 UHS 0 0 16384 lo0
100.200.200.254 100.200.200.110 UH 1 105 1492 ng0

dotdash · Mar 2, 2007, 3:55 PM

Just got a chance to try with 1.0.1-SNAPSHOT-02-27-2007 (via update firmware)
Still getting 'host is not on local network' error.

hoba · Mar 2, 2007, 3:56 PM

We are missing a testbed to fix this bug atm. We'll work on it soon. Stay tuned.