All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Rasmus Aveskogh" <rasmus.aveskogh@utfors.se>
To: netfilter@lists.netfilter.org
Cc: erland.almstrom@utfors.se
Subject: Problems with arbitrary TOS-field settings.
Date: Thu, 19 Dec 2002 18:15:27 +0100	[thread overview]
Message-ID: <000801c2a782$3a8c8570$a10214ac@SE.INTRA> (raw)

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


Hi.

I'm having some trouble setting the TOS-field in the IP header _to an arbitrary value_
using iptables.
To manage to do this I first patched iptables (1.2.5) and my kernel (2.4.18-3) with 
the patches for FTOS. I recompiled and reinstalled but ended up with:

# iptables -t mangle -A OUTPUT -j FTOS --set-ftos 128
iptables: No chain/target/match by that name

"Ok? Well I might as well upgrade to latest iptables and latest kernel-patches"

Though and done, iptables 1.2.7a installed and all the "patch-o-matic"-patches
installed. According to the documentation the TOS/FTOS-features was now obsolete
in favor of the DSCP option. So I tried again:

# iptables -t mangle -A OUTPUT -j DSCP --set-dscp 128
iptables: No chain/target/match by that name

Well, it says somewhere that only values up to 0x4f was supported
by DSCP, but a lower values doesn't affect the error.

FTOS still seems to be part of the cose though, but same error occurs.

What can I do to fix this? And even if DSCP works, how can I set the 8 IP-header
TOS-bits to a value between 0x00 and 0xff?

Thanks in advance
Rasmus Aveskogh - Utfors AB

[-- Attachment #2: Type: text/html, Size: 2285 bytes --]

             reply	other threads:[~2002-12-19 17:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-19 17:15 Rasmus Aveskogh [this message]
2002-12-24 18:13 ` Problems with arbitrary TOS-field settings Arnt Karlsen

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='000801c2a782$3a8c8570$a10214ac@SE.INTRA' \
    --to=rasmus.aveskogh@utfors.se \
    --cc=erland.almstrom@utfors.se \
    --cc=netfilter@lists.netfilter.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.