IP address issue for end users


We added 22 access points to existing network. Setup is like this : 10 ap's are part of vlan 80 in building-1 Remaining 12 ap's part of vlan 81 in building-2 Users connecting to ap's ( vlan 80 )should get IP from vlan 90 Users connecting to ap's (vlan 81) should get IP from vlan 91 Now the issue is when we are in building-1 end user is getting IP , when he is moving to building 2 user not getting IP, but few users at building-2 are getting IP. As a resolution I have done the below: Grouped building-1 ap's and users in a single vlan 80 Grouped building-2 ap's and users in a single vlan 81 Now it seems to be better , but not sure is this correct resolution can anyone guide me.

10 replies

Userlevel 7
Hi,

it's function as designed, the feature is called "Permit Inter-WLAN Service Roaming".

Here a post that explains it...
https://community.extremenetworks.com/extreme/topics/wireless_location_issues
https://gtacknowledge.extremenetworks.com/articles/Solution/Client-is-not-getting-a-new-Role-and-IP-...

Just turn of "Permit Inter-WLAN Service Roaming" in the advanced option of the WLAN Service and the clients will use the VLAN in this building.

-Ron
Userlevel 7
Are you using the same SSID for both services? Try disabling Inter-WLAN Service Roaming in the advance tab on each WLAN-Service.
Userlevel 7
Also you should be aware that we are at the mercy of the client device to do a clean dhcp renew when flipping subnets...
Doug wrote:

Also you should be aware that we are at the mercy of the client device to do a clean dhcp renew when flipping subnets...

I've not created topology for AP's , I created two different topologies for end users of either of the buildings. I've created a single vlan (vlan 80) for AP's in both the buildings with dhcp scope..... will the resolution be same in this case also...
Userlevel 7
Doug wrote:

Also you should be aware that we are at the mercy of the client device to do a clean dhcp renew when flipping subnets...

Yes, the resolution would be the same.
Doug wrote:

Also you should be aware that we are at the mercy of the client device to do a clean dhcp renew when flipping subnets...

Issue resolved getting IP address, but not able to access internet. In Building-1 got ip and able to access internet but when moved to building-2 got Building-2 IP but not able to access internet.
Userlevel 7
Doug wrote:

Also you should be aware that we are at the mercy of the client device to do a clean dhcp renew when flipping subnets...

When you are connected to the network that does not work, can you ping the clients default gateway? Does it reply?
Doug wrote:

Also you should be aware that we are at the mercy of the client device to do a clean dhcp renew when flipping subnets...

yes, i am able to ping default gateway of the end user vlan
Userlevel 7
Doug wrote:

Also you should be aware that we are at the mercy of the client device to do a clean dhcp renew when flipping subnets...

How about DNS resolving, is that working too? Try doing an nslookup on something. Also are there any policy rules that are different on one VNS versus the other? If the policy on the controller looks good and you are making it to the default gateway, chances are the issues are not with the wireless....
Doug wrote:

Also you should be aware that we are at the mercy of the client device to do a clean dhcp renew when flipping subnets...

We are using public DNS, end user gets public DNS, name resolution is not happening..... There are no different policies....... I again checked what I found is few users are able to browse internet and few cannot. In building-2 , even I two was able to access internet when I went to building-2 to cross check again. Totally strange..

Reply