From: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2005@gmx.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Help? Router/Bandwidth throttle needed.
Date: Thu, 23 Jun 2005 00:31:46 +0000 [thread overview]
Message-ID: <42BA02F2.6020801@gmx.net> (raw)
In-Reply-To: <20050620194426.4E85C18133@www.idealconditions.com>
rsenykoff@harrislogic.com schrieb:
>>Here's a 'map' of my network 'plan':
>>
>>+-------+ +--------+ +-------+
>>| Dumb | | Linux | | Linux |
>>| Cable +---+ Bridge +----+-----+ DHCP/ +----> Bunch of workstations
>>| Modem | | w/ QoS | | | NAT | on 192.168.10.X
>>+-------+ +--------+ | +-------+
>>X.X.X.62 Eth0 X.X.X.61 | Eth0 X.X.X.57
>> Eth1 ??? | Eth1 192.168.10.1
>> |
>> |
>> +-----> 3 more servers: X.X.X.58->60
> [...]
> The script does assume that the NICs are eth0 and eth1. Change if needed.
> You should make a note of which NIC goes which way (using MAC address is
> good) and label on the back. This will come in handy as your upload is not
> the same as your download.
Using ifrename to name your interfaces according to the function they have
is very much recommended. That way you never have to remember which
interface is the one you want to access. I use names like bridgeext for
eth0 and bridgeint for eth1.
Another recommendation for bridging is to use a separate interface for
administration and to assign no IP to br0/bridgeext/bridgeint. That way
the machine will still be accessible even if STP and friends go crazy
on the bridged nics.
Regards,
Carl-Daniel
--
http://www.hailfinger.org/
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next prev parent reply other threads:[~2005-06-23 0:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-20 19:59 [LARTC] Help? Router/Bandwidth throttle needed ICI Support
2005-06-21 2:08 ` gypsy
2005-06-22 14:31 ` ICI Support
2005-06-22 16:31 ` rsenykoff
2005-06-22 22:29 ` ICI Support
2005-06-22 23:55 ` rsenykoff
2005-06-23 0:31 ` Carl-Daniel Hailfinger [this message]
2005-06-23 0:45 ` ICI Support
2005-06-23 3:06 ` gypsy
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=42BA02F2.6020801@gmx.net \
--to=c-d.hailfinger.devel.2005@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.