I don't know how well the audit framework handles namespaces, but we could plug into audit to monitor for bind() and listen() calls, then surface UI to forward traffic into the guest container.

This is the long-term plan, but will not be targeted for M69.

1) tremplin (in the VM guest) will plug into the audit framework to find when the container guest is listening on 127.0.0.1 or 0.0.0.0
2) tremplin will surface the listen event to the CrOS host
3) the host will prepare a tunnel to the container guest

Any further plans for adding UI to support forwarding more ports to the Linux guest, following on to  Issue 863578 ? Would like to be able to customize which ports are forwarded (8088 for goma, for example). Thanks.

This should be done in a generic way to enable support for this in ARC++ as well.

I'm interested in what the shape of the generic solution ends up being - ideally it would *just work* for any other app platform as well. :)