2 subnets

2 subnets

[varun_saa]

Hello,
      My server is on Mandrake10.1
eth0 is WAN with static IP connected to 512Kbps DSL.

We have two subnets :

   192.168.0.0/24
   192.168.21.0/24

Clients on both subnets will browse, send/
recieve mails and use MSN or Yahoo chat.

Right now I am using eth1 as LAN as follows :

eth1   - 192.168.0.0/24
eth1:1 - 192.168.21.0/24

Right now I am using shorewall. But I would like
to switch to iptables.

My question is having seperate network card 
for each subnets a better option.

eth1 and eth2.

Or eth1 and eth:1 is also fine

Thanks

Varun

Re: 2 subnets

[Mariusz Kruk]

On Thu, Apr 21, 2005 at 07:18:33PM +0500, varun_saa@vsnl.net wrote:
> Hello,
>       My server is on Mandrake10.1
> eth0 is WAN with static IP connected to 512Kbps DSL.
> 
> We have two subnets :
> 
>    192.168.0.0/24
>    192.168.21.0/24
[...]
> My question is having seperate network card 
> for each subnets a better option.
> 
> eth1 and eth2.
> 
> Or eth1 and eth:1 is also fine

This depends on two things:
1. Do you want to physicaly separate these two network segments?
2. If you want to, for example, shape the traffic, you'll have a more
complicated setup if you have separate interfaces.

Therefore it's up to you and depends only on your needs in this matter.

-- 
/\-\/\-\/\-\/\-\/\-\/\-\/\ Always  remember  that you are unique.  Just
\  Kruk@epsilon.eu.org   / like everyone else.
/ http://epsilon.eu.org/ \ 
\/-/\/-/\/-/\/-/\/-/\/-/\/ 

Re: 2 subnets

[Bernardo Vieira]

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?


Mariusz Kruk wrote:

>On Thu, Apr 21, 2005 at 07:18:33PM +0500, varun_saa@vsnl.net wrote:
>  
>
>>Hello,
>>      My server is on Mandrake10.1
>>eth0 is WAN with static IP connected to 512Kbps DSL.
>>
>>We have two subnets :
>>
>>   192.168.0.0/24
>>   192.168.21.0/24
>>    
>>
>[...]
>  
>
>>My question is having seperate network card 
>>for each subnets a better option.
>>
>>eth1 and eth2.
>>
>>Or eth1 and eth:1 is also fine
>>    
>>
>
>This depends on two things:
>1. Do you want to physicaly separate these two network segments?
>2. If you want to, for example, shape the traffic, you'll have a more
>complicated setup if you have separate interfaces.
>
>Therefore it's up to you and depends only on your needs in this matter.
>
>  
>

Re: 2 subnets

[Mariusz Kruk]

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.

-- 
[------------------------] Bet   you   can't  stop  reading  here  <---
[  Kruk@epsilon.eu.org   ] I knew it...
[ http://epsilon.eu.org/ ] 
[------------------------] 

Re: 2 subnets

[Bernardo Vieira]

-----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-----