All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Martin A. Brown" <mabrown-lartc@securepipe.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Ingress mode
Date: Fri, 15 Aug 2003 04:24:42 +0000	[thread overview]
Message-ID: <marc-lartc-106092157728146@msgid-missing> (raw)
In-Reply-To: <marc-lartc-106078054523424@msgid-missing>

Hi there Raghuveer,

Just a brief answer here.

 : I want to apply traffic control rules for the incomming traffic to my
 : firewall, which is what we call it as Ingress mode, am I right....?
 : Just to confirm, suppose my firewall WAN interface is eth0 with IP
 : 66.218.71.198 and LAN interface is eth1 with IP 192.168.1.2. So any
 : traffic from Internet---->WAN is where I want to do traffic control for
 : my LAN IP's. Hence amI right in saying that in ingress mode traffic
 : control will be happening at eth0 interface(or ppp0 interface, WAN with
 : ppp0 enabled).
 :
 : I saw in the link documents that, for ingress we are using imq0, so how
 : this will fit into my scenario...?. I understood that in ingress mode
 : we have to drop the packets instead of queueing it like in egress mode,
 : so is it going to have any effects other than latency...?

If you are using the Internet-connected host simply as a
routing, firewalling, masquerading and bandwidth controlling host, simply
forget about using IMQ.  Just shape the inbound traffic on your eth0
before you transmit it to the clients, and shape the outbound traffic on
ppp0 (wan0?) before you transmit it to the Internet.

Best of luck,

-Martin

-- 
Martin A. Brown --- SecurePipe, Inc. --- mabrown@securepipe.com

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

      parent reply	other threads:[~2003-08-15  4:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-13 13:28 [LARTC] Ingress mode Raghuveer
2003-08-13 13:32 ` Martin A. Brown
2003-08-14  6:39 ` Raghuveer
2003-08-15  4:24 ` Martin A. Brown [this message]

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-106092157728146@msgid-missing \
    --to=mabrown-lartc@securepipe.com \
    --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.