Skip to main content

10 Messages

 • 

200 Points

Thu, Feb 13, 2020 8:27 PM

Answered

R510 Unleashed Clients no getting IPs from DHCP

There is an r710 connected to the same switch and doesn't have the same problem.
When I assign a static IP to the client there is still no network access.
The only thing that works is enabling 'randomized MAC' on the client, that way it gets an IP from DHCP no problem.
Also this is on my default WLAN / VLAN, i have another WLAN on a different tagged VLAN and that one doesn't have the same issue on the same AP.

What could be the problem?

Responses

246 Messages

 • 

4.2K Points

9 months ago

Hi,

Could be a VLAN config. The switch port where is the AP is connected, is it configured as Access or Trunk port? If you are passing multiple VLANs, configure it as trunk port.

If the switch port config is fine, do a packet capture (using wireshark if possible) on the DHCP server side to see if it is receiving the traffic from the client.

10 Messages

 • 

200 Points

9 months ago

Since setting a static IP on the client doesn't give connectivity it's not a DHCP problem.
Neatgear switch GS110TP V3.
My management/main VLAN is 1, guest is 10.
VLAN 1 in untagged  on all ports VLAN 10 is tagged.

I tried tagging VLAN 1 on the port r510 is connected to, it didn't solve the problem.

Again exact same setup works on r710 connected to the same switch.
No idea what else to try.

Also the fact that randomized mac allows access and native device mac doesn't is strange.

10 Messages

 • 

200 Points

9 months ago

Got an r720 to replace the r510, same thing. Pretty sure it is an unleashed specific bug.

Basically when there is a WLAN on the default VLAN1 (which us UNTAGGED)and another WLAN on a different VLAN (TAGGED) on the same unleashed network clients connecting to the SLAVE, get no access to the network unless they use a random MAC. Clients connecting to the MASTER can have random or native MAC.

TAGGING VLAN1 on solves this issue.
This is 100% reproducible for me by switching the master/slave AP in my network of two APs.

Does this need to be filed as a bug somehow?

10 Messages

 • 

200 Points

9 months ago

Issues came back. Tagging VLAN1 didn't solve it.

1 Message

 • 

60 Points

6 months ago

I'm having the same issue as described above with r510 Unleashed APs and Netgear GS110TP. The client device connects to the AP and shows in the dashboard but can't get a DHCP IP address. If I set a static IP, It still can't ping the server or router but can ping the AP.

1 Message

 • 

62 Points

3 months ago

I have the same issue. I deployed R320 unleashed standalone without the internet. I set up the ruckus to be the DHCP server. An IoT Hub (Rak Wireless) connects to my AP. The other 2 hubs received an IP address. however, the other two didn't. I can see that Hubs are connected from the client list but no IP address.

Employee

 • 

604 Messages

 • 

10K Points

Hi John,

If some devices are getting IPs and some are not, please use the Unleashed inbuilt utility called Client Troubleshooting.



This will help you to find at what point it is failing.

Regard,
Syamantak Omer

Regards,

Syamantak Omer

6 Messages

 • 

146 Points

2 months ago

I have the same issue with R510 Unleashed 200.9.10.4.202:
  • multiple WLANs are configured with own VLAN tags
  • the WLAN with VLAN 10 doesn't pass DHCP requests from the client over AP to the external DHCP server
  • other WLANs with different VLAN tags work fine
  • if on that faulty WLAN, I change VLAN from 10 to e.g. 222, this WLAN works immediately
Tested on 2 clients: android 10, windows 10

6 Messages

 • 

146 Points

Ok, found the issue. The problem was in the mikrotik switch port settings

1 Message

 • 

10 Points

can I know what the port settings should be?