From: "Jörg Harmuth" <harmuth@mnemon.de>
To: netfilter@lists.netfilter.org
Subject: Re: TOS problem
Date: Mon, 25 Jul 2005 16:25:40 +0200 [thread overview]
Message-ID: <42E4F664.70801@mnemon.de> (raw)
In-Reply-To: <200507251448.41773.marcin.giedz@eulerhermes.pl>
Marcin Giedz schrieb:
> Hello
>
> A few days ago I wrote post about "Ip:Port REDIRECTION problem". Since that
> time I have searched once again iptables HOW-TOs and find that one of the
> solutions for my problem is changing TOS to other value. This is done by
> simple rule:
> iptables -t mangle -A PREROUTING -p tcp --dport 4000 -j TOS --set-tos 0x10
> Next I redirect port 4000 from this router to another machine:
> iptables -t nat -A PREROUTING -p tcp --dport 4000 -j DNAT 192.168.49.60:80
>
> This works OK on router when this rule is being ran but when I dump (tcpdump)
> packtes on 192.168.49.60, "ToS" value is changed to 0x0. No any rules are
> being set on 192.168.49.60 - simple machine. Why "ToS" is changing? What do I
> wrong?
Your providing too little information, so nobody can help you - even if
he/she desired to do so.
Hmm, iptables isn't known for unreliability. Did you tcpdump on the
routers outgoing interface ? What about TOS there ?
I read your previous posting again, and your problem seems to be routing
or iptables (not really sure). Why do you think that setting TOS to
"Minimize-Delay" could help to solve your problems ?
Have a nice time,
Joerg
next prev parent reply other threads:[~2005-07-25 14:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-25 12:48 TOS problem Marcin Giedz
2005-07-25 14:25 ` Jörg Harmuth [this message]
2005-07-26 10:58 ` Marcin Giedz
2005-07-26 12:49 ` Jörg Harmuth
2005-07-26 15:23 ` Marcin Giedz
-- strict thread matches above, loose matches on Subject: below --
2003-03-05 12:56 nedco
2003-03-05 13:55 ` Maciej Soltysiak
2003-03-05 20:05 ` Nedko Nedev
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=42E4F664.70801@mnemon.de \
--to=harmuth@mnemon.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox