From: m.dages@avk.net
To: lartc@vger.kernel.org
Subject: Antwort: Re: [LARTC] tc and masquerading probs
Date: Mon, 21 May 2001 15:30:16 +0000 [thread overview]
Message-ID: <marc-lartc-99045859130110@msgid-missing> (raw)
Hi,
thank you for your support. Your idea, looking also at the source ip with
the u32 filter works very well.
Markus
wningtung.leung wrote:
>> On Fri, 18 May 2001 m.dages@avk.net wrote:
>> Ok, now I've read the Linux 2.4 Advance Routing Howto and some other
>> documents that I could found about tc. All the examples describes an
>> environment with a linux box that has 2 ethernet cards, but our router
only
>> have 1. This ony ethernet adapter (eth0) is bounded to the ppp0 device
and
>> handles the LAN traffic.
>> Here's a short sheme:
>>
>> INTERNET <-----> [ ppp0/Dynamic IP --- Linux router ---
>> eth0/192.168.100.250] <------> Office Lan 192.168.100.0/24
>It doesn't matter wether it's a eth or ppp device, just look at it as a
>network interface and everything works fine.
>
>The solution I propose (haven't tested it though):
>
>Don't use firewall marks, but use the u32 filter instead.
>
>Look at the source and target IP and redirect the pakket to the correct
>class.
>
>(source != router && dest = low_prio_host) -> slow_class
>(source != router && dest = hi_prio_host) -> no_limit
>(source = router) -> no_limit
>
>This is only an idea for the downstream, I haven't been thinking about
>limitimg the upstream.
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/2.4Routing/
next reply other threads:[~2001-05-21 15:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-21 15:30 m.dages [this message]
2001-05-22 1:27 ` Antwort: Re: [LARTC] tc and masquerading probs Manfred Bartz
2001-05-22 19:50 ` Wingtung.Leung
2001-05-22 23:57 ` organix
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=marc-lartc-99045859130110@msgid-missing \
--to=m.dages@avk.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.