From: Andy Furniss <andy.furniss@dsl.pipex.com>
To: hadi@cyberus.ca
Cc: netdev@oss.sgi.com
Subject: Re: IMQ / new Dummy device post.
Date: Sat, 17 Apr 2004 11:39:19 +0100 [thread overview]
Message-ID: <40810957.6030209@dsl.pipex.com> (raw)
In-Reply-To: <1082145341.1026.125.camel@jzny.localdomain>
jamal wrote:
> On Fri, 2004-04-16 at 15:35, Andy Furniss wrote:
>
>
>>This is what I wanted to know. Is it possible to make an option to get
>>them after NAT in and pre NAT out?
>
>
> No i dont plan to. Why do you want to go that path?
I think it's the only way I can shape/share my ingress traffic between a
process (eg. bittorrent/squid) running on my shaping machine and
traffic that is forwarded to my LAN. I masquerade onto one real dynamic IP.
In the case of pre nat outbound - I know people can mark pre NAT and
shape on that, but it would allow people with big LANs doing NAT to use
WRR/ESFQ on src for egress traffic.
>
>
>>I don't think this applies to my setup Masqerading many local onto one
>>real address.
>
>
> If you have local on eth0(or substitute with whatever device you have
> local on), the example i gave should work fine. You just have to change
> the way you approach the setup. In case i didnt understand you, please
> post the details of your setup.
My setup is very simple - the only reason I use IMQ+NAT patch is because
I want to use my gateway/shaping PC to run bittorrent and I want the LAN
machines to have priority/fair share of incoming traffic. I guess my
setup is not that common - more common are people who run squid on the
same PC they shape/do NAT on.
ppp0 one dynamic real IP -> gateway PC -> eth0 -> LAN 192.168.0.0/24
|
-> local process.
Andy.
next prev parent reply other threads:[~2004-04-17 10:39 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 [this message]
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
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=40810957.6030209@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).