4 * 200 Pro 512 MB Ram 6 * 4 SCSI drives 1 * intel 100B network card (onboard) 1 * PCI 4 port switch (installed by myself) 1 * all the other drama that makes up a server
So far as Linux (Red Hat 8.0) is concerned, it's installed and working lovely. It detects all the processors, uses all the ram, plays Half Life TFC/CStrike perfectly... a wvdial setup takes care of the 56 k modem attached to the server ( /dev/ttyS0 ), and an IPTables firewall/NAT takes care of my internal LAN and outside communications to the internet... It's been doing this and doing it well for years, except for when I started on THIS server. ifconfig eth0 down (this is the onboard LAN card 10.0.0.2) ifconfig eth1 down (this is the PCI Switch on 10.0.0.1) /etc/rc.d/rc.firewall (starts the IPTables script for Firewall/NAT) wvdial (dials the internet, and I assume starts ppp0) ifconfig eth1 up (restarts eth1) ifconfig eth0 up (restarts eth0, but I dont use it so unneccessary) Long winded, and not at all possible for my wife to do should it end up crashing when I'm not home... Dual fold question, why do I have to DISABLE eth0 and eth1 for ppp0 to be the default route, and is there a way that we can have this made a little bit easier if not a little bit eliminated... I've tried switching the Intel LAN card off in bios, but for some reason it STILL requires all lan cards to be disabled before ppp0 is the default route... Standing by to answer any queries you may have/try any suggestions you may offer Andy
