Tag Info

New answers tagged

0

You could try this (incoming traffic to port 1234 will be redirected to 4321 in the localhost, where you could have your script listening): iptables -I INPUT -p tcp --dport 1234 -j ACCEPT iptables -I INPUT -p tcp --dport 4321 -j ACCEPT iptables -t nat -I PREROUTING -p tcp --dport 1234 -j REDIRECT --to-ports 4321 If you want to access the port 1234 from ...


5

If I understand your question correctly, I might rephrase it as, "If the network infrastructure allows HTTP traffic to pass on a certain port, will it also allow pure TCP (without full HTTP-compliant operation or even fake HTTP headers) to pass on that port?" Unfortunately, the answer is, "It depends on details you have not yet discovered regarding how the ...


5

TCP and HTTP are different things. TCP is the transport layer. By definition, it's responsible for carrying application layer protocols (HTTP in your case) over it. TCP does not run over a port. It is the arbitrator of ports. In other words, when you connect to an HTTP server, you connect on TCP port 80. When you connect to HTTPS, you're connecting ...


0

I finally figured out what happened. The problem was "The guest has two network adapters, one is bridged and has a public IP address which is 128.x.x.219, the other works in NAT mode and has a local IP address which is 192.168.106.129." It seems we should not do that. We should not have two virtual adapters on the same VM, with one of them working in bridged ...


0

To list all TCP sockets accepting connections you could simply use netstat -nlt.



Top 50 recent answers are included