search for: nondynamic

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,

...interface they might want to use in advance. similar can be true for the client side: ssh -b 1.2.3.4 -w any office ssh -b 2.3.4.5 -w any office allow-hotplug /tun*=tun iface tun inet manual up route add default dev "$IFACE" will also soon have to end up with specific single-interfaces nondynamic config. imagine mixing this: the office knows several bridges and possibly even other uses of tun/tap. might be the same for clients. now tun/tap interfaces do not have to be named tun* or tap*. namespaces can be used. so: clients: ssh -o "Tunnel Ethernet" -w officebridge1:officebridge1...