All of lore.kernel.org
 help / color / mirror / Atom feed
From: Muhammad Reza <reza@mra.co.id>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Multipath Connection problem on RH-8.0
Date: Thu, 13 May 2004 04:38:08 +0000	[thread overview]
Message-ID: <40A2FBB0.5080504@mra.co.id> (raw)
In-Reply-To: <40A1D154.5080508@mra.co.id>

Julian Anastasov wrote:

>	Hello,
>
>On Wed, 12 May 2004, Muhammad Reza wrote:
>
>  
>
>>default  proto static
>>        nexthop via 172.16.0.1  dev eth0 weight 256 dead onlink pervasive
>>        nexthop via 192.168.0.1  dev eth1 weight 1
>>I search the list about this error, and found that i shall use the
>>upgrade version of iproute2, and i compile that too.
>>but with same config, and new iproute2 i can't connect to internet now.
>>please be advice, what wrong with my config (attach), and what version
>>of linux should work ?
>>    
>>
>
>	Can you check the example 'ip route get' commands and
>"2.4 Keeping them alive" from nano.txt. Make sure after upgrading
>iproute2 that your nexthops are not dead. Also, list you rules
>and routes and make sure they are valid, I see your commands but
>I do not know which of them are accepted from the kernel.
>
>Regards
>
>--
>Julian Anastasov <ja@ssi.bg>
>
>  
>
now i downgrade to rh-7.2 (2.4.20-w/ julian patch)and iproute version 
iproute2-ss010824.
but still cant do multipath routing.
this is my trace with ip route get;
[root@firewall root]# ip route get 202.138.253.17
202.138.253.17 via 172.16.0.1 dev eth0 src 172.16.0.232
cache mtu 1500 advmss 1460
[root@firewall root]# ip route get 202.138.253.17 from 192.168.0.2
202.138.253.17 from 192.168.0.2 via 192.168.0.1 dev eth1
cache mtu 1500 advmss 1460
[root@firewall root]# ip route get 202.138.253.17 from 172.16.0.232
202.138.253.17 from 172.16.0.232 via 172.16.0.1 dev eth0
cache mtu 1500 advmss 1460
[root@firewall root]# ip route list table main
192.168.0.0/30 dev eth1 proto kernel scope link src 192.168.0.2
172.16.0.0/24 dev eth0 scope link
10.10.10.0/24 dev eth2 scope link
127.0.0.0/8 dev lo scope link
[root@firewall root]# ip route list table MRA
default via 172.16.0.1 dev eth0 proto static src 172.16.0.232
prohibit default proto static metric 1
[root@firewall root]# ip route list table DEF
default proto static
nexthop via 172.16.0.1 dev eth0 weight 1
nexthop via 192.168.0.1 dev eth1 weight 1

with this configuration i still couldn connect to internet

how to debug and solve this problem... ?
please be advice..

regards
reza







_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

  parent reply	other threads:[~2004-05-13  4:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-12  7:25 [LARTC] Multipath Connection problem on RH-8.0 Muhammad Reza
2004-05-12 20:31 ` Julian Anastasov
2004-05-13  4:38 ` Muhammad Reza [this message]
2004-05-13  7:23 ` Julian Anastasov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=40A2FBB0.5080504@mra.co.id \
    --to=reza@mra.co.id \
    --cc=lartc@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.