From: Arindam Haldar <arindamhaldar@inbox.lv>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Multi Routing Problem.
Date: Wed, 21 Aug 2002 11:10:31 +0000 [thread overview]
Message-ID: <marc-lartc-102993034208993@msgid-missing> (raw)
In-Reply-To: <marc-lartc-102984498529503@msgid-missing>
hi again, :)
i tried again & now am succesfull.. :) this is my script
#!/bin/sh
ipr="/sbin/ip"
NetExtA="...6.64/26"
IPExtA="....6.106"
GtExtA="....6.70"
NetExtB="...9.0/25"
IPExtB="....9.124"
GtExtB="....9.1"
Netlcl="172.31.13.0/24"
IPlcl="172.31.13.1"
NetgrpA="172.31.13.10/31"
NetgrpB="172.31.13.20/31"
NetgrpC="172.31.13.30/31"
$ipr rule del prio 99 from $NetExtA
$ipr rule del prio 98 from $NetgrpA
$ipr rule del prio 74 from $NetExtB
$ipr rule del prio 73 from $NetgrpB
$ipr rule del prio 49 from $NetgrpC
# $ipr rule del prio 48
echo 100 EXTnA >> /etc/iproute2/rt_tables
echo 75 EXTnB >> /etc/iproute2/rt_tables
echo 50 BALANCE >> /etc/iproute2/rt_tables
$ipr rule add prio 99 from $NetExtA table EXTnA
$ipr rule add prio 98 from $NetgrpA table EXTnA
$ipr rule add prio 74 from $NetExtB table EXTnB
$ipr rule add prio 73 from $NetgrpB table EXTnB
$ipr rule add prio 49 from $NetgrpC table BALANCE
# $ipr rule add prio 48 table BALANCE
$ipr route add default table EXTnB via $GtExtB dev eth1 src $IPExtB
$ipr route add $NetgrpB via $IPlcl dev eth2 table EXTnB
$ipr route add default table EXTnA via $GtExtA dev eth0 src $IPExtA
$ipr route add $NetgrpA via $IPlcl dev eth2 table EXTnB
$ipr route add default table BALANCE nexthop via $GtExtB dev eth1
nexthop via $GtExtA dev eth0
$ipr route add $NetgrpC via $IPlcl dev eth2 table EXTnB
things work fine from the client's end, and follows the
routing/balancing as defined.. but when i use **2 append ** ip route
commands to table BALANCE--viz
ip route append default via $GtExtB dev eth1 ta BALANCE
ip route append default via $GtExtA dev eth0 ta BALANCE
then everything **STOPS**... WHY ????
julian u wrote in ur mail about adding >>>ip rule add prio 5 ta main
& i also saw it in the docs too but i couldnt understand the
importance.. more so coz there was no routing attached to this prio..
will the default route of ta main(32766) be carried to table main (prio
5) ??.. can u please tell me more about it ?...
awaitng a reply
thanking u in advance
A.H
Julian Anastasov wrote:
> Hello,
>
> On Mon, 19 Aug 2002, Arindam Haldar wrote:
>
>
>>& applied julian's patch to kernel 2.4.19 & have gone thru the docs at
>>the site... i have defined basically 3 groups for clients--> cache,
>>cisco, balance.. the name specifies the importance.. this is the details
>>of what i did-->
>
>
> Carefully analyze the docs...
>
>
>>[root@Lr1 root]# ip rule ls
>>0: from all lookup local
>
>
> # direct communications are first priority
> ip rule add prio 5 table main
>
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2002-08-21 11:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-19 8:31 [LARTC] Multi Routing Problem Arindam Haldar
2002-08-20 21:10 ` Julian Anastasov
2002-08-21 11:10 ` Arindam Haldar [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-08-18 16:26 Arindam Haldar
2002-08-18 21:03 ` Arindam Haldar
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=marc-lartc-102993034208993@msgid-missing \
--to=arindamhaldar@inbox.lv \
--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.