two problems with broadcom NICs

Hello, I've got a bunch of new Dell PowerEdge SC440 machines, but I've some problems running FreeBSD on them. OS: FreeBSD 6.2-RELEASE (but also -stable of yesterday), SMP (but tried also GENERIC monoprocessor), both i386 and amd64, always same results. Situation: Two Broadcom NICs, one on the

Re: two problems with broadcom NICs

On Fri, Mar 02, 2007 at 09:47:47AM +0100, Alessandro de Manzano wrote: Hello, What could be ? What could I try ? Ideas ? You can check if changing the interface UP flag makes in any better: ifconfig interface up -- Wojciech A. Koszek [EMAIL PROTECTED]

Re: two problems with broadcom NICs

On Fri, Mar 02, 2007 at 09:47:47AM +0100, Alessandro de Manzano wrote: The first one (bge0) is the motherboard integrated, the second one (none1) is on PCI-express ERRATA: sorry, I swapped them, bge0 is the PCI-express one, none1 is the motherboard integrated one! -- bye! Ale

Re: Thinking about IPv6 and DEPRECATED addresses

Tsuyoshi MOMOSE wrote: On 2007/02/28, at 20:33, Max Laier wrote: So, I am contemplating adding to rtsock.c the ability to send these types of events up. I am thinking on adding this there for two reasons.. a) SCTP already hooks into the routing socket to get interface changes. and b) It

New optimized soreceive_stream() for TCP sockets, proof of concept

-20070302.diff Any testing, especially on 10Gig cards, and feedback appreciated. -- Andre ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: New optimized soreceive_stream() for TCP sockets, proof of concept

Andre Oppermann writes: Instead of the unlock-lock dance soreceive_stream() pulls a properly sized (relative to the receive system call buffer space) from the socket buffer drops the lock and gives copyout as much time as it needs. In the mean time the lower half can happily add as

Unification and simplification of outbound TCP options handling

function is then used in both the syncache and the normal tcp_output path instead of their previous versions. It it alignment agnostic and can be used to write directly into mbufs with any alignment. The patch is here: http://people.freebsd.org/~andre/tcp_options-20070302.diff Any testing and reviews

Re: two problems with broadcom NICs

--On Friday, March 02, 2007 09:47:47 +0100 Alessandro de Manzano [EMAIL PROTECTED] wrote: Hello, I've got a bunch of new Dell PowerEdge SC440 machines, but I've some problems running FreeBSD on them. OS: FreeBSD 6.2-RELEASE (but also -stable of yesterday), SMP (but tried also GENERIC

Re: two problems with broadcom NICs

On Friday 02 March 2007 03:47 am, Alessandro de Manzano wrote: Hello, I've got a bunch of new Dell PowerEdge SC440 machines, but I've some problems running FreeBSD on them. OS: FreeBSD 6.2-RELEASE (but also -stable of yesterday), SMP (but tried also GENERIC monoprocessor), both i386 and

TCP source port reuse problems

Hi, After upgrading my firewall to FreeBSD 6.2-RELEASE (with IPfilter), I noticed that TCP connections between my firewall and internal hosts (all FreeBSD and mostly 6.2) were randomly dropping out. I've found a variety of anomolies in both FreeBSD and IPfilter and will post about them

[PATCH] Ethernet cleanup; 802.1p input and M_PROMISC

Hello all, I would like to announce an updated version of the 802.1p input patch, available at: http://people.freebsd.org/~bms/dump/latest-8021p.diff I have cut down the original scope of the patch. I previously ran into problems when I tried to move VLAN tag input and output processing

CARP behaviour

During testing of M_PROMISC I noticed a couple of issues with our CARP. 1. carp doesn't seem to maintain input/output statistics on its ifnet. 2. carp doesn't seem to detect that the underlying route to the subnet its address is exposed on changed to another interface. Are these conditions