From: Andy Furniss <andy.furniss@dsl.pipex.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] ESFQ question
Date: Sun, 29 Feb 2004 10:14:51 +0000 [thread overview]
Message-ID: <4041BB9B.7030608@dsl.pipex.com> (raw)
In-Reply-To: <40314FDA.10508@skyraven.pcnet.ro>
Mihai Tanasescu wrote:
> Hello,
>
> I've seen that esfq can do flows based on src/dest addresses.
>
> I have a small lan with private ip's.
> I guess that in my case esfq would only work for the download part as
> for the upload esfq only sees the src address = the NAT address (as I
> can figure from KPTD).
>
>
> Is there any solution for this ?
> (regarding esfq ..not by using iptables -j MARK and setting up different
> classes for everyone....and using sfq)
If you use IMQ it's the same, but there is a NAT patch which lets
ingress work properly - maybe it would be possible to make a patch that
does the same for egress.
Andy.
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2004-02-29 10:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-16 23:18 [LARTC] ESFQ question Mihai Tanasescu
2004-02-29 10:14 ` Andy Furniss [this message]
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=4041BB9B.7030608@dsl.pipex.com \
--to=andy.furniss@dsl.pipex.com \
--cc=lartc@vger.kernel.org \
/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