vlans

Oh man! Ad-blocking software has been detected! :'(

This website is run by the community, for the community... and it needs advertisements in order to keep running. Blocking our ads means your killing our stats!
Please disable your ad-block, or become a premium member to hide all advertisements and this notice.

hi everyone,

im working on a solution for my project for uni. was just wondering if someone can confirm that it is NOT possible to have vlans over WAN leased line. For example, I have two offices, one in london and one in glasgow, both have design staff, they are going to be connected together using leased line, is it possible to have both these departments in the same vlan ? say (vlan 10) . over a leased line?


Cheers all

 

Oh man! Ad-blocking software has been detected! :'(

This website is run by the community, for the community... and it needs advertisements in order to keep running. Blocking our ads means your killing our stats!
Please disable your ad-block, or become a premium member to hide all advertisements and this notice.

Yes, you can.

 

thanks for getting back boson,

so hows that done, can you expand please?

would I create subnets sized around the Culmulative number of hosts in the same department on all sites? i.e Glasgow has 60 design members, London has 90 design members = 150, so i would subnet my original class B addy to allow for 150 hosts plus a bit of growth. Then just allocate the addys as normal amongst the departments on each site?

thanks in advance for your help

 

Connect the offices by leased line and trunk the VLANs. Exactly how you do that depends on the devices you use.

You can design VLANs in any (valid) way you want to, just like you can create logical, routed networks in any way you want to.

 

so i would trunk the links in order for tagging ( isl or dot1q ) to be used?

is there any particular devices you could kindly reccomend?

also would the subnetting scheme I explained before be valid boson?

thanks alot mate for your help it is much appreciated

 

You would connect and configure them just as you would if it were a plain old local wired network. I'm partial to Cisco, but that's because that's what I'm used to.

Your subnetting scheme depends on what address ranges you're using. If you've got a whole 16-bit Class B to yourself, you can divide up those 65,536 addresses however you see fit. I'd probably put them on a 24-bit range unless you plan on more growth than that.

The question I have is this: why do you feel the need to separate departmental traffic? Or is this just a theoretical question?

 

Yeh, sorry about that. We turned verbose mode off for a bit and it must have been just then he posted (sorry Mike )

 

Im just following the spec sheet from uni mate. "traffic from each department should be logically seperated from other departments"

dont ask me why i think its just to show that we understand how vlans work

cheers mate

 

It's back on again.

 

No problem - just wanted you to consider the reasons behind separating the departmental traffic. There are valid (and not-so-valid) reasons for doing so... but you get so much more out of the exercise if you work them through in your head on your own. VLANs aren't very intuitive, but once the lightbulb comes on, you'll begin to see several practical applications for them.

 

thanks again boson, i think il just stick to vlans for each site and not have them accross the wan seems easier and less hassle ( projects due in on friday :/ ) thanks again though mates its much appreciated

 

So are you splitting up each site into it's own VLAN (Glasgow in 10, Liverpool in 20), or are you splitting up the departments at each site into their own VLANs (Design Glasgow in 10, Production Glasgow in 20, Design Liverpool in 30, Production Liverpool in 40)?