[CentOS] Re: Network routes

Thu Jan 31 03:28:55 UTC 2008
Jason Pyeron <jpyeron at pdinc.us>

 

> -----Original Message-----
> From: centos-bounces at centos.org 
> [mailto:centos-bounces at centos.org] On Behalf Of Scott Silva
> Sent: Wednesday, January 30, 2008 12:30
> To: centos at centos.org
> Subject: [CentOS] Re: Network routes
> 
> on 1/29/2008 5:24 PM Jason Pyeron spake the following:
> >  
> > 
> >> -----Original Message-----
> >> From: centos-bounces at centos.org 
> >> [mailto:centos-bounces at centos.org] On Behalf Of Les Mikesell
> >> Sent: Tuesday, January 29, 2008 18:25
> >> To: CentOS mailing list
> >> Subject: Re: [CentOS] Network routes
> >>
> >>
> >> You probably want to remove the default route through 
> NE.TW.KB.1 and add 
> >> routes for the specific networks that you can reach though 
> >> it.  Normally  routing is done toward a destination network/address
> > without 
> >> regard to the route of a packet you might be replying to.  
> As for an 
> >> 'outage', how do you define/detect the outage?  Normally 
> if you want
> > routes to be 
> >> determined dynamically you would set up a routing protocol 
> with the 
> >> next-hop routers - or for simple failover the alternative gateway 
> >> routers might be configured via hsrp or vrrp to have a floating IP 
> >> address that the rest of the LAN uses as the default 
> gateway address.
> >>
> > 
> > Droping the failover requirements, pings still do not 
> respond off the local
> > subnet.
> > 
> > [root at host20 ~]# route -n
> > Kernel IP routing table
> > Destination     Gateway         Genmask         Flags 
> Metric Ref    Use
> > Iface
> > NET.WOR.KA.0    0.0.0.0         255.255.255.0   U     0     
>  0        0 eth1
> > 192.168.1.0     0.0.0.0         255.255.255.0   U     0     
>  0        0 eth0
> > NE.TW.RKB.0     0.0.0.0         255.255.255.0   U     0     
>  0        0 eth0
> > 169.254.0.0     0.0.0.0         255.255.0.0     U     0     
>  0        0 eth1
> > 0.0.0.0         NET.WOR.KA.1    0.0.0.0         UG    0     
>  0        0 eth1
> 
> But none of the destinations have a gateway address.
> So all of the traffic is trying to go from every interface to 
> the default gateway.
> Do both interfaces go out the same router?
> As an example in my system, I have a local interface and a 
> wan interface. Only 
> the wan interface needs to use the default route, as it is 
> the only interface 
> that talks to the outside world. But my internal interface 
> has routes to other 
> private networks through IPSec tunnels on other routers.
> 
> So the internal interface has multiple routes and each has a 
> gateway address 
> of the router that handles that route.
> 
> Are your network-a and network-b addresses actually public 
> addresses or 
> rfc-1918 private addresses?
> 


Public.

BTW thank you all for the help so far.

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
-                                                               -
- Jason Pyeron                      PD Inc. http://www.pdinc.us -
- Sr. Consultant                    10 West 24th Street #100    -
- +1 (443) 269-1555 x333            Baltimore, Maryland 21218   -
-                                                               -
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

This message is for the designated recipient only and may contain
privileged, proprietary, or otherwise private information. If you
have received it in error, purge the message from your system and
notify the sender immediately.  Any other use of the email by you
is prohibited.