What would cause this? It happens randomly when trying to telnet/ftp/or ping from/to Empeg... Sometimes it boots up and functions as it should, other times (usually) it gives this message..

Any ideas? Is anyone else experiencing this?
-mark

MK2: 36gb
Tivo: 90gb
CPU: 120gb
...I think drive manufacturers love me!

I posted this in response to your post about this in bug reports, but you never responded. So, in case you missed it...

"FYI,

I get the neighbor table complaints if I have not brought up the loopback interface.

ifconfig lo 127.0.0.1 up

Seems to fix it right up."

-Mike

ifconfig 127.0.0.1 lo up makes the error message go away, but it still doesn't work (ftpd); BUT...
ifconfig eth0 down
ifconfig eth0 up

does... why would it do this???
-mark

MK2: 36gb
Tivo: 90gb
CPU: 120gb
...I think drive manufacturers love me!

IIRC, the loopback interface should be brought up before any eth interfaces, but I don't remember why. If you bring up lo before eth0 (without the eth0 down/up) does it work?

-Mike

Well I've had the same. Every time I get this error there is a 2nd default route to 0.0.0.0 in my route table (route -n). When I delete it (route del default) the error goes away. Installing the loopback seems to fix this also (probably updates the route table) but with me it works fine without.

Don't know for sure where this 2nd default route comes from but it looks as if the player has something to do with it (maybe in combination with synchronizing?).

In short, this is my "normal" routing table :

Kernel IP routing table
Destination_____Gateway________Genmask
10.10.0.0_______0.0.0.0_________255.255.0.0
0.0.0.0_________10.10.0.1_______0.0.0.0

And there's an extra
0.0.0.0_________0.0.0.0_________0.0.0.0

When this error occurs (as for the ___ : bbs eats my spaces).

Walter
-------------------------------------
Reg:1934/Mk1:158-6Blue/Mk2:380-12Blue