Acked-by: Gert Doering <g...@greenie.muc.de>
Stared at code, ran full t_client/t_server tests.
In my test I had a "vlan 200" which was the native/untagged VLAN on the
tap interface now (so ipv4/v6 config goes to "tap9") and a "vlan 207"
which was tagged (-> tap9.207), and clients in "pvid 200" could nicely
talk to clients in "pvid 207" by means of linux routing between tap9
and tap9.207. Shutting down tap9.207 stopped communication (= proof
that it really went out of openvpn and in again).
Your patch has been applied to the master branch.
commit d626fa179b215a12398051ffca25b43ecfc0ad60
Author: Antonio Quartulli
Date: Wed Oct 9 16:34:20 2019 +0200
VLAN: allow forwarding tagged and untagged packets on the server TAP device
Signed-off-by: Fabian Knittel <fabian.knit...@lettink.de>
Signed-off-by: Antonio Quartulli <a...@unstable.cc>
Acked-by: Gert Doering <g...@greenie.muc.de>
Message-Id: <20191009143422.9419-...@unstable.cc>
URL:
https://www.mail-archive.com/openvpn-devel@lists.sourceforge.net/msg18919.html
Signed-off-by: Gert Doering <g...@greenie.muc.de>
--
kind regards,
Gert Doering
_______________________________________________
Openvpn-devel mailing list
Openvpn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openvpn-devel
