linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bastian Bittorf <bittorf@bluebottle.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Bastian Bittorf <bittorf@bluebottle.com>,
	Pavel Machek <pavel@ucw.cz>,
	jirislaby@gmail.com, mickflemm@gmail.com,
	mcgrof@do-not-panic.com, linux-wireless@vger.kernel.org,
	kvalo@codeaurora.org
Subject: Re: Low latency communication over wifi
Date: Mon, 28 Sep 2015 14:52:38 +0200	[thread overview]
Message-ID: <20150928125238.GJ22537@medion.lan> (raw)
In-Reply-To: <1443443851.2401.6.camel@sipsolutions.net>

* Johannes Berg <johannes@sipsolutions.net> [28.09.2015 14:38]:
> Depends what you're measuring, but ping should apply the same DSCP tag
> on the response I believe.

your are right, I did not know this till yet 8-)
(i applied 0xb8 with 'ping -c1 -Q' just for testing)

14:49:52.491925 IP (tos 0xb8, ttl 64, id 51117, offset 0, flags [+], proto ICMP (1), 
	length 1500) 192.168.2.1 > 192.168.2.103: ICMP echo reply, id 14925, seq 1, length 1480
14:49:52.491993 IP (tos 0xb8, ttl 64, id 51117, offset 1480, flags [none], proto ICMP (1),
	length 48) 192.168.2.1 > 192.168.2.103: icmp

bye, bastian

  reply	other threads:[~2015-09-28 12:55 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-23 11:03 Low latency communication over wifi Pavel Machek
2015-09-23 11:21 ` Johannes Berg
2015-09-26 10:24   ` Pavel Machek
2015-09-28  7:41     ` Johannes Berg
2015-09-28 12:15       ` Bastian Bittorf
2015-09-28 12:37         ` Johannes Berg
2015-09-28 12:52           ` Bastian Bittorf [this message]
2015-09-30 17:24       ` Pavel Machek
2015-09-30 17:33         ` Bastian Bittorf
2015-09-30 18:28         ` Johannes Berg
2015-09-23 11:27 ` ath5k filling logs (was Re: Low latency communication over wifi) Pavel Machek
2015-09-23 11:42 ` Low latency communication over wifi Bastian Bittorf

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=20150928125238.GJ22537@medion.lan \
    --to=bittorf@bluebottle.com \
    --cc=jirislaby@gmail.com \
    --cc=johannes@sipsolutions.net \
    --cc=kvalo@codeaurora.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mcgrof@do-not-panic.com \
    --cc=mickflemm@gmail.com \
    --cc=pavel@ucw.cz \
    /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;
as well as URLs for NNTP newsgroup(s).