Ben Greear wrote:
Patrick McHardy wrote:
That comes from iproute itself, but the missing LOWER-UP flag
indicates it and that should be enough for bridging and bonding.
I'm unsure about this though since its still a big difference in
userspace visible behaviour, people might just as well manuall
Patrick McHardy wrote:
Ben Greear wrote:
Patrick McHardy wrote:
Stephen Hemminger wrote:
But then if you are doing bonding or bridging of vlan's and you
bring down the root network device, the upper layer is not
notified (for failover).
operstate should be enough for this I guess. Ben,
Ben Greear wrote:
Patrick McHardy wrote:
Stephen Hemminger wrote:
But then if you are doing bonding or bridging of vlan's and you
bring down the root network device, the upper layer is not
notified (for failover).
operstate should be enough for this I guess. Ben, what does iproute show
Patrick McHardy wrote:
Stephen Hemminger wrote:
On Wed, 21 Nov 2007 11:51:43 -0800
Ben Greear <[EMAIL PROTECTED]> wrote:
For consideration, this patch seems to work for me. I'm not sure
why we ever listed to these events. I've only tested on a NIC that
doesn't support hw-accel at the momen
Stephen Hemminger wrote:
On Wed, 21 Nov 2007 11:51:43 -0800
Ben Greear <[EMAIL PROTECTED]> wrote:
For consideration, this patch seems to work for me. I'm not sure
why we ever listed to these events. I've only tested on a NIC that
doesn't support hw-accel at the moment..will test with e1000
On Wed, 21 Nov 2007 11:51:43 -0800
Ben Greear <[EMAIL PROTECTED]> wrote:
> For consideration, this patch seems to work for me. I'm not sure
> why we ever listed to these events. I've only tested on a NIC that
> doesn't support hw-accel at the moment..will test with e1000 later.
>
> Thanks,
> Be
For consideration, this patch seems to work for me. I'm not sure
why we ever listed to these events. I've only tested on a NIC that
doesn't support hw-accel at the moment..will test with e1000 later.
Thanks,
Ben
--
Ben Greear <[EMAIL PROTECTED]>
Candela Technologies Inc http://www.candelatech
Hello!
Found something strange today.
Suppose I have eth2 with VLAN 2 (eth2.2) associated with it. I
add a routing table that is associated with eth2.2 (table 76 in my case).
Now, I run:
ifconfig eth2 down
ifconfig eth2 up
All of the routes in routing table 76 are now gone! I can
understand
