From owner-freebsd-bugs@FreeBSD.ORG Wed Nov 5 02:50:28 2003 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6DB6816A4CE for ; Wed, 5 Nov 2003 02:50:28 -0800 (PST) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5762243FDD for ; Wed, 5 Nov 2003 02:50:27 -0800 (PST) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.9/8.12.9) with ESMTP id hA5AoOFY071519 for ; Wed, 5 Nov 2003 02:50:24 -0800 (PST) (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.9/8.12.9/Submit) id hA5AoOL2071518; Wed, 5 Nov 2003 02:50:24 -0800 (PST) (envelope-from gnats) Date: Wed, 5 Nov 2003 02:50:24 -0800 (PST) Message-Id: <200311051050.hA5AoOL2071518@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: Vlad Manilici Subject: Re: kern/58927: Verification of reverse path in ip_fw2.c causes problems X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Vlad Manilici List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Nov 2003 10:50:28 -0000 The following reply was made to PR kern/58927; it has been noted by GNATS. From: Vlad Manilici To: freebsd-gnats-submit@FreeBSD.org Cc: Subject: Re: kern/58927: Verification of reverse path in ip_fw2.c causes problems Date: Wed, 5 Nov 2003 05:39:45 -0500 Hi, It seems that not the reverse path check is the problem, but the kernel. Disabling thins check, and testing with "normal" traffic (i.e., same direct and reverse path) brings nothing. I should't have blamed my ISP and this check so quick :). He still has the same IP on 2 different MACs on his Cisco, s.t. I send to one of them (as configured in ARP) and receive from the other. But this strange stuff is a digression :-). Again, my NIC card (3Com 905c-tx) accepts traffic destined to it only when in promiscuous mode. I use the nr. 1 fix. The 2.nd is false. When I boot my old 4.7 partition, I am able to use the card as normal. Thus, I strongly suspect the 5.1 kernel... Also note that 5.1 actually did function on my system correctly. After this problem first occured, I bought another NIC of the same type (3C905C-TX), and changed it. The problem persists. Might there be something wrong with the PCI controller/motherboard? Still, shouldn't the kernel properly detect deffective hardware? As a reference, my boot messages: Copyright (c) 1992-2003 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.1-RELEASE-p10 #12: Wed Nov 5 11:25:18 CET 2003 root@:/usr/obj/usr/src/sys/K2 Preloaded elf kernel "/boot/kernel/kernel" at 0xc04e9000. Preloaded elf module "/boot/kernel/acpi.ko" at 0xc04e921c. Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 999723311 Hz CPU: AMD Athlon(tm) Processor (999.72-MHz 686-class CPU) Origin = "AuthenticAMD" Id = 0x642 Stepping = 2 Features=0x183f9ff AMD Features=0xc0440000 real memory = 268353536 (255 MB) avail memory = 255213568 (243 MB) Pentium Pro MTRR support enabled npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard pcibios: BIOS version 2.10 Using $PIR table, 9 entries at 0xc00f1720 acpi0: power button is handled as a fixed feature programming model. Timecounter "ACPI-fast" frequency 3579545 Hz acpi_timer0: <24-bit timer at 3.579545MHz> port 0xe408-0xe40b on acpi0 acpi_cpu0: on acpi0 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 agp0: mem 0xe4000000-0xe7ffffff at device 0.0 on pci0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: at device 0.0 (no driver attached) isab0: at device 4.0 on pci0 isa0: on isab0 atapci0: port 0xd800-0xd80f at device 4.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 uhci0: port 0xd400-0xd41f irq 9 at device 4.2 on pci0 usb0: on uhci0 usb0: USB revision 1.0 uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered ums0: Logitech USB Mouse, rev 1.10/6.20, addr 2, iclass 3/1 ums0: 4 buttons and Z dir. uhci1: port 0xd000-0xd01f irq 9 at device 4.3 on pci0 usb1: on uhci1 usb1: USB revision 1.0 uhub1: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered uhub1: port error, restarting port 1 uhub1: port error, giving up port 1 ulpt0: Hewlett-Packard DeskJet 845C, rev 1.10/1.00, addr 2, iclass 7/1 ulpt0: using bi-directional mode uhub2: ALCOR Generic USB Hub, class 9/0, rev 1.10/1.00, addr 3 uhub2: 4 ports with 4 removable, self powered pcm0: port 0xa400-0xa43f irq 9 at device 9.0 on pci0 pcm0: xl0: <3Com 3c905C-TX Fast Etherlink XL> port 0xa000-0xa07f mem 0xde800000-0xde80007f irq 5 at device 10.0 on pci0 xl0: Ethernet address: 00:04:75:f8:d6:4a miibus0: on xl0 ukphy0: on miibus0 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto bktr0: mem 0xe1000000-0xe1000fff irq 9 at device 13.0 on pci0 bktr0: Hauppauge Model 44804 C148 bktr0: Warning - Unknown Hauppauge Tuner 0x30 bktr0: Hauppauge WinCast/TV, Philips PAL I tuner. pci0: at device 13.1 (no driver attached) atapci1: port 0x8400-0x843f,0x8800-0x8803,0x9000-0x9007,0x9400-0x9403,0x9800-0x9807 mem 0xde000000-0xde01ffff irq 10 at device 17.0 on pci0 ata2: at 0x9800 on atapci1 ata3: at 0x9000 on atapci1 fdc0: port 0x3f7,0x3f2-0x3f5 irq 6 drq 2 on acpi0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 ppc0 port 0x778-0x77b,0x378-0x37f irq 7 drq 3 on acpi0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold ppbus0: on ppc0 sio0 port 0x3f8-0x3ff irq 4 on acpi0 sio0: type 16550A sio1 port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A atkbdc0: port 0x64,0x60 irq 1 on acpi0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 orm0: