All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sander thrill12@gmx.net
To: lartc@vger.kernel.org
Subject: [LARTC] balancing behind NAT?
Date: Fri, 01 Dec 2000 13:16:21 +0000	[thread overview]
Message-ID: <marc-lartc-98373938216987@msgid-missing> (raw)
In-Reply-To: <marc-lartc-98373938216983@msgid-missing>

<PRE>At 03:58 1-12-00 +0000, you wrote:

&gt;<i>Hi,
</I>&gt;<i>
</I>&gt;<i>Im trying to setup a traffic shaping in a simialar setup to youris. The
</I>&gt;<i>stuff below makes sense but I can't figure out how to shape the
</I>&gt;<i>downstream. Could you give me an example from your config to start me
</I>&gt;<i>off.
</I>&gt;<i>
</I>&gt;<i>The thing I don't understand is that packets coming from the internet to
</I>&gt;<i>(for example) 192.168.0.4 will not be marked so how can they be
</I>&gt;<i>routed to the right class ?
</I>&gt;<i>
</I>&gt;<i>thanks
</I>&gt;<i>
</I>&gt;<i>david.
</I>
Hi,

I am sorry to say, I wasn't able to get that to work either (partially 
because I don't need it in my configuration). But I do think that you can 
follow the advanced routing howto more closely on that one when you use the 
interface to the local network, as the IP-adress is translated back to the 
internal adress long before it travels through this interface.
So in theory:
#example from the advanced routing-howto, slightly changed
tc filter add dev eth0 parent 10:0 protocol ip prio 25 u32 match ip dst \
        150.151.0.0 flowid 10:100

This should work (with the previous rules being pretty much the same as I 
gave them).

Sander Raaijmakers


</PRE>

  parent reply	other threads:[~2000-12-01 13:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-30 12:25 [LARTC] balancing behind NAT? lethal
2000-11-30 18:00 ` Sander
2000-12-01 13:16 ` Sander [this message]
2000-12-02 22:54 ` Wingtung.Leung

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-98373938216987@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.