From: Andy Furniss <adf.lists@gmail.com>
To: lartc@vger.kernel.org
Subject: Re: reroute icmp traffic from one interface to another
Date: Tue, 31 May 2016 15:40:25 +0000 [thread overview]
Message-ID: <574DB069.5060803@gmail.com> (raw)
In-Reply-To: <20160531171329.Horde.SLfG6i6j_hmWsfb5FjpBZwP@ermis.noc.duth.gr>
Ηλια Χατζηστυλη wrote:
>
> Hello, I have an openwrt firmware installed in my router and I want
> to configure a Home and a Guest interface. So I have two internal
> interfaces(home,guest) and the external(eth1). First I have to send
> all traffic from the two internal interfaces(wlan0,wlan0-1) to
> external(eth1). With my project I have to measure latency so I use
> nping. However when I use the command "sudo nping -c 3200
> --data-length 1460 x.x.x.x" with network seted to upload bandiwidth
> 2Mbps and with data length 1460 B (1460*8\x11740) we expect minimum
> delay 11740/2000000=5.8ms . Nonetheless, the avg ping time is about
> 0.8-3 ms which means that my iptables commands doesn't work properly
> for the ping traffic (icmp type). Do you know how I can route this
> traffic with the tcp one? I'm pretty sure that icmp traffic is
> enqueued because when the home user is uploading a file nping command
> takes out the proper delay.
Easier to look at iptables counters to see what's hitting rules.
You don't say how you limit to 2mbit. Linux QOS doesn't emulate bitrate
latency so your test is not valid for seeing where packets go.
netem rate option does try to limit according to packet size subject to
timer granularity (see man tc-netem).
FWIW your calculation for rth should probably be more like (1460+8+20+14)*8.
next prev parent reply other threads:[~2016-05-31 15:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-31 14:13 reroute icmp traffic from one interface to another Ηλια Χατζηστυλη
2016-05-31 15:40 ` Andy Furniss [this message]
2016-05-31 23:40 ` Ηλια Χατζηστυλη
2016-06-01 16:45 ` Andy Furniss
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=574DB069.5060803@gmail.com \
--to=adf.lists@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox