New answers tagged port-forwarding
0
Quick examples for forwarding traffic coming from outside and interfaces within the same machine from address original to another address for ip versions 4 and 6 (possibly excluding ipsec traffic with an endpoint on the original address and existing connections at point of execution). This also does NOT redirect traffic generated by locally executing ...
0
Here is a usefull article to check:
https://www.watchguard.com/help/docs/help-center/en-US/Content/en-US/Fireware/nat/nat_static_config_about_c.html?Highlight=port%20forwarding
1
If the Raspberry Pi is running OpenVPN Client you don't need to open the port on your FritzBox router.
However the right iptables rule in PREROUTING is the one with 10.8.0.6 as destination
# START OPENVPN RULES
# NAT table rules
*nat
:POSTROUTING ACCEPT [0:0]
-A PREROUTING -i venet0 -p tcp -m tcp --dport 9000 -j DNAT --to-destination 10.8.0.6:9000
-A ...
1
You have a couple of options for allowing external access to your server with private IP:
Forwarding a port from the router/firewall, which protects this server. How to do it depends on the type of the router/firewall.
Using ngrok to circumvent the firewall.
Build yourself VPN connection into the server's LAN - again on the router/firewall. Again, depends ...
1
After digging into this a bit more (and reading the excellent book SSH Mastery), I was able to resolve my issue: Even though I had set a ServerAliveInterval in my client .ssh/config file, I had not set a ClientAliveInterval in my server sshd_config file.
As a result, the server was not timing out, and was maintaining the connection. In combination with the ...
0
Sorry, we figured it out. The connected UDP Server had an issue when talking to different subnets.
It just wouldn't send any response when the subnet didn't match the directly connected one.
Configuration worked otherwise.
0
There seems to be an additional "." at the end of your DNAT for UDP rule in the IP address part. I believe you might have received an error when trying to add the rule and maybe not noticing it. Maybe you should provide iptables dump of the nat table.
0
Oddly enough, even though telnet doesn't work, I can still connect to the SQL Server by specifying 127.0.0.1,1439 using standard SQL Server tools.
Don't know why telnet hangs when testing locally but not on the remote machine. I guess that just means it's not a valid test of connectivity.
0
If nginx is configured as a reverse/cache proxy server, then I think what you are looking for is:
location /123 {
proxy_pass http://localhost:3001;
}
0
lighttpd can listen on port 443 and terminate the TLS.
lighttpd mod_proxy can be used to reverse proxy to backend HTTP (not HTTPS) services, typically running on the same local machine.
https://redmine.lighttpd.net/projects/lighttpd/wiki/Docs_ModProxy
0
From the information you provided it isn't directly clear if your FORWARD policy allows forwarding or not. If not - you don't have the rules to forward DNATted traffic from tun0 to eth0.
0
That's what you use a reverse proxy for.
Have the proxy listen on port 443 with a valid certificate, and configure your various backends with or without TLS security depending on your security goal.
I have no experience with lighttpd specifically, but a quick web search indicates that it should be possible for you to achieve something like this without ...
0
First of all the, the port you need is 22 as this is the port of SSH and it seems like you configured your router properly.
Port 21 is the default FTP protocol port.
Then, I’d check your centos server iptables status, as by default it is turned on and blocking all incoming connections.
Just for the test, I’d shut the service down and try reconnecting.
You ...
0
If you can't open a port up to the Internet, set up your own server, like a cheap VPS, and forward traffic via SSH via that.
2
This is not currently possible. SSH does not currently support srv records.
There are some proposed patches that do so, but they are not part of mainstream repositories. (You could perhaps alias sshsrv to ssh.).
Presumably you're looking for something more portable than specifying Port in your local ~/.ssh/config, which could work for anything that shared ...
1
What you really need here is a reverse proxy (such as Nginx) that can do SSL termination for you on port 443 and then pass the request to Tomcat on port 8443.
SSL/TLS is complex, and in my view, relying on IPTABLES to handle the SSL handshake and get your request to the Tomcat application is not a good idea.
If you really need to use IPTABLES, connect to ...
0
This might depend on which interface your tomcat is bound to. If it's bound to the loopback interface then this isn't going to work at all.
Mostly the REDIRECT target is used with a specified interface like:
iptables -t nat -A PREROUTING -i eth1 -p tcp --dport 443 -j REDIRECT --to-port 8443
(replace eth1 with the actual network interface that tomcat is ...
Top 50 recent answers are included
