From owner-freebsd-net@FreeBSD.ORG Mon Jun 11 14:06:54 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 3967016A41F for ; Mon, 11 Jun 2007 14:06:54 +0000 (UTC) (envelope-from rea-fbsd@codelabs.ru) Received: from pobox.codelabs.ru (pobox.codelabs.ru [144.206.177.45]) by mx1.freebsd.org (Postfix) with ESMTP id E36DE13C448 for ; Mon, 11 Jun 2007 14:06:53 +0000 (UTC) (envelope-from rea-fbsd@codelabs.ru) DomainKey-Signature: a=rsa-sha1; q=dns; c=simple; s=one; d=codelabs.ru; h=Received:Date:From:To:Cc:Message-ID:MIME-Version:Content-Type:Content-Disposition:Sender:X-Spam-Status:Subject; b=KRre2SSByMvAD96JjY1gdNtE6/dyqOSMuAueLSTEnF1yOwzB1Fqm7smXI24otgb5fAc3Di2PjLrSZDCbYPvv+5MotXGRzLqF7iLXh7IRZnyx+NT8C+VhADH866+NOlQZ+x4w/xXDEt8VuX/PExN/E5jvEwn/kQ+rLDvKZfx2Rzs=; Received: from void.codelabs.ru (void.codelabs.ru [144.206.177.25]) by pobox.codelabs.ru with esmtpsa (TLSv1:AES256-SHA:256) id 1HxkXh-0009fy-Aw; Mon, 11 Jun 2007 18:06:49 +0400 Date: Mon, 11 Jun 2007 18:06:44 +0400 From: Eygene Ryabinkin To: freebsd-net@freebsd.org Message-ID: <20070611140644.GH86872@void.codelabs.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline Sender: rea-fbsd@codelabs.ru X-Spam-Status: No, score=-1.7 required=4.0 tests=ALL_TRUSTED,AWL,BAYES_40 Cc: shigeaki@f.csce.kyushu-u.ac.jp, freebsd-current@freebsd.org, yongari@freebsd.org Subject: nfe(4) strangeness on the 7-CURRENT X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Jun 2007 14:06:54 -0000 Good day. I had recently upgraded my amd64 box to the 7-CURRENT and started using nfe(4) instead of nve(4), because the latter was almost unusable on the moderate traffic flow from the amd64 box to some other machine due to the watchdog timeouts. But the stock nfe(4) was not good too: it provoked some kernel crashes. So, I resorted to the nfe(4) driver from http://www.f.csce.kyushu-u.ac.jp/~shigeaki/software/freebsd-nfe.html Things are working, but I have many kernel messages like this: ----- TCP: [third_local_machine]:65385 to [second_local_machine]:443 tcpflags 0x4; tcp_input : Listen socket: Spurious RST, segment rejected TCP: [127.0.0.1]:61775 to [127.0.0.1]:40001 tcpflags 0x11; syncache_expand: Segment failed SYNCOOKIE authentication, segment rejected (probably spoofed) TCP: [third_local_machine]:63851 to [second_local_machine]:443 tcpflags 0x4; tcp_input: Listen socket: Spurious RST, segment rejected TCP: [third_local_machine]:62901 to [second_local_machine]:443 tcpflags 0x4; tcp_input: Listen socket: Spurious RST, segment rejected TCP: [third_local_machine]:55359 to [second_local_machine]:443 tcpflags 0x4; tcp_input: Listen socket: Spurious RST, segment rejected TCP: [209.132.176.167]:60779 to [first_local_machine]:25 tcpflags 0x4; tcp_input: Listen socket: Spurious RST, segment rejected TCP: [69.147.83.53]:54604 to [first_local_machine]:25 tcpflags 0x4; tcp_input: Listen socket: Spurious RST, segment rejected TCP: [third_local_machine]:63187 to [second_local_machine]:443 tcpflags 0x4; tcp_input: Listen socket: Spurious RST, segment rejected TCP: [209.132.176.167]:38662 to [first_local_machine]:25 tcpflags 0x4; tcp_input: Listen socket: Spurious RST, segment rejected TCP: [209.132.176.167]:38662 to [first_local_machine]:25 tcpflags 0x4; tcp_input: Listen socket: Spurious RST, segment rejected TCP: [127.0.0.1]:60500 to [127.0.0.1]:40001 tcpflags 0x11; syncache_expand: Segment failed SYNCOOKIE authentication, segment rejected (probably spoofed) ----- I would count this as the hardware or driver failures, but the messages for the 127.0.0.1 shows that this is not related to the packet corruption in the NIC driver. And SSH transfers are working fine, so if there would be packet corruption, then it will broke SSH MAC layer. The motherboard is ASUS M2NPV-VM. The device itself is detected as ----- nfe0: port 0xc800-0xc807 mem 0xfe02b000-0xfe02bfff irq 22 at device 20.0 on pci0 miibus0: on nfe0 e1000phy0: PHY 1 on miibus0 e1000phy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX-FDX, auto nfe0: Ethernet address: 00:18:f3:97:38:85 nfe0: [FILTER] ----- The kernel signature is '7.0-CURRENT FreeBSD 7.0-CURRENT #3: Fri Jun 8 06:26:42 MSD 2007'. The non-default part of my -CURRENT is the usb4bsd stack instead of the stock one. But I had the same error messages without usb4bsd. Should I just relax and ignore the messages, or this is the sign of the brokenness? Thank you! -- Eygene