Hot answers tagged

2

The configuration looks correct, and the other services already set up are apparently working correctly. After discussing the problem with the questioner, we tested setting the router to map the HTML port 80 on the web server to a different external port, and this works. It seems that the ISP is discouraging web servers by blocking port 80, and this is why ...


2

Windows netsh can setup a proxy to allow administrators to proxy ipv6 traffic over ipv4. Netsh also has an option to configure a proxy for ipv4 to ipv4. For your setup use netsh interface portproxy add v4tov4 listenport=80 connectaddress=127.0.0.1 connectport=8080 replacing the 127.0.0.1 with the address you wish to proxy to. here's a little breakdown on ...


1

You're getting scanned for vulnerable services. This isn't related to running Gary's Mod, it's just something that happens to anything with a public IP address (like your router) on the internet. More specifically, I see connection attempts for: ipprot=6 (TCP) dport=21 (FTP), an ancient file-sharing protocol that's hopelessly insecure and nobody should be ...


1

sshd -T -C user=david,host=localhost,addr=127.0.0.1 \ | grep -E 'gatewayports|allowtcpforwarding' should return correct values for your user.


1

Try temporarily disabling the firewall on the target computer, then connect from outside the network. If the connection still fails you know the problem is with the port-forwarding on the router. If the connection succeeds you know the problem is with the firewall configuration on the computer. Because you can connect locally, I suspect the router current ...


1

The packet you captured shows a Port Control Protocol (PCP: the IETF standards-track successor to NAT-PMP) port mapping request. The client port for the requested mapping is 9/TCP. The client doesn't have any suggestion for what the external port should be, so it leaves the suggested external port field set to zero. IETF RFC 6887, which defines PCP, makes ...


1

You could use something like ngrok for this. Install it and run: ngrok http 8080 And it will give you a unique subdomain that you can use to access your server. No port forwarding or anything of that sort required.


1

nslookup test.ddns.net responds with 127.0.0.1, which is the localhost. Therefore you're not even sending packets over your home network, but only inside the computer you're working on. I tried it like this test.ddns.net/test/test.html But i get "website not reachable". This is because you're running your server ion port 443 and 8080, not port 80. You ...



Only top voted, non community-wiki answers of a minimum length are eligible