Re: kern/138694: [bge] FreeBSD 6.3 release does not recognize Broadcom BCM5709C card on IBM X3550 M2

Synopsis: [bge] FreeBSD 6.3 release does not recognize Broadcom BCM5709C card on IBM X3550 M2 Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: linimon Responsible-Changed-When: Sat Sep 12 03:45:23 UTC 2009 Responsible-Changed-Why: Over to maintainer(s). http://www.

Re: kern/138691: [netinet] [patch] Multicast: Keep membership and filters in sync

Old Synopsis: Multicast: Keep membership and filters in sync New Synopsis: [netinet] [patch] Multicast: Keep membership and filters in sync Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: linimon Responsible-Changed-When: Sat Sep 12 03:39:08 UTC 2009 Responsible-Chan

Re: kern/137164: [netinet] [patch] assert panic imo_match_source()

Old Synopsis: [socket] [panic] assert panic imo_match_source() New Synopsis: [netinet] [patch] assert panic imo_match_source() Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: linimon Responsible-Changed-When: Sat Sep 12 03:38:26 UTC 2009 Responsible-Changed-Why: A p

Re: kern/138690: [netinet] [patch] multicast: uninited memory used in filter at IP_DROP_MEMBERSHIP + IP_ADD_MEMBERSHIP

Old Synopsis: Multicast: uninited memory used in filter at IP_DROP_MEMBERSHIP + IP_ADD_MEMBERSHIP New Synopsis: [netinet] [patch] multicast: uninited memory used in filter at IP_DROP_MEMBERSHIP + IP_ADD_MEMBERSHIP Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: lin

Re: kern/138689: [netinet] patch] Multicast: IP_DROP_MEMBERSHIP should return EADDRNOTAVAIL for invalid address

Old Synopsis: [patch] Multicast: IP_DROP_MEMBERSHIP should return EADDRNOTAVAIL for invalid address New Synopsis: [netinet] patch] Multicast: IP_DROP_MEMBERSHIP should return EADDRNOTAVAIL for invalid address Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: linimon

Re: kern/138739: [wpi] wpi(4) does not work very well under 8.0-BETA4

Old Synopsis: wpi(4) does not work very well under 8.0-BETA4 New Synopsis: [wpi] wpi(4) does not work very well under 8.0-BETA4 Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: linimon Responsible-Changed-When: Sat Sep 12 00:53:04 UTC 2009 Responsible-Changed-Why: Ov

Re: New tcpdump in 8.x

On Sat, Sep 12, 2009 at 12:12:05AM +0200, sth...@nethelp.no wrote: > > Who has used tcpdump on FreeBSD 8.x and likes it? Is it just me or is > > it now far harder to investigate network problems using it? > > > > Prior to 8.x, the default output includes SEQ number ranges for any > > TCP packets

Re: New tcpdump in 8.x

> Who has used tcpdump on FreeBSD 8.x and likes it? Is it just me or is > it now far harder to investigate network problems using it? > > Prior to 8.x, the default output includes SEQ number ranges for any > TCP packets with data, so a 'tcpdump -n' looks like the following and > it's immediately

New tcpdump in 8.x

[Please excuse long lines] Who has used tcpdump on FreeBSD 8.x and likes it? Is it just me or is it now far harder to investigate network problems using it? Prior to 8.x, the default output includes SEQ number ranges for any TCP packets with data, so a 'tcpdump -n' looks like the following and i

Re: em driver input errors

Glad to hear this. Jack On Fri, Sep 11, 2009 at 4:46 AM, Mike Tancsa wrote: > At 11:28 AM 9/9/2009, Mike Tancsa wrote: > >> At 11:17 AM 9/9/2009, Mike Tancsa wrote: >> >>> The board is an intel >>> >>> http://www.intel.com/support/motherboards/server/s3000ah/ >>> >>> Not sure if its wired as P

Re: FIB for RELENG_6?

Naoki Hamada wrote: Hello, guys! Is there a patch set of FIB for RELENG_6 (now 6.4-STABLE)? If there is any, I want apply it to my multi-homed server in preparation for a forthcoming IP address transition process and mitigate its complication. I tried a FIB enabled 7.2 machine with recent change

FIB for RELENG_6?

Hello, guys! Is there a patch set of FIB for RELENG_6 (now 6.4-STABLE)? If there is any, I want apply it to my multi-homed server in preparation for a forthcoming IP address transition process and mitigate its complication. I tried a FIB enabled 7.2 machine with recent changes and found it perfect

Re: em driver input errors

At 11:28 AM 9/9/2009, Mike Tancsa wrote: At 11:17 AM 9/9/2009, Mike Tancsa wrote: The board is an intel http://www.intel.com/support/motherboards/server/s3000ah/ Not sure if its wired as PCI-X or just a 32bit bus. I am just popping in an em pcie nic to see if that makes a difference. I hav

Re: amd64/138688: [rum] possibly broken on 8 Beta 4 amd64: able to wpa authenticate + obtain dhclient address, no communication though.

Old Synopsis: rum possibly broken on 8 Beta 4 amd64: Linksys WUSB54GC v1 device appears as rum, clonable to wlan0, able to wpa authenticate + obtain dhclient address, no communication though. New Synopsis: [rum] possibly broken on 8 Beta 4 amd64: able to wpa authenticate + obtain dhclient addres