All of lore.kernel.org
 help / color / mirror / Atom feed
From: Grant Taylor <gtaylor@riverviewtech.net>
To: Mail List - Netfilter <netfilter@vger.kernel.org>
Subject: Re: Single-NIC Traffic Shaping
Date: Sun, 02 Nov 2008 15:00:40 -0600	[thread overview]
Message-ID: <490E14F8.6020402@riverviewtech.net> (raw)
In-Reply-To: <490DF590.3010507@amfes.com>

On 11/2/2008 12:46 PM, Daniel L. Miller wrote:
> Since tc acts on an interface basis - can I perhaps setup a bridge with 
> a single interface in it?  So address the physical interface eth0 for my 
> LAN, set the bridge for the Internet modem, and then use tc on the 
> bridge but not on the ethernet interface?

Unless you have a good reason, I would strongly suggest that you add a 
second NIC to the box and put your internet connection on that second NIC.

Technically I /believe/ you can do it with a single NIC, but it is 
extremely complex to do in such as you have to take in to account both 
internal (LAN), external (Internet), inbound, and outbound traffic all 
on the same interface and in the same tree structure.  Where as if you 
have separate NICs you can separate your interfaces and tree structures 
such that internet reply traffic is processed as traffic going out the 
internal interface and internet request traffic is processed as traffic 
going out the external interface.  Usually people do not want to rate 
limit / QoS their internal LAN traffic, requests or replies.

Further, if someone is on the same network segment as your internet 
connection, (with Static IP or DHCP) it may be possible for them to do 
some nefarious things (think MAC addresses) to be able to connect 
directly in to your systems across the internet bypassing your router 
all together.



Grant. . . .

  reply	other threads:[~2008-11-02 21:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-02 16:51 Single-NIC Traffic Shaping Daniel L. Miller
2008-11-02 18:46 ` Daniel L. Miller
2008-11-02 21:00   ` Grant Taylor [this message]
2008-11-03  1:34     ` Daniel L. Miller
2008-11-03  2:15       ` Grant Taylor

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=490E14F8.6020402@riverviewtech.net \
    --to=gtaylor@riverviewtech.net \
    --cc=netfilter@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.