1. Forum
  2. FidoNet
  3. linux.debian.user

  • VirtualBox VM and VLAN interfaces

    From Marco Moock@3:633/10 to All on Saturday, June 13, 2026 11:50:01
    Hello!

    As no one on the VBox mailing list had ideas, I will try it here.

    I have a Debian system with a VLAN trunk and some vlan interfaces
    (called vlan2, vlan3 etc.).

    If I bridge the vlan interface (not the trunk) to the VM, the incoming
    traffic still has the vlan tags, like if I bridge it with the trunk.

    I used NetworkManger to create those interfaces.

    Are other people here experiencing the same issue?

    --
    kind regards
    Marco

    Spam bitte an abfalleimer2001@stinkedores.dorfdsl.de

    --- PyGate Linux v1.5.16
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Geert Stappers@3:633/10 to All on Sunday, June 14, 2026 10:30:01
    On Sat, Jun 13, 2026 at 11:29:30AM +0200, Marco Moock wrote:
    Hello!

    As no one on the VBox mailing list had ideas, I will try it here.

    Here an ex virtual box user. ( Here a happy QEMU user. )


    I have a Debian system with a VLAN trunk and some vlan interfaces (called vlan2, vlan3 etc.).

    If I bridge the vlan interface (not the trunk) to the VM, the incoming traffic still has the vlan tags, like if I bridge it with the trunk.

    Acknowledge


    I used NetworkManger to create those interfaces.

    Are other people here experiencing the same issue?


    Yes. However they don't experience it as an issue.
    They understand where to tag and where (and how) to untag.



    Regarding
    } As no one on the WHATEVER mailing list had ideas, I will try it here.


    http://www.catb.org/~esr/faqs/smart-questions.html





    Groeten
    Geert Stappers
    --
    Silence is hard to parse

    --- PyGate Linux v1.5.16
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Marco Moock@3:633/10 to All on Sunday, June 14, 2026 12:10:01
    Am 14.06.26 um 10:30 schrieb Geert Stappers:
    Yes. However they don't experience it as an issue.
    They understand where to tag and where (and how) to untag.

    If it bridge the trunk interface, I expect that the tags are there. If I bridge the vlan interface, I expect untagged traffic.

    vlan2@enp3s0 is the vlan interface. I use NetworkManager to create them.

    --
    Gruá
    Marco

    Spam bitte an abfalleimer2001@stinkedores.dorfdsl.de

    --- PyGate Linux v1.5.16
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Anssi Saari@3:633/10 to All on Monday, June 15, 2026 16:10:01
    Marco Moock <mm@dorfdsl.de> writes:

    If I bridge the vlan interface (not the trunk) to the VM, the incoming traffic still has the vlan tags, like if I bridge it with the trunk.

    When adding a VLAN interface to a bridge, there's an untagged option
    which can be used to specify which VLAN IDs should be stripped on
    egress. That is, when using the bridge util. I believe nothing is
    stripped by default, which seems to be the configuration you have.

    I used NetworkManger to create those interfaces.

    Don't know about that thing. I guess it should have some setup for this?
    If it's missing from the GUI, maybe you can put it in the text config
    files?

    bridge vlan show should show your bridge configuration, including what,
    if anything, is egress untagged.

    --- PyGate Linux v1.5.16
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Marco Moock@3:633/10 to All on Tuesday, June 16, 2026 20:50:01
    Am 15.06.26 um 16:10 schrieb Anssi Saari:
    bridge vlan show should show your bridge configuration, including what,
    if anything, is egress untagged.

    :~$ sudo bridge vlan show
    port vlan-id
    ~$

    I use the Virtualbox function bridge, so maybe this is different from
    the bridge that can be created using bridge-utils.

    --
    Gruá
    Marco

    Spam bitte an abfalleimer2001@stinkedores.dorfdsl.de

    --- PyGate Linux v1.5.17
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Anssi Saari@3:633/10 to All on Wednesday, June 17, 2026 09:30:01
    Marco Moock <mm@dorfdsl.de> writes:

    I use the Virtualbox function bridge, so maybe this is different from
    the bridge that can be created using bridge-utils.

    Looks like. I really don't know much about Virtualbox.

    With a very quick look though, apparently VB doesn't do VLAN filtering
    so the way forward is to do a Linux bridge and do the VLAN filtering
    there. And connect the virtual guest to that.

    --- PyGate Linux v1.5.17
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)