Hot answers tagged firewall
Your method is the hackish method. You should consider installing the iptables-persistent package which automatically will handle loading up of iptables rules at boot. This will store rules in /etc/iptables/rules.v4 and /etc/iptables/rules.v6 and will load at boot. Make revisions to those files and restore from those if you edit your rule sets.
You can check if the port is in use by running this command. sudo lsof -i :<Port Number> i am useing 8080 as an example because i have nothing running on port 6700 change 8080 to your port number sudo lsof -i :8080 COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME havp 1331 havp 3u IPv4 3434363 0t0 TCP 192.168.1.127:http-alt ...
Ask lsof (man lsof). sudo lsof -i :6700 Note: Really read man lsof! I'm not sitting at a linux box right now.
Sounds like a DNS issue. You most likely setup your external DNS to point to your firewall/router (external IP). Your firewall then does an IP/Port forward to the correct IP on your network. For this to work on your internal network, you will need to do a similar DNS setup. But you need to point the address to your internal IP address. You can do it for ...
I solved my own problem. I initially recalled (assumed. sigh) that I had specified the IP when issuing the 'curl' command from within the container, but in fact I had specified the hostname. Once I noticed that I had in fact specified the hostname, and that the hostanme resolved to the loopback, i figured out my problem. In my apache httpd.conf, the ...
Only top voted, non community-wiki answers of a minimum length are eligible