Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: Theodor Milkov <zimage@delbg.com>
To: lartc@vger.kernel.org
Subject: [LARTC] Policy routing work in 2.2 but not in 2.4
Date: Fri, 18 Jan 2002 23:43:01 +0000	[thread overview]
Message-ID: <marc-lartc-101139769518368@msgid-missing> (raw)

Hello,

I recently upgraded one of our routers with 2.4.17 Linux kernel and
unfortunately my policy routing that used to work with 2.2.20 kernel
failed. Quick test:

# uname -r
2.2.20

# ip rule ls
0:      from all lookup local
32765:  from all to 1.1.1.1 tos 0x02 lookup 199
32766:  from all lookup main
32767:  from all lookup 253

# ip route ls table 199
1.1.1.1 via 10.0.0.2 dev eth1

# ip route get to 1.1.1.1 tos 0x02
1.1.1.1 tos 0x02 via 10.0.0.2 dev eth1  src 10.0.0.1
       cache  mtu 1500 rtt 375ms

# ip route get to 1.1.1.1 tos 0x08
1.1.1.1 tos 0x08 via 192.168.0.1 dev eth0  src 192.168.0.2
       cache  mtu 1500 rtt 375ms

In this example everything seems ok - 192.168.0.1 is default gw. Lets
see the next example:

# uname -r
2.4.17

# ip ru ls
0:      from all lookup local
32765:  from all to 1.1.1.1 tos 0x02 lookup 199
32766:  from all lookup main
32767:  from all lookup 253

# ip route ls table 199
1.1.1.1 via 10.0.0.2 dev eth2

# ip route get to 1.1.1.1 tos 0x02
RTNETLINK answers: Network is unreachable
# ip route get to 1.1.1.1 tos 0x08
RTNETLINK answers: Network is unreachable

So, in this example the 'ip rule' is ignored and thus lookup to table
199 never happens. Both kernels where compiled with
'CONFIG_IP_ROUTE_TOS=y'. iproute packages are iproute2-ss001007 for
linux-2.2 kernel and iproute2-ss010824 for linux-2.4. What could be wrong?

Best regards,

-- 
       Theodor Milkov           Administrator IP Networks
       Davidov Net              Phone: +359 (2) 730158
       PGP: http://www.zimage.delbg.com/zimage.asc



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

                 reply	other threads:[~2002-01-18 23:43 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=marc-lartc-101139769518368@msgid-missing \
    --to=zimage@delbg.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox