From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bernardo Vieira Subject: Re: 2 subnets Date: Fri, 22 Apr 2005 11:09:14 -0300 Message-ID: <4269058A.7020208@terra.com.br> References: <20050422132502.GA19589@epsilon.rdc.pl> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20050422132502.GA19589@epsilon.rdc.pl> List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: netfilter-bounces@lists.netfilter.org Errors-To: netfilter-bounces@lists.netfilter.org Content-Type: text/plain; charset="us-ascii" To: netfilter@lists.netfilter.org -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I'll give that a try. thx! Mariusz Kruk wrote: > On Thu, Apr 21, 2005 at 12:19:33PM -0300, Bernardo Vieira wrote: > >> Getting a ride on Mariusz's question, but probably deviating off >> topic: I if a had the setup where the two subnets run off the >> same network card on virtual interfaces, i.e. not physically >> separeted, could I still run a DHCP server on them? How about >> bandwidth limiting? Could anyone give me some pointers? > > > To clarify the things, the ethX:Y is a obsolete notation. This was > the only way to specify multiple IPs on one physical interface up > to 2.0 or 2.2 line of kernels. It's still provided for > compatibility reasons, I think. With modern kernels and tools you > don't have to use this notation at all. Kernel itself doesn't know > a thing about something called, for example, eth1:2. It's just > another IP addr added to eth1 interface. Therefore, you can > normally configure DHCP to bind to interface eth1 and assign IPs > from both nets based on MAC address of requesting host. If you > route the packets, it's irrelevant whether you push them to eth1 or > eth1:2. They end up on the same interface. So you can still attach > your queues and disciplines to eth1. > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFCaQUugs4DP681Hi8RAtGwAKCxmRqHJJ1wdzL9GTuYhtai4uNL1ACfRmqf qeRHJwqLeFHRWvS/DNDOnzk= =oxgL -----END PGP SIGNATURE-----