All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Logu" <logumail@gmx.net>
To: lartc@vger.kernel.org
Subject: [LARTC] Is it possible to control uplink in a NATted environment
Date: Tue, 08 Jun 2004 13:17:11 +0000	[thread overview]
Message-ID: <7faa01c44d59$4ae7a660$140110ac@lorco> (raw)

Hi all,

Given below ia the simple network diagram. I need to control uplink for the
individual private network IPs as depicted in the diagram. Is this possible
in a NATed environment using CBQ or HTB. I learnt that we can control only
outgoing traffic. So if I control in the eth1 interface the source IP will
be masqueraded, and it may not result in the desired behaviour.

Is there a solution to address this issue.

                              GATEWAY

  private net work   |-----------|
 -------------------|                 |------------------------Internet
                      eth0 |-----------| eth1 NAT

Thanks
-logu

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

             reply	other threads:[~2004-06-08 13:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-08 13:17 Logu [this message]
2004-06-09  0:04 ` [LARTC] Is it possible to control uplink in a NATted environment Damion de Soto

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='7faa01c44d59$4ae7a660$140110ac@lorco' \
    --to=logumail@gmx.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.