I’ve got a container on
192.168.2.81/24, it has a
I am trying to get access to a port that I am listening on ie
nc -l 10000.
When I try to access the port ie
telnet 192.168.2.81 10000 I’m getting:
telnet: can't connect to remote host (192.168.2.81): Connection refused.
I see the request with
tcpdump from inside the container:
IP 192.168.2.81.10000 > 192.168.2.1.44442: Flags [R.], seq 0, ack 4120349937, win 0, length 0
There is no firewall on either the host or in my container.
Incidentally I was able to get this working between two containers with bridged interfaces, but only if I was listening on Arch Linux and connecting with telnet from Alpine Linux. Not the other way round.
I was also unable to get this working via a VPN tunnel. For example I have a VPN tunnel connected in my container. I have the remote port forwarded on the remote server.
I should then be able to listen in the container, with
nc, and if I connect to the server IP with that port see something inside the VM.
I’ve tested it with two physical hosts, and it works, so I know it’s not a miss-configuration with the VPN server.
I also do see something inside the container:
IP 172.16.39.64.26129 > vpnserver.example.com.40138: Flags [R.], seq 0, ack 1936498654, win 0, length 0
In this case 172.16.39.64 local IP of my VPN. vpnserver.example.com is the remote’s hostname.