WLAN clients as Routers not contactable through AirControl?

[clannet]

Hi,
We use clients devices set as routers for isolation between AP's. Air Control discovers these devices fine but displays the IP of the router side not the WLAN side so it is not possible to connect through Aircontrol which is a big pity. Aircontrol must know the WLAN side IP from the discovery process.

It would double the usefullness of this great utility if it could display the discovered WLAN IP

Anyhow...What a giant leap forward in usability!!

Nick

[UBNT-Thomas]

Hi Nick,

You can manually override the management IP address in the connect dialog (make sure to expand the device details), have you already tried this?

[sirthor]

may i chime in hear. this is important. we are typically on the wan side of things. manually connecting a couple of hundred cpe a long time. after connecting a few that way they still show up with the lan ip. and the web gui still lauches to that ip.

another bug i'm seeing is that tabbing from the user id to the password causes the cursor to only appear shortly. must use the mose to get the cursosr back in the dialog box.

allowing us to change the default user would be a nice fix.

[wisptec2]

Ya, I just ran in to this problem as well. I can't go thur a ton of subs just to add them. The discovery tool finds them fine but not AirControl

[UBNT-Thomas]

Ya, I just ran in to this problem as well. I can't go thur a ton of subs just to add them. The discovery tool finds them fine but not AirControl

AirControl should have the same behavior WRT discovery scan than the tool. How long was the server running? Did you also try to hit the scan button manually? How many devices were found by AirControl, how many by Discovery Tool. More detailed info will help us to sort out issues quicker.

[wisptec2]

AirControl should have the same behavior WRT discovery scan than the tool. How long was the server running? Did you also try to hit the scan button manually? How many devices were found by AirControl, how many by Discovery Tool. More detailed info will help us to sort out issues quicker.

Sorry Thomas, AirControl finds all my units but the CPEs that are in router mode come up with the LAN side IP Address not the WAN IP. So I cant log in to them with the 192.168.XXX.XXX sceam when the WAN is 10.XXX.XXX.XXX.
But the Discovery Tool finds all units just like AirControl but it gives you the WAN IP not the LAN. Hope that helps.

[UBNT-Thomas]

Sorry Thomas, AirControl finds all my units but the CPEs that are in router mode come up with the LAN side IP Address not the WAN IP. So I cant log in to them with the 192.168.XXX.XXX sceam when the WAN is 10.XXX.XXX.XXX.
But the Discovery Tool finds all units just like AirControl but it gives you the WAN IP not the LAN. Hope that helps.

Before you connected the device in AirControl, was it showing the WLAN IP (discovery functionality should be identical)? Was it turned into the LAN IP after connect, when the device started to report stats?

If you are not sure, disconnect and delete the device entry in AirControl, then scan again and check what address you see initially. I suspect that the address is reverted to the LAN address after connect. I will see to reproduce this next week and try come up with a fix ASAP.

[wisptec2]

Before you connected the device in AirControl, was it showing the WLAN IP (discovery functionality should be identical)? Was it turned into the LAN IP after connect, when the device started to report stats?

If you are not sure, disconnect and delete the device entry in AirControl, then scan again and check what address you see initially. I suspect that the address is reverted to the LAN address after connect. I will see to reproduce this next week and try come up with a fix ASAP.

No, it showes the LAN IP upon scan

[UBNT-Thomas]

Hmmm, and the discovery tool shows the WLAN IP? What version of discovery tool are you using?

[sirthor]

when i scan using the discovery tool i get the LAN IP. of course when going to the web GUI it gives me the option of which IP to use.

[jjllc]

AirControl should have the same behavior WRT discovery scan than the tool. How long was the server running? Did you also try to hit the scan button manually? How many devices were found by AirControl, how many by Discovery Tool. More detailed info will help us to sort out issues quicker.

The discovery tool scanned the network and also came up with the lan ip address. It does however also discover the wlan ip also. I programed all of my wlan addresses in and I was able to pull up all the features on air control but it will not save the ip address for connecting later. You have to put it in each time you want to connect to the unit. It would be nice to get that changed.

I have also noticed that I have to double click the password field to type in the password and that you cannot just tab through. That becomes a little cumbersome.
But overall this management tool rocks!

[UBNT-Thomas]

Thanks, I have all the info needed. Discovery provides all IP addresses, AirControl needs to figure out which one actually connects to the unit. At the moment, it simply picks the first address, which happens to be the LAN address. Expect a fix later this week.

[UBNT-Thomas]

The discovery tool scanned the network and also came up with the lan ip address. It does however also discover the wlan ip also. I programed all of my wlan addresses in and I was able to pull up all the features on air control but it will not save the ip address for connecting later. You have to put it in each time you want to connect to the unit. It would be nice to get that changed.

OK, once you connected the units, why would you need to connect them again? AirControl will remember the connections and restore them on restart. So you should NOT have to do what you indicate. Please provide more detail so that we can sort out the real issue.

[ddecoria]

Hi, just wanted to confirm that I am having the same issue. Looking forward to the fix.

Thanks,
Dustin

[UBNT-Thomas]

Update with patch instructions available, please see:

http://www.ubnt.com/forum/showpost.php?p=51414&postcount=1

Let me know how it works for you.

[wisptec2]

Is this the IP address fix or the Server 2003 fix?

[UBNT-Thomas]

Fix is for WLAN IP Address - The other issue was not server 2003 specific but a Java VM installation related quirk, workaround info is posted on the same thread, should you run into it.

[davedee]

That fix works for me.

Thats a very useful application for network management and look forward to further features!

[drwho17]

I'm using PPPoE to assign the WLAN IP address, I'm not seeing it in the latest aircontrol build. I only see the LAN IP address.

[wisptec2]

Thanks for the fast fix Thomas.
Works grate!!!

[sirthor]

fixed some of the issues. the wanip needs to be the default to truly be useful. still can't do batch updates to clients. must go through web gui manually. was able to batch update 3.3.2 devices when tried to connect. 3.4 and 5.rc2 must do the manual thing. dont always get a connection with the updated devices. went about half with a connection and half i had to manually enter the wanip.

[lukkes]

i have no that problem, im using the last version, and al my systems is identified by the wan ip, all is working as a router too