+ Post New Thread
Page 2 of 2 FirstFirst 12
Results 16 to 24 of 24
Wired Networks Thread, VLANs onto existing subnets in Technical; I suppose that means every port switch will be tagged with two VLANs, the default and the new guest VLAN ...
  1. #16
    Sheridan's Avatar
    Join Date
    Oct 2010
    Posts
    1,289
    Thank Post
    112
    Thanked 86 Times in 58 Posts
    Rep Power
    28
    I suppose that means every port switch will be tagged with two VLANs, the default and the new guest VLAN (50) - that might take a bit more setting up.

  2. #17

    Join Date
    Mar 2012
    Location
    Devon
    Posts
    223
    Thank Post
    0
    Thanked 15 Times in 14 Posts
    Rep Power
    10
    Another vote here for Procurves. We have various models through the school, and they are easy to manage through either the individual web interface or Procurve Manager.

  3. #18

    Join Date
    Dec 2009
    Posts
    914
    Thank Post
    98
    Thanked 184 Times in 159 Posts
    Rep Power
    54
    Quote Originally Posted by Sheridan View Post
    I suppose that means every port switch will be tagged with two VLANs, the default and the new guest VLAN (50) - that might take a bit more setting up.
    Nope no extra setting up. Your on the switch anyway to configure one or two ports, just select them all at once not individuals

  4. #19
    januttall's Avatar
    Join Date
    Sep 2010
    Posts
    225
    Thank Post
    17
    Thanked 28 Times in 28 Posts
    Blog Entries
    1
    Rep Power
    13
    all you need to do is tag or trunk the vlans you want on to the specific port for the AP the only other place you need to do this is the feed from the switch higher up this also need the feeder (other switch) port to have the trunk ports. don't set all your ports to have all the tagged traffic this is a bad idea.

  5. #20

    Join Date
    Dec 2009
    Posts
    914
    Thank Post
    98
    Thanked 184 Times in 159 Posts
    Rep Power
    54
    Quote Originally Posted by januttall View Post
    don't set all your ports to have all the tagged traffic this is a bad idea.
    I did say it wasnt best practice

  6. #21
    januttall's Avatar
    Join Date
    Sep 2010
    Posts
    225
    Thank Post
    17
    Thanked 28 Times in 28 Posts
    Blog Entries
    1
    Rep Power
    13
    just wait till you get a student or device that desides to bridge the VLANs PC's Can be set to use multiple VLANS. DONT TAGG ALL PORTS!! BAD IDEA.

  7. #22

    Join Date
    May 2011
    Location
    Jus North of London, close but not too close
    Posts
    736
    Thank Post
    172
    Thanked 56 Times in 54 Posts
    Rep Power
    35
    With Ruckus only tag the ports you need (as long as you haven't put the Ruckus management on a different vLAN), if you plug into the wrong port probably the most that will happen is the Guest SSID won't work from the AP.
    Last edited by Davit2005; 21st March 2013 at 12:26 PM.

  8. #23
    Sheridan's Avatar
    Join Date
    Oct 2010
    Posts
    1,289
    Thank Post
    112
    Thanked 86 Times in 58 Posts
    Rep Power
    28
    The APs and ZD are all on different subnets but the same (default) vlan (i.e not assigned)

  9. #24

    Join Date
    Oct 2008
    Posts
    213
    Thank Post
    2
    Thanked 11 Times in 11 Posts
    Rep Power
    21
    I have never used ruckus but I assume they are VLAN aware APs (I would expect so since cheaper unifi ones are). As others have said, it doesnt matter what subnet your existing vlans are on your switches, your "new" vlan will be treat separately (the whole idea of a vlan). So as long as you have (say) vlan 50 set up on every switch that needs a ruckus AP and you have with tagged uplinks and the ruckus switch port as tagged to vlan 50 (with default vlan left alone and probably still set to untagged on whatever your default PVID is). I imagine inside the ruckus management software you have your "normal" SSID set up and can add "guest SSID" but locked to VLAN 50. Have your L3 switch route as appropriate and the voodoo will work.

    If you want to test the setup easily, set up two PCs with static ip addresses different to any of your network subnets (we dont use 192.168.x.x so that is ideal for my tests). Set up a port on one switch as untagged VLAN50 with PVID of vlan50 (it wont be a member of your "default" vlan), do the same on another switch elsewhere and they should be able to talk to each other without leaking out onto your network. If that works then your guest wireless should work too (dont forget to either not use your test ports or put them back! It is so easy to forget this and wonder why PCxxx isnt connecting to the domain...!)

SHARE:
+ Post New Thread
Page 2 of 2 FirstFirst 12

Similar Threads

  1. Moving Existing Servers Onto Xen Server
    By clarky2k3 in forum Thin Client and Virtual Machines
    Replies: 0
    Last Post: 13th August 2009, 04:00 PM
  2. Wake on LAN across VLANs/subnets - 3Com Layer-3 Switch 5500
    By SSTechIII in forum Wireless Networks
    Replies: 17
    Last Post: 28th April 2008, 09:09 PM
  3. New Netgear switch into existing VLAN
    By mullet_man in forum Wireless Networks
    Replies: 0
    Last Post: 20th September 2007, 02:32 PM
  4. VLANs/ Subnets help
    By Ste_Harve in forum Wireless Networks
    Replies: 19
    Last Post: 25th June 2007, 12:42 PM
  5. How do you seperate your networks. Subnet / Vlan
    By drjturner in forum Wireless Networks
    Replies: 16
    Last Post: 28th September 2006, 07:24 AM

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •