CARP Failover

2011-01-28 Thread Mike Barnard
Hi, I have two firewalls, FW1 and FW2. Each server has three interfaces, bce0, bce1 and bce2 and of course the carp interfaces. FW1: bce0: 41.xxx.yyy.244/29 bce1: 172.19.254.14/30 bce2: 41.xxx.yyy.252/29 carp0: 41.202.229.243 carp1: 41.202.229.251 FW2: bce0: 41.xxx.yyy.245/29 bce1: 172.19.254.15

[ath] ath_rate_sample changes; please test

2011-01-28 Thread Adrian Chadd
Hi, I've just committed some changes to the ath_rate_sample module which teach it the bare minimum to transmit MCS frames when in 11n mode. No, this doesn't mean 11n mode is yet available or ready (there's some further work in the TX path first.) I'd appreciate some testing of this just to ensur

Re: Proposed patch for Port Randomization modifications according to RFC6056

2011-01-28 Thread Ivo Vachkov
Hello, I would like to thank for the help and for the recommendations. I attach second version of the patch, I proposed earlier, including following changes: 1) All RFC6056 algorithms are implemented. 2) Both IPv4 and IPv6 stacks are modified to use the new port randomization code. 3) There are

Re: em driver, 82574L chip, and possibly ASPM

2011-01-28 Thread Mike Tancsa
On 1/23/2011 10:21 AM, Mike Tancsa wrote: > On 1/21/2011 4:21 AM, Jan Koum wrote: > One other thing I noticed is that when the nic is in its hung state, the > WOL option is gone ? > > e.g > > em1: flags=8843 metric 0 mtu 1500 > options=19b > ether 00:15:17:ed:68:a4 > > vs > > >

Re: CARP Failover

2011-01-28 Thread David DeSimone
Mike Barnard wrote: > > FW1 is connected to SW1 and FW2 is connected to SW2. Both SW1 and SW2 > connected to the aggregating switch. > > I have configured CARP in failover mode and the interesting thing is both > firewall carp interfaces come up as master: > > FW1: > carp0: flags=49 metric 0 mtu

Re: Proposed patch for Port Randomization modifications according to RFC6056

2011-01-28 Thread Doug Barton
On 01/28/2011 06:33, Ivo Vachkov wrote: Hello, I would like to thank for the help and for the recommendations. I attach second version of the patch, I proposed earlier, including following changes: 1) All RFC6056 algorithms are implemented. 2) Both IPv4 and IPv6 stacks are modified to use the

Re: Proposed patch for Port Randomization modifications according to RFC6056

2011-01-28 Thread Ivo Vachkov
On Fri, Jan 28, 2011 at 9:00 PM, Doug Barton wrote: > On 01/28/2011 06:33, Ivo Vachkov wrote: >> >> Hello, >> >> I would like to thank for the help and for the recommendations. >> >> I attach second version of the patch, I proposed earlier, including >> following changes: >> >> 1) All RFC6056 algo

Re: kern/154169: [multicast] [ip6] Node Information Query multicast address wrong (FF02::2:x:y)

2011-01-28 Thread linimon
Old Synopsis: Node Information Query multicast address wrong (FF02::2:x:y) New Synopsis: [multicast] [ip6] Node Information Query multicast address wrong (FF02::2:x:y) Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: linimon Responsible-Changed-When: Fri Jan 28 23:58

Re: conf/154062: [vlan] [patch] change to way of auto-generatation of vlan devices based on the chosen parent device

2011-01-28 Thread linimon
Old Synopsis: [ patch ] change to way of auto-generatation of vlan devices based on the chosen parent device New Synopsis: [vlan] [patch] change to way of auto-generatation of vlan devices based on the chosen parent device Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Change

Re: Proposed patch for Port Randomization modifications according to RFC6056

2011-01-28 Thread Doug Barton
On 01/28/2011 11:57, Ivo Vachkov wrote: On Fri, Jan 28, 2011 at 9:00 PM, Doug Barton wrote: How does net.inet.ip.portrange.randomalg sound? I would also suggest that the second sysctl be named net.inet.ip.portrange.randomalg.alg5_tradeoff so that one could do 'sysctl net.inet.ip.portrange.ran