[LARTC] Multipath Connection problem on RH-8.0

[LARTC] Multipath Connection problem on RH-8.0

[Muhammad Reza]

[-- Attachment #1: Type: text/plain, Size: 922 bytes --]

Dear List.

I try to build multipath connection w/ load balance to internet with two 
different gateway;
My system is RH-8.0 with  iproute-2.4.7-7.90.1.rpm and Kernel-2.4.26 
(patching with Julian A. patch),and follow guide from  
http://www.linuxvirtualserver.org/~julian/nano.txt,
The problem is;
when i try to connect to Internet form gateway machine it;s success , 
but  only one interface is active, no load balancing at all ,
This is my default table
#ip r ls table DEF
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 ?

regrads



[-- Attachment #2: script --]
[-- Type: text/plain, Size: 921 bytes --]

ip link set lo up
ip addr add 127.0.0.1/8 brd + dev lo
ip link set eth2 up
ip addr add 10.10.10.1/24 brd + dev eth2
ip rule add prio 50 table main
ip route del default table main
ip link set dev eth0
ip addr flush dev eth0
ip addr add 172.16.0.232/24 brd 172.16.0.255 dev eth0
ip link set dev eth1 up
ip addr flush dev eth1
ip addr add 192.168.0.2/30 brd 192.168.0.3 dev eth1

ip rule add prio 100 from 172.16.0.0/24 table MRA
ip route add default via 172.16.0.1 dev eth0 src 172.16.0.232 proto static table MRA
ip route append prohibit default table MRA metric 1 proto static
ip rule add prio 200 from 192.168.0.2/30 table ADSL
ip route add default via 192.168.0.1 dev eth1 src 192.168.0.2 proto static table ADSL
ip route append prohibit default table ADSL metric 1 proto static
ip rule add prio 222 table DEF
ip route add default table DEF proto static nexthop via 172.16.0.1 dev eth0 nexthop via 192.168.0.1 dev eth1

Re: [LARTC] Multipath Connection problem on RH-8.0

[Julian Anastasov]

	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>
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

Re: [LARTC] Multipath Connection problem on RH-8.0

[Muhammad Reza]

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/

Re: [LARTC] Multipath Connection problem on RH-8.0

[Julian Anastasov]

	Hello,

	To all: do you have some working script(s) that we can
recommend for setups with 2 or 3 uplinks in multipath route? Then we
can link them to the web page as reference.

On Thu, 13 May 2004, Muhammad Reza wrote:

> now i downgrade to rh-7.2 (2.4.20-w/ julian patch)and iproute version
> iproute2-ss010824.
> but still cant do multipath routing.

	Then can you explain what you learned from "2.4 Keeping them alive"
and what you have to keep the state for each GW from the multipath route
valid?

> 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

	This is strange:

> 172.16.0.0/24 dev eth0 scope link
> 10.10.10.0/24 dev eth2 scope link

	It means your settings are not created from script.
Also, the script does not bring dev eth0 up, there is a missing
"up".

> 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

	What do you have in table ADSL?

	Can you provide output from:

ip addr
ip rule
ip route list table all

> [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

	From where? What shows tcpdump -ln ... ?

> regards
> reza

Regards

--
Julian Anastasov <ja@ssi.bg>
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/