All of lore.kernel.org
 help / color / mirror / Atom feed
From: bert hubert ahu@ds9a.nl
To: lartc@vger.kernel.org
Subject: [LARTC] Second problem with Bandwidth limiting
Date: Wed, 18 Oct 2000 09:51:51 +0000	[thread overview]
Message-ID: <marc-lartc-98373938216804@msgid-missing> (raw)
In-Reply-To: <marc-lartc-98373938216802@msgid-missing>

<PRE>On Wed, Oct 18, 2000 at 09:59:36AM +0200, Fredrik Rambris wrote:

&gt;<i> Add a loopback interface and set the limit there. Local access to the
</I>&gt;<i> machine should not be limited. Like this:
</I>
This is not the right way to go about it.

&gt;<i>          +--------------+ +-------------+ +-------------------+
</I>&gt;<i> Internet-&lt;128kbit&lt; Eth1 |-| Lo1 &gt;128kbit&gt;-| Proxy &lt;-100MBit-&gt; |-LAN
</I>&gt;<i>          +--------------+ +-------------+ +-------------------+
</I>&gt;<i> 
</I>&gt;<i> So only trafic to and from Internet would be limited. Trafic to an from
</I>&gt;<i> the LAN would be 100MBit.
</I>&gt;<i> 
</I>&gt;<i> Is this possible?! Or is there another better solution to get the same
</I>&gt;<i> result?
</I>
Mark packets coming in over the internet with either ipchains or netfilter.
This needs 'shape on fwmark' or something like that enabled in the kernel
configuration.

If the packets traverse your router untouched (ie, don't go via the proxy),
the mark will remain on them. Then you shape outgoing packets in eth0 that
have this mark on them, and don't shape other packets.

Regards,

bert hubert


-- 
PowerDNS                     Versatile DNS Services  
Trilab                       The Technology People   
'SYN! .. SYN|ACK! .. ACK!' - the mating call of the internet


</PRE>

           reply	other threads:[~2000-10-18  9:51 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <marc-lartc-98373938216802@msgid-missing>]

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-98373938216804@msgid-missing \
    --to=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.