replacing an old Slackware "router" with a new one
SlackwareThis Forum is for the discussion of Slackware Linux.
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.
replacing an old Slackware "router" with a new one
For many years, my small home Lan has had an old dual processor 386 as my server. It runs Slackware 15. It has FINALLY reached the end of its seviceable life. I purchased a more modern (used) Pentium machine, put in a second NIC card, and tried to use it. Each machine runs BIND to throw out local addresses. In each case, I use the Arno configuration tool to hopefully set up Masquerading and filtering Internet traffic. To make sure I have not made any spelling or configuration errors I have copied the firewall configuration file from the old to the new machine. On the new server, I can mount my two NASes on different local addresses, 192.168.0.252 and 192.168.1.252. Computers connecting to the new server get and appropriate address, but only the NAS on the "0" network gets attached. They cannot go onto the Internet. Perhaps someone can offer a suggestion as to what I have mis-configured on the new machine, or what I might have missed. Thank you.
Can you upload your config files for us to review?
On another tangent that is not related to your post, you could install a third NIC (aka eth2) and make that management.
If your new Intel machine supports virtualisation, then create a VM to load your Slackware into.
If that works, bridge eth0 (make it WAN) and bridge eth1 (make it LAN).
I have tried to attach the configuration file, but somehow have seemingly been unsuccessful. (I have even renamed it as firewall.txt instead of firewall.conf)
Last edited by apolinsky; 06-20-2024 at 04:41 PM.
Reason: trying to attach file
For many years, my small home Lan has had an old dual processor 386 as my server. It runs Slackware 15. It has FINALLY reached the end of its seviceable life. I purchased a more modern (used) Pentium machine, put in a second NIC card, and tried to use it. Each machine runs BIND to throw out local addresses. In each case, I use the Arno configuration tool to hopefully set up Masquerading and filtering Internet traffic. To make sure I have not made any spelling or configuration errors I have copied the firewall configuration file from the old to the new machine. On the new server, I can mount my two NASes on different local addresses, 192.168.0.252 and 192.168.1.252. Computers connecting to the new server get and appropriate address, but only the NAS on the "0" network gets attached. They cannot go onto the Internet. Perhaps someone can offer a suggestion as to what I have mis-configured on the new machine, or what I might have missed. Thank you.
Why have you that adresse : 192.168.1.252 ?
You local network is for 192.168.0. in your config file.
netmask is 255.255.255.0 on each network. The two NASes are on different addresses, sequestered from one another. The 192.168.1.0 network is the zone that most wifi uses, while the 192.168.0.0 network is restricted to just a few locally connected machines. The Slackware "router with two NICS has two dedicated addresses, 192.168.0.1 and 192.168.1.2 which controls the routing between the two networks.
If your problems are around Internet access for clients on the 192.168.1.x subnet that have to cross the Slackware router to leave via 192.168.0.x subnet, make sure you have enabled ip_forward (check if "sysctl -a | grep net.ipv4.ip_forward" if is set to 1) on your Slackware router, you have allowed/configured your modem to NAT 192.168.1.x devices towards the external world, and you have a return route added at your modem to the 192.168.1.x subnet, using your Slackware router IP address as next hop.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.