Arpresolve
-
Hi,
At one of my schools i have dell r310 running esxi
we have a pfsense 2.0 VM running and as of late we've been losing WAN connectivity once or twice a week.
i've posted about this in the multiwan section of the forum 2 weeks ago, since then i've disabled the secondary wan interface, and removed the gateway group. The problem remains the same it seemsanyone know whats going on and how to solve it?
Dec 5 14:45:48 pfsense check_reload_status: Syncing firewall Dec 5 15:25:43 pfsense dhclient: EXPIRE Dec 5 15:25:43 pfsense dhclient: Deleting old routes Dec 5 15:25:43 pfsense dhclient: PREINIT Dec 5 15:25:43 pfsense kernel: arpresolve: can't allocate llinfo for XXX.XXX.WAN.GW Dec 5 15:25:43 pfsense kernel: arpresolve: can't allocate llinfo for XXX.XXX.WAN.GW Dec 5 15:25:43 pfsense kernel: arpresolve: can't allocate llinfo for XXX.XXX.WAN.GW Dec 5 15:25:43 pfsense kernel: arpresolve: can't allocate llinfo for XXX.XXX.WAN.GW Dec 5 15:25:43 pfsense kernel: arpresolve: can't allocate llinfo for XXX.XXX.WAN.G Dec 5 15:25:43 pfsense kernel: arpresolve: can't allocate llinfo for XXX.XXX.WAN.GW Dec 5 15:25:43 pfsense kernel: arpresolve: can't allocate llinfo for XXX.XXX.WAN.GW ..... Dec 5 15:25:52 pfsense kernel: arpresolve: can't allocate llinfo for XXX.XXX.WAN.GW Dec 5 15:25:52 pfsense kernel: arpresolve: can't allocate llinfo for XXX.XXX.WAN.GW Dec 5 15:25:52 pfsense apinger: ALARM: WAN_TELENET(8.8.8.8) *** WAN_TELENETdown *** Dec 5 15:25:52 pfsense kernel: arpresolve: can't allocate llinfo for XXX.XXX.WAN.GW Dec 5 15:25:52 pfsense kernel: arpresolve: can't allocate llinfo for XXX.XXX.WAN.GW ..... Dec 5 15:26:02 pfsense kernel: arpresolve: can't allocate llinfo for XXX.XXX.WAN.GW Dec 5 15:26:02 pfsense check_reload_status: Reloading filter Dec 5 15:26:02 pfsense kernel: arpresolve: can't allocate llinfo for XXX.XXX.WAN.GW ..... Dec 5 15:26:07 pfsense kernel: arpresolve: can't allocate llinfo for XXX.XXX.WAN.GW Dec 5 15:26:07 pfsense php: : The command '/sbin/route change -inet default dynamic' returned exit code '68', the output was 'route: bad address: dynamic' Dec 5 15:26:07 pfsense kernel: arpresolve: can't allocate llinfo for XXX.XXX.WAN.GW Dec 5 15:26:07 pfsense kernel: arpresolve: can't allocate llinfo for XXX.XXX.WAN.GW Dec 5 15:26:07 pfsense kernel: arpresolve: can't allocate llinfo for XXX.XXX.WAN.GW Dec 5 15:26:07 pfsense php: : ERROR! PPTP enabled but could not resolve the $pptpdtarget Dec 5 15:26:07 pfsense kernel: arpresolve: can't allocate llinfo for XXX.XXX.WAN.GW Dec 5 15:26:08 pfsense kernel: arpresolve: can't allocate llinfo for XXX.XXX.WAN.GW .... Dec 5 15:26:15 pfsense kernel: arpresolve: can't allocate llinfo for XXX.XXX.WAN.GW Dec 5 15:26:15 pfsense kernel: arpresolve: can't allocate llinfo for XXX.XXX.WAN.GW Dec 5 15:26:16 pfsense kernel: arpresolve: can't allocate llinfo for XXX.XXX.WAN.GW Dec 5 15:26:44 pfsense dhclient: FAIL Dec 5 15:26:47 pfsense dhclient: ARPSEND Dec 5 15:26:49 pfsense dhclient: ARPCHECK Dec 5 15:26:49 pfsense dhclient: BOUND Dec 5 15:26:49 pfsense dhclient: Starting add_new_address() Dec 5 15:26:49 pfsense dhclient: ifconfig em0 inet XXX.XXX.WAN.IP netmask 255.255.192.0 broadcast 255.255.255.255 Dec 5 15:26:49 pfsense dhclient: New IP Address (em0): XXX.XXX.WAN.IP Dec 5 15:26:49 pfsense dhclient: New Subnet Mask (em0): 255.255.192.0 Dec 5 15:26:49 pfsense dhclient: New Broadcast Address (em0): 255.255.255.255 Dec 5 15:26:49 pfsense dhclient: New Routers (em0): XXX.XXX.WAN.GW Dec 5 15:26:49 pfsense dhclient: Adding new routes to interface: em0 Dec 5 15:26:49 pfsense dhclient: /sbin/route add default XXX.XXX.WAN.GW Dec 5 15:26:49 pfsense dhclient: Creating resolv.conf Dec 5 15:26:49 pfsense check_reload_status: rc.newwanip starting em0 Dec 5 15:26:49 pfsense apinger: alarm canceled: WAN_TELENET(8.8.8.8) *** WAN_TELENETdown *** -
Hi, I have a similar problem.. did you find a solution to this?
-
thus far the problem seems to have been solved
we had 2 wan connections but one of them had been offline for a long time (issue's with the isp)
the problem occured weekly, each time it had something todo with dhcp lease expiring and problem to renew them ….once we managed to get our secondary wan functioning again like it should, the problem went away.( a month now )