On 8/13/20 4:03 PM, Grant Edwards wrote:
I'm not sure what "go out of your way" means in this context. I assume
I'd create a network namespace for Plex, and then use either macvlan
or ipvlan to share one of the physical interaces between the root
namespace and the Plex namespace.
I've found that MACVLAN / MACVTAP, and I assume IPVLAN / IPVTAP, have a
bit of a flaw. Specifically, I've not been able to put an IP address on
the parent interface, e.g. eth1, and get communications between the host
and the {MAC,IP}V{LAN,TAP} clients. To get such host to
{MAC,IP}V{LAN,TAP} communications, I've had to add an additional
{MAC,IP}V{LAN,TAP} and put the host's IP on that.
Conversely, I've been able to use traditional bridging or OVS to
accomplish this.
I'd like the 'lo' interfaces to be shared as well, but I'm not sure
that's possible.
I think that's contrary to how network namespaces work.
I've got a colleague at work who has written a proxy program that will
listen on a port in one network namespace and connect to the same (or
optionally different) port in another network namespace. It sort of
behaves much like OpenSSH's local port forwarding going from one network
namespace to another network namespace with the service running.
Somewhat akin to SSH agent forwarding.
--
Grant. . . .
unix || die
