Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Bandwith sharing in NAT environment.
Date: Sat, 09 Aug 2003 21:23:13 +0000	[thread overview]
Message-ID: <marc-lartc-106046429209058@msgid-missing> (raw)
In-Reply-To: <marc-lartc-106044670230870@msgid-missing>

On Saturday 09 August 2003 18:30, Rajesh wrote:
> Hi
>
> I wish to implement Bandwith sharing in a NAT environment.
>
> The question is whether I can classify input packets on the basis of
> ip-addresses (private LAN addresses)? These packets finally need to be
> NATed before going on to Internet.
>
> Would the tc filters see the private addresses and put it in the
> appropriate classes or would the tc filters see only the NATed address and
> the filter would fail in putting the packets in the appropriate classes?
>
> The n/w diag would be somewhat like this
>
> private address LAN ips ------>iptables(NAT)------>Internet.
>
> Can I mark packets using iptables matching source ip-address?
Yes.

> What address will tc filter see when the private addresses are masqueraded
> ?
The ip address of your firewall.  So you have to mark the packets in 
prerouting before the natting....

Stef

-- 

stef.coene@docum.org
 "Using Linux as bandwidth manager"
     http://www.docum.org/
     #lartc @ irc.oftc.net

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

  reply	other threads:[~2003-08-09 21:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-09 16:30 [LARTC] Bandwith sharing in NAT environment Rajesh
2003-08-09 21:23 ` Stef Coene [this message]
2003-08-14 11:15 ` Raghuveer
2003-08-14 11:26 ` S Mohan

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-106046429209058@msgid-missing \
    --to=stef.coene@docum.org \
    --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