DHCP and VLANS

[MrWu]

Hi;

 

Just wondering what the best way to dish out IP addresses according to it's VLAN

 

Production Network:

IP Address Range: 10.18.96.1 – 10.18.99.254

Subnet Mask: 255.255.252.0

 

Proposed Wireless VLANs:

 

Guest

Student

Staff

 

Was maybe looking at assigning these the 192.168.xxx.xxx ranges

 

my Netgear Core (GSM 7328S has VLAN, Routing and DHCP capability upto 1024 host)

I also have Windows 2008 R2 DHCP server

 

So how would you go about the above? Would you use DHCP facilities from the Netgear, or make use of the Windows 2008 r2 box... (if so do you use what is called a Helper IP addresses?)

 

Thanks as always for the wisdom!

 

Wil

[CyberNerd]

personally I wouldn't rely on Netgear to do anything.

It makes sense to use the windows DHCP server here

 

How about:

 

Student

Network: 192.168.0.0

Broadcast: 192.168.3.255

Range: 192.168.0.1 - 192.168.3.254

Subnet:255.255.252.0

Hosts: 1022

 

Guest

Network: 192.168.4.0

Broadcast: 192.168.4.255

Range: 192.168.4.1 - 192.168.4.254

Subnet: 255.255.255.0

Hosts: 254

 

Staff

Network: 192.168.5.0

Broadcast: 192.168.5.255

Range: 192.168.5.1 - 192.168.5.254

Subnet: 255.255.255.0

Hosts: 254

 

Remember to keep some of the ip ranges reserved, ie only publish 191.168.0.10 - 191.168.3.254 as usable DHCP in the student network incase you need to add some static entries

Edited July 17, 2012 by CyberNerd

[twin--turbo]

191???

 

You need a helper address , and this will be the DC if you use AD to do the DHCP.

 

Rob

[MrWu]

191???

 

You need a helper address , and this will be the DC if you use AD to do the DHCP.

 

Rob

 

I knew what Cybernerd meant lol...

 

So in a nutshell

 

I have now RADIUS running on a server which is authenticating ok on my flat network with UniFi at the moment

 

Next I'll divide the network up in VLANS to test.

 

So in essence do I need to have multiple NIC cards on the DC/DHCP server to dish out the different scopes, or is that what a Helper address is for?

 

PS reading up on these things right now. :-) just that real life experience in here is a lot clearer and concise!

Edited July 17, 2012 by MrWu

[twin--turbo]

253 hosts too

 

Rob

[MrWu]

Now that's Nitpicking!

[twin--turbo]

is your core L3?

 

if so you only need one nic on the server.

 

each vlan on the core needs a DHCP helper address which is the IP of the Server. I can't help with the config on Netgear but it's a doddle on Cisco IOS

 

Each vlan should have a Vlan IP ( this will be the default route for that vlan ) and (at leats in cisco land) inter vlan routing just works...

[twin--turbo]

Now that's Nitpicking!

 

You could class the DG as host , can't remember how the Cisco exams treat the DG ( host or not... ) ... We used to have a linux box as the DG so it was a host realy..

 

Rob

[MrWu]

is your core L3?

 

if so you only need one nic on the server.

 

each vlan on the core needs a DHCP helper address which is the IP of the Server. I can't help with the config on Netgear but it's a doddle on Cisco IOS

 

Each vlan should have a Vlan IP ( this will be the default route for that vlan ) and (at leats in cisco land) inter vlan routing just works...

 

Thanks Twin Turbo

 

Yes it's 4 Netgear Cores stacked via 10Gbe, so the whole stack is L3

 

I'm reading through the manuals at the mo and playing with the interface, there's a truck load of options on the thing so will have a play!

 

I think the puzzle is slotting in now.....Windows 2008 r2 DHCP with one NIC > then Netgear Core doing the L3 routing/VLANS > Lightspeed Webfilter Layer 2 Bridging (in line) appliance > Sonicwall Firewall / Juniper routing that traffic to the internets...

 

Well, a few weeks over summer to test and build !

[CyberNerd]

sorry a couple of typos, then copy and pasted them lol

[twin--turbo]

LOL.....