Quoting Matt Herbert <[EMAIL PROTECTED]>:
> Hey group,
> I'm helping out a friend with his firewall box for media one. He
> has a stock Redhat 6.1 machine doing IP Masquerading for his
> internal network. Now when we installed it the external nic was
> found first and assigned eth0 (tulip driver) and the internal nic was
> found second and thusly became eth1 (3c95x). This is causing some
> problems with programs that are going out eth0 to get to the internal
> network. So does anybody know if I can change /etc/conf.modules to
> make the tulip driver be eth1 and the 3c95x be eth0? ie:
"Programs going out eth0 to get to the internal network"..
I think you'll find that if you do manage to switch them around, the same
problem will occur. How do you have your routes setup? Eth interfaces are
bound to an IP, and things such as netmasks determine where to send what, with
the default route recieving packets it can't route itself. Example:
eth0: IP 172.1.2.3 Netmask 255.255.255.0 default route
eth1: IP 10.0.0.1 Netmask 255.255.255.0
Anything addressed to 10.0.0.X in this will go out eth1. Anything addressed
*ANYWHERE ELSE* will goto eth0. This is a *VERY* simplified example, and not
all of these terms are correct, but just to give you an idea..
Basically, IP info really has nothing to do with the physical device.
---
Thomas Charron
<< Wanted: One decent sig >>
<< Preferably litle used >>
<< and stored in garage. ?>>
**********************************************************
To unsubscribe from this list, send mail to
[EMAIL PROTECTED] with the following text in the
*body* (*not* the subject line) of the letter:
unsubscribe gnhlug
**********************************************************
