Re: Q: multi-homed server with multiple default routers
From: RRG (rigoberto_at_sunguru.com)
Date: 05/19/03
- Next message: David Combs: "Re: emacs 21.3 wants "libXaw3d.so.5"; got Xaw3d-1.5.tar.gz; NOW WHAT?"
- Previous message: scriptOmatic: "Re: ls -l Invalid argument"
- In reply to: Ryo Furue: "Re: Q: multi-homed server with multiple default routers"
- Next in thread: Darren Dunham: "Re: Q: multi-homed server with multiple default routers"
- Reply: Darren Dunham: "Re: Q: multi-homed server with multiple default routers"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: 19 May 2003 10:40:39 -0700
furufuru@ccsr.u-tokyo.ac.jp (Ryo Furue) wrote in message news:<e10cccdf.0305190524.62b26a1e@posting.google.com>...
> Darren Dunham <ddunham@redwood.taos.com> wrote in message news:<IDuxa.838$vX5.93232372@newssvr13.news.prodigy.com>...
> > Ryo Furue <furufuru@ccsr.u-tokyo.ac.jp> wrote:
> [...]
> > > When the Solaris machine sends a packet whose
> > > source address is "X.Y.Z.22", I want the packet to be
> > > sent to the router "X.Y.Z.1"; when the source address
> > > is "X.Y.Z.188", I want the packet to be sent to
> > > "X.Y.Z.129".
> >
> > This is "source based routing" or "policy routing". Solaris doesn't do
> > that. Instead only the destination address and routing table are used
> > to determine the interface and hardware destination.
> [...snip...]
>
> Thank you for the explanation, which was very clear!
>
> There's one thing I'd like to correct myself: In the first posting
> I said (or at least implied) that
>
> # route add 0.0.0.0 X.Y.Z.1 -ifp hme0
> # route add 0.0.0.0 X.Y.Z.129 -ifp hme1
>
> would enable source based routing. I was wrong. At first it seemed
> working: The machine grabbed X.Y.Z.129 as the router in responding to
> an incoming packet to the hme1 interface. But, then the machine didn't
> use X.Y.Z.1 even when responding to a packet for hme0....
>
> Anyhow, thank you again,
> Ryo
The standard is to define the routers in the /etc/gateways file.
The in.routed process reads the optional /etc/gateways file upon
initialization to add additional static routes. This is another way
to add a permanent (passive) route other than adding a default router.
It is also a method to add one or more permanent routes that are not
default routes. These are the fields in the /etc/gateways:
net dest.net gateway router metric cnt [passive] [active]
For example
net 128.50.3.0 gateway sword-r metric 2 passive
I hope this help you.
RRG - SCSA/SCNA
- Next message: David Combs: "Re: emacs 21.3 wants "libXaw3d.so.5"; got Xaw3d-1.5.tar.gz; NOW WHAT?"
- Previous message: scriptOmatic: "Re: ls -l Invalid argument"
- In reply to: Ryo Furue: "Re: Q: multi-homed server with multiple default routers"
- Next in thread: Darren Dunham: "Re: Q: multi-homed server with multiple default routers"
- Reply: Darren Dunham: "Re: Q: multi-homed server with multiple default routers"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|