On Saturday, 6 June 2020 15:00:14 BST Ralph Corderoy wrote: > If you understand the method nodogsplash uses for control and want to > get something working alongside it, whether SSH, OpenVPN, or Wireguard,
I'm not sure I fully understand nodogsplash, but I understood enough 2-3 years ago to get the functionality I wanted. I want to retain that functionality and also have the VPN. > then > https://developers.redhat.com/blog/2018/10/22/introduction-to-linux-interfac > es-for-virtual-networking/ might be useful in understanding all the terms > and what they provide. That's certainly a useful site. Going back to my original question: > <Quote> > Another option could be to use macvlan interfaces. Very much like a extra > physical interfaces, does not require special router support, but cannot be > added to a bridge. (you can however build a macvlan interface off a bridge > interface.) > > root@sun:~# for i in 0 1; do ip l add mcv$i address b8:27:eb:0$i:1$i:2$i > link eth0 type macvlan mode private; done > root@sun:~# ip r > default via 172.17.0.1 dev eth0 src 172.17.255.10 metric 202 > default via 172.17.0.1 dev mcv0 proto dhcp src 172.17.255.241 metric 205 > default via 172.17.0.1 dev mcv1 proto dhcp src 172.17.255.92 metric 206 > 10.8.0.0/24 dev tun0 proto kernel scope link src 10.8.0.1 > 169.254.0.0/16 dev eth0.314 scope link src 169.254.94.218 metric 204 > 172.17.0.0/16 dev eth0 proto dhcp scope link src 172.17.255.10 metric 202 > 172.17.0.0/16 dev mcv0 proto dhcp scope link src 172.17.255.241 metric 205 > 172.17.0.0/16 dev mcv1 proto dhcp scope link src 172.17.255.92 metric 206 > </Quote> > > Before I try this out, I'm going to need to understand more about what is > going on. In particular, what does his line "but cannot be added to a > bridge. (you can however build a macvlan interface off a bridge > interface.)" mean? > > The bottom line: Can macvlan interfaces be used in this instance? Looking at your link, the example code given there looks nothing like the example code given by my helpful user on the Raspberry Pi Forums as above. At https://developers.redhat.com/blog/2018/10/22/introduction-to-linux-interfaces-for-virtual-networking/ the example code is: # ip link add macvlan1 link eth0 type macvlan mode bridge # ip link add macvlan2 link eth0 type macvlan mode bridge # ip netns add net1 # ip netns add net2 # ip link set macvlan1 netns net1 # ip link set macvlan2 netns net2 I'm assuming that I would need something like: # ip link add macvlan1 link eth0 type macvlan mode private # ip link add macvlan2 link eth1 type macvlan mode private # ip netns add net1 # ip netns add net2 # ip link set macvlan1 netns net1 # ip link set macvlan2 netns net2 Would this be the way to go? -- Terry Coles -- Next meeting: Online, Jitsi, Tuesday, 2020-07-07 20:00 Check to whom you are replying Meetings, mailing list, IRC, ... http://dorset.lug.org.uk New thread, don't hijack: mailto:dorset@mailman.lug.org.uk
