From: Paul Lewis (yio@nowanet.pl)
Date: Sun May 04 2003 - 10:17:49 EEST
Hi Readers
Still tracking this down, not a node error after searching around the
Internet for clues. Seems to be a general error message.
Eventually located the following in the kernel log in the early hours..
Lots of these messages
Now to find out how many 'neighbour' are allowed. may be related to the
number of active interfaces I have operational on my system
May 3 20:29:52 gb7cip kernel: neighbour table overflow
May 3 20:29:57 gb7cip kernel: neighbour table overflow
May 3 20:30:02 gb7cip kernel: neighbour table overflow
May 3 20:30:07 gb7cip kernel: neighbour table overflow
May 3 20:30:12 gb7cip kernel: neighbour table overflow
May 3 20:30:17 gb7cip kernel: neighbour table overflow
May 3 20:30:22 gb7cip kernel: neighbour table overflow
Paul
In message <BodzvMB$B$s+azfcekh.bero@roskapostia.tunk.net>, Paul Lewis
<kdw.pxyzq@ua-online.net> writes
>Hello Readers
>
>Anyone got pointers to this error.
>
>Internet search has not come up with an answer.
>Do I have control over the buffer referred to?
>
>Occurred since I added encap routes to my server's gateway
>
>T 44.131.10.55
>GB7CR:CRNODE CRCHAT:GB7CIP-5 connect_to: connect: No buffer space
>available
>
>Paul g4apl
>
-- xpvstees@academica.fi - To unsubscribe from this list: send the line "unsubscribe linux-hams" in the body of a message to htibkcw.zluk@rea-alp.com More majordomo info at http://vger.kernel.org/majordomo-info.html
This archive was generated by hypermail 2b30 : Sun May 04 2003 - 10:29:55 EEST