Many thanks everyone that replied,
I chickened out and I've gone with the VLAN solution. Secure unless someone
gets access to the mail server or proxy. Plenty good enough at the moment.
And I keep my spare LINUX box to play with :-)
If anyone wants any extra info, drawings etc of what I've done, just shout.
Kind regards
Adrian
----- Original Message -----
From: "Gary Stainburn"
On Wednesday 19 May 2004 3:57 pm, Thomas Adam wrote:
--- "adrian.wells"
wrote: I have a suse box that I want to use as a router with two NIC's - I assume that this is the best technique, I've read a howto by Bert Huburt (Linux
Yes,
If we assume that:
eth0 is internal eth1 is internal, with a link to the router on the same subnet...
Then, simply:
route add default gw <IP> eth1
That would only enable toe Suse box to get out. It sounds like they want boxes inside that to access the net too. The best way is the install shorewall on the Linux box.
It makes the various bits of creating a firewall very simple, including enabling ip forwarding, and setting up the iptables rules to make everything safe.
Personally, I've just set up a Connexant 4-port ADSL router with built in firewalling. It was an absolute doddle, is the size of a modem, and sits inside the TV cabinet with the video/DVD etc. (The lights also tell me when the lad's got his PC turned on while I'm downstairs watching telly)
-- Gary Stainburn
This email does not contain private or confidential material as it may be snooped on by interested government parties for unknown and undisclosed purposes - Regulation of Investigatory Powers Act, 2000
-- To unsubscribe, e-mail: suse-linux-uk-schools-unsubscribe@suse.com For additional commands, e-mail: suse-linux-uk-schools-help@suse.com