From: Shantanu Kumar <shantanu.iitg@gmail.com>
To: lartc@vger.kernel.org
Subject: [LARTC] Re: iproute2 rules not being followed !!!!!!!
Date: Sun, 17 Jul 2005 17:23:37 +0000 [thread overview]
Message-ID: <70198d7c0507171023681c09b9@mail.gmail.com> (raw)
Hi...
I m really very sorry...
actually I did a very stupid mistake...
in adding rules I added using "from" instead of "to" .... :)
I m really sorry for wasting all the time..
REgards
Shantanu
On 7/17/05, Shantanu Kumar <shantanu.iitg@gmail.com> wrote:
> Hi...
>
> I have installed ip route 2 package on Linux kernel 2.4.25
>
> I am using 2 tables:
>
> ###################################
>
> ebox:100.254~# ip route list table ALTER
> default via 192.168.100.253 dev br0
>
> ebox:100.254~# ip route list table main
> 10.0.0.254 dev ppp0 proto kernel scope link src 10.0.0.1
> 192.168.100.0/24 dev br0 proto kernel scope link src 192.168.100.254
> 192.168.100.0/24 dev eth1 proto kernel scope link src 192.168.100.233
> 192.168.200.0/24 dev eth2 proto kernel scope link src 192.168.200.254
> 127.0.0.0/8 dev lo scope link
> default via 10.0.0.254 dev ppp0
>
>
>
> #####################################
>
>
> Now I set up the rules :
>
> #####################################
>
> ebox:100.254~# ip rule list
> 0: from all lookup local
> 7: from 216.239.59.147 lookup main
> 8: from 202.141.80.6 lookup ALTER
> 32739: from 202.141.80.6 lookup ALTER
> 32740: from 66.102.11.99 lookup ALTER
> 32741: from 66.102.11.104 lookup main
> 32742: from 64.73.37.225 lookup main
> 32743: from 216.239.59.103 lookup main
> 32744: from 210.43.44.8 lookup main
> 32745: from 64.233.183.19 lookup main
> 32746: from 64.233.183.83 lookup ALTER
> 32747: from 64.233.183.106 lookup ALTER
> 32748: from 210.157.158.37 lookup ALTER
> 32749: from 66.249.87.99 lookup main
> 32752: from 213.244.168.210 lookup main
> 32753: from 66.197.129.37 lookup ALTER
> 32754: from 82.102.4.72 lookup ALTER
> 32755: from 216.73.82.14 lookup ALTER
> 32756: from 216.73.82.70 lookup ALTER
> 32757: from 216.74.132.11 lookup main
> 32758: from 216.109.117.205 lookup ALTER
> 32759: from 202.138.124.172 lookup main
> 32760: from 216.109.127.16 lookup main
> 32761: from 209.244.156.19 lookup ALTER
> 32762: from 68.142.228.136 lookup ALTER
> 32763: from 82.102.4.57 lookup ALTER
> 32765: from 216.109.118.65 lookup main
> 32766: from all lookup main
> 32767: from all lookup default
>
>
> #####################################
>
>
> But when I try to trace the route of a packet with destination address
> such that according to ip rule table ALTER should be considered ...
> its not following the rule... its always following table Main...
>
> #####################################
>
> ebox:100.254~# tcptraceroute -n 202.141.80.6
> Selected device ppp0, address 10.0.0.1, port 40113 for outgoing packets
> Tracing the path to 202.141.80.6 on TCP port 80 (http), 30 hops max
> 1 10.0.0.254 0.333 ms 0.212 ms 0.210 ms
> 2 202.141.80.6 [open] 0.589 ms 0.591 ms 0.588 ms
>
>
> ######################################
>
>
>
> I would appreciate if I can get any help on why this is not working .!!!!
>
> Thanks.
>
> Regards
> Shantanu
>
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
reply other threads:[~2005-07-17 17:23 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=70198d7c0507171023681c09b9@mail.gmail.com \
--to=shantanu.iitg@gmail.com \
--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.