is this how i vlan?

[skanky]

not sure if this is how its done, i have a speedtouch 780WL (as provided by BE), i want all devices to be able to see all the other devices, the main reason i want to seperate them is to be a bit more organised so if/when i need to add further devices in future.

the setup i need goes a little something like:

192.168.1.254 = router
192.168.1.1 to 192.168.1.2 = wired adapters
192.168.2.1 to 192.168.2.2 = wireless adapters
192.168.3.1 to 192.168.3.2 = printers

obviously i've removed the MAC addresses, but does this look right in the config file i've been editing as the interface for the speedtouch isnt too hot!

[ dhcs.ini ]
debug traceconfig state=disabled
policy verifyfirst=enabled trustclient=enabled
pool config name=LAN intf=LocalNetwork poolstart=192.168.1.1 poolend=192.168.1.2 netmask=24 gateway=192.168.1.254
pool config name=WLAN intf=LocalNetwork poolstart=192.168.2.1 poolend=192.168.2.2 netmask=24 gateway=192.168.1.254
pool config name=PRINTER intf=LocalNetwork poolstart=192.168.3.1 poolend=192.168.2.2 netmask=24 gateway=192.168.1.254
server=192.168.1.254
lease add clientid=(MAC ADDRESS HERE) pool=LAN addr=192.168.1.1 leasetime=0 expirytime=0 gateway=192.168.1.254 macaddr=00:00:00:00:00:00
lease add clientid=(MAC ADDRESS HERE) pool=LAN addr=192.168.1.2 leasetime=0 expirytime=0 gateway=192.168.1.254 macaddr=00:00:00:00:00:00
lease add clientid=(MAC ADDRESS HERE) pool=WLAN addr=192.168.2.1 leasetime=0 expirytime=0 gateway=192.168.1.254 macaddr=00:00:00:00:00:00
lease add clientid=(MAC ADDRESS HERE) pool=WLAN addr=192.168.2.2 leasetime=0 expirytime=0 gateway=192.168.1.254 macaddr=00:00:00:00:00:00
lease add clientid=(MAC ADDRESS HERE) pool=PRINTER addr=192.168.3.1 leasetime=0 expirytime=0 gateway=192.168.1.254 macaddr=00:00:00:00:00:00
lease add clientid=(MAC ADDRESS HERE) pool=PRINTER addr=192.168.3.2 leasetime=0 expirytime=0 gateway=192.168.1.254 macaddr=00:00:00:00:00:00

 

[oddjob62]

I don't see anything to do with VLANs there. Looks like 3 DHCP pools.

And what's the point of having DHCP if you statically assign everything. Might as well just have static addresses all round.

 

[skanky]

I don't see anything to do with VLANs there. Looks like 3 DHCP pools.

And what's the point of having DHCP if you statically assign everything. Might as well just have static addresses all round.

i'm none too good with the terminology as i'm not a network guy by trade but will that do what i'm after?

i'm using that as a small example, i use static addresses as i sometimes need to RDP from an outside source to a particular PC so i need to be able to forward a port to a certain PC which will stay that same IP all the time.

 

[Curiosityx]

Not quite it appears that you have just configured different network addresses for each group.

If you want to segment the network i would recommend doing it on a layer 3 switch or a layer 2 switch using a router for inter vlan routing.

As mentioned above it appears that you have created three dhcp pools not three separate vlans.

 

[skanky]

As mentioned above it appears that you have created three dhcp pools not three separate vlans.

i'm obviously not a network guy but whats the difference between a dhcp pool and a vlan? i partly thought trying to do this to organise a bit and still want everything to see everything else so i dont really need to segment anything away.

or should i just give up, have 1 dhcp pool, document what device is where and leave it at that?

 

[Curiosityx]

DHCP pools are used to automatically assign IP addresses to a subset of client devices but a single DHCP pool can only lease out addresses to a single subnet.

VLAN's are a method of segmentating an existing network for the purpose of reducing the size of a broadcast domain, creating logical groups of client devices and to improve security.

If say you had multiple Vlans on different subnets it is possible to have one DHCP server configured to service each subnet belonging to a different vlan by using a DHCP helper address assigned on the switch or router. This single DHCP server would contain the pools for all subnets, when it received a request from say subnet "192.168.1.0/24" it would look at its available pools and assign a free address to the client.

http://en.wikipedia.org/wiki/Virtual_LAN

http://en.wikipedia.org/wiki/Dynamic_Host_Configuration_Protocol

Personally for small networks Vlans arnt necessary unless your running voice on the same network as data.

 

[oddjob62]

Good post Curiosityx

Personally for small networks Vlans arnt necessary unless your running voice on the same network as data.

Even with VOIP it would have to be a decent size to "require" the use of VLANs

 

[Curiosityx]

Good post Curiosityx



Even with VOIP it would have to be a decent size to "require" the use of VLANs

True but personally as rule of thumb i always separate the two as well as defining vlans for management