On Fri, Aug 22, 2008 at 12:44 PM, Les Mikesell <lesmikesell@xxxxxxxxx> wrote:
;Are you suggesting the following?
;assume eth1 is a better ISP than eth0
ifdown eth0
ifup eth1
ISP on eth1 goes down
automagically detect down ISP on eth1, so
ifdown eth1
ifup eth0
automagically detect ISP back up on eth1, so
ifdown eth0 again
;That isn't gonna fly.
Looks like nate pointed out the right journal article and looks very promising. Will let you know how it goes.
"Source-based routing capabilities are common on high end networking gear, but they rarely are seen or utilized in server environments. Linux has excellent but poorly understood source-based routing support. The whole universe of advanced Linux routing and traffic shaping is well described at lartc.org."
ip rules and ip route priority are key.
Florin Andrei wrote:Routes only work when you can reach the next hop. That is, if you try to add a route through an interface that is not up, the command will fail and the route will not be added. If you want a route to be added when an interface comes up, there is already a place to do that. However, as others have pointed out you shouldn't expect multiple concurrent default routes to do something useful - but if you have multiple interfaces you can configure them both to add default routes and bring only one up at a time.
ABBAS KHAN wrote:
I'm adding the default gateway to the route through "route add default gw 10.10.10.10 <http://10.10.10.10>" which is also shown in "route -n" but the problem is that as soon as I restart the network through /etc/init.d/network restart; the route sets to default one...!
SO, my question is there any way to save the modified route permanently by hardcoding the changes?
It would be very nice if the init.d script would allow the sysadmin to do something like "service network saveroutes". I always thought that would be a neat feature.
--
Les Mikesell
lesmikesell@xxxxxxxxx
;Are you suggesting the following?
;assume eth1 is a better ISP than eth0
ifdown eth0
ifup eth1
ISP on eth1 goes down
automagically detect down ISP on eth1, so
ifdown eth1
ifup eth0
automagically detect ISP back up on eth1, so
ifdown eth0 again
;That isn't gonna fly.
Looks like nate pointed out the right journal article and looks very promising. Will let you know how it goes.
"Source-based routing capabilities are common on high end networking gear, but they rarely are seen or utilized in server environments. Linux has excellent but poorly understood source-based routing support. The whole universe of advanced Linux routing and traffic shaping is well described at lartc.org."
ip rules and ip route priority are key.
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos
_______________________________________________ CentOS mailing list CentOS@xxxxxxxxxx http://lists.centos.org/mailman/listinfo/centos
