Tag Info

Hot answers tagged

14

You can accomplish the redirection with iptables: iptables -A INPUT -i eth0 -p tcp --dport 80 -j ACCEPT iptables -A INPUT -i eth0 -p tcp --dport 8080 -j ACCEPT iptables -A PREROUTING -t nat -i eth0 -p tcp --dport 80 -j REDIRECT --to-port 8080


9

I think what you want is: iptables -A FORWARD -m state -p tcp -d 192.168.1.200 --dport 8080 --state NEW,ESTABLISHED,RELATED -j ACCEPT iptables -t nat -A PREROUTING -p tcp --dport 8001 -j DNAT --to-destination 192.168.1.200:8080


6

What you are searching for is called port forwarding. To enable port forwarding, you must log into your router and tell it that all unexpected incoming traffic from the network, on a certain port, is to be forwarded to that particular internal IP address. An analogy is that your router which performs NAT (network address translation) is like the front desk ...


5

You should look at using a reverse proxy, such as Nginx... e.g. put this in your nginx.conf file: server { listen 80; server_name your_ip_address your_server_name access_log /var/log/nginx/your_domain/access.log ; error_log /var/log/nginx/your_domain/error.log info ; location / { proxy_pass http://127.0.0.1:3000; ...


5

iptables -t nat -A PREROUTING -d 1.1.1.1 -p tcp --dport 80 -j DNAT --to-destination 1.1.1.1:8080


5

ssh user@localhost won't work, at least not with the rules you've used. The PREROUTING chain works on packets coming into the machine, whereas if you're connecting to localhost, packets are being generated locally. The upside, though, is that your configuration should work for external connections. Have you tried it from somewhere else? Edit: This is a ...


4

technically it's not possibly unless your router has a built in reverse proxy or some layer 7 routing which none that I know of do. If you want to really do it this way and want to make it scalable, then you will need to have a reverse proxy which has maps of site names and where to proxy it to. <VirtualHost *:80> ServerName www.domain-a1.com ...


4

If you add tunneling to your SSH session, there is an additional data stream created for the tunnel over the same encrypted connection. You also can create more than one tunnel or don't start an interactive session (with the -N parameter). So, basically, there is no real difference, just different methods to use the encrypted connection.


3

According to the manual, you may, on the public host, set the option (in sshd_config): GatewayPorts yes and then on local try ssh -R *:8000:localhost:22 user@public (note the extra *:). If you do not have access to public's sshd_config, you may make an extra port forward like so: on local (lancomp): ssh -R 8001:localhost:22 user@public on public: ssh ...


3

It's only useful if you have more than 1 public IP. Say you have 1.1.1.1 and 1.1.1.2 as your public IPs, you can then specify that if someone hits port 22 on 1.1.1.1 it will be forwarded to 192.168.0.1 and hitting port 22 on 1.1.1.2 wont (for example).


3

There are ways of doing this, like installing a mail forwarder on your web server. What I would do, though, is just point the MX record to mail.server.com and not bother with redirection. Because it introduces complexity that you don't really need to have. If something happens to your mail, you're going to have to take into account the interaction of your ...


3

A primary purpose of HTTPS is to prevent "man-in-the-middle", which is exactly what a transparent proxy like this is trying to do. To do so, you'd need to have a certificate valid for everything or a system to generate certificates on the fly. In either case you're going to need an internal CA (no already-trusted external one will give you a cert for ...


3

Rinetd setup is easier I think.


3

Many routers don't support this sort of back-traversal. (Connecting to the outside from a machine on the inside.) That may be part of your problem. Further more: For telnet you need port 23, 22 is SSH and 21 (together with 20) is FTP. To check that the port-forwarding is actually working properly you can use something like ShieldsUp! (www.grc.com, Click on ...


3

SSH is really a generic secure communication mechanism which can transport arbitrary data over an insecure underlying channel. By default this data is a shell session (i.e. your local terminal is connected to a shell running on the remote system), but there are different types of data which can be transported. One such type is a stream socket connection ...


2

A stateful firewall can track UDP. It just creates an established connection for UDP once it has seen a packet coming from a masqueraded internal machine to an IP address on the internet. Any responding traffic is automatically forwarded to the internal machine.


2

I think this cries out for "why would you do that?!" Just edit server1.com's DNS zone and add something like mail.server1.com A [server2'sIPAddress] and configure mail.server1.com as the MX record for the server1.com domain. There's nothing that says a server can't have more than one name, or even more than one domain. Keep in mind if you're paying for ...


2

Well, since you got the service up and running, there are a couple of things you may have to check, since you have centos running (I assume the 5 series). Make sure that iptables allows http traffic. If not, run: iptables -I INPUT 5 -m tcp -p tcp --dport 80 -j ACCEPT AND If you have SELinux running, you will need to enable http access. You can verify ...


2

If you just need to redirect all incoming traffic to a specified port forwarded to your another machine try rinetd instead of iptables. It's a traffic redirection server.


2

Works fine for me. A couple things to check: This won't NAT connections made from the VPN server itself, for this you need the rule in the OUTPUT chain. Is the client configured to route all traffic through the VPN? If not you may find that the response packets are not being sent back through the VPN. Are you sure you're using the client side IP address, ...


2

IF the host is never going to be using that interface, then you really shouldn't do anything on the host. Instead setup virtual box to bridge the virtual interface for your VM directly to that physical interface. Then setup your VM as if it was physically connected to whatever that interface was connected to.


1

Just running through a check list of things Is websphere running and listening on port 90 ? netstat -a On the same server can you telnet localhost 90 and see the websphere server ? In case these dont fix it, can you paste netstat -a and sudo iptables -L here.


1

I don't believe Apache has a default rule that disallows all except for localhost, but it is my guess that what you are experiencing. In the httpd.conf , there is a directive that sets Apache so that nobody can access it, and it looks like this: <Directory /> Options FollowSymLinks AllowOverride None Order deny,allow Deny from all ...


1

Maybe I don't understand your question here, but how about squid that you already tagged? client -> transparent proxy GER -> transparent proxy UK -> some site that only work for UK clients


1

Forget iptables. Do a ssh -D 1234 to have a SOCKS proxy. Then you can configure your navigator to use this. (Or configure tsocks). Of course you can also do it with iptables, but since you already have a ssh, it should be easier. Look for NAT and iptables keywords.


1

You might want to look into either of nginx, Apache with mod_proxy or pound. Most prefer nginx, bit pound is also à good choice.


1

According to the web, the Netgear's port forwarding is called "rules" on this device, so as long as you have access to the device, you should be able to setup the device.


1

If a client has no port open (in the language of most small residental routers), that only blocks incoming connections. A machine behind that router can still initiate connections with others. Once it does, the router remembers that and allows two-way communication. NAT, the function that lets you have more than one machine share a single public IP, has ...



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