wrsw_vlan should disable untagging automatically when switching from access to other modes
see bug report ---------- Forwarded message --------- From: Maciej Lipinski maciej.lipinski@cern.ch Date: Mon, 6 Jan 2020 at 14:26 Subject: Re: bug in wrs vlan config for 5.0.1 To: Beck, Dietrich Dr. D.Beck@gsi.de Cc: Grzegorz Daniluk grzegorz.daniluk@cern.ch
Dietrich, As far as I can tell, what happens is the following:
- when you set the port into ACCESS mode, the "untag" feature of the on this port is automatically enabled. This means that the port not only tags received frames but also untagged the transmitted frames
- when you change mode to TRUNK, this feature is not disabled automatically, you need to force it by adding to your command "--puntag 0", e.g.: wrsw_vlans --port 1 --pmode 0 --puntag 0 When you set a port directly to TRUNK mode (after startup or clear), untagging is disabled so all works. I agree that it is not an intuitive behavior, we will consider changing it. Please, let me know whether using the --puntag 0 helped regards maciej On Mon, 6 Jan 2020 at 11:58, Beck, Dietrich Dr. D.Beck@gsi.de wrote: Hi Greg and Maciej, a happy new year to both of you! I am on vacation (out of office) so, I am unable to give the exact sequence.
Setup node --- WRS --- WRS --- node The bug/feature can be triggered by configure the ports interconnecting WRS as ACCESS reconfigure the same ports as TRUNK As I said, I tapped the Ethernet frames between the WRS using wireshark: Those frames do NOT have a VLAN Tag. This can be reproduced after starting again from scratch (after 'wrs_vlans --clear'). However, if I omit step '1' and configure the ports as TRUNK directly, then everything works as expected (and the frames tapped with wireshark have a VLAN tag). Cheers, Dietrich
Von: Grzegorz Daniluk grzegorz.daniluk@cern.ch Gesendet: Montag, 6. Januar 2020 10:44:28 An: Beck, Dietrich Dr. Cc: Maciej Lipinski; Hahn, Alexander; Zweig, Marcus Betreff: Re: bug in wrs vlan config for 5.0.1 Hi Dietrich, Happy New Year!Could you please send us the exact commands you're executing? Cheers,Greg On Mon, 23 Dec 2019 at 16:35, Dietrich Beck d.beck@gsi.de wrote: Hi Maciej,
I think there is a bug (or something undocumented) for WRS 5.0.1 when configuring VLANS.
(I put a few colleagues in CC to prevent them from doing the same mistake as me).
Setup
- a few TRs connected to two WRS
- ports with TR configured as ACCESS
- ports with/between WRS configured as TRUNK
- config done with CLI 'wrs_vlans'
what does not work
- 1st step: configuring ALL ports as ACCESS
- 2nd stop: changing ports between WRS to TRUNK bug:
- 'wrs_vlans --plist' shows the desired config
- but TRUNK ports don't work as ACCESS ports
what does work
- 1st step: configuring only ports with nodes as ACCESS
- 2nd step: configuring ports between WRS as TRUNK
conclusion
changing 'pmode' from 'ACCESS' to 'TRUNK' never works for me. (I almost got mad on this). I confirmed by checking with wireshark
- config port directly as 'TRUNK' -> VLAN Tag is in Ethernet header
- changing port from 'ACCESS' to 'TRUNK' -> no VLAN Tag
Cheers,
Dietrich
--