kernel: arpresolve: can't allocate llinfo for 65.59.233.102

[Dominic Blais]

Hi!

I just noticed that it is my default route that is changing for the aforementioned in the subject IP address. What the "$?% could cause that? Could MPD push that route as default? For what reason? That IP address doesn't even belong to us.


--



-----Message d'origine-----
De : Gleb Smirnoff [mailto:glebius at FreeBSD.org] 
Envoyé : 10 septembre 2012 10:03
À : Dominic Blais
Cc : freebsd-net at freebsd.org
Objet : Re: kernel: arpresolve: can't allocate llinfo for 65.59.233.102

On Mon, Sep 10, 2012 at 09:29:44AM -0400, Dominic Blais wrote:
D> Hi,
D> 
D> We have a PPPoE server running FreeBSD 9.0-RELEASE-p3 with mpd-5.6. It used to work very well for 6 weeks and now the "Internet traffic" stops almost each day.
D> 
D> Symptoms:
D> 
D> - I still can ssh to the server from the LAN.
D> - The users connected to mpd by PPPoE can't access Internet.
D> - I tried to do a "whois 65.59.233.102" to know where it's from and the whois server doesn't answer probably because the request never get sent.
D> 
D> 
D> I tried to restart mpd, the users are reconnecting but they still can't access the Internet. I need to reboot to recover from that. Note that, each day it happened, it's always the same IP address (65.59.233.102) that's in the error message. That error appears up to 5 times per second.
D> 
D> Actually, this server has only 1 NIC (bge0). It has an IP on that internet and also a vlan interface (vlan0 [pvid 2]) that's used for PPPoE between mpd and the pppoe clients.

I'm not sure that this message is directly related to connectivity problems.

Have you tried common debugging sequence when internet connectivity breaks:
tcpdumping, looking at ARP table, route table, etc?

-- 
Totus tuus, Glebius.