Re: arplookup 127.0.0.1 failed: could not allocate llinfo
On Sat, Nov 20, 1999 at 12:28:26PM +1030, Daniel J. O'Connor wrote: > Any chance of getting that committed? :) On my list of things to look at for the weekend. -- -- David([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: arplookup 127.0.0.1 failed: could not allocate llinfo
On 19-Nov-99 Luoqi Chen wrote: > configured. Under BSD4.4, there's no need to add such a route, it will be > automatically generated by the kernel. So the simplest solution to this > problem is to delete all `route add xxx 127.0.0.1' statements from the > script. Any chance of getting that committed? :) --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: arplookup 127.0.0.1 failed: could not allocate llinfo
> There is no need to fix kernel if the same result could be achieved by simple > rc.network file modification. Yes, solution proposed in conf/14913 is > not complete and only works in network_interfaces="auto" case, but the > modification to make it work in 100% cases is pretty trivial. > I finally found the problem, it was not a kernel bug, it was dhcp client. In /sbin/dhclient-script, it tried to install a route from localhost to the ether interface, which was bogus if the loop-back interface was not configured. Under BSD4.4, there's no need to add such a route, it will be automatically generated by the kernel. So the simplest solution to this problem is to delete all `route add xxx 127.0.0.1' statements from the script. -lq To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: arplookup 127.0.0.1 failed: could not allocate llinfo
There is no need to fix kernel if the same result could be achieved by simple rc.network file modification. Yes, solution proposed in conf/14913 is not complete and only works in network_interfaces="auto" case, but the modification to make it work in 100% cases is pretty trivial. On 19-Nov-99 Luoqi Chen wrote: >> Well, >> >> I REALLY should search mailing lists before sending useless messages... >> >> There is PR conf/14913 which describes what is going wrong. Will somebody >> commit the fix? >> > I was REALLY surprised that people are so ready to accept this as a > configuration bug. By all means, it is NOT, it is a kernel bug, and > has to be fixed inside the kernel. Users ought to be able to config > interfaces in whatever order they choose. > > -lq > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: arplookup 127.0.0.1 failed: could not allocate llinfo
> Well, > > I REALLY should search mailing lists before sending useless messages... > > There is PR conf/14913 which describes what is going wrong. Will somebody > commit the fix? > I was REALLY surprised that people are so ready to accept this as a configuration bug. By all means, it is NOT, it is a kernel bug, and has to be fixed inside the kernel. Users ought to be able to config interfaces in whatever order they choose. -lq To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: arplookup 127.0.0.1 failed: could not allocate llinfo
Well, I REALLY should search mailing lists before sending useless messages... There is PR conf/14913 which describes what is going wrong. Will somebody commit the fix? On 19-Nov-99 Luoqi Chen wrote: > With the latest current, whenever I start amd, I would see a lot of log > messages repeating: > arplookup 127.0.0.1 failed: could not allocate llinfo > arpresolve: can't allocate llinfo for 127.0.0.1rt > If I ifconfig my ether interface down, as expected, the messages would stop. > It's puzzling that a packet destined for 127.0.0.1 could end up on the output > queue of an ethernet card. It happens only if I run amd, I could telnet > to localhost without any problem. Any idea? > > -lq > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message -- E-Mail: Alexander N. Kabaev <[EMAIL PROTECTED]> Date: 19-Nov-99 Time: 10:39:27 -- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: arplookup 127.0.0.1 failed: could not allocate llinfo
I am having similar problem after installing recent binary snapshot from current.freebsd.org. I do not run amd, but every time when I am trying to ping or telnet to my $HOSTNAME (not localhost!!), I am starting to get these messages. On 19-Nov-99 Luoqi Chen wrote: > With the latest current, whenever I start amd, I would see a lot of log > messages repeating: > arplookup 127.0.0.1 failed: could not allocate llinfo > arpresolve: can't allocate llinfo for 127.0.0.1rt > If I ifconfig my ether interface down, as expected, the messages would stop. > It's puzzling that a packet destined for 127.0.0.1 could end up on the output > queue of an ethernet card. It happens only if I run amd, I could telnet > to localhost without any problem. Any idea? > > -lq > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message -- E-Mail: Alexander N. Kabaev <[EMAIL PROTECTED]> Date: 19-Nov-99 Time: 09:37:48 -- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
