similar to: [Bridge] max number of enslaved devices

Hi there, I have a question with regards to cascading multiple HTB qdiscs. Assume that I want to build the following hierarchy: (qdisc htb 1:0) -> (class htb 1:1) -> (qdisc htb 2:0) -> (class htb 2:1) -> (class htb 2:2) I want to attache aggregate u32 filters at 1:0 for supernets, then at 2:0 (and 3:0, 4:0, etc), I attach the more specific u32 filters for say HTTP and

I have a bridge br0, it enslaves two NICs: eth0 and eth1. By using "cat /proc/net/dev ", i can see the Rx/Tx packets and bytes through each interface. just like this: [* time tick 1 *] Inter-| Receive | Transmit face |bytes packets errs drop fifo frame compressed multicast|bytes packets errs drop fifo colls carrier compressed

I can think of several potential differences. ?You may miss any bridge specific traffic (STP, LLDP) using the interfaces generated by the bridge itself. If you have vlan tagged sub interfaces you might also miss that traffic if you were snooping a particular interface. Obviously you will miss any on-wire broadcast traffic specific to the layer1 connection a particular interface was connected to

Hi all Assume that you have a linux bridge with two interfaces eth0 and eth1 enslaved to this bridge What is the difference between sniffing the bridge and sniffing its interfaces? tcpdump -i br0 vs tcpdump -i eth0 Thanks MiniME -------------- next part -------------- An HTML attachment was scrubbed... URL:

On Fri, 16 Feb 2018 10:11:21 -0800, Sridhar Samudrala wrote: > This patch enables virtio_net to switch over to a VF datapath when a VF > netdev is present with the same MAC address. It allows live migration > of a VM with a direct attached VF without the need to setup a bond/team > between a VF and virtio net device in the guest. > > The hypervisor needs to enable only one

On Wed, Apr 03, 2019 at 12:52:47AM -0400, Si-Wei Liu wrote: > When a netdev appears through hot plug then gets enslaved by a failover > master that is already up and running, the slave will be opened > right away after getting enslaved. Today there's a race that userspace > (udev) may fail to rename the slave if the kernel (net_failover) > opens the slave earlier than when the

On Wed, Apr 03, 2019 at 12:52:47AM -0400, Si-Wei Liu wrote: > When a netdev appears through hot plug then gets enslaved by a failover > master that is already up and running, the slave will be opened > right away after getting enslaved. Today there's a race that userspace > (udev) may fail to rename the slave if the kernel (net_failover) > opens the slave earlier than when the

I use bonding under CENTOS4.5 x32_62. I have these weird messages when I'm restarting network. Do you have any ideas how to fix this? (there is similar bug for centos5 http://bugs.centos.org/view.php?id=2404, but the author says that it worked for him in centos4...) Thanks Vitaly Dec 17 08:34:21 3_10 kernel: bonding: Warning: the permanent HWaddr of eth0 - 00:1A:64:0A:DC:9C - is still in

Hi, Sometimes, I found one of my Mellanox NIC renamed to rename6, instead of eth1. The right names of NICs in my system should be: eth0 Mellanox NIC eth1 Mellanox NIC eth2 Intel NIC eth3 Intel NIC eth4 Intel NIC eth5 Intel NIC eth0 and eth1 will combined as bond1 with mode 4. However, the current names are: eth0 Mellanox

Ahoy, I've encountered some confusing semantics with using PACKET(7) sockets on bridge-enslaved interfaces. Specifically, if my socket accepts all types of frame (bind() to ETH_P_ALL) then it gets all packets; but if it accepts any specific type (e.g. ETH_P_IP), then it receives no packets at all. That is how it's coded in net/core/dev.c's netif_receive_skb(). First ETH_P_ALL

Hi I am mouving from PC-NFS to SAMBA and thare are some thinks that I would like to see in SAMBA. In NFS, when I do not want a share to be accessible, I just use the command: unshare /shared/directory This make the /shared/directory imediataly not accessible. Even by some one already using it! I?m using SAMBA 1.9.18p10 in a SUN Solaris 2.5 and i try to change smb.comf to disable one share,

Sorry if this is an old problem. I have just installed 1.9.18p10 - the latest version. I noticed the nis homedir option in the config file, but have not had much luck in implementing it. I had hoped it would mean my [homes] shares would map to the correct server - the one which physically carries a users home directory - regardless of the machine to which the connection attempt was made. My

On 3 December 2017 at 07:05, Michael S. Tsirkin <mst at redhat.com> wrote: > On Fri, Dec 01, 2017 at 12:08:59PM -0800, Shannon Nelson wrote: >> On 11/30/2017 6:11 AM, Michael S. Tsirkin wrote: >> > On Thu, Nov 30, 2017 at 10:08:45AM +0200, achiad shochat wrote: >> > > Re. problem #2: >> > > Indeed the best way to address it seems to be to enslave the

On 3 December 2017 at 07:05, Michael S. Tsirkin <mst at redhat.com> wrote: > On Fri, Dec 01, 2017 at 12:08:59PM -0800, Shannon Nelson wrote: >> On 11/30/2017 6:11 AM, Michael S. Tsirkin wrote: >> > On Thu, Nov 30, 2017 at 10:08:45AM +0200, achiad shochat wrote: >> > > Re. problem #2: >> > > Indeed the best way to address it seems to be to enslave the

Getting "bnx2i: iSCSI not supported, dev=eth0" for all the NIC adapters on all of my R710's running CentOS 5.5. Here is an sample of the error messages: bonding: Warning: either miimon or arp_interval and arp_ip_target module parameters must be specified, otherwise bonding will not detect link failures! see bonding.txt for details. bonding: bond0: setting mode to active-backup

On Tue, Dec 19, 2017 at 10:41 AM, Stephen Hemminger <stephen at networkplumber.org> wrote: > On Tue, 19 Dec 2017 13:21:17 -0500 (EST) > David Miller <davem at davemloft.net> wrote: > >> From: Stephen Hemminger <stephen at networkplumber.org> >> Date: Tue, 19 Dec 2017 09:55:48 -0800 >> >> > could be 10ms, just enough to let udev do its renaming

On Tue, Dec 19, 2017 at 10:41 AM, Stephen Hemminger <stephen at networkplumber.org> wrote: > On Tue, 19 Dec 2017 13:21:17 -0500 (EST) > David Miller <davem at davemloft.net> wrote: > >> From: Stephen Hemminger <stephen at networkplumber.org> >> Date: Tue, 19 Dec 2017 09:55:48 -0800 >> >> > could be 10ms, just enough to let udev do its renaming

On Tue, Jun 26, 2018 at 5:29 PM, Michael S. Tsirkin <mst at redhat.com> wrote: > On Tue, Jun 26, 2018 at 04:38:26PM -0700, Siwei Liu wrote: >> On Mon, Jun 25, 2018 at 6:50 PM, Michael S. Tsirkin <mst at redhat.com> wrote: >> > On Mon, Jun 25, 2018 at 10:54:09AM -0700, Samudrala, Sridhar wrote: >> >> > > > > Might not neccessarily be something

On 3 December 2017 at 19:35, Stephen Hemminger <stephen at networkplumber.org> wrote: > On Sun, 3 Dec 2017 11:14:37 +0200 > achiad shochat <achiad.mellanox at gmail.com> wrote: > >> On 3 December 2017 at 07:05, Michael S. Tsirkin <mst at redhat.com> wrote: >> > On Fri, Dec 01, 2017 at 12:08:59PM -0800, Shannon Nelson wrote: >> >> On 11/30/2017

On 3 December 2017 at 19:35, Stephen Hemminger <stephen at networkplumber.org> wrote: > On Sun, 3 Dec 2017 11:14:37 +0200 > achiad shochat <achiad.mellanox at gmail.com> wrote: > >> On 3 December 2017 at 07:05, Michael S. Tsirkin <mst at redhat.com> wrote: >> > On Fri, Dec 01, 2017 at 12:08:59PM -0800, Shannon Nelson wrote: >> >> On 11/30/2017