simple IP configuration question?

Julian Underwood <mailings@underwoods.net> · Tue, 24 Aug 2004 23:38:35 -0400 (EDT)

Dear Linux-Net list,

I am struggling with a Fedora Core 2 server which I am trying to put 
together and was wondering if someone could offer a suggestion. This 
should be a simple answer for someone.  I have a server which is connected 
directly to DSL and to a LAN.

            DSL (static,168.100.199.66)
             |   eth1
        [Server]
             |    eth0
        192.168.0.7
             |
           LAN------>SonicWall(192.168.0.1)--->Cable Modem

The clients on the LAN go to the outside world via the SonicWall and 
access the server at .7 for file services.  The DSL is only for web 
services externally.  If I put in all the settings into Fedora's 
"system-config-network" which would seem to work--nothing works at all! 
That is, only one interface will work at a time.  If both interfaces have 
specified gateways, neither interface works--cannot ping either one.

However, if the chosen interface's gateway is left blank, the other 
interface will work fine; leaving the 'gateway-less' interface useless 
(cannot ping it).  How can I get both to work? :-)  What am I missing?

eth1:168.100.199.66, 255.255.255.248, gw:168.100.199.65, dns:168.100.1.3
eth0:192.168.0.7, 255.255.255.0, gw:192.168.0.1, dns:not specified.

Here is my routing table when the above values are filled in (and 
consequently nothing working; can't browse from server or ping it):

Kernel IP routing table
Destination     Gateway      Genmask       Flags Metric Ref    Use Iface
168.100.199.64    *        255.255.255.248 U      0      0        0 eth1
192.168.0.0       *        255.255.255.0   U      0      0        0 eth0
169.254.0.0       *        255.255.0.0     U      0      0        0 eth0
127.0.0.0         *        255.0.0.0       U      0      0        0 lo
default      192.168.0.1   0.0.0.0         UG     0      0        0 eth0

Could someone offer a suggestion on what I should do?  I don't know why 
this is so difficult.  I've had suggestions:"it should just work", "add a 
route", and "use iproute2." I think I need to add a route(s), just not 
sure what--any ideas?

Thanks,

Julian

P.S.- does 168.100.199.64 in the routing table look out of place, 
considering what my gw and IP are?

-

: send the line "unsubscribe linux-net" in

the body of a message to majordomo@vger.kernel.org

More majordomo info at  http://vger.kernel.org/majordomo-info.html