From: Andy Furniss <andy.furniss@dsl.pipex.com>
To: Andy Furniss <andy.furniss@dsl.pipex.com>
Cc: hadi@cyberus.ca, netdev@oss.sgi.com
Subject: Re: IMQ / new Dummy device post.
Date: Sun, 18 Apr 2004 21:34:53 +0100 [thread overview]
Message-ID: <4082E66D.2020707@dsl.pipex.com> (raw)
In-Reply-To: <4082AE45.7030101@dsl.pipex.com>
Andy Furniss wrote:
<snip>
>> To accomodate your need for b), the idea would be as follows:
>> packet gets demasquared, mark it with a fwmark
>
>
> I guess you really mean mark then demasquerade.
>
>> based on some recognition
>> you have for bittorent or squid and lastly policy route it to the dummy
>> device based on fwmark (since routing happens last).
>> I will need to modify the dummy to not drop such packets which are
>> fwmarked.
>
>
> OK I can see this as a possibility - assuming I can mark. Maybe conmark
> will be OK with connbytes sometime. I don't really know how to use it,
> but if it is possible to mark egress connections in output and have
> connmark match their incoming packets that would be a solution. I
> haven't got a clue if connmark can do this, though, just speculating.
Hmm second thoughts - if I can route packets to dummy after demasquerade
then I don't need to mark - I can use u32 as I do now to seperate per
IP. Am I missing something here?
>
> Does anyone else know, and why it's not compatable with connbytes?
>
> Andy.
>
>> cheers,
>> jamal
>>
>>
>>
>
>
>
>
next prev parent reply other threads:[~2004-04-18 20:34 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-15 9:42 IMQ / new Dummy device post Andy Furniss
2004-04-15 12:15 ` jamal
2004-04-15 19:35 ` Andy Furniss
2004-04-16 3:52 ` jamal
2004-04-16 19:35 ` Andy Furniss
[not found] ` <1082145341.1026.125.camel@jzny.localdomain>
2004-04-17 10:39 ` Andy Furniss
2004-04-17 12:09 ` jamal
2004-04-17 21:56 ` Andy Furniss
2004-04-18 14:28 ` jamal
2004-04-18 16:35 ` Andy Furniss
2004-04-18 20:34 ` Andy Furniss [this message]
2004-04-18 21:07 ` jamal
2004-04-18 21:31 ` Andy Furniss
2004-04-18 21:45 ` Andy Furniss
2004-04-18 20:53 ` jamal
2004-04-18 21:23 ` Martin Josefsson
2004-04-18 21:58 ` Andy Furniss
2004-04-19 8:14 ` Martin Josefsson
2004-04-19 12:33 ` syrius.ml
-- strict thread matches above, loose matches on Subject: below --
2004-04-19 14:22 syrius.ml
2004-04-20 2:15 ` jamal
2004-04-21 1:43 ` syrius.ml
2004-04-21 12:49 ` syrius.ml
2004-04-21 20:19 ` syrius.ml
2004-04-22 13:16 ` jamal
2004-04-22 17:43 ` syrius.ml
2004-04-23 11:29 ` jamal
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=4082E66D.2020707@dsl.pipex.com \
--to=andy.furniss@dsl.pipex.com \
--cc=hadi@cyberus.ca \
--cc=netdev@oss.sgi.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;
as well as URLs for NNTP newsgroup(s).