At 03:27 PM 17/08/2000, you wrote:
>Hello Steve,
>
>This won't work.
>
>       router
>   192.168.1.254
>         |
>eth1: 192.168.1.10
>    linux server
>eth0: 192.168.1.1
>         |
>workstations: 192.168.1.x
>
>Different physical network interfaces on your linux server should
>not be on the same network addressing scheme (192.168.1.x/24).
>
>Use something like 192.168.2.x in the eth0 side of your network.

Else subnet the address range.


         router
         192.168.1.254  (Mask 255.255.255.128) \
           |                                    \ 1 network of 128 IP's
eth1:   192.168.1.129  (Mask 255.255.255.128)  /
         Linux Server
eth0:   192.168.1.1     (Mask 255.255.255.128)
           |
         Wkstns: 192.168.1.2 -> 192.168.1.126  (Mask 255.255.255.128)


Should work fine too.

Either way, you need to alter one address of the NIC's..

Darryl




>         Mike
>
>On Wed, Aug 16, 2000 at 02:51:24PM -0500, 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
>
>--
>  .--.  Michael J. Maravillo                   office://+63.2.894.3592/
>( () ) Q Linux Solutions, Inc.              mobile://+63.917.490.9390/
>  `--\\ A Philippine Open Source Solutions Co.  http://www.q-linux.com/
>
>
>
>_______________________________________________
>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