Date: Thu, 8 Jan 2004 09:25:49 +0100
From: Tomas Szepe <szepe@pinerecords.com>
To: davem@redhat.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: Networking problems with 2.6.1-rc2
Message-ID: <20040108082549.GB31515@louise.pinerecords.com>
References: <20040107164908.GA24660@louise.pinerecords.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20040107164908.GA24660@louise.pinerecords.com>
User-Agent: Mutt/1.4.1i
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1301
Lines: 38

On Jan-07 2004, Wed, 17:49 +0100
Tomas Szepe <szepe@pinerecords.com> wrote:

> The box I'm seeing this on has a single inet interface "eth0,"
> which is connected to LAN.
> 
> 	# ip addr add 172.27.0.1/16 brd + dev eth0 label eth0:1
> 	$ nmap -sP -T Insane '172.27.*.*'
> 
> There are no live addresses from the 172.27.0.0/16 range on the LAN.
> After about a minute into the ping sweep, nmap starts printing messages like:
> 
> 	Strange read error from 172.27.4.26: Transport endpoint is not connected
> 	Strange read error from 172.27.4.27: Transport endpoint is not connected
> 	Strange read error from 172.27.4.28: Transport endpoint is not connected
> 	...
> 
> and dmesg reveals these errors:
> 
> 	Neighbour table overflow.
> 	NET: 46 messages suppressed.
> 	...
> 
> Then, trying to issue a simple "ping 172.27.5.5" results in:
> 
> 	connect: No buffer space available
> 
> I'm unable to reproduce the problem with a 2.4 kernel.

I've just verified this problem exists in 2.6.1-rc3 as well as 2.6.1-rc2-mm1.

-- 
Tomas Szepe <szepe@pinerecords.com>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/