UserAgent: Mozilla/5.0 (X11; CrOS x86_64 10895.78.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.120 Safari/537.36
Platform: 10895.78.0 (Official Build) stable-channel eve

Example URL:

Steps to reproduce the problem:
1. Run any UDP or TCP application in a Crostini container (pjsip, socat, nginx, etc)
2. Try to send-udp/open-tcp from system on Lan/Wan/Wifi toward applications running on Eve/container.
3. Try to connect to udp or tcp applications running in a CrOS container from outside the CrOS computer.
4. You will realize that you can get to, say, Eve's external IP, 192.168.x.x, but that lacking iptables entries, no udp, or tcp connections are getting to that container at 100.115.92.x from the CrOS's external interfaces.

What is the expected behavior?
CrOS & Crostini are fabulous! [and Eve too!], but to give developers such a nice linux container platform that they can't make inbound udp/tcp connections to, is mean.
[CrOS/Crostini can make outbound tcp/udp sessions, but it is only half the picture]

What went wrong?
I suspect you guys/gals know all this, and just have a huge backlog of stuff in front of this issue, but I want to say thanks for such an awesome environment on such awesome hardware, and I hope you can provide a way to setup forwarding for udp/tcp from the external ip-interfaces to the internal container-interfaces for developers without having to go into dev mode and mess with iptables on the host.

Did this work before? N/A 

Chrome version: 69.0.3497.120  Channel: stable
OS Version: 10895.78.0
Flash Version: