All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel L. Miller" <dmiller@amfes.com>
To: netfilter@vger.kernel.org
Subject: Re: Single-NIC Traffic Shaping
Date: Sun, 02 Nov 2008 17:34:58 -0800	[thread overview]
Message-ID: <490E5542.6000606@amfes.com> (raw)
In-Reply-To: <490E14F8.6020402@riverviewtech.net>

Grant Taylor wrote:
> 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.
"Good reason"?!  It's the best reason of all!  $$$$!

This particular application is for my super-advanced home network - I 
have a Linux box doing relatively nothing, but I have added Squid to 
it.  This, along with the rest of my home gaming machines 
(cough-I-mean-workstations-cough) are hanging off a simple 5-port switch 
w/ router, then the DSL modem.  I wanted to take advantage of some 
bandwidth control tools on that box to shape the whole network - so I've 
added DHCP to the Linux box, turned it off on the router, and the Linux 
box is now the default gateway for the network.  Given the 100BaseT 
connection, I'm not overly worried about saturating it to keep up with 
my 5M DSL - but the goal was to optimize speed by controlling upload 
bandwidth - not choke the connection (which has been the result of my 
current efforts).

 I may give up on the single NIC idea - especially since this box has 
two NIC's built-in - but then I've got the outrageous expense of another 
patch cord - not to mention I'd be out of ports on the router!

But I thought it would be neat to have a single box that can physically 
"hang" off the "side" of the network and perform this job, instead of 
"physically" flowing through it.
-- 
Daniel

  reply	other threads:[~2008-11-03  1:34 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
2008-11-03  1:34     ` Daniel L. Miller [this message]
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=490E5542.6000606@amfes.com \
    --to=dmiller@amfes.com \
    --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.