search for: bpdus

...ols 0.9.5 will be bridging between different VLANs on the same physical interface (for example: a bridge consisting of eth1.100 and eth1.110). This physical interface is being connected to modern Cisco switches running PVST+. The Cisco switch does not like this configuration as the tags on its BPDUs are being changed but the contents of the BPDUs are left unchanged. I need to be running PVST+ because there will be multiple Linux servers performing this VLAN translation/remapping (so there are going to be some loops that I will need blocked). Has anyone succeeded in getting VLAN translation...

...put an > address on eth0.48 then the packets get tagged by Linux but if the > switch port is not configured to receive the packets for VLAN 48 as > tagged then it will simply drop these packets and you will not get > connectivity. > Additionally, the switch should gripe about 802.1q BPDUs. Check the in-memory system log (or syslog server if you have configured that). show logging | i 1Q Example: 1w1d: %SPANTREE-2-RECV_1Q_NON_TRUNK: Received 802.1Q BPDU on non trunk FastEthernet0/2 on vlan 100. > > So getting the actual VLAN config of the switch port would help to > dete...

...t network backend support https://github.com/qemu/qemu/commit/0e0e7facc775e9bb020314f48751b3d09f316c8b#diff-a0a1810b6e249e68f1a290e37399becb Checked latest libvirt on the git repo, and didn't see this as an option. So tried to use the mcast tunnel mode. I keep getting duplicate packets with BPDUs and LLDP packets going between the Point to point connection between the VMs. VMs have bridges on them. When I used the TCP tunnel interface, if the client came up before the server end, the connection failed to establish. So both methods not super reliable. If I manually change the netdev settin...

Fixes message_age field update in config BPDUs. Also checks whether the BPDU message age has exceeded bridge max age before transmitting config BPDUs. Signed-off-by: Kishore A K <KishoreAK@myw.ltindia.com> Index: linux-2.6.7/net/bridge/br_stp.c ============================================================= --- linux-2.6.7/net/bridge/br...

Hello, I've got a very strange problem. Lately I've been setting up my linux servers for network (layer2) redundancy with a bridge interface containing two ethernet interfaces connecting to two switches. So far I didn't have any problems with it, but now a very strange thing happens with a new server I'm installing. The server is an ibm x346 having two onboard BCM5721 cards, the

...th the bug in the 802.1D-1998 spec > > 1998 - 8.6.2.2 Record Configuration Information - Use > you will notice that if the path cost ever goes up and everything > else is held constant, the BPDU will be dropped and the network not > react to the change, and the dropping of the BPDUs will make it seem > like the link is down. > > now lets look at the equivalent section in the 8021.D-2004 spec: > > 2004 - 17.6 Priority vector calculations > > as you can see here, this bug has been fixed, because the last > condition takes care of the problem, if...

...8 then the packets get tagged by Linux but if the > > switch port is not configured to receive the packets for VLAN 48 as > > tagged then it will simply drop these packets and you will not get > > connectivity. > > > > Additionally, the switch should gripe about 802.1q BPDUs. > Check the in-memory system log (or syslog server if you have configured > that). > > show logging | i 1Q > > Example: > 1w1d: %SPANTREE-2-RECV_1Q_NON_TRUNK: > Received 802.1Q BPDU on non trunk FastEthernet0/2 on vlan 100. > > > > > > So getting the actua...

Hi, I have downloaded rstp from sourceforge and I get a segfaults when running the daemon. This is the line where the problem arises: TST(ifc->master->stp_up,); just at the beginning of function: void bridge_bpdu_rcv(int if_index, const unsigned char *data, int len) in file bridge_track.c -------------- next part -------------- An HTML attachment was scrubbed... URL:

...by Linux but if the > > > switch port is not configured to receive the packets for VLAN 48 as > > > tagged then it will simply drop these packets and you will not get > > > connectivity. > > > > > > > Additionally, the switch should gripe about 802.1q BPDUs. > > Check the in-memory system log (or syslog server if you have configured > > that). > > > > show logging | i 1Q > > > > Example: > > 1w1d: %SPANTREE-2-RECV_1Q_NON_TRUNK: > > Received 802.1Q BPDU on non trunk FastEthernet0/2 on vlan 100. > >...

Do you need the whole configuration? On the switch end, we have the relevant VLAN (VLAN 48) with the assigned IP address of 192.168.48.101 and the range of ports (Gi1/0/1 - Gi1/0/8) assigned to that VLAN. Seems - and acts - like a legitimate setup and works fine, except for this particular instance. Thanks. Boris. On Fri, Jan 23, 2015 at 8:54 PM, Dennis Jacobfeuerborn < dennisml at