Using Linux as Network Glue - page 2
IntroductionI had no previous experience with Linux. After reading about the different distributions, I opted for Debian 2.1 (slink), as at the time of writing this was the most recent stable Debian release, complete with 2.0.36 kernel. To make the Linux ipchains software work with this kernel it had to be recompiled with the following options set:
This is with kernel series 2.0.x--according to the IP Chains HOWTO 2.2.x configuration is
much more straightforward.
Also, the dual ethernet cards in the system (2 old 10base2 Western Digital WD8013 cards) had to be configured. I added the line
io=0x220,0x300 to /etc/modutils/modconf and then ran update-modules.
Since then I have moved our primary and secondary DNS and email services over onto Linux machines as well, using bind and sendmail. The ipchains software is now running on a very old 486 machine.
Our Network's Topology
The 10.0.0.0 network is our private network.
The 188.8.131.52 network is internet interfacing.
The backoffice system is on a box with ip 184.108.40.206
We have an isdn router (10.0.0.2) on our private network which has a route to the backoffice box.
We masquerade our connections from the 220.127.116.11 network when connecting through to 18.104.22.168. In this way we did not need to set up a route back to the 22.214.171.124 network, as the connection will appear to have come from 10.0.0.1, to which we already have a route.
10.0.0.0 is a private network address aka RFC1918 (126.96.36.199 and 188.8.131.52 aren't our real addresses, just examples).
- 1Linux Top 3: Alpine Linux 3.4, deepin 15.2 and Linux Lite 3.0
- 2Linux 4.7 Set to Boost Live Patching, Security and Power Management
- 3Linux 4.6 Charred Weasel adds USB 3.1 Support
- 4Linux Top 3: OpenIndiana 2016.04, Ubuntu 16.04 and Debian's New Leader
- 5Linux Top 3: KaOS 2016.04, TurnKey 14.1 and pfSense 2.3