+ Post New Thread
Page 2 of 4 FirstFirst 1234 LastLast
Results 16 to 30 of 46
Wireless Networks Thread, Ruckus & VLANs in Technical; The strange thing I can't get anything to communicate through the switches unless the device is setup with a ip ...
  1. #16

    Join Date
    Apr 2012
    Location
    Cheshire
    Posts
    128
    Thank Post
    4
    Thanked 1 Time in 1 Post
    Rep Power
    0
    The strange thing I can't get anything to communicate through the switches unless the device is setup with a ip address on the main range of 1.0.0.0. Anything else it won't have it regardless of what vlan is tagged. Could this be because the switches are only layer 2 and although I am trying to vlan for a different range (192) the switch is refusing to deal with it? the switches have no gateway address set. Do I need layer 3 switches to make these vlans work because I am using a different IP range/subnet?

  2. #17

    Join Date
    Apr 2012
    Location
    Cheshire
    Posts
    128
    Thank Post
    4
    Thanked 1 Time in 1 Post
    Rep Power
    0
    Scrap that, plugged in 2 laptops both with 192 addresses on a switch configured with an ip on the range of 1.0 and the two laptops could ping each other. Sooo problem isn't with the switches, problem is with smoothwall in that I cannot ping any of the vlan sub interfaces from a client even if I directly plug in. If I change one of the vlan sub interfaces to an 1.0 ip untagged I can ping.

  3. #18
    ass17's Avatar
    Join Date
    Feb 2013
    Posts
    361
    Thank Post
    5
    Thanked 40 Times in 37 Posts
    Rep Power
    27
    If you use smoothy as your dhcp do your laptops get an ip?

  4. #19

    Join Date
    Apr 2012
    Location
    Cheshire
    Posts
    128
    Thank Post
    4
    Thanked 1 Time in 1 Post
    Rep Power
    0
    Nope, this is what I have got now, very basic:

    Smoothwall port 4-1 VLAN2 ip address 192.168.12.1 255.255.255.0 connected to port 12 on the switch, port 12 on the switch, untagged vlan 1 tagged vlan 2
    Laptop plugged into Port 3 on the same switch, untagged on vlan 2 to test.

    No IP address received even though smoothwall is setup and enabled to give out ip addresses for the sub interface associated with vlan 2.

    If I configure the laptop with a static address and try to ping this sub interface for vlan 2 on smoothwall I get nothing

    I have tried another switch too to rule out any problems there and I get the same issue, I just can't understand it its driving me insane!!

  5. #20

    Join Date
    May 2011
    Location
    Jus North of London, close but not too close
    Posts
    888
    Thank Post
    198
    Thanked 77 Times in 71 Posts
    Rep Power
    52
    Can you make a spare port on the Smoothwall a member if that vLAN so you can rule out switches altogether and plug laptop directly into SmoothWall??

    I.E not make it a sub interface but make the port only for that vlan.

  6. #21

    Join Date
    Apr 2012
    Location
    Cheshire
    Posts
    128
    Thank Post
    4
    Thanked 1 Time in 1 Post
    Rep Power
    0
    Still no joy, does smoothwall have any funny restrictions such as if a range is in use on one interface does it block its use on another? for example:

    Port 1 - Main Network - 1.0.100.156 255.255.0.0
    Port 2 - External (Uplink to router) - 192.168.100.161 255.255.255.0
    Port 3 - not in use
    Port 4-1 - VLAN 2 - 192.168.12.1 255.255.255.0

    Could the external configuration cause a problem with it being a 192.168? or is there anything else in smoothwall that needs configuring? I followed the guide that timbo wrote.

  7. #22
    timbo343's Avatar
    Join Date
    Dec 2005
    Location
    Leeds/York area, North Yorkshire
    Posts
    3,153
    Thank Post
    319
    Thanked 310 Times in 216 Posts
    Rep Power
    124
    If you are still having problems with the smoothwall and VLAN setup, here is a little how to on how to get this working.

    See post 43 on this thread BYOD with Smoothwall and Ruckus

    Edit: Oh.. i see you have already seen this document
    Last edited by timbo343; 1st August 2014 at 04:40 PM.

  8. #23
    ass17's Avatar
    Join Date
    Feb 2013
    Posts
    361
    Thank Post
    5
    Thanked 40 Times in 37 Posts
    Rep Power
    27
    The way we do it is via a core layer 3 switch which allows inter-vlan routing.

    Each edge switch has a default gateway which is the IP set on the core switch port to which the edge switch is connected to.

    Then off top of my head I'm sure on our core switch we set static routes and rules for vlans.

    Without being at work I can't go through it with you in detail, plus we installed it over a year ago and haven't touch the networking since, because it works. I will try to familiarise myself again with how everything comes together and get back to you...

  9. #24

    Join Date
    Apr 2012
    Location
    Cheshire
    Posts
    128
    Thank Post
    4
    Thanked 1 Time in 1 Post
    Rep Power
    0
    Quote Originally Posted by ass17 View Post
    The way we do it is via a core layer 3 switch which allows inter-vlan routing.

    Each edge switch has a default gateway which is the IP set on the core switch port to which the edge switch is connected to.

    Then off top of my head I'm sure on our core switch we set static routes and rules for vlans.

    Without being at work I can't go through it with you in detail, plus we installed it over a year ago and haven't touch the networking since, because it works. I will try to familiarise myself again with how everything comes together and get back to you...
    I reckon because i am trying to use vlans with a different subnet altogether from the main network the lack of layer 3 equipment is making it impossible however if i setup my vlans with different ranges within the 1.0.0.0 network and then just use ruckus to deny access to certain ranges within this network then i might be ok. I think the vlans will be happy as long as i dont deviate from the 1.0.0.0 network because they are only layer 2 does that make sense?

  10. #25
    ass17's Avatar
    Join Date
    Feb 2013
    Posts
    361
    Thank Post
    5
    Thanked 40 Times in 37 Posts
    Rep Power
    27
    Yeah makes sense, we use 10.0 for all wifi devices and 172 for domain static devices, but I'm sure L3 only makes this possible.

    You should be ok to vlan using same range on 1.0

  11. #26

    Join Date
    Apr 2012
    Location
    Cheshire
    Posts
    128
    Thank Post
    4
    Thanked 1 Time in 1 Post
    Rep Power
    0
    Quote Originally Posted by ass17 View Post
    Yeah makes sense, we use 10.0 for all wifi devices and 172 for domain static devices, but I'm sure L3 only makes this possible.

    You should be ok to vlan using same range on 1.0
    Right ive managed to get the interfaces talking somehow!

    I have an interesting issue now though in that if i create the vlan interfaces on the port that isnt connected i can see these in dhcp server and dns proxy and can select them. If i create the vlan interfaces on the port that is connected they dont appear...

  12. #27
    ass17's Avatar
    Join Date
    Feb 2013
    Posts
    361
    Thank Post
    5
    Thanked 40 Times in 37 Posts
    Rep Power
    27
    Sounds strangely backwards, not sure...

  13. #28

    Join Date
    Apr 2012
    Location
    Cheshire
    Posts
    128
    Thank Post
    4
    Thanked 1 Time in 1 Post
    Rep Power
    0
    Right everything is working now turns out i found a legacy bug with smoothwall and vlans which they have now sorted for me. I just now have one remaining issue. I have configured dhcp on all of my vlan interfaces with a separate range for each for example:

    172.16.0.2 to 172.16.0.254 for staff
    172.16.1.2 to 172.16.4.254 for students
    172.16.5.2 to 172.16.5.254 for guest
    172.16.6.2 to 172.16.7.254 for 6th form

    I have untagged a port on the switch for my laptop on the staff vlan and i can confirm i have received a lease from smoothwall however it has given me 172.16.6.2 which is 6th form only im not connecting on this vlan whats gone wrong?

  14. #29
    timbo343's Avatar
    Join Date
    Dec 2005
    Location
    Leeds/York area, North Yorkshire
    Posts
    3,153
    Thank Post
    319
    Thanked 310 Times in 216 Posts
    Rep Power
    124
    I would check the switch config and look for which vlan the port is configured for. Sounds like a config error more than anything else to me

  15. #30

    Join Date
    Apr 2012
    Location
    Cheshire
    Posts
    128
    Thank Post
    4
    Thanked 1 Time in 1 Post
    Rep Power
    0
    Ive got the card that the vlans are on plugged into port 12 on the switch which is:

    Untagged vlan 1
    Tagged 100-103

    Laptop in port 4 untagged on vlan 100 (staff) smoothwall is set as vlan 100 for staff staff dhcp range is 172.16.0.2-172.16.0.254 but i dont get an ip from this range hmm



SHARE:
+ Post New Thread
Page 2 of 4 FirstFirst 1234 LastLast

Similar Threads

  1. Ruckus - different VLAN for each SSID
    By localzuk in forum Wireless Networks
    Replies: 2
    Last Post: 21st August 2013, 12:26 PM
  2. Wireless Guest SSID VLAN Ruckus
    By robbie-w in forum Wireless Networks
    Replies: 1
    Last Post: 5th March 2012, 06:27 PM
  3. Ruckus and Cisco VLan's?
    By bjohnny42 in forum Wireless Networks
    Replies: 4
    Last Post: 29th July 2011, 03:57 PM
  4. Ruckus VLANs
    By cookie_monster in forum Wireless Networks
    Replies: 7
    Last Post: 26th April 2010, 11:15 AM
  5. RUckus SSID VLANs
    By badders in forum Wireless Networks
    Replies: 4
    Last Post: 13th April 2010, 10:59 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
  •