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?
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
Hi, I try to simulate an HPE switch by using the Linux host with vlan tagging.
Here is the interface config
The nvue config:
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 !