Routing (Router) Nightmare

Routing (Router) Nightmare

Post by Matt Seiber » Tue, 10 Nov 1998 04:00:00



After almost a year of faithful service, my router decided to go belly up
early in the AM of Saturday, this weekend.  I am in the painful process of
rebuilding the system (the boot drive went south on me) and realized that
when my wife and I packed for out future move, I packed all my
configuration guides up (darn the luck!)

I've got this set up:

RH4.2
eth0    15,310
eth1    9,300

Here is what I'm trying to get back to:

eth0    192.168.100.101 netmask 255.255.255.0
eth0:0  146.84.xxx.xxx  netmask 255.255.255.0
eth1    10.1.255.1      netmask 255.255.255.0

and routes that work this way:

the Local net (192.168) default route is to 192.168.100.101.  The router
then determines where the packet is destined.
If the packet is to 192.168.100.xxx, go out eth0
if the packet is for 146.84.xxx.xxx, go out eht0:0
if the packet is for anyone else, shoot it to 10.1.255.1 (my P-50)

Can someone (anyone) cobble together the description of what I need in what
files to do this?  I know it means modifying files in
/etc/sysconfig/network-scripts and maybe /etc/rc.d/init.d/network, but I've
done so much work on NT and OS/2 recently that I can't remember the syntax.


Thanx!

Matt

 
 
 

Routing (Router) Nightmare

Post by Tobias Reckhard (jest » Wed, 11 Nov 1998 04:00:00




Quote:>I've got this set up:

>RH4.2
>eth0        15,310
>eth1        9,300

What are those numbers supposed to mean (15310 and 9300)?

Quote:>Here is what I'm trying to get back to:

>eth0        192.168.100.101 netmask 255.255.255.0
>eth0:0      146.84.xxx.xxx  netmask 255.255.255.0
>eth1        10.1.255.1      netmask 255.255.255.0

>and routes that work this way:

>the Local net (192.168) default route is to 192.168.100.101.  The router
>then determines where the packet is destined.
>If the packet is to 192.168.100.xxx, go out eth0

route add -net 192.168.100.0 eth0

Quote:>if the packet is for 146.84.xxx.xxx, go out eht0:0

route add -net 146.84.0.0 netmask 255.255.0.0 eth0:0

Quote:>if the packet is for anyone else, shoot it to 10.1.255.1 (my P-50)

route add default gw 10.1.255.1 eth1

Quote:>Can someone (anyone) cobble together the description of what I need in what
>files to do this?  I know it means modifying files in
>/etc/sysconfig/network-scripts and maybe /etc/rc.d/init.d/network, but I've
>done so much work on NT and OS/2 recently that I can't remember the syntax.

I don't know where these commands should go on a RedHat system, but
you can just grep for the route command, I guess.

HTH
Tobias

 
 
 

1. tcp/ip routing question - setting the default route beyond the local router?

Hi,

A friend has the enviable problem that routing to the two
ISP's is not working as they want them to.  They have one
cisco router that always uses one ISP, and not the other.
The goal is to have the DMZ/internet servers use one ISP,
and the other internal networks and desktops use the other.

It's been suggested that a static route to the desired ISP
be setup on the internet server, and it's default route
pointed there.  Will that work?  

What will?

Please send replies to email, since I don't often get to news.
If there is interest, a summary of the solution will be posted.

Thanks,

Pamela Pledger

--

---------------------------------------------

Taos Mountain           http://www.taos.com
---------------------------------------------

2. migrate data from one hard disk to another

3. Nightmare with the Hewlett Packard router

4. Columbia Appletalk Package: CAP

5. Was -- ("compiling kde2.2.1 == nightmare, redhat and kde updating == nightmare")

6. HELP: fsck.minix error

7. compiling kde2.2.1 == nightmare, redhat and kde updating == nightmare

8. Data-corrupting ext3 bug in 2.4.20

9. 2 NICs and routes/gateways - the usual nightmare (or not?)

10. 2 NICs, IP routing and other nightmares

11. routing table nightmare blues

12. A "No route to host" nightmare.

13. need route map for LAN behind gate/router/nameserver