All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kurt Wagner kwagner@cosy.sbg.ac.at
To: lartc@vger.kernel.org
Subject: [LARTC] ip route - TOS argument does not allways work
Date: Thu, 15 Feb 2001 14:40:10 +0000	[thread overview]
Message-ID: <marc-lartc-98373940417021@msgid-missing> (raw)

<PRE>hi all,

I need different routes for packets with different TOS values, and tried
to do this with ip. I noticed that ip does not recognice all possible
values for the TOS byte, even when I enter them in
/etc/iproute/rt_dsfield.


to demonstrate this, I added prohibit rules for different marked packets
and tried if the packets are dropped when I try to &quot;ping -Q tosvalue
&lt;somehost&gt;&quot;:


#: ip route add prohibit default tos 0xb8
#: ip route add prohibit default tos 0x11  
#: ip route add prohibit default tos 0x10 
#: ip route add prohibit default tos 0x02 

#: ip route
&lt;some rules snipped&gt;
prohibit default tos high 
prohibit default tos test 
prohibit default tos lowdelay 
prohibit default tos mincost
default via 192.168.10.1 dev eth0 

#: cat /etc/iproute2/rt_dsfield 
0x11    test
0xb8    high
0xbc    video
0xe0    burstplan
0x10    lowdelay
0x08    throughput
0x04    reliability
0x02    mincost 

so ip look at rt_dsfield and enters the names not the values, that's
fine. but...

#: ping -Q 0xb8 192.168.10.1
PING 192.168.10.1 (192.168.10.1) from 192.168.10.2 : 56(84) bytes of data.
64 bytes from 192.168.10.1: icmp_seq=0 ttl%4 time=1.919 msec

#: ping -Q 0x11 192.168.10.1
connect: Network is unreachable

#: ping -Q 0x10 192.168.10.1
connect: Network is unreachable

#: ping -Q 0x02 192.168.10.1
PING 192.168.10.1 (192.168.10.1) from 192.168.10.2 : 56(84) bytes of data.
64 bytes from 141.201.123.33: icmp_seq=0 ttl%4 time=1.793 msec


so it works for tos=0x10 and 0x11, but not for tos=0xb8 and 0x02.

it is possible to construct more examples which work, or don't work, but I
see no pattern or reason for this strange behavior.



any hints? ideas?


Kurt



</PRE>

                 reply	other threads:[~2001-02-15 14:40 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-98373940417021@msgid-missing \
    --to=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.