View Full Version : Discovery Utility
I must have reconfigured my NIC a hundred times over the last few days in conjunction with plugging in and out the three Ubiquiti products I own (Bullets and PicoStation) to test and edit their settings in AirOS. How frustrating to only now realise that I could have saved a lot of time by using the Discovery Utility to find and connect to all three devices without all the hassle :oops:
AFAIK the only reference to the Discovery Utility is a link to the .zip file to download it. It would be great if there were Wiki and/or Knowledge Base articles explaining what the Discovery Utility does!!
Cheers
NetSet Manager is a good tool to change you network settings.
http://www.netsetman.com
danielh
06-19-2009, 07:40 AM
the discovery utility is still pretty limited and wouldn't have saved you from changing your network settings
how do i wish it would allow ip changes! :)
how do i wish it would allow ip changes! http://www.netsetman.com
danielh
06-19-2009, 07:52 AM
i saw.
that's a good first step for an installer in the field, but not quite functional for my purpose
danielh
06-19-2009, 08:09 AM
to be more specific, if i wanted to do that i can just use ifconfig as my system runs under linux.
the idea was to integrate the antenna/network configuration into an existing tool that we use, which we cannot do if the protocol doesn't support it
along5664
06-19-2009, 01:02 PM
do what I do, have one machine that I configure with, have all software on it and have multiple ip addreses on the interface.....My config box now has about 15 different subnets on one interface.....
danielh
06-19-2009, 01:17 PM
as i said, perfectly fine for an installer in the field. my purpose is a bit different.
we supply turnkey systems for an embedded box. sometimes (often) we have to integrate it into an existing customer network, which involves reconfiguring the ip addresses.
our current tool is (slowly) moving toward being able to do it on the fly, single-click style, for tranzeo antennas (we reverse engineered the on-wire protocol, since even tranzeo don't seem to have a spec for that protocol: it's ubicom proprietary). we'd love to be able to do the same with ubiquity
along5664
06-19-2009, 01:22 PM
gotch ya....
the discovery utility is still pretty limited and wouldn't have saved you from changing your network settings
how do i wish it would allow ip changes! :)
You do not need to change your network settings to connect/configure a Ubnt device if you use the Discovery Utility!
I have my NIC set to "Obtain an IP address automatically" and "Obtain DNS server address automatically". Just connected 3 new Ubnt devices to the network (via a switch) and was able to connect to each device and configure it just by using the Discovery Utility.
After doing a little reading, I now understand why this works:
-Ubnt device is connected in its default configuration
-NIC is configured for auto IP and DNS
-NIC hasn't obtained an IP address previously
-neither obtain an IP address so both fall back to an APIPA address in the 169.254.x.x range
-Discovery Utility is used to identify the APIPA address of the Ubnt device
-now we can connect via the APIPA address
When the Ubnt device is in it's default configuration it seems to have a static address (192.168.1.20) as well as an APIPA address. In the Configuration Utility you need to right click the Ubnt device and select "details" to view the APIPA address.
tmulkey2
10-23-2009, 09:19 AM
I normally reassign the mangement IP's if they are bridged an all connected at layer 2 just give each device an IP in the same network, for instance 192.168.1.21, 192.168.1.22, 192.168.1.23. If they are routed, then I just give them each and IP in the individual network, and if I am running between locations I just setup additional IP networks on my laptop.
Example.
I have one unit that is 192.168.1.21 In bulding A, and another that is 192.168.2.21 in building B, and third that is 192.168.3.21, in building C They all have a subnet mask of 255.255.255.0. They will not connect, and I have to work on the settings on each of them locally to try to get them connected. This is why you always setup and preconfigure and test on the ground, but I was lazy and now I am paying the price right.
In Windows XP on my laptop I just click the Start button, then go to "Connect to" and right click it and hit open.
The go to Local Area Connection and right click it and hit properties.
Next Scoll down till you see TCP/IP and then hit properties. I can put the info for the first network in there on that screen.
This much you know if you are changing IP's all the time here is the time saver.
Click the advanced button. You will a section that says IP addresses, you can just click add and put in more 192.168.2.X and 192.168.3.X X=an avialable IP. Now you can hit the units from each location without reseting you laptop each time.
Its a real time saver when you have one that isn't working in the air and you are running back and fourth between locations
wehrwolfzug
08-12-2010, 03:40 PM
Do you have a link to this tool?
Ok, I found the tool. Thanks for the help
http://www.ubnt.com/support/downloads/utilities
