Trouble with double ethernet PCI :(
-
-
Here it is:
$ dmesg Copyright (c) 1992-2009 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 is a registered trademark of The FreeBSD Foundation. FreeBSD 7.2-RELEASE-p5 #0: Sun Dec 6 23:20:31 EST 2009 sullrich@FreeBSD_7.2_pfSense_1.2.3_snaps.pfsense.org:/usr/obj.pfSense/usr/pfSensesrc/src/sys/pfSense_SMP.7 Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Core(TM)2 Duo CPU E7500 @ 2.93GHz (2926.01-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x1067a Stepping = 10 Features=0xbfebfbff <fpu,vme,de,pse,tsc,msr,pae,mce,cx8,apic,sep,mtrr,pge,mca,cmov,pat,pse36,clflush,dts,acpi,mmx,fxsr,sse,sse2,ss,htt,tm,pbe>Features2=0x408e3bd <sse3,dtes64,mon,ds_cpl,vmx,est,tm2,ssse3,cx16,xtpr,pdcm,sse4.1,xsave>AMD Features=0x20100000 <nx,lm>AMD Features2=0x1 <lahf>Logical CPUs per core: 2 real memory = 1037697024 (989 MB) avail memory = 1001541632 (955 MB) ACPI APIC Table: <020410 APIC1108> FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP/HT): APIC ID: 1 ioapic0 <version 2.0="">irqs 0-23 on motherboard wlan: mac acl policy registered kbd1 at kbdmux0 cryptosoft0: <software crypto="">on motherboard padlock0: No ACE support. acpi0: <shuttl shuttle="">on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) acpi0: reservation of 0, a0000 (3) failed acpi0: reservation of 100000, 3dd00000 (3) failed Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 acpi_hpet0: <high precision="" event="" timer="">iomem 0xfed00000-0xfed003ff on acpi0 Timecounter "HPET" frequency 14318180 Hz quality 900 pcib0: <acpi host-pci="" bridge="">port 0xcf8-0xcff on acpi0 pci0: <acpi pci="" bus="">on pcib0 pcib1: <acpi pci-pci="" bridge="">irq 16 at device 1.0 on pci0 pci1: <acpi pci="" bus="">on pcib1 pcib2: <pci-pci bridge="">at device 0.0 on pci1 pci2: <pci bus="">on pcib2 pcib3: <pci-pci bridge="">irq 16 at device 0.0 on pci2 pci3: <pci bus="">on pcib3 re0: <realtek 8168="" 8168b="" 8168c="" 8168cp="" 8168d="" 8111b="" 8111c="" 8111cp="" pcie="" gigabit="" ethernet="">port 0xb800-0xb8ff mem 0xfe8ff000-0xfe8fffff,0xfdef0000-0xfdefffff irq 16 at device 0.0 on pci3 re0: Using 1 MSI messages re0: Chip rev. 0x3c000000 re0: MAC rev. 0x00400000 miibus0: <mii bus="">on re0 rgephy0: <rtl8169s 8110s="" 8211b="" media="" interface="">PHY 1 on miibus0 rgephy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto re0: Ethernet address: 00:e0:4c:68:60:ba re0: [FILTER] pcib4: <pci-pci bridge="">irq 17 at device 1.0 on pci2 pci4: <pci bus="">on pcib4 re1: <realtek 8168="" 8168b="" 8168c="" 8168cp="" 8168d="" 8111b="" 8111c="" 8111cp="" pcie="" gigabit="" ethernet="">port 0xc800-0xc8ff mem 0xfe9ff000-0xfe9fffff,0xfdff0000-0xfdffffff irq 17 at device 0.0 on pci4 re1: Using 1 MSI messages re1: Chip rev. 0x3c000000 re1: MAC rev. 0x00400000 miibus1: <mii bus="">on re1 rgephy1: <rtl8169s 8110s="" 8211b="" media="" interface="">PHY 1 on miibus1 rgephy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto re1: Ethernet address: 00:e0:4c:68:61:56 re1: [FILTER] pcib5: <pci-pci bridge="">irq 18 at device 2.0 on pci2 pci5: <pci bus="">on pcib5 vgapci0: <vga-compatible display="">port 0xac00-0xac07 mem 0xfe400000-0xfe7fffff,0xd0000000-0xdfffffff irq 16 at device 2.0 on pci0 pci0: <multimedia, hda="">at device 27.0 (no driver attached) pcib6: <acpi pci-pci="" bridge="">irq 16 at device 28.0 on pci0 pci6: <acpi pci="" bus="">on pcib6 pcib7: <acpi pci-pci="" bridge="">irq 17 at device 28.1 on pci0 pci7: <acpi pci="" bus="">on pcib7 pci7: <network, ethernet="">at device 0.0 (no driver attached) uhci0: <uhci (generic)="" usb="" controller="">port 0xa880-0xa89f irq 23 at device 29.0 on pci0 uhci0: [GIANT-LOCKED] uhci0: [ITHREAD] usb0: <uhci (generic)="" usb="" controller="">on uhci0 usb0: USB revision 1.0 uhub0: <intel 1="" 9="" uhci="" root="" hub,="" class="" 0,="" rev="" 1.00="" 1.00,="" addr="">on usb0 uhub0: 2 ports with 2 removable, self powered uhci1: <uhci (generic)="" usb="" controller="">port 0xa800-0xa81f irq 19 at device 29.1 on pci0 uhci1: [GIANT-LOCKED] uhci1: [ITHREAD] usb1: <uhci (generic)="" usb="" controller="">on uhci1 usb1: USB revision 1.0 uhub1: <intel 1="" 9="" uhci="" root="" hub,="" class="" 0,="" rev="" 1.00="" 1.00,="" addr="">on usb1 uhub1: 2 ports with 2 removable, self powered uhci2: <uhci (generic)="" usb="" controller="">port 0xa480-0xa49f irq 18 at device 29.2 on pci0 uhci2: [GIANT-LOCKED] uhci2: [ITHREAD] usb2: <uhci (generic)="" usb="" controller="">on uhci2 usb2: USB revision 1.0 uhub2: <intel 1="" 9="" uhci="" root="" hub,="" class="" 0,="" rev="" 1.00="" 1.00,="" addr="">on usb2 uhub2: 2 ports with 2 removable, self powered uhci3: <uhci (generic)="" usb="" controller="">port 0xa400-0xa41f irq 16 at device 29.3 on pci0 uhci3: [GIANT-LOCKED] uhci3: [ITHREAD] usb3: <uhci (generic)="" usb="" controller="">on uhci3 usb3: USB revision 1.0 uhub3: <intel 1="" 9="" uhci="" root="" hub,="" class="" 0,="" rev="" 1.00="" 1.00,="" addr="">on usb3 uhub3: 2 ports with 2 removable, self powered ehci0: <intel 82801gb="" r="" (ich7)="" usb="" 2.0="" controller="">mem 0xfe3f7c00-0xfe3f7fff irq 23 at device 29.7 on pci0 ehci0: [GIANT-LOCKED] ehci0: [ITHREAD] usb4: EHCI version 1.0 usb4: companion controllers, 2 ports each: usb0 usb1 usb2 usb3 usb4: <intel 82801gb="" r="" (ich7)="" usb="" 2.0="" controller="">on ehci0 usb4: USB revision 2.0 uhub4: <intel 1="" 9="" ehci="" root="" hub,="" class="" 0,="" rev="" 2.00="" 1.00,="" addr="">on usb4 uhub4: 8 ports with 8 removable, self powered pcib8: <acpi pci-pci="" bridge="">at device 30.0 on pci0 pci8: <acpi pci="" bus="">on pcib8 skc0: <d-link dge-530t="" gigabit="" ethernet="">port 0xe800-0xe8ff mem 0xfebfc000-0xfebfffff irq 17 at device 9.0 on pci8 skc0: DGE-530T Gigabit Ethernet Adapter rev. (0x9) sk0: <marvell semiconductor,="" inc.="" yukon="">on skc0 sk0: Ethernet address: 1c:af:f7:6c:0a:51 miibus2: <mii bus="">on sk0 e1000phy0: <marvell 88e1011="" gigabit="" phy="">PHY 0 on miibus2 e1000phy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX-FDX, auto skc0: [ITHREAD] isab0: <pci-isa bridge="">at device 31.0 on pci0 isa0: <isa bus="">on isab0 atapci0: <intel ich7="" udma100="" controller="">port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xffaf at device 31.1 on pci0 ata0: <ata 0="" channel="">on atapci0 ata0: [ITHREAD] atapci1: <intel ich7="" sata300="" controller="">port 0xa080-0xa087,0xa000-0xa003,0x9c00-0x9c07,0x9880-0x9883,0x9800-0x980f irq 19 at device 31.2 on pci0 atapci1: [ITHREAD] ata2: <ata 0="" channel="">on atapci1 ata2: [ITHREAD] ata3: <ata 1="" channel="">on atapci1 ata3: [ITHREAD] pci0: <serial bus,="" smbus="">at device 31.3 (no driver attached) acpi_button0: <power button="">on acpi0 speaker0: <pc speaker="">port 0x61 on acpi0 cpu0: <acpi cpu="">on acpi0 est0: <enhanced speedstep="" frequency="" control="">on cpu0 p4tcc0: <cpu frequency="" thermal="" control="">on cpu0 cpu1: <acpi cpu="">on acpi0 est1: <enhanced speedstep="" frequency="" control="">on cpu1 est: CPU supports Enhanced Speedstep, but is not recognized. est: cpu_vendor GenuineIntel, msr 6160b2506000b25 device_attach: est1 attach returned 6 p4tcc1: <cpu frequency="" thermal="" control="">on cpu1 pmtimer0 on isa0 orm0: <isa option="" rom="">at iomem 0xc0000-0xcc7ff pnpid ORM0000 on isa0 atkbdc0: <keyboard controller="" (i8042)="">at port 0x60,0x64 on isa0 atkbd0: <at keyboard="">irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] atkbd0: [ITHREAD] sc0: <system console="">at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio0: configured irq 4 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0: configured irq 4 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 8250 or not responding sio0: [FILTER] sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled vga0: <generic isa="" vga="">at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 ukbd0: <dell 0="" 2="" dell="" usb="" keyboard,="" class="" 0,="" rev="" 1.10="" 2.00,="" addr="">on uhub0 kbd2 at ukbd0 Timecounters tick every 1.000 msec IPsec: Initialized Security Association Processing. ad4: FAILURE - SET_MULTI status=51 <ready,dsc,error>error=4 <aborted>ad4: 7687MB <ssd 8gb="" 02.09092="">at ata2-master SATA150 SMP: AP CPU #1 Launched! Trying to mount root from ufs:/dev/ad4s1a pflog0: promiscuous mode enabled carp0: INIT -> BACKUP re1: link state changed to UP carp0: 2 link states coalesced carp0: link state changed to DOWN sk0: link state changed to UP arp: 192.168.1.250 is on sk0 but got reply from 00:22:19:ba:63:27 on re1 carp0: link state changed to UP carp0: link state changed to DOWN carp0: INIT -> MASTER (preempting) carp0: link state changed to UP arp: 192.168.1.250 is on sk0 but got reply from 00:22:19:ba:63:27 on re1 arp: 192.168.1.250 is on sk0 but got reply from 00:22:19:ba:63:27 on re1 arp: 192.168.1.250 is on sk0 but got reply from 00:22:19:ba:63:27 on re1 arp: 192.168.1.250 is on sk0 but got reply from 00:22:19:ba:63:27 on re1 arp: 192.168.1.250 is on sk0 but got reply from 00:22:19:ba:63:27 on re1 arp: 192.168.1.250 is on sk0 but got reply from 00:22:19:ba:63:27 on re1 arp: 192.168.1.250 is on sk0 but got reply from 00:22:19:ba:63:27 on re1 arp: 192.168.1.250 is on sk0 but got reply from 00:22:19:ba:63:27 on re1 arp: 192.168.1.250 is on sk0 but got reply from 00:22:19:ba:63:27 on re1 arp: 192.168.1.250 is on sk0 but got reply from 00:22:19:ba:63:27 on re1 arp: 192.168.1.250 is on sk0 but got reply from 00:22:19:ba:63:27 on re1 arp: 192.168.1.250 is on sk0 but got reply from 00:22:19:ba:63:27 on re1 arp: 192.168.1.250 is on sk0 but got reply from 00:22:19:ba:63:27 on re1 arp: 192.168.1.250 is on sk0 but got reply from 00:22:19:ba:63:27 on re1 arp: 192.168.1.250 is on sk0 but got reply from 00:22:19:ba:63:27 on re1 arp: 192.168.1.250 is on sk0 but got reply from 00:22:19:ba:63:27 on re1 arp: 192.168.1.250 is on sk0 but got reply from 00:22:19:ba:63:27 on re1 arp: 192.168.1.250 is on sk0 but got reply from 00:22:19:ba:63:27 on re1 arp: 192.168.1.250 is on sk0 but got reply from 00:22:19:ba:63:27 on re1 arp: 192.168.1.250 is on sk0 but got reply from 00:22:19:ba:63:27 on re1 arp: 192.168.1.250 is on sk0 but got reply from 00:22:19:ba:63:27 on re1 arp: 192.168.1.250 is on sk0 but got reply from 00:22:19:ba:63:27 on re1 arp: 192.168.1.250 is on sk0 but got reply from 00:22:19:ba:63:27 on re1 arp: 192.168.1.250 is on sk0 but got reply from 00:22:19:ba:63:27 on re1 arp: 192.168.1.250 is on sk0 but got reply from 00:22:19:ba:63:27 on re1 arp: 192.168.1.250 is on sk0 but got reply from 00:22:19:ba:63:27 on re1 arp: 192.168.1.250 is on sk0 but got reply from 00:22:19:ba:63:27 on re1 arp: 192.168.1.250 is on sk0 but got reply from 00:22:19:ba:63:27 on re1 arp: 192.168.1.250 is on sk0 but got reply from 00:22:19:ba:63:27 on re1 arp: 192.168.1.250 is on sk0 but got reply from 00:22:19:ba:63:27 on re1 arp: 192.168.1.250 is on sk0 but got reply from 00:22:19:ba:63:27 on re1 arp: 192.168.1.250 is on sk0 but got reply from 00:22:19:ba:63:27 on re1 arp: 192.168.1.250 is on sk0 but got reply from 00:22:19:ba:63:27 on re1 arp: 192.168.1.250 is on sk0 but got reply from 00:22:19:ba:63:27 on re1 arp: 192.168.1.250 is on sk0 but got reply from 00:22:19:ba:63:27 on re1 arp: 192.168.1.9 is on sk0 but got reply from 00:26:b9:85:39:3b on re1 arp: 192.168.1.250 is on sk0 but got reply from 00:22:19:ba:63:27 on re1 arp: 192.168.1.9 is on sk0 but got reply from 00:26:b9:85:39:3b on re1 arp: 192.168.1.250 is on sk0 but got reply from 00:22:19:ba:63:27 on re1 arp: 192.168.1.250 is on sk0 but got reply from 00:22:19:ba:63:27 on re1 arp: 192.168.1.9 is on sk0 but got reply from 00:26:b9:85:39:3b on re1 arp: 192.168.1.250 is on sk0 but got reply from 00:22:19:ba:63:27 on re1 arp: 192.168.1.9 is on sk0 but got reply from 00:26:b9:85:39:3b on re1 arp: 192.168.1.250 is on sk0 but got reply from 00:22:19:ba:63:27 on re1 arp: 192.168.1.250 is on sk0 but got reply from 00:22:19:ba:63:27 on re1 arp: 192.168.1.250 is on sk0 but got reply from 00:22:19:ba:63:27 on re1 arp: 192.168.1.250 is on sk0 but got reply from 00:22:19:ba:63:27 on re1 arp: 192.168.1.250 is on sk0 but got reply from 00:22:19:ba:63:27 on re1 arp: 192.168.1.250 is on sk0 but got reply from 00:22:19:ba:63:27 on re1 arp: 192.168.1.9 is on sk0 but got reply from 00:26:b9:85:39:3b on re1 arp: 192.168.1.250 is on sk0 but got reply from 00:22:19:ba:63:27 on re1 arp: 192.168.1.9 is on sk0 but got reply from 00:26:b9:85:39:3b on re1 arp: 192.168.1.250 is on sk0 but got reply from 00:22:19:ba:63:27 on re1 arp: 192.168.1.250 is on sk0 but got reply from 00:22:19:ba:63:27 on re1 arp: 192.168.1.250 is on sk0 but got reply from 00:22:19:ba:63:27 on re1 arp: 192.168.1.250 is on sk0 but got reply from 00:22:19:ba:63:27 on re1 arp: 192.168.1.250 is on sk0 but got reply from 00:22:19:ba:63:27 on re1 arp: 192.168.1.250 is on sk0 but got reply from 00:22:19:ba:63:27 on re1 arp: 192.168.1.250 is on sk0 but got reply from 00:22:19:ba:63:27 on re1 arp: 192.168.1.9 is on sk0 but got reply from 00:26:b9:85:39:3b on re1 arp: 192.168.1.9 is on sk0 but got reply from 00:26:b9:85:39:3b on re1 arp: 192.168.1.250 is on sk0 but got reply from 00:22:19:ba:63:27 on re1 arp: 192.168.1.9 is on sk0 but got reply from 00:26:b9:85:39:3b on re1 arp: 192.168.1.9 is on sk0 but got reply from 00:26:b9:85:39:3b on re1 arp: 192.168.1.250 is on sk0 but got reply from 00:22:19:ba:63:27 on re1 arp: 192.168.1.9 is on sk0 but got reply from 00:26:b9:85:39:3b on re1 arp: 192.168.1.9 is on sk0 but got reply from 00:26:b9:85:39:3b on re1 arp: 192.168.1.250 is on sk0 but got reply from 00:22:19:ba:63:27 on re1 arp: 192.168.1.250 is on sk0 but got reply from 00:22:19:ba:63:27 on re1 arp: 192.168.1.9 is on sk0 but got reply from 00:26:b9:85:39:3b on re1 arp: 192.168.1.250 is on sk0 but got reply from 00:22:19:ba:63:27 on re1 $ pciconf -l -v hostb0@pci0:0:0:0: class=0x060000 card=0x40011297 chip=0x2e308086 rev=0x03 hdr=0x00 class = bridge subclass = HOST-PCI pcib1@pci0:0:1:0: class=0x060400 card=0x40011297 chip=0x2e318086 rev=0x03 hdr=0x01 class = bridge subclass = PCI-PCI vgapci0@pci0:0:2:0: class=0x030000 card=0x40011297 chip=0x2e328086 rev=0x03 hdr=0x00 class = display subclass = VGA none0@pci0:0:27:0: class=0x040300 card=0x40011297 chip=0x27d88086 rev=0x01 hdr=0x00 class = multimedia subclass = HDA pcib6@pci0:0:28:0: class=0x060400 card=0x40011297 chip=0x27d08086 rev=0x01 hdr=0x01 class = bridge subclass = PCI-PCI pcib7@pci0:0:28:1: class=0x060400 card=0x40011297 chip=0x27d28086 rev=0x01 hdr=0x01 class = bridge subclass = PCI-PCI uhci0@pci0:0:29:0: class=0x0c0300 card=0x40011297 chip=0x27c88086 rev=0x01 hdr=0x00 class = serial bus subclass = USB uhci1@pci0:0:29:1: class=0x0c0300 card=0x40011297 chip=0x27c98086 rev=0x01 hdr=0x00 class = serial bus subclass = USB uhci2@pci0:0:29:2: class=0x0c0300 card=0x40011297 chip=0x27ca8086 rev=0x01 hdr=0x00 class = serial bus subclass = USB uhci3@pci0:0:29:3: class=0x0c0300 card=0x40011297 chip=0x27cb8086 rev=0x01 hdr=0x00 class = serial bus subclass = USB ehci0@pci0:0:29:7: class=0x0c0320 card=0x40011297 chip=0x27cc8086 rev=0x01 hdr=0x00 class = serial bus subclass = USB pcib8@pci0:0:30:0: class=0x060401 card=0x40011297 chip=0x244e8086 rev=0xe1 hdr=0x01 class = bridge subclass = PCI-PCI isab0@pci0:0:31:0: class=0x060100 card=0x40011297 chip=0x27b88086 rev=0x01 hdr=0x00 class = bridge subclass = PCI-ISA atapci0@pci0:0:31:1: class=0x01018a card=0x40011297 chip=0x27df8086 rev=0x01 hdr=0x00 class = mass storage subclass = ATA atapci1@pci0:0:31:2: class=0x01018f card=0x40011297 chip=0x27c08086 rev=0x01 hdr=0x00 class = mass storage subclass = ATA none1@pci0:0:31:3: class=0x0c0500 card=0x40011297 chip=0x27da8086 rev=0x01 hdr=0x00 class = serial bus subclass = SMBus pcib2@pci0:1:0:0: class=0x060400 card=0x00000000 chip=0x8232104c rev=0x02 hdr=0x01 class = bridge subclass = PCI-PCI pcib3@pci0:2:0:0: class=0x060400 card=0x00000000 chip=0x8233104c rev=0x02 hdr=0x01 class = bridge subclass = PCI-PCI pcib4@pci0:2:1:0: class=0x060400 card=0x00000000 chip=0x8233104c rev=0x02 hdr=0x01 class = bridge subclass = PCI-PCI pcib5@pci0:2:2:0: class=0x060400 card=0x00000000 chip=0x8233104c rev=0x02 hdr=0x01 class = bridge subclass = PCI-PCI re0@pci0:3:0:0: class=0x020000 card=0x816810ec chip=0x816810ec rev=0x02 hdr=0x00 class = network subclass = ethernet re1@pci0:4:0:0: class=0x020000 card=0x816810ec chip=0x816810ec rev=0x02 hdr=0x00 class = network subclass = ethernet none2@pci0:7:0:0: class=0x020000 card=0x40011297 chip=0x438011ab rev=0x10 hdr=0x00 class = network subclass = ethernet skc0@pci0:8:9:0: class=0x020000 card=0x4b011186 chip=0x4b011186 rev=0x11 hdr=0x00 class = network subclass = ethernet</ssd></aborted></ready,dsc,error></dell></generic></system></at></keyboard></isa></cpu></enhanced></acpi></cpu></enhanced></acpi></pc></power></serial></ata></ata></intel></ata></intel></isa></pci-isa></marvell></mii></marvell></d-link></acpi></acpi></intel></intel></intel></intel></uhci></uhci></intel></uhci></uhci></intel></uhci></uhci></intel></uhci></uhci></network,></acpi></acpi></acpi></acpi></multimedia,></vga-compatible></pci></pci-pci></rtl8169s></mii></realtek></pci></pci-pci></rtl8169s></mii></realtek></pci></pci-pci></pci></pci-pci></acpi></acpi></acpi></acpi></high></shuttl></software></version></lahf></nx,lm></sse3,dtes64,mon,ds_cpl,vmx,est,tm2,ssse3,cx16,xtpr,pdcm,sse4.1,xsave></fpu,vme,de,pse,tsc,msr,pae,mce,cx8,apic,sep,mtrr,pge,mca,cmov,pat,pse36,clflush,dts,acpi,mmx,fxsr,sse,sse2,ss,htt,tm,pbe> -
You have three network interfaces on the system: re0, re1 and sk0.
You apparently have a D-Link DGE-530T card (the Startech card is a rebadged DLink?)
re1 and sk0 were reported UP (the interfaces saw carrier from a switch or other system). Is anything connected to re0?
The kind of message:
arp: 192.168.1.250 is on sk0 but got reply from 00:22:19:ba:63:27 on re1
arp: 192.168.1.250 is on sk0 but got reply from 00:22:19:ba:63:27 on re1
arp: 192.168.1.250 is on sk0 but got reply from 00:22:19:ba:63:27 on re1
arp: 192.168.1.250 is on sk0 but got reply from 00:22:19:ba:63:27 on re1suggests there is some kind of confusion about sk0 and re1, for example the IP address of sk0 is 192.168.1.x/24 but a system with IP address 192.168.1.250 is on the network connected to re1 when it should be on the network connected to sk0. Maybe you should swap the cables on sk0 and re1.
From your description I suspect you have one port (called sk0) on the motherboard and two ports (called re0 and re1) on a plug-in card .
-
The Startech card is a dual Realtek 8111 card using a PLX bridge to provide the interface for both NICs from a single PCI-e x1.
He apparently also has a D-Link DGE-530T PCI card.The Shuttle PC, it seems, uses a Marvell Phy. connected to the Intel chipset similar to how CSA works. Hence, it shows up as:
e1000phy0 -
Dreamslacker, your reply caused me to look a bit more closely at the pciconf output. That shows there are four ethernet devices visible in the PCI device tree, one of which is unrecognised by the operating system. (pciconf shows this as device none2). Analysis of the pciconf data shows its a device made by Marvell (chip=0xyyyy11ab) part of a Shuttle Computer assembly (card=0xyyyy1297), so this is probably the on-board NIC.
The e1000phy is on miibus2 which is on sk0 which is on skc0, the D-Link DGE-530T.
Some of the PCI bridges are TI parts (chip=0xyyyy104c) but that's not relevant to the current issue.
In summary, there are 4 devices in this system which identify themselves as Ethernet devices, there are drivers for three of them and the remaining one is probably the motherboard NIC.
-
Indeed this Shuttle has 4 ethernet ports, 2 of them in one card. :)
But only one port in the 2-port card has any function. It's coming up as re0. The other single port card is sk0.
So there is only re0, re1, and sk0. Only one port in the 2-port card is usable, but I cannot get the other to working.
In attempting to assign interfaces, this is the result initially from looking at option 1:
re0 00:e0:4c:68:60:ba
re1 00:e0:4c:68:61:56 (up)
sk0 1c:af:f7:6c:0a:51 (up)
tun0 0 (up)
tun1 0 (up)In any case I can only get 3 MAC addresses out of this directly from the console but a MAC scan with all ports on a switch show only one.
This Shuttle is intended to replace an existing older shuttle and is using thta shuttle's settings, except for LAN, but since I have changed things around for troubleshooting and so I can connect the ports to the network for testing.
I was thinking of removing the other card (the single port), and seeing if the behavior changes at all - the idea is to get that second port on the 2-port card to work, and it has not shown any response thus far. Perhaps there is a way to scan for this hardware, or am I missing a jumper somewhere? This is most confusing but enjoyable in seeing if this would work. My other shuttle is using one board-based port, and a single port card, and then 2 USB ethernet adaptors. The use of the 2-port card is new for me, having not worked with these before.
-
The e1000phy is on miibus2 which is on sk0 which is on skc0, the D-Link DGE-530T.
Which is the odd thing, I have the exact same card and am pretty sure the e1000phy doesn't show up on that interface. Whereas Shuttle is fairly fond of using Marvell Phys and NICs.
If he's using any of the 'newer' G3X/ G41 XPCs, this would be a 88E8056 nic supported by the MSK(4) driver.
I'm wondering if the issue actually lies with the use of the PCIe card. The PCIe x16 slot technically only supports a single PCIe x1 device without disabling the integrated graphics.
No one that I know of has actually placed a PCIe x1 device with a PCIe bridge onboard on such a setup so that bridge chip might be causing issues with the assignment of IRQs. -
The e1000phy is on miibus2 which is on sk0 which is on skc0, the D-Link DGE-530T.
Which is the odd thing, I have the exact same card and am pretty sure the e1000phy doesn't show up on that interface. Whereas Shuttle is fairly fond of using Marvell Phys and NICs.
If he's using any of the 'newer' G3X/ G41 XPCs, this would be a 88E8056 nic supported by the MSK(4) driver.
I'm wondering if the issue actually lies with the use of the PCIe card. The PCIe x16 slot technically only supports a single PCIe x1 device without disabling the integrated graphics.
No one that I know of has actually placed a PCIe x1 device with a PCIe bridge onboard on such a setup so that bridge chip might be causing issues with the assignment of IRQs.By chance would the disabling of the on-board graphics change the behavior?
-
By chance would the disabling of the on-board graphics change the behavior?
It might just work but the system might choose not to boot in such an instance due to the lack of graphics. You can always try to do so but a CMOS reset is required if it doesn't work out.
Also, this means that you need either the embedded variant or enable the console output on the harddisk install.
1) Remove the Realtek NIC
2) Install pfsense
3) Set the output redirect to serial console via WebGUI
4) Replace the realtek nic and disable onboard graphics
5) Boot and hook up another computer via serial 9600/8/N/1
6) Reconfigure the interfaces off the serial consoleThe way I look at it, you have 3 devices sharing 1 IRQ off the PCIe slot (Int. gfx & 1 each for each of the realtek interfaces) - something that the platform wasn't designed to do (it was meant to only share 2 devices - 1 PCIe x1 and the Int. gfx). A real dual-NIC chipset such as the Intel 82571 would probably have worked.
-
By chance would the disabling of the on-board graphics change the behavior?
It might be easier to try a snapshot build of pfSense 2.0 BETA (go to http://snapshots.pfsense.org/ and follow appropriate links) than mess with disabling video. pfSense 2.0 uses a more up to date version of FreeBSD with updated device drivers which might recognise your onboard NIC.
The way I look at it, you have 3 devices sharing 1 IRQ off the PCIe slot (Int. gfx & 1 each for each of the realtek interfaces) - something that the platform wasn't designed to do (it was meant to only share 2 devices - 1 PCIe x1 and the Int. gfx).
I don't understand the basis for this remark. The re devices report using different IRQs (16 and 17) and then report they are using MSI (Message Signalled Interrupts) which should give them distinct interrupts.
-
I don't understand the basis for this remark. The re devices report using different IRQs (16 and 17) and then report they are using MSI (Message Signalled Interrupts) which should give them distinct interrupts.
My mistake.
I just assumed that the switched devices share the IRQ there because that is what I've encountered when using similar setups albeit with a Intel PT Dual port (with the extra PCIe lanes taped up to force x1 mode) on the 945GC chipset.