Historic archive of defunct list cerowrt-commits@lists.bufferbloat.net
 help / color / mirror / Atom feed
From: GitHub <noreply@github.com>
To: cerowrt-commits@lists.bufferbloat.net
Subject: [dtaht/ceropackages-3.10] 3eecc0: Complete the egress classification for "pass-throu...
Date: Wed, 15 Oct 2014 01:33:27 -0700	[thread overview]
Message-ID: <543e31576ced_58843fbbcbf8f2c03167b@hookshot-fe2-cp1-prd.iad.github.net.mail> (raw)

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

  Branch: refs/heads/master
  Home:   https://github.com/dtaht/ceropackages-3.10
  Commit: 3eecc0a6f6d7d61d7ad2001cd3927a893ca1baa9
      https://github.com/dtaht/ceropackages-3.10/commit/3eecc0a6f6d7d61d7ad2001cd3927a893ca1baa9
  Author: Sebastian Moeller <moeller0@gmx.de>
  Date:   2014-10-14 (Tue, 14 Oct 2014)

  Changed paths:
    M net/sqm-scripts/files/usr/lib/sqm/simple_pppoe.qos

  Log Message:
  -----------
  Complete the egress classification for "pass-through" PPPoE packets

Implement the egress classification for IPv4 and IPv6 as a series of
tc u32 filters that specifically adress the relevant header bytes by
offset. This most probably wil only work with exactly the encapsulation
I tested with (PPPoE without VLAN), all offsets were confirmed with
loking at captured packets from the router:
tcpdump -s 200 -i ge00 -w ge00.cap
Here cerowrt was accessing the wan vie a PPPoE client using ge00 as
interface to the DSL-modem. This needs more testers.



                 reply	other threads:[~2014-10-15  8:33 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=543e31576ced_58843fbbcbf8f2c03167b@hookshot-fe2-cp1-prd.iad.github.net.mail \
    --to=noreply@github.com \
    --cc=cerowrt-commits@lists.bufferbloat.net \
    /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