All of lore.kernel.org
 help / color / mirror / Atom feed
* [LARTC] Second problem with Bandwidth limiting
       [not found] <marc-lartc-98373938216802@msgid-missing>
@ 2000-10-18  9:51 ` bert
  0 siblings, 0 replies; only message in thread
From: bert @ 2000-10-18  9:51 UTC (permalink / raw)
  To: lartc

<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>

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2000-10-18  9:51 UTC | newest]

Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
     [not found] <marc-lartc-98373938216802@msgid-missing>
2000-10-18  9:51 ` [LARTC] Second problem with Bandwidth limiting bert

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.