Steve,

I've just finished fighting this battle.  Following are some suggestions
based on what I just had to do:

1) Change your ethX cabling so that eth0 accesses the DSL modem and eth1
accesses your LAN (I know, it seems stupid, but I didn't find my problems
until I did this).

Go into linuxconf - From the command prompt at any console enter:

#linuxconf

Then do the following from linuxconf (steps 2 - 7):

2) Go into "Basic Host Information."  Change your static IP address on
adaptor 1, (eth0) to 10.0.0.2, netmask 255.255.255.0 UNLESS you know that
your eth0 port on your DSL modem is set to something other than 10.0.0.1.  
If so set it to match that subnet class.

3) Go into adaptor 2 (eth1). Set your netmask at 192.168.1.25.

4) Then go into "Set Defaults" and set the default gateway to 10.0.0.1 (or
an address corresponding with eth0), and check "Enable routing".

5) Then go into "Set other routes to networks" Set it up similar to the
following:

Network       Netmask           Gateway
209.98.8.3    255.255.255.0     10.0.0.1

Substitute your ISP's primary nameserver address for 209.98.8.3.  Gateway
should be the same as what you set for "Default Gateway" earlier.

6) Now go into "Set routes to alternate local nets".  Set it up as such:
(Don't know if you need this one, but my setup is working with it set)

Network      Netmask            Interface
10.0.0.1     255.255.255.0      eth0
192.168.1.0  192.168.1.25       eth1

7) Then exit linuxconf by clicking on "quit" and then "Act/Changes" so you
save your changes.

8) Go into all the computers on your LAN and change their netmask to match
what you set for eth1: 192.168.1.25

Assuming your modem is configured properly and you have IP masquerading or
ipchains set up right this should get you going.

>0.0.0.0         192.168.1.254   0.0.0.0         UG        0 0          0
>eth1
>0.0.0.0         192.168.1.254   0.0.0.0         UG        0 0          0
>eth0

You have both modems set to try to access the router.  One should be
facing the LAN, the other the router.  If you set up as I stated above
this should fix your problem.  You should only have one showing as the
Gateway. Here's my netstat -rn table:

$ netstat -rn
Kernel IP routing table
Destination    Gateway   Genmask         Flags  MSS Window  irtt   Iface
10.0.0.2       0.0.0.0   255.255.255.255 UH        0 0         0   eth0
10.0.0.0       0.0.0.0   255.255.255.0   U         0 0         0   eth0
192.168.1.0    0.0.0.0   255.255.255.0   U         0 0         0   eth1
127.0.0.0      0.0.0.0   255.0.0.0       U         0 0         0   lo
0.0.0.0        10.0.0.1  0.0.0.0         UG        0 0         0   eth0

Glen




On Wed, 16 Aug 2000, Stephen E. Hargrove wrote:

>My server has two NICs, eth0 (192.168.1.1) and eth1 (192.168.1.10).
>eth0 connects to my private network and eth1 connects to the external
>DSL modem (Cayman 3220 DSL router).  The router acts as a firewall
>(which I hate but really can't do anything about).  The router is
>defined as 192.168.1.254, and has 4 ethernet connections on the front.
>If I plug directly into the router, I can access http://192.168.1.254
>from my browser and configure it.  However, I can't access it from any
>station on my network (i.e., from 192.168.1.1 or 192.168.1.6, etc.).
>When I attempt, it responds with the following error:
>
>A network error occurred:
>unable to connect to server (TCP Error: No route to host)
>The server may be down or unreachable
>
>I can't ping it or telnet to it, either.  So, I must have something
>wrong in my routing tables, right?  Here's my netstat -rn:
>
>Kernel IP routing table
>Destination     Gateway         Genmask         Flags   MSS Window  irtt
>Iface
>192.168.1.1     0.0.0.0         255.255.255.255 UH        0 0          0
>eth0
>192.168.1.10    0.0.0.0         255.255.255.255 UH        0 0          0
>eth1
>192.168.1.0     0.0.0.0         255.255.255.0   U         0 0          0
>eth0
>192.168.1.0     0.0.0.0         255.255.255.0   U         0 0          0
>eth1
>127.0.0.0       0.0.0.0         255.0.0.0       U         0 0          0
>lo
>0.0.0.0         192.168.1.254   0.0.0.0         UG        0 0          0
>eth1
>0.0.0.0         192.168.1.254   0.0.0.0         UG        0 0          0
>eth0
>
>I'm using IPMasquerade, and as far as that goes, everything seems to be
>working correctly (all PCs can access the 'net, etc.).
>
>Does anyone have any ideas on how I can go about accessing
>192.168.1.254?  I'm stumped.
>--
>Steve
>
>
>
>
>_______________________________________________
>Redhat-list mailing list
>[EMAIL PROTECTED]
>https://listman.redhat.com/mailman/listinfo/redhat-list
>



_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list

Reply via email to