Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S266242AbUAGQtS (ORCPT ); Wed, 7 Jan 2004 11:49:18 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S266244AbUAGQtS (ORCPT ); Wed, 7 Jan 2004 11:49:18 -0500 Received: from louise.pinerecords.com ([213.168.176.16]:29329 "EHLO louise.pinerecords.com") by vger.kernel.org with ESMTP id S266242AbUAGQtR (ORCPT ); Wed, 7 Jan 2004 11:49:17 -0500 Date: Wed, 7 Jan 2004 17:49:08 +0100 From: Tomas Szepe To: davem@redhat.com Cc: linux-kernel@vger.kernel.org Subject: Networking problems with 2.6.1-rc2 Message-ID: <20040107164908.GA24660@louise.pinerecords.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.1i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1095 Lines: 33 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. -- Tomas Szepe - 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/