diff options
| author | Philippe Schaaf <philippe.schaaf@secunet.com> | 2022-07-21 11:38:03 +0200 |
|---|---|---|
| committer | Philippe Schaaf <philippe.schaaf@secunet.com> | 2022-07-21 11:38:03 +0200 |
| commit | f6a290932e773b7412978f29fc50c6a8f3dce222 (patch) | |
| tree | e76a792f77dc5374c365e0a999ad84dd4110f989 /pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch | |
| parent | 1a44a2d35581bd80520b6c7706c9dff4d775df3f (diff) | |
use vde switch in hubmode by default
Within a dual VM test-setup a strange behaviour was observed.
The two VMs are connected via one vde_switch instance
(instancevirtualisation.vlans = [ 1 ]; IMO a bad attribute name for
switch instances, has nothing to do with VLANs in sense of 802.1Q).
A ping on the base interface (eth1) works, but not on VLAN
subinterfaces (vlan1@eth1). A tcpdump of eth1 includes the ARP requests
tagged with the subinterfaces VLAN ID, but responses seems not to pass
the vde_switch. This works fine if performed on the base interface.
Putting the vde_switch in hub mode results in flooding
traffic to all vde_switch ports. This results in a expected behaviour
and a ping on a VLAN subinterface works as expected.
Signed-off-by: Philippe Schaaf <philippe.schaaf@secunet.com>
Diffstat (limited to 'pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch')
0 files changed, 0 insertions, 0 deletions