How clear and straight forward is your explanation, thanks. Can I use this settings in some way to bypass port 80 block from ISP to activate my own web server on a windows machine?
If your ISP is blocking port 80 incoming to you, then you can use this to forward another external port (for example 8080 ) to your internal port 80 but you can't use it to unblock that port.
Great video! Would this work for a server running in the cloud? I tried other options (iptables, firewalld, ufw) but they have not worked as I expected. I'm a bit new with Linux and networking...
Thanks for the nice feedback. It's hard to tell if this would work. It depends a bit on how the infrastructure is shared with your cloud provider/VPS. As you're most likely running on a virtualized or containerized environment, you might not have the right access or permissions to make these changes. Also it depends if your host is using iptables or nftables or another method.
I am running this under a cloud vm. For some reason after adding the masquerade rule it starts showing: sudo: unable to resolve host {VMname): Temporary failure in name resolution. Do you know why this would happen?
Maybe the change caused DNS to no longer be reachable? Is it local? Also make sure your own hostname (cat /etc/hostname) is present in your hosts file (/etc/hosts).
THANK YOU !
Wow. Amazing. Thanks for sharing your knowledge.
How clear and straight forward is your explanation, thanks. Can I use this settings in some way to bypass port 80 block from ISP to activate my own web server on a windows machine?
If your ISP is blocking port 80 incoming to you, then you can use this to forward another external port (for example 8080 ) to your internal port 80 but you can't use it to unblock that port.
thanks a lot was very helpfully
very helpfull!!! thank you very much!!!!
Thanks for the nice feedback :)
thanks
Great video!
Would this work for a server running in the cloud? I tried other options (iptables, firewalld, ufw) but they have not worked as I expected. I'm a bit new with Linux and networking...
Thanks for the nice feedback. It's hard to tell if this would work. It depends a bit on how the infrastructure is shared with your cloud provider/VPS. As you're most likely running on a virtualized or containerized environment, you might not have the right access or permissions to make these changes. Also it depends if your host is using iptables or nftables or another method.
I am running this under a cloud vm. For some reason after adding the masquerade rule it starts showing: sudo: unable to resolve host {VMname): Temporary failure in name resolution. Do you know why this would happen?
Maybe the change caused DNS to no longer be reachable? Is it local? Also make sure your own hostname (cat /etc/hostname) is present in your hosts file (/etc/hosts).
Is it possible to redirect all system TCP traffic to client socks proxy endpoint?
question, will this allow anyone on the internet to access the port i forwarded using my public ip?
That should work, yes
@@jensdbe yup, it worked. thanks!!