Re: arplookup going mad
On Sun, Feb 16, 2003 at 06:47:47PM +0100, Marc Schneiders wrote: Date: Sun, 16 Feb 2003 18:47:47 +0100 (CET) From: Marc Schneiders [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: arplookup going mad I have posted a question about this earlier, without getting an answer. Then the problem was occasionally. Now the machine is going mad over the same thing. It gives this every second in messages: Feb 16 18:35:06 voo /kernel: arpresolve: can't allocate llinfo for 13.16.2.97rt Feb 16 18:35:06 voo /kernel: arplookup 213.196.2.97 failed: host is not on local network Feb 16 18:35:06 voo /kernel: arpresolve: can't allocate llinfo for 13.16.2.97rt Feb 16 18:35:06 voo /kernel: arplookup 213.196.2.97 failed: host is not on local network Feb 16 18:35:06 voo /kernel: arpresolve: can't allocate llinfo for 13.16.2.97rt Feb 16 18:35:06 voo /kernel: arplookup 213.196.2.97 failed: host is not on local network Feb 16 18:35:06 voo /kernel: arpresolve: can't allocate llinfo for 13.16.2.97rt Feb 16 18:35:06 voo /kernel: arplookup 213.196.2.97 failed: host is not on local network Feb 16 18:35:06 voo /kernel: arpresolve: can't allocate llinfo for 13.16.2.97rt Feb 16 18:35:06 voo /kernel: arplookup 213.196.2.97 failed: host is not on local network Feb 16 18:35:06 voo /kernel: arpresolve: can't allocate llinfo for 13.16.2.97rt Feb 16 18:35:06 voo /kernel: arplookup 213.196.2.97 failed: host is not on local network Feb 16 18:35:06 voo /kernel: arpresolve: can't allocate llinfo for 13.16.2.97rt How do I put an end to this? The IP mentioned is NOT on the local network. I do NOT tell it anywhere it is. Nothing has changed in my config. Why does it do this, and why every second all of a sudden? How do I stop it? man llinfo gives 0, apropos llinfo gives 0. man arplookup: nothing, apropos arplookup: nothing. man 4 arp (not an answer but may be help you to resolve the problem) I rebooted, to no avail. It came back within half an hour. Since the machine is colocated (and not next door) I do not want to lock myself out by trying funny things with arp -s. And I tried that on a machine here, and it refused it anyway for a host not on the local network. As it should, I am sure. Any really good ideas? uname -a: FreeBSD [hostname] 4.7-STABLE FreeBSD 4.7-STABLE #13: Sat Nov 16 16:09:35 CET 2002 marc@[hostname]:/usr/obj/usr/src/sys/FUCHSIA i386 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message -- Regards, Dancho Penev To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: arplookup going mad
Feb 16 18:35:06 voo /kernel: arplookup 213.196.2.97 failed: host is not on local network Feb 16 18:35:06 voo /kernel: arpresolve: can't allocate llinfo for 13.16.2.97rt I had this back in the summer time, and it was due to having an IP address aliased on one of my nics in a block that was not on the local subnet. Check the block the NIC's bound IP is on, then verify that any blocks that the aliases are in are reachable from that machine. Steve How do I put an end to this? The IP mentioned is NOT on the local network. I do NOT tell it anywhere it is. Nothing has changed in my config. Why does it do this, and why every second all of a sudden? How do I stop it? man llinfo gives 0, apropos llinfo gives 0. man arplookup: nothing, apropos arplookup: nothing. man 4 arp (not an answer but may be help you to resolve the problem) I rebooted, to no avail. It came back within half an hour. Since the machine is colocated (and not next door) I do not want to lock myself out by trying funny things with arp -s. And I tried that on a machine here, and it refused it anyway for a host not on the local network. As it should, I am sure. Any really good ideas? uname -a: FreeBSD [hostname] 4.7-STABLE FreeBSD 4.7-STABLE #13: Sat Nov 16 16:09:35 CET 2002 marc@[hostname]:/usr/obj/usr/src/sys/FUCHSIA i386 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message -- Regards, Dancho Penev To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: arplookup going mad
On Mon, 17 Feb 2003, at 16:43 [=GMT-0500], IAccounts wrote: Feb 16 18:35:06 voo /kernel: arplookup 213.196.2.97 failed: host is not on local network Feb 16 18:35:06 voo /kernel: arpresolve: can't allocate llinfo for 13.16.2.97rt I had this back in the summer time, and it was due to having an IP address aliased on one of my nics in a block that was not on the local subnet. Thanks for your eply. Alas, this is not the case. The machine has 3 IP numbers from one half class C from my ISP. And a separate full class C (199.a.b/24) is routed to it. This all works fine. The IP number the arplookup complaints are about is from another server, which I have collocated elsewhere. For a while I thought I had caused the problem by giving two of the three IPs my ISP gave me the same reverse DNS names as two on my other (old) server, which at the time I was considering to take down after two months or so, but didn't. I described this a few months back here. Basically reverse DNS now sees the same name for (names and numbers invented): OLD NEW apple.exter.net 13.16.2.97 apple.exter.net 97.98.99.99 pear.joyrider.nl 13.16.2.98 pear.joyrider.nl 97.98.99.98 u.com2.us 97.98.99.110 (main IP) The normal DNS only gives out 13.14.15.16 for apple.exter.net. The old thing. So if the new machine does a lookup for the IP of its own apple.exter.net, it gets 13.16.2.97, and not the IP on its own NIC, 97.98.99.99. Then it starts looking for 13.16.2.97 and sending these arp complaints. This is what I thought. But I think it isn't relevant. For two reasons: 1. Why not similar problems for pear.joyrider.nl? 2. Why still problems when I change the DNS for apple.exter.net and give it two IPs in the zone for exter.net? 3. Since reverse DNS is not only a mess with me (because I have to deal with sys admins of my ISP to get it changed...), but all over the net, I would think this problem would occur a lot more, if wrong reverse DNS caused it. Check the block the NIC's bound IP is on, then verify that any blocks that the aliases are in are reachable from that machine. Everything works fine, only at times syslog is very busy. By the way, it stopped as miraculously as it started in the mean time. Which makes me believe it is a problem caused by some router. I would like to understand it though... -- [01] All ideas are vintage not new or perfect. http://logoff.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
