search for: officebridge1

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,

...ingle-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-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...