No I'm not; I'm quitting to a shell first, and I've even tried quitting when Empeg first boots up.. It seems to be completely random... the actual message is
"neighbour table overflow", and it happens if I try to
a) ftp to empeg
b) telnet to empeg
and sometimes even
c) ping from empeg...

(note that the message is displayed on the serial port...)
Here's what happens w/ ftp:

eth0 Link encap:Ethernet HWaddr 00:02:D7:10:00:9F
inet addr:192.168.0.8 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:12 errors:0 dropped:0 overruns:0 frame:0
TX packets:2 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
Interrupt:7 Base address:0x8000

empeg:/empeg/bin# ftp 192.168.0.8
neighbour table overflow
ftp: connect: No buffer space available

...here's ping:
empeg:/empeg/bin# ping 192.168.0.8
PING 192.168.neighbour table overflow
0.8 (192.168.0.8): 56 data bytes
ping: sendto: No buffer space available
ping: wrote 192.168.0.8 64 chars, ret=-1
neighbour table overflow
ping: sendto: No buffer space available
ping: wrote 192.168.0.8 64 chars, ret=-1
neighbour table overflow
ping: sendto: No buffer space available


What's wierd is, it's RANDOM, sometime it works... any ideas?

-mark

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