Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: "Török Edwin" <edwin+ml-cerowrt@etorok.net>
To: Dave Taht <dave.taht@gmail.com>
Cc: "cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] cerowrt-3.10.34-4 dev build released
Date: Sun, 06 Apr 2014 00:25:39 +0300	[thread overview]
Message-ID: <534074D3.4050608@etorok.net> (raw)
In-Reply-To: <CAA93jw7r4Ru6KXJnVm7XO+dWHyS7o--8bY+okGSw+rGwEGv5ew@mail.gmail.com>

On 04/05/2014 06:53 PM, Dave Taht wrote:
> On Sat, Apr 5, 2014 at 1:34 AM, Török Edwin <edwin+ml-cerowrt@etorok.net> wrote:
>> I hacked the script to set the interface name for iptables to pppoe-ge00 (not for uci, cause uci
>> doesn't have an enabled=1 for pppoe):
>>                 setup_ipset
>> +               interface=pppoe-ge00
>>                 setup_iptables "$interface"
>>
>> Any idea how to fix this properly without hardcoding the interface name?
> 
> I_have_no_spacebar_this_morning_(too_damp).
> 
> One_thought_had_been_to_hook_it_into_the_wan_firewall_chains.
> 
> another_would_be_to_more_deeply_inspect_the_interface_definition
> and_"do_the_right_thing"_against_various_protos.
> 

Does this affect sqm-scripts too?
It only sets QoS classification on ge00, not pppoe-ge00. By the time the packets reach ge00, do they still have the QoS bits set?

Best regards,
--Edwin

  reply	other threads:[~2014-04-05 21:25 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-03  1:17 Dave Taht
2014-04-03  1:48 ` Stephen Hemminger
2014-04-03  1:58   ` Dave Taht
2014-04-03  2:43   ` Dave Taht
2014-04-03 10:09     ` David Personette
2014-04-03 15:17   ` Jim Gettys
2014-04-03 18:20 ` Neil Shepperd
2014-04-03 22:36   ` Dave Taht
2014-04-03 22:51     ` Maxim Kharlamov
2014-04-03 22:54       ` Dave Taht
2014-04-03 22:56       ` Aaron Wood
2014-04-03 22:57         ` Aaron Wood
2014-04-03 22:58           ` Dave Taht
2014-04-03 23:01             ` Maxim Kharlamov
2014-04-04  1:26               ` David Personette
2014-04-04  7:04             ` Aaron Wood
2014-04-04  6:57     ` Toke Høiland-Jørgensen
2014-04-05 12:49     ` Neil Shepperd
2014-04-05 16:02       ` Dave Taht
2014-04-05 16:15         ` Dave Taht
2014-04-05  8:34 ` Török Edwin
2014-04-05 15:53   ` Dave Taht
2014-04-05 21:25     ` Török Edwin [this message]
2014-04-07 14:45   ` Toke Høiland-Jørgensen
2014-04-07 15:27     ` Török Edwin
2014-04-07 15:31       ` Toke Høiland-Jørgensen
2014-04-07 17:58       ` Dave Taht
2014-04-07 18:51         ` Török Edwin
2014-04-05 19:11 ` Jim Reisert AD1C
2014-04-05 19:26   ` Dave Taht
2014-04-06  0:15     ` Jim Reisert AD1C
2014-04-06 10:23       ` Robert Bradley

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

  List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=534074D3.4050608@etorok.net \
    --to=edwin+ml-cerowrt@etorok.net \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=dave.taht@gmail.com \
    /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