[linux]: TCP connection might cause extension process panics on Linux hosts

[legomushroom]

TCP connection might cause extension process panics on Linux hosts. This is happening due to configuration in firewall rules to block kernel initiated RST messages for local network sockets that we use in NAT logic.

Reproduce steps

1. Create a Codespace that can act as Linux host.
2. Change some network interface IP address:

sudo ifconfig docker0 173.17.0.1 netmask 255.255.0.0

3. Start a local HTTP server on port 3000 Codespace:

node ./index.js

4. Start the extension and connect to another Codespace:

sudo gh net start

5. Make an HTTP request on another Codespace to the IP address defined in (2):

wget -d 173.17.0.1:3000

5. Notice that request sometimes successful, but subsequent http request to the same endpoint fail. Sometimes the CLI GUI may contain an error stack trace and network forwarding does not work anymore. Sometime the request fails even initially.

Expected behavior

HTTP request completes successfully without causing the extension process to panic. Subsequent HTTP requests to the same endpoint work as expected.

Desktop (please complete the following information):

NAME="Alpine Linux"
ID=alpine
VERSION_ID=3.15.0
PRETTY_NAME="Alpine Linux v3.15"
HOME_URL="https://alpinelinux.org/"
BUG_REPORT_URL="https://bugs.alpinelinux.org/"

Logs

local-side.log

remote-side.log

[legomushroom]

Fixed in v0.6.4 🎉