mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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
Date: Thu, 8 Jan 2004 09:25:49 +0100	[thread overview]
Message-ID: <20040108082549.GB31515@louise.pinerecords.com> (raw)
In-Reply-To: <20040107164908.GA24660@louise.pinerecords.com>

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>

      reply	other threads:[~2004-01-08  8:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-07 16:49 Tomas Szepe
2004-01-08  8:25 ` Tomas Szepe [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20040108082549.GB31515@louise.pinerecords.com \
    --to=szepe@pinerecords.com \
    --cc=davem@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®