I noticed while moving my m0n0wall to a new PC today that the link0 property (for interrupt mitigation) was not loaded on my WAN interface. All of my NIC's are Intel e100's, using the fxp driver.
I have tried with both 1.3b5 and 1.21 (my old and new machines) and they both exhibit the same problem. The machines are both up and running right now, these are completely different sets of hardware.
I tried manually setting the link0 attribute using ifconfig fxp1 link0 and it turned on as expected.
$ dmesg
Copyright (c) 1992-2007 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 6.2-RELEASE-p8 #0: Fri Nov 23 16:06:22 CET 2007
root@mb62.neon1.net:/usr/src/sys/i386/compile/M0N0WALL_GENERIC
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: Intel Celeron (1002.28-MHz 686-class CPU)
Origin = "GenuineIntel" Id = 0x68a Stepping = 10
Features=0x383f9ff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE>
real memory = 201261056 (191 MB)
avail memory = 170668032 (162 MB)
wlan: mac acl policy registered
kbd1 at kbdmux0
ath_hal: 0.9.17.2 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413)
acpi0: <GBT AWRDACPI> on motherboard
acpi0: Power Button (fixed)
cpu0: <ACPI CPU> on acpi0
acpi_button0: <Power Button> on acpi0
pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff,0x4000-0x4041,0x5000-0x500f on acpi0
pci0: <ACPI PCI bus> on pcib0
pcib1: <PCI-PCI bridge> at device 1.0 on pci0
pci1: <PCI bus> on pcib1
pci1: <display, VGA> at device 0.0 (no driver attached)
isab0: <PCI-ISA bridge> at device 7.0 on pci0
isa0: <ISA bus> on isab0
atapci0: <Intel PIIX4 UDMA33 controller> port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xf000-0xf00f at device 7.1 on pci0
ata0: <ATA channel 0> on atapci0
ata1: <ATA channel 1> on atapci0
uhci0: <Intel 82371AB/EB (PIIX4) USB controller> port 0xe000-0xe01f irq 10 at device 7.2 on pci0
uhci0: [GIANT-LOCKED]
usb0: <Intel 82371AB/EB (PIIX4) USB controller> on uhci0
usb0: USB revision 1.0
uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
pci0: <bridge> at device 7.3 (no driver attached)
fxp0: <Intel 82558 Pro/100 Ethernet> port 0xe400-0xe41f mem 0xe4200000-0xe4200fff,0xe4100000-0xe41fffff irq 11 at device 8.0 on pci0
miibus0: <MII bus> on fxp0
inphy0: <i82555 10/100 media interface> on miibus0
inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
fxp0: Ethernet address: 00:90:27:13:73:46
fxp1: <Intel 82559 Pro/100 Ethernet> port 0xe800-0xe83f mem 0xe4201000-0xe4201fff,0xe4000000-0xe40fffff irq 12 at device 9.0 on pci0
miibus1: <MII bus> on fxp1
inphy1: <i82555 10/100 media interface> on miibus1
inphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
fxp1: Ethernet address: 00:d0:b7:18:fc:ef
acpi_tz0: <Thermal Zone> on acpi0
fdc0: <floppy drive controller> port 0x3f2-0x3f5,0x3f7 irq 6 drq 2 on acpi0
fdc0: [FAST]
fd0: <1440-KB 3.5" drive> on fdc0 drive 0
sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0
sio0: type 16550A
sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0
sio1: type 16550A
atkbdc0: <Keyboard controller (i8042)> port 0x60,0x64 irq 1 on acpi0
atkbd0: <AT Keyboard> irq 1 on atkbdc0
kbd0 at atkbd0
atkbd0: [GIANT-LOCKED]
pmtimer0 on isa0
orm0: <ISA Option ROMs> at iomem 0xc0000-0xc7fff,0xc8000-0xc9fff on isa0
vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
sc0: <System console> at flags 0x100 on isa0
sc0: VGA <16 virtual consoles, flags=0x300>
Timecounter "TSC" frequency 1002275789 Hz quality 800
Timecounters tick every 1.000 msec
Fast IPsec: Initialized Security Association Processing.
IP Filter: v4.1.23 initialized. Default = block all, Logging = enabled
md0: Preloaded image </mfsroot> 14680064 bytes at 0xc0a15e74
ad0: 6149MB <QUANTUM FIREBALL CR6.4A A5U.1200> at ata0-master PIO4
acd0: CDROM <ASUS CD-S400/A/V2.3S> at ata1-master PIO4
Trying to mount root from ufs:/dev/md0
fxp0: Microcode loaded, int_delay: 1000 usec bundle_max: 0
Now, ifconfig -a: (yes, fxp1 AKA 192.168.1.191 is my WAN. I'm testing within my existing LAN)
So, it looks like there is a bug somewhere. I don't think this is the desired behavior, because it seems like a good thing to lessen the interrupt load, especially on a potentially hostile network.
Thanks for m0n0wall. It's a truly wonderful product. I love it
m0n0wall Forum > m0n0wall Support (English) > Bug Reports > Resolved
Topic: LINK0 not set on fxp WAN interface