Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Question: Using tag vlan in Linux host possible? #12

Closed
Sispheor opened this issue Feb 27, 2024 · 2 comments
Closed

Question: Using tag vlan in Linux host possible? #12

Sispheor opened this issue Feb 27, 2024 · 2 comments

Comments

@Sispheor
Copy link

Hi,
I try to simulate an HPE switch by using the Linux host with vlan tagging.

Here is the interface config

auto lo
iface lo inet loopback

auto eth1
iface eth1

auto eth1.165
iface eth1.165
    address 10.162.0.20/20
    vlan-raw-device eth1

auto eth1.167
iface eth1.167
    address 10.162.24.20/21
    vlan-raw-device eth1

The nvue config:

bridge:
      domain:
        br_default:
          vlan:
            '165': {}
            '167': {}
            '2': {}
    interface:
      lo:
        type: loopback
        ip:
          address:
            127.0.0.1/8: {}
            172.30.0.1/32: {}
      vlan165:
        description: SVI to test External network connectivity
        type: svi
        vlan: 165
        ip:
          address:
            10.162.0.13/20: {}
      vlan167:
        description: SVI to test OAM network connectivity
        type: svi
        vlan: 167
        ip:
          address:
            10.162.24.12/21: {}
      swp30:
        bridge:
          domain:
            br_default:
              vlan:
                '165': {}
                '167': {}

Ping it's not working between the two device. I was wondering if there is any Docker limitation for this kind of deployment.
The Linux host is a Debian. May I need to add the "vlan" package to the Dockerfile.
Did you ever try this?

Thanks a lot for your time !

@networkop
Copy link
Owner

I don't think there should be a limitation here, most likely a configuration issue. you can use tcpdump to see if any packets are being send/received on the interconnected interfaces

@Sispheor
Copy link
Author

Thanks, I'll dig

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants