Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 6 replies
  • Answers 1 answer
  • Subscribers 27 subscribers
  • Views 4801 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

How to get IP addresses assigned over wifi using VLANs?

rfcat_vk

Hi floks,

the weather being a little warm I decided to addd some features to my XG regarding IoT network security.

Installed an AP55C using VLAN on a spare port via a managed switch

Configured 2 VLANs

Added DHCP servers for each VLAN.

The AP picked up an IP address from the VLAN it is tagged with.

Created a number of SSIDs using bridge to VLAN for each VLAN, so far all good and a WIFI group

Next step connect a device to a SSID. Failure. Device connects or at least the XG sees it in the wireless tabs, but no address automatically assigned.

The XG decided that it knows about the device and shows it connected via an IP address from another network (there have been some discussions about this security breach in previous threads.

Device advises it cannot get an IP address so I assign one manually, update the clienless config, create a static address in the correct DHCP server.

XG wireless show device with 2 IP addresses, the original and new. The original IP address has been removed and the session dropped.

The device advises the connection has been refused by the the XG. I did try a second device and still no address assignments.

I have tried both VLANs to get addresses assigned to wifi connected devices, but nothing connects or is assigned.

So what am I missing in the wifi configuration that will allow an assignment to be requested over WIFI VLANs?

 

Ian



This thread was automatically locked due to age.
Parents Reply Children
  • +1 in reply to rfcat_vk

    Fixed the issue. Appears as though the AP55C is the untagged interface for devices to connect. The managed switch needs both ports setup as tagged, the XG and AP connections.

    Ian

     

    Gets very interesting when the remote AP shares a cable with some LAN devices, another VLAN required with Untagged interfaces. The bad news is that setup does not work, you can either have LAN devices of AP, but not both.

  • 0 in reply to rfcat_vk

    A very interesting session in moving to VLANs and WIFI.

    Ended up with one dead AP55.

    I would not say the process of setting up VLANs over WIFI is very intuitive, a lot of guess work is involved. Devices not communicating when setup in their final location, having to be connected and configured on a main switch then moved to the remote switch.

    I have most of the devices working, a couple I can see on the network but will not connect.

    The biggest issue is the number of IP addresses some device pickup and do not let go. My printer currently has 4 addresses, hopefully they will age off something eventually. Not brave enough to restart the XG yet.

    Ian

  • 0 in reply to rfcat_vk

    If i understand you correctly, AP can work only in VLAN, if you start to use VLAN. So you need only Bridge to AP VLAN and the AP needs his "own" VLAN to work in. 

    There is no way in SG/XG to work with LAN bridges and VLANs. 

  • 0 in reply to LuCar Toni

    Hi LuCar,

    I understood all of that, that is why I started to build VLANs for my WIFI.

    Currently working for most devices, especially when the cat does not step on my keyboard.

    Ian