Re: rtadvd and carp
On 1 March 2011 02:28, User Red35 wrote: > > I am getting started with IPv6 and I am trying to get rtadvd working on > the carp interface but it is not working so far. > > > ### I have carp failover between two firewalls. The default gateway for > ### hosts internal to the firewall is 172.31.98.103 for IPv4 > ### and 2001:470:dead:98::103 for IPv6 > > # ifconfig carp1 > carp1: flags=49 metric 0 mtu 1500 > inet 172.31.98.103 netmask 0x > inet6 2001:470:dead:98::103 prefixlen 64 > nd6 options=3 > carp: MASTER vhid 1 advbase 1 advskew 60 > # > > > ### rtadvd does not work since carp1 does not have a link local address > > > # rtadvd -f -D carp1 > rtadvd[13262]: link-layer address option has null length on > carp1. Treat as not included. > rtadvd[13262]: RA timer on carp1 is set to 16:0 > rtadvd[13262]: IPV6_JOIN_GROUP(link) on carp1: Can't assign > requested address > # > > > ### Per RFC 4861 Router advertisements are supposed to use > ### link-local addresses... carp does not have one. > > > ### > ### http://tools.ietf.org/html/rfc4861#page-39 > ### > > Section 6.1.2 > > IP Source Address is a link-local address. Routers must use > their link-local address as the source for Router Advertisement > and Redirect messages so that hosts can uniquely identify > routers. > > ### > > > Is it possible to manually add the link-local address to a carp interface > via ifconfig (or other utility)? > > I assume given the carp MAC 00:00:5e:00:01:01 the link-local address would > look like this? > > fe80::200:5eff:fe00:101 > > Has anyone got anything similar working? > I'm afraid you need to specify carpdev for the carp interface to manage this work. As far as I know, FreeBSD doesn't support carpdev (yet). -- wbr, pluknet ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: FreeBSD TDMA kernel PANIC
On Tuesday, March 01, 2011 03:49:41 Kyungsoo Lee wrote: > Hi, > > whenever I try to set my mini PCI-e card (Anatel AR5BXB6) as Master > (tdmaslot 0), kernel shows PANIC msg like the below. > It's OK when I set the card as not Master like tdmalsot 1,2, and more. What > is the problem? And how can I fix it? > > Interestingly, the kernel PANIC occurs when I use this card with IBM T60. > When I use this card with IBM T61, there is no PANIC message like the below. > Instead, kernel shows never ending "Ath0: Stuck beacon; bmiss..." messages. > > How can I solve the problem? I searched but it is hard to find the answer > for my cases. The panic doesn't seem to be related to ath(4) or do you see ath or wlan in the backtrace? Adrian fixed a few issues regarding stuck beacons in head, you might wanna try this. Also, your last post said you configured the device with % ifconfig wlan0 create wlandev ath0 wlanmode tdma tdmaslot 0 up This is either not the whole truth or you should definitely set a SSID as otherwise no network will be opened. -- Bernhard ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Interface descriptions via pcap broken
I installed wireshark on my 9-CURRENT machine yesterday and found that the interface description fields are all set to 0xa5. From reading the code it looks like the data is being fetched via pcap. Device: usbus1 Description: \xa5\xa5\xa5\xa5\xa5\xa5\xa5\xa5\xa5\xa5\xa5\xa5\xa5\xa5 \xa5\xa5\xa5\xa5\xa5\xa5\xa5\xa5\xa5\xa5\xa5\xa5\xa5\xa5\xa5\xa5\xa5\xa5 \xa5\xa5\xa5\xa5\xa5\xa5\xa5\xa5\xa5\xa5\xa5\xa5\xa5\xa5\xa5\xa5\xa5\xa5 \xa5\xa5\xa5\xa5\xa5\xa5\xa5\xa5\xa5\xa5\xa5\xa5\xa5\xa5 IP: unknown Has a recent change broken this? -- Bruce Cran ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
FreeBSD TDMA kernel PANIC
Hi, whenever I try to set my mini PCI-e card (Anatel AR5BXB6) as Master (tdmaslot 0), kernel shows PANIC msg like the below. It's OK when I set the card as not Master like tdmalsot 1,2, and more. What is the problem? And how can I fix it? Interestingly, the kernel PANIC occurs when I use this card with IBM T60. When I use this card with IBM T61, there is no PANIC message like the below. Instead, kernel shows never ending "Ath0: Stuck beacon; bmiss..." messages. How can I solve the problem? I searched but it is hard to find the answer for my cases. Thank you and I expect wise solutions. K. dumped core - see /var/crash/vmcore.0 Sat Feb 26 21:08:44 UTC 2011 FreeBSD 8.2-RELEASE FreeBSD 8.2-RELEASE #0: Fri Feb 25 23:41:00 UTC 2011 root@:/usr/obj/usr/src/sys/MYKERNEL i386 panic: non-maskable interrupt trap GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-marcel-freebsd"... Unread portion of the kernel message buffer: <<2>N2MI> INSAM I ISA a0a, 0E,I SEAI SA ff f<2> RApafri t<2 >R<2>Ay Me rpraorri,t yl iekrerloyr ,h alridkwealrye hfaaridlwuarree. failure. Fatal trap 19: non-maskable interrupt trap while in kernel mode Fatal trap 19: non-maskable interrupt trap while in kernel mode cpuid = 1; cpuid = 0; apic id = 01apic id = 00 instruction pointer = 0x20:0xc0bd00b5 instruction pointer = 0x20:0xc0bd00b5 stack pointer= 0x28:0xc2fc1c58 stack pointer= 0x28:0xc2fc4c58 frame pointer= 0x28:0xc2fc1c58 frame pointer= 0x28:0xc2fc4c58 code segment = base 0x0, limit 0xf, type 0x1b code segment = base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 = DPL 0, pres 1, def32 1, gran 1 processor eflags = processor eflags = interrupt enabled, interrupt enabled, IOPL = 0IOPL = 0 current process = current process = 11 (idle: cpu1)11 (idle: cpu0) trap number = 19 trap number = 19 panic: non-maskable interrupt trap cpuid = 1 KDB: stack backtrace: #0 0xc08e1ab7 at kdb_backtrace+0x47 #1 0xc08b2b77 at panic+0x117 #2 0xc0beea83 at trap_fatal+0x323 #3 0xc0bef432 at trap+0x652 #4 0xc0bd5dfc at calltrap+0x6 #5 0xc04e5cc9 at acpi_cpu_idle+0xe9 #6 0xc0bdfb2b at cpu_idle_acpi+0x1b #7 0xc0be136b at cpu_idle+0x1b #8 0xc08d48f1 at sched_idletd+0x231 #9 0xc0887b01 at fork_exit+0x91 #10 0xc0bd5e74 at fork_trampoline+0x8 Uptime: 9m37s Physical memory: 490 MB Dumping 45 MB: 30 14 #0 doadump () at pcpu.h:231 231 pcpu.h: No such file or directory. in pcpu.h (kgdb) #0 doadump () at pcpu.h:231 #1 0xc08b2913 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:419 #2 0xc08b2bb0 in panic (fmt=Variable "fmt" is not available. ) at /usr/src/sys/kern/kern_shutdown.c:592 #3 0xc0beea83 in trap_fatal (frame=0xc2fc1c18, eva=0) at /usr/src/sys/i386/i386/trap.c:946 #4 0xc0bef432 in trap (frame=0xc2fc1c18) at /usr/src/sys/i386/i386/trap.c:731 #5 0xc0bd5dfc in calltrap () at /usr/src/sys/i386/i386/exception.s:166 #6 0xc0bd00b5 in acpi_cpu_c1 () at /usr/src/sys/i386/acpica/acpi_machdep.c:556 #7 0xc04e5cc9 in acpi_cpu_idle () at /usr/src/sys/dev/acpica/acpi_cpu.c:930 #8 0xc0bdfb2b in cpu_idle_acpi (busy=1) at /usr/src/sys/i386/i386/machdep.c:1224 #9 0xc0be136b in cpu_idle (busy=1) at /usr/src/sys/i386/i386/machdep.c:1314 #10 0xc08d48f1 in sched_idletd (dummy=0x0) at /usr/src/sys/kern/sched_ule.c:2555 #11 0xc0887b01 in fork_exit (callout=0xc08d46c0 , arg=0x0, frame=0xc2fc1d28) at /usr/src/sys/kern/kern_fork.c:845 #12 0xc0bd5e74 in fork_trampoline () at /usr/src/sys/i386/i386/exception.s:273 (kgdb) ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
rtadvd and carp
I am getting started with IPv6 and I am trying to get rtadvd working on the carp interface but it is not working so far. ### I have carp failover between two firewalls. The default gateway for ###hosts internal to the firewall is 172.31.98.103 for IPv4 ###and 2001:470:dead:98::103 for IPv6 # ifconfig carp1 carp1: flags=49 metric 0 mtu 1500 inet 172.31.98.103 netmask 0x inet6 2001:470:dead:98::103 prefixlen 64 nd6 options=3 carp: MASTER vhid 1 advbase 1 advskew 60 # ### rtadvd does not work since carp1 does not have a link local address # rtadvd -f -D carp1 rtadvd[13262]: link-layer address option has null length on carp1. Treat as not included. rtadvd[13262]: RA timer on carp1 is set to 16:0 rtadvd[13262]: IPV6_JOIN_GROUP(link) on carp1: Can't assign requested address # ### Per RFC 4861 Router advertisements are supposed to use ### link-local addresses... carp does not have one. ### ### http://tools.ietf.org/html/rfc4861#page-39 ### Section 6.1.2 IP Source Address is a link-local address. Routers must use their link-local address as the source for Router Advertisement and Redirect messages so that hosts can uniquely identify routers. ### Is it possible to manually add the link-local address to a carp interface via ifconfig (or other utility)? I assume given the carp MAC 00:00:5e:00:01:01 the link-local address would look like this? fe80::200:5eff:fe00:101 Has anyone got anything similar working? Thanks, Geoffrey ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
any is vfs.nfsrv.nfs_privport=0 by default
vfs.nfsrv.nfs_privport controls wither or not NFS enforces the traditional RPC semantics that require that requests come from "privileged" ports. By default this check is disabled. Hardening guides typically suggest this be enabled, usually via the rc.conf knob nfs_reserved_port_only=YES. I'm trying to find a good reason why the default is the way it is. Digging around in the source tree it appears that the rc.conf setting has been that way since either /etc/rc.conf or /etc/defaults/rc.conf has been in the tree. I do not consider the fact that the security provided is weak at best to be a good reason to disable it. I suspect support for PC-NFS or something like that may be the reason, but if that's the case it really doesn't make any sense. -- Brooks pgpiiC2vOSyrJ.pgp Description: PGP signature
Re: seeking recommendation: 1000Base-SX PCI NIC for FreeBSD 8
Jay Borkenhagen writes: > Hi, > > After having been disappointed by one vendor *, I am returning to this > list to seek recommendations for 1000Base-SX PCI NICs. I am looking > to run them on FreeBSD 8 and beyond, and I need support for MTU > 1500 > bytes (initially around 4470, but possibly closer to 9k later). > > On http://www.freebsd.org/releases/8.1R/hardware.html#ETHERNET I found > mention of several "SX" cards, but I have first-hand experience with > none of them. If anyone here can confirm jumbo support and current > retail availability of any such cards, I would be very appreciative. > Hi, My posting of 16-Feb elicited one private response from John-Mark Gurney (thanks!) suggesting an external media converter with a 1000Base-TX NIC. While that is a possibility, I would prefer to avoid having to purchase, test, spare, rackmount, etc. Does anyone out there have experience with any of the following SX NICs & FreeBSD? (list from http://www.freebsd.org/releases/8.1R/hardware.html#ETHERNET: + Broadcom NetXtreme II BCM5706 1000Base-SX + Broadcom NetXtreme II BCM5708 1000Base-SX + Broadcom NetXtreme II BCM5709 1000Base-SX + 3Com 3c996-SX + SysKonnect SK-9D41 (1000baseSX) + SMC TigerCard 1000 (SMC9462SX) + D-Link DGE-500SX + D-Link 550SX + D-Link 560SX + Marvell Yukon 88E8021 SX/LX + Marvell Yukon 88E8022 SX/LX + Marvell Yukon 88E8061 SX/LX + Marvell Yukon 88E8062 SX/LX + SysKonnect SK-9Sxx + SK-9843 SK-NET GE-SX + 3Com 3c985-SX + 3Com 3c985B-SX + Alteon AceNIC V + Digital EtherWORKS 1000SX + Netgear GA620 Thanks. Jay B. ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: ipfw nat and dual-homed box
On 2/28/11 8:53 AM, Eugene Grosbein wrote: On 28.02.2011 22:44, Julian Elischer wrote: On 2/27/11 3:29 AM, Eugene Grosbein wrote: On 27.02.2011 17:08, Eugene Grosbein wrote: [skip] For performance reasons, I need to create similar setup using in-kernel "ipfw nat" what does not have such "multiple instances" feature but has its own "keep-state" mechanics: To correct myself: of course, ipfw nat has multiple instances... It does not offer something like natd's "globalport" feature to check all NAT instances for entry before creation of new one. nat config if $if0 unreg_only nat config if $if1 unreg_only nat 123 ip from any to any via $if0 keep-state # For incoming packets create dynamic rule. nat 124 ip from any to any via $if1 keep-state # For outgoing packet use corresponding NAT instance. fwd $if0_gate ip from $if0_ip to any out xmit $if1 # Force packet go out right interface. fwd $if1_gate ip from $if1_ip to any out xmit $if0 This works just fine if we do not try to use ipfw nat's port forwarding. Here it breaks because "keep-state" creates dynamic rule for incoming connections before translation's done, so it records external IP of the box as destination IP. Hence, replies will be translated using wrong NAT instance when routing table chooses wrong outgoing interface - replies won't match ipfw's dynamic rules. I think this is a bug in 8.2-STABLE. Am I right? Or, perhaps, there is another way to setup ipfw nat for dual-homed LAN? Eventually one answer (which you may or may not like) is to run your NAT daemons in separate VIMAGE jails so that there are effectively separate machines on each outgoing interface. eac can have its own firewalls etc then. Unfortunately I can't tell you if the ipfw NAT will work in this set up as I have not tested it. As I've already noted, the task can be solved without separate VIMAGE using just one running natd. And I've presented working natd config for that. I want to run ipfw nat for better performance. Note again, the task is to NOT separate NAT instances but to the contrary, I need to use BOTH translation tables combined for outgoing packets. And I've presented configuration using ipfw nat that's supposed to work too, but there I've found misfeature or a bug I want to discuss :-) Eugene Grosbein not totally relevant, but for readability and clarity as to what is actually happening, split your various flows into different sets of firewall rules using skipto rules. it makes my head hurt to have to read rules where you have to watch for packets going in opposite directions through the same rules. using ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: ipfw nat and dual-homed box
On 28.02.2011 22:44, Julian Elischer wrote: > On 2/27/11 3:29 AM, Eugene Grosbein wrote: >> On 27.02.2011 17:08, Eugene Grosbein wrote: >> >> [skip] >> >>> For performance reasons, I need to create similar setup using in-kernel >>> "ipfw nat" >>> what does not have such "multiple instances" feature but has its own >>> "keep-state" mechanics: >> To correct myself: of course, ipfw nat has multiple instances... It does not >> offer >> something like natd's "globalport" feature to check all NAT instances for >> entry >> before creation of new one. >> >>> nat config if $if0 unreg_only >>> nat config if $if1 unreg_only >>> nat 123 ip from any to any via $if0 keep-state # For incoming packets >>> create dynamic rule. >>> nat 124 ip from any to any via $if1 keep-state # For outgoing packet use >>> corresponding NAT instance. >>> fwd $if0_gate ip from $if0_ip to any out xmit $if1 # Force packet go out >>> right interface. >>> fwd $if1_gate ip from $if1_ip to any out xmit $if0 >>> >>> This works just fine if we do not try to use ipfw nat's port forwarding. >>> Here it breaks because "keep-state" creates dynamic rule for incoming >>> connections >>> before translation's done, so it records external IP of the box as >>> destination IP. >>> Hence, replies will be translated using wrong NAT instance when routing >>> table >>> chooses wrong outgoing interface - replies won't match ipfw's dynamic rules. >>> >>> I think this is a bug in 8.2-STABLE. Am I right? >>> Or, perhaps, there is another way to setup ipfw nat for dual-homed LAN? > Eventually > one answer (which you may or may not like) is to run your NAT daemons in > separate VIMAGE jails so that there are effectively separate machines > on each > outgoing interface. eac can have its own firewalls etc then. > Unfortunately I can't tell you if the ipfw NAT will work in this set up > as I have not tested it. As I've already noted, the task can be solved without separate VIMAGE using just one running natd. And I've presented working natd config for that. I want to run ipfw nat for better performance. Note again, the task is to NOT separate NAT instances but to the contrary, I need to use BOTH translation tables combined for outgoing packets. And I've presented configuration using ipfw nat that's supposed to work too, but there I've found misfeature or a bug I want to discuss :-) Eugene Grosbein ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: ipfw nat and dual-homed box
On 2/27/11 3:29 AM, Eugene Grosbein wrote: On 27.02.2011 17:08, Eugene Grosbein wrote: [skip] For performance reasons, I need to create similar setup using in-kernel "ipfw nat" what does not have such "multiple instances" feature but has its own "keep-state" mechanics: To correct myself: of course, ipfw nat has multiple instances... It does not offer something like natd's "globalport" feature to check all NAT instances for entry before creation of new one. nat config if $if0 unreg_only nat config if $if1 unreg_only nat 123 ip from any to any via $if0 keep-state # For incoming packets create dynamic rule. nat 124 ip from any to any via $if1 keep-state # For outgoing packet use corresponding NAT instance. fwd $if0_gate ip from $if0_ip to any out xmit $if1 # Force packet go out right interface. fwd $if1_gate ip from $if1_ip to any out xmit $if0 This works just fine if we do not try to use ipfw nat's port forwarding. Here it breaks because "keep-state" creates dynamic rule for incoming connections before translation's done, so it records external IP of the box as destination IP. Hence, replies will be translated using wrong NAT instance when routing table chooses wrong outgoing interface - replies won't match ipfw's dynamic rules. I think this is a bug in 8.2-STABLE. Am I right? Or, perhaps, there is another way to setup ipfw nat for dual-homed LAN? Eventually one answer (which you may or may not like) is to run your NAT daemons in separate VIMAGE jails so that there are effectively separate machines on each outgoing interface. eac can have its own firewalls etc then. Unfortunately I can't tell you if the ipfw NAT will work in this set up as I have not tested it. ++ || +--+ | | | | | | ++ | ISP1--| | | n | | |ng0--| g | | | | | - | | +--+ | b | | +--+ | r |--ng2+---inside interface. | | | i | | |ng1--| d | | ISP2--| | | g | | | | || | | | +| | +--+ | || ++ ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org" ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Current problem reports assigned to freebsd-net@FreeBSD.org
Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description o kern/155030 net[igb] igb(4) DEVICE_POLLING does not work with carp(4) o kern/155010 net[msk] ntfs-3g via iscsi using msk driver cause kernel o kern/155004 net[bce] [panic] kernel panic in bce0 driver o kern/154943 net[gif] ifconfig gifX create on existing gifX clears IP s kern/154851 net[request]: Port brcm80211 driver from Linux to FreeBSD o kern/154850 net[netgraph] [patch] ng_ether fails to name nodes when t o kern/154831 net[arp] [patch] arp sysctl setting log_arp_permanent_mod o kern/154679 net[em] Fatal trap 12: "em1 taskq" only at startup (8.1-R o kern/154676 net[netgraph] [panic] HEAD, 8.1-RELEASE panic after some o kern/154600 net[tcp] [panic] Random kernel panics on tcp_output o kern/154567 net[ath] ath(4) lot of bad series(0) o kern/154557 net[tcp] Freeze tcp-session of the clients, if in the gat o kern/154443 net[if_bridge] Kernel module bridgestp.ko missing after u o kern/154286 net[netgraph] [panic] 8.2-PRERELEASE panic in netgraph o kern/154284 net[ath] Modern ath wifi cards (such as AR9285) have miss o kern/154255 net[nfs] NFS not responding o kern/154214 net[stf] [panic] Panic when creating stf interface o kern/154185 netrace condition in mb_dupcl o kern/154169 net[multicast] [ip6] Node Information Query multicast add o kern/154134 net[ip6] stuck kernel state in LISTEN on ipv6 daemon whic o kern/154091 net[netgraph] [panic] netgraph, unaligned mbuf? o conf/154062 net[vlan] [patch] change to way of auto-generatation of v o kern/154006 net[tcp] [patch] tcp "window probe" bug on 64bit o kern/153938 net[run] [panic] [patch] Workaround for use-after-free pa o kern/153937 net[ral] ralink panics the system (amd64 freeBSDD 8.X) wh o kern/153936 net[ixgbe] [patch] MPRC workaround incorrectly applied to o kern/153816 net[ixgbe] ixgbe doesn't work properly with the Intel 10g o kern/153772 net[ixgbe] [patch] sysctls reference wrong XON/XOFF varia o kern/153671 net[em] [panic] 8.2-PRERELEASE repeatable kernel in if_em o kern/153497 net[netgraph] netgraph panic due to race conditions o kern/153454 net[patch] [wlan] [urtw] Support ad-hoc and hostap modes o kern/153308 net[em] em interface use 100% cpu o kern/153255 net[panic] 8.2-PRERELEASE repeatable kernel panic under h o kern/153244 net[em] em(4) fails to send UDP to port 0x o kern/152893 net[netgraph] [panic] 8.2-PRERELEASE panic in netgraph o kern/152853 net[em] tftpd (and likely other udp traffic) fails over e o kern/152828 net[em] poor performance on 8.1, 8.2-PRE o kern/152569 net[net]: Multiple ppp connections and routing table prob o kern/152360 net[dummynet] [panic] Crash related to dummynet. o kern/152235 net[arp] Permanent local ARP entries are not properly upd o kern/152141 net[vlan] [patch] encapsulate vlan in ng_ether before out o kern/151690 net[ep] network connectivity won't work until dhclient is o kern/151681 net[nfs] NFS mount via IPv6 leads to hang on client with o kern/151593 net[igb] [panic] Kernel panic when bringing up igb networ o kern/150920 net[ixgbe][igb] Panic when packets are dropped with heade o bin/150642 netnetstat(1) doesn't print anything for SCTP sockets o kern/150557 net[igb] igb0: Watchdog timeout -- resetting o kern/150251 net[patch] [ixgbe] Late cable insertion broken o kern/150249 net[ixgbe] Media type detection broken o bin/150224 netppp(8) does not reassign static IP after kill -KILL co f kern/149969 net[wlan] [ral] ralink rt2661 fails to maintain connectio o kern/149937 net[ipfilter] [patch] kernel panic in ipfilter IP fragmen o kern/149786 net[bwn] bwn on Dell Inspiron 1150: connections stall o kern/149643 net[rum] device not sending proper beacon frames in ap mo o kern/149609 net[panic] reboot after adding second default route o kern/149539 net[ath] atheros ar9287 is not supported by ath_hal o kern/149516 net[ath] ath(4) hostap with fake MAC/BSSID results in sta o kern/149373 net[realtek/atheros]: None of my network card working o kern/149307 net[ath] Doesn't work Atheros 9285 o kern/149306 net[alc] Doesn't work Atheros AR8131 PCIe Gigabit Etherne o kern/149117 net
