Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I understand that the above command forwards connections on port 23 to 192.168.0.41 on port 23. This isn't exactly what I need. I'm looking for something that will allow me to forward connections on port 23 to 192.168.0.41 on port 80, for example.
# Set WAN to receiving interface
WAN=eth0
iptables -t nat -A PREROUTING -p tcp -i $WAN --dport 23 -j DNAT --to 192.168.0.41:80
iptables -A FORWARD -p tcp -i $WAN -d 192.168.0.41 --dport 80 -j ACCEPT
Besides mangling the packet to make it look acceptable to the target host (what nat + PREROUTING does), you also need a rule to make it get sent there (what filter + FORWARD does).
--- rod.
You can run the commands, as root, from a commandline. Most installations have a script or scripts to configure firewalls, routers, etc., and the commands could be placed in an appropriate spot within one of those scripts. It would be up to you to figure out where they would best fit. Many such scripts are built from GUI tools or canned firewall scripts. Using the GUI or the documentation & comments embedded in existing scripts might give you some clues. The commands that I provided came from the homeLANSecurity package that I use.
--- rod.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.