Displaying 2 results from an estimated 2 matches for "alice1".
Did you mean:
alice
2018 May 30
2
tunnel interface names
...or tap*. namespaces can be used. so:
clients:
ssh -o "Tunnel Ethernet" -w officebridge1:officebridge1-alice office-hub
on the hub:
allow-hotplug /officebridge1-*=officebridge1-port
iface officebridge1-port inet manual
bridge officebridge1
and
client:
ssh -b 1.2.3.4 -w office1:office-alice1 office
ssh -b 2.3.4.5 -w office2:office-alice2 office
allow-hotplug /office*=office
iface office inet manual
up route add default dev "$IFACE"
and server:
allow-hotplug /office-alice*=office-alice
iface office-alice inet manual
up route add 3.4.5.0/24 dev "$IFACE"
what is...
2018 May 29
2
tunnel interface names
the fact that ssh insists on tap* and tun* tun/tap-device-names is a real nag and prevents from nice and easy solutions in some cases.
the channel type used for tun/tap forwarding is tun at openssh.com, and it defines the remote tunnel id to be integer.
so from what i understood these packet definitions are static per channel type, so for compatiblity the tun at openssh.com type has to stay,