Re: kern/140742: rum(4) Two asus-WL167G adapters cannot talk to each other

Old Synopsis: assus-WL167G rum driver New Synopsis: rum(4) Two asus-WL167G adapters cannot talk to each other Responsible-Changed-From-To: freebsd-i386->freebsd-net Responsible-Changed-By: gavin Responsible-Changed-When: Sun Nov 22 12:08:40 UTC 2009 Responsible-Changed-Why: Over to maintainer(s)

Intel NIC 0x10f08086

Hi List, Hi Jack! I have an Intel NIC with the pci chip=0x10f08086 rev=0x05 as onboard Card on an "Intel DP55WB" Mainboard. According to Google it is an "82578DC". Now i wonder how to make it work. I tried to add the PCI ID to both em(4) and igb(4) but the attach failed, so it looks like some

ARP regression in releng-8

Hi all, I try to figure out something simple like the ARP retransmission timeout to populate the ipv4InterfaceRetransmitTime in the RFC4293 MIB. In line 357 of netinet/if_ether.c it says: /* * Return EWOULDBLOCK if we have tried less than arp_maxtries. It * will be m

[CFR] unified rc.firewall

Hi, The ipfw and ip6fw were unified into ipfw2, now. But, we still have rc.firewall and rc.firewall6. However, there are conflicts with each other, and it confuses the users, IMHO. So, I made a patch to unify rc.firewall and rc.firewall6, and obsolete rc.firewall6 and rc.d/ip6fw. Please review t

RE: ARP regression in releng-8

I will look into it and get back to you. -- Qing > -Original Message- > From: owner-freebsd-...@freebsd.org [mailto:owner-freebsd- > n...@freebsd.org] On Behalf Of Harti Brandt > Sent: Sunday, November 22, 2009 5:09 AM > To: freebsd-net@freebsd.org > Subject: ARP regression in releng-8 >

RE: openbgpd + 8.0

I am not sure if what you are observing is a side effect of svn-r196714. In particular, the code I added for: - Routing messages are not generated when adding and removing interface address aliases. If my memory serves me right, I put in the above patch

RE: openbgpd + 8.0

Just to be a bit more specific, in r196714 /sys/netinet/in.c: /* QL: XXX 1090* Report a blank rtentry when a route has not been 1091* installed for the given interface address. 1092*/ 1093 -- Qing > -Original Message- > From: owner-freebsd-...@freebsd.org [mailto

Re: openbgpd + 8.0

On Sun, Nov 22, 2009 at 8:44 PM, Li, Qing wrote: > Just to be a bit more specific, in r196714 /sys/netinet/in.c: [...] Just wanting to let you know the following behavior changes: 1. Some customers of mine used to run 7.x with quagga. Another app was adding static routes with a nexthop of 127.0.

Re: [CFR] unified rc.firewall

Hajimu UMEMOTO wrote: > Hi, > > The ipfw and ip6fw were unified into ipfw2, now. But, we still have > rc.firewall and rc.firewall6. However, there are conflicts with each > other, and it confuses the users, IMHO. > So, I made a patch to unify rc.firewall and rc.firewall6, and obsolete > rc.firew

Re: kern/140778: [em] randomly panic in vlan/em

Old Synopsis: randomly panic in vlan/em New Synopsis: [em] randomly panic in vlan/em Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: linimon Responsible-Changed-When: Sun Nov 22 23:18:23 UTC 2009 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.or

Re: kern/140796: [ath] [panic] privileged instruction fault

Old Synopsis: panic: privileged instruction fault (ath related) New Synopsis: [ath] [panic] privileged instruction fault Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: linimon Responsible-Changed-When: Sun Nov 22 23:31:33 UTC 2009 Responsible-Changed-Why: Over to m

bridging vs wifi, proxy arp broken on 8.0 rc? (was: Re: Bridged networking for virtualbox on -current?)

In article <4b09992f.1080...@shapeshifter.se> you write: >Doug Barton wrote: >> Fredrik Lindberg wrote: >>> Doug Barton wrote: Is bridged networking for vbox supposed to work on -current? It says on the wiki that it does, but I tried it tonight and couldn't get it to work.

Re: bridging vs wifi, proxy arp broken on 8.0 rc?

Juergen Lock wrote: > The problem with bridging and wifi is that on wifi you usually can > use only a single mac address... Ok, I'm not heartbroken if it won't work, but it would be nice if the wiki were updated so that no one else wastes time on it like I did last night. Doug -- Imp

Re: if_bridge as if_vlan parent

Tom Judge wrote: Josh Paetzel wrote: On Nov 21, 2009, at 11:39 AM, Tom Judge wrote: Hi, I was why I get the following error when trying to create a vlan on top of if_bridge: # ifconfig bridge0 create # ifconfig vlan2 vlan 2 vlandev bridge0 ifconfig: SIOCSETVLAN: Protocol not supported An

Re: kern/140036: [iwn] [lor] lock order reversal with iwn0_com_lock and iwn0 softc lock

The following reply was made to PR kern/140036; it has been noted by GNATS. From: Benjamin Kaduk To: Bernhard Schmidt Cc: bug-follo...@freebsd.org Subject: Re: kern/140036: [iwn] [lor] lock order reversal with iwn0_com_lock and iwn0 softc lock Date: Mon, 23 Nov 2009 02:25:35 -0500 (EST) On Su

Re: kern/140684: [bce] Broadcom NetXtreme II BCM5709 1000Base-T - fail after soft reboot

Old Synopsis: Broadcom NetXtreme II BCM5709 1000Base-T - fail after soft reboot New Synopsis: [bce] Broadcom NetXtreme II BCM5709 1000Base-T - fail after soft reboot Responsible-Changed-From-To: freebsd-i386->freebsd-net Responsible-Changed-By: linimon Responsible-Changed-When: Mon Nov 23 07:46:4