I''m sure that I had found (and printed out ...) a really good tutorial that explain how to use Julian Anastasov''s routing patch, but I can''t seem to find it now. Any pointers? -- ****************************************************************** Glen W. Mabey Glen.Mabey@usu.edu http://mabeys.homelinux.com/glen/ ****************************************************************** _______________________________________________ LARTC mailing list / LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
Hello, On Wed, 7 Jul 2004, Glen Mabey wrote:> I''m sure that I had found (and printed out ...) a really good tutorial > that explain how to use Julian Anastasov''s routing patch, but I can''t > seem to find it now. > > Any pointers?http://www.ssi.bg/~ja/ Regards -- Julian Anastasov <ja@ssi.bg> _______________________________________________ LARTC mailing list / LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
Glen Mabey wrote:> I''m sure that I had found (and printed out ...) a really good tutorial > that explain how to use Julian Anastasov''s routing patch, but I can''t > seem to find it now. > > Any pointers? >http://h2o.sky.lt/stuff/docs/nano.txt always keep a copy :P
Dear All,
I follow this this tutorial, but I''t seem failed to detect dead gateway
from both router side and client side.
If one link is down, I except that routing will flush automatically
after 60 second. But this not happened. Keeping them alive with pinging
trick don''t make any changes.
Maybe something I miss configured, here my configuration on router
#/sbin/ip ro sh table main
xxx.138.255.168/30 dev eth2 proto kernel scope link src
xxx.138.255.170
xxx.138.254.0/26 dev eth1 proto kernel scope link src xxx.138.254.2
172.16.0.0/24 dev eth0 scope link
172.16.0.0/16 via 172.16.0.1 dev eth0
127.0.0.0/8 dev lo scope link
# /sbin/ip ro ls table 201
default via 202.138.254.1 dev eth1 proto static src 202.138.254.2
prohibit default proto static metric 1
#/sbin/ip ro ls table 202
default via 202.138.255.169 dev eth2 proto static src 202.138.255.170
prohibit default proto static metric 1
#/sbin/ip ro ls table 222
default proto static
nexthop via 202.138.255.169 dev eth2 weight 2
nexthop via 202.138.254.1 dev eth1 weight 1
Established connection tracking is enable in iptables rules,
I use 2.4.26 kernel, please enlight and help me.
Regards,
Reza
-----Original Message-----
From: Julian Anastasov [mailto:ja@ssi.bg]
Sent: Thursday, July 08, 2004 2:04 PM
To: Glen Mabey
Cc: LARTC Mailing List
Subject: Re: [LARTC] tutorial for Julian Anastasov''s patches
Hello,
On Wed, 7 Jul 2004, Glen Mabey wrote:
> I''m sure that I had found (and printed out ...) a really good
tutorial
> that explain how to use Julian Anastasov''s routing patch, but I
can''t
> seem to find it now.
>
> Any pointers?
http://www.ssi.bg/~ja/
Regards
--
Julian Anastasov <ja@ssi.bg>
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
Hello, On Fri, 9 Jul 2004, Mohammad Reza wrote:> If one link is down, I except that routing will flush automatically > after 60 second. But this not happened. Keeping them alive with pinging > trick don''t make any changes.The ''ping'' trick works for gateways which become unreachable in the ARP cache when their link is down (which does not happen in all setups) or when the devices are marked down. In all other cases you have to recreate your multipath routes with script on fatal events such as "link" failed, indirect gateways are failed, device is registered/unregisterd, etc.> Regards, > RezaRegards -- Julian Anastasov <ja@ssi.bg> _______________________________________________ LARTC mailing list / LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/