❗️Toto je původní verze internetového fóra ISPforum.cz do února 2020 bez možnosti registrace nových uživatelů. Aktivní verzi fóra naleznete na adrese https://telekomunikace.cz
Aircontrol 2 je von....
nansdílel by někdo link ? nemám práva na odkaz ... asi nebudu sám ...
0 x
- midnight_man
- Příspěvky: 3680
- Registrován: 14 years ago
Some documentation and notes for AirControl2 may be found here:
http://wiki.ubnt.com/AirControl2
A three minute video demonstration of the new functionalty is available here:
http://dl.ubnt.com/aircontrol2/beta1/beta1.html
Notes:
It is not recommended to test in a production environment. Test only on a small subset of devices, since there may be issues.
This is a work in progress. We are continuously working on new functionality.
More configuration options will be added with future releases
AirControl2 uses a client/server app architecture. You will need to install the server software on one computer, and then run the client software on any computers accessing the server.
For M Series devices, v5.3+ firmware is required for mass-configuration. All versions support monitoring, reboot, firmware updates.
Mass configuration changes are not supported on legacy devices yet.
AC2 relies strongly on topological relations. Adding devices beyond L2 is done differently in AirControl2 than in AC 1.x. Please refer to corresponding sections in the guide for more info.
Known Issues
(We will keep this section open with new issues that are found)
Please evaluate, and let us know if you have any suggestions, bug reports, etc. Standard UBNT Beta rules apply: http://www.ubnt.com/beta
Please create a new thread for any new issues, comments, or discussions.
Download:
Windows: http://www.ubnt.com/downloads/aircontro ... 24-win.exe
Ubuntu: http://www.ubnt.com/downloads/aircontro ... ubuntu.deb
Mac: http://www.ubnt.com/downloads/aircontro ... -MacOS.jar
http://wiki.ubnt.com/AirControl2
A three minute video demonstration of the new functionalty is available here:
http://dl.ubnt.com/aircontrol2/beta1/beta1.html
Notes:
It is not recommended to test in a production environment. Test only on a small subset of devices, since there may be issues.
This is a work in progress. We are continuously working on new functionality.
More configuration options will be added with future releases
AirControl2 uses a client/server app architecture. You will need to install the server software on one computer, and then run the client software on any computers accessing the server.
For M Series devices, v5.3+ firmware is required for mass-configuration. All versions support monitoring, reboot, firmware updates.
Mass configuration changes are not supported on legacy devices yet.
AC2 relies strongly on topological relations. Adding devices beyond L2 is done differently in AirControl2 than in AC 1.x. Please refer to corresponding sections in the guide for more info.
Known Issues
(We will keep this section open with new issues that are found)
Please evaluate, and let us know if you have any suggestions, bug reports, etc. Standard UBNT Beta rules apply: http://www.ubnt.com/beta
Please create a new thread for any new issues, comments, or discussions.
Download:
Windows: http://www.ubnt.com/downloads/aircontro ... 24-win.exe
Ubuntu: http://www.ubnt.com/downloads/aircontro ... ubuntu.deb
Mac: http://www.ubnt.com/downloads/aircontro ... -MacOS.jar
Naposledy upravil(a) midnight_man dne 24 Aug 2012 22:28, celkem upraveno 1 x.
0 x
404 Not Found The resource could not be found. - také jsem na tento link narazil, žel bohu asi přetížený server nebo nějaký průser
0 x
midnight_man píše:Download:
Windows: http://www.ubnt.com/downloads/aircon...120824-win.exe
Ubuntu: http://www.ubnt.com/downloads/aircon...824-ubuntu.deb
Mac: http://www.ubnt.com/downloads/aircon...0824-MacOS.jar
Chces rict, ze ti ty linky funguji nebo jsi to jen okopcil?
0 x
jooo milej pane, ten odkaz si zkopiroval spatne
uz to mam stazeny a jde se testovat ....
FYI : http://www.ubnt.com/downloads/aircontro ... 24-win.exe
ale ze mi to dalo zabrat .... muhehe

FYI : http://www.ubnt.com/downloads/aircontro ... 24-win.exe
ale ze mi to dalo zabrat .... muhehe
0 x
- midnight_man
- Příspěvky: 3680
- Registrován: 14 years ago
opravene,
neskopirovalo to odkazy ale len skrátenú verziu viditelneho linku
neskopirovalo to odkazy ale len skrátenú verziu viditelneho linku

0 x
midnight_man píše:opravene,
neskopirovalo to odkazy ale len skrátenú verziu viditelneho linku
i presto diky...
0 x
já sem aasi slepej ale nevidim kam mam zadat ip range pro hledání zařízení pod více rozsahama ip adres ...
0 x
-
- Příspěvky: 278
- Registrován: 13 years ago
OT: Nejedna se o fake? Na UBNT foru nekdo probiral fake release, kterj ukaze jen AirControl home page.
Jede to.
Jede to.
Naposledy upravil(a) thanui.linux dne 26 Aug 2012 11:19, celkem upraveno 1 x.
0 x
-----------------------------------------------------------
RBcka i UBNT mají své přednosti - využívám obojí
RBcka i UBNT mají své přednosti - využívám obojí
Topology resolution overview
Adding devices to the topology tree
Adding devices automatically
Run Discover task by clicking on the circular arrow button below the AirControl2 logo at the top-left corner of the window.
If "Resolve topology" option is checked, the task will try to resolve topological relations among discovered devices. To do that it will need to login into each discovered device and extract network information by executing commands on it via SSH. User will be prompted to enter credentials for all the devices.
In the task window user can choose from which device in the topology discovery/resolution needs to be started. If "Topology Root" is chosen, discovery/resolution start from AC2 server by sending Layer-2 device-discovery broadcasts.
If discovery/resolution is started from a specific device in topology, the task will login into the device and execute discovery on that device via SSH 'discover' command. This approach is useful for discovering devices residing on subnets different from the ones that AC2 server running on.
Adding devices manually
If a device is not reachable through Layer-2 discovery, operator needs to add it manually by invoking context menu (using "right-click") on a "Topology root" or any device inside the topology tree and selecting "Add device manually" command. In the displayed add-device task panel operator needs to specify:
IP address of the device (DNS-name resolution currently not supported)
SSH port and SSH credentials
Membership type
Membership type defines how device discovery and topology resolution is performed with respect to this device. There are following types:
"Regular subnet member" - device resides on the same local subnet with respect to it's parent node
"Gateway to subnet" - device is on a different subnet with respect to it's parent. It is used as a "gateway" for discovering devices on it's subnet, as mentioned above the "discover" shell command will be executed by AC2 on the gateway device .
"NAT Gateway to Subnet" - similar to the "Gateway to subnet", such device is used as a gateway for discovering devices downstream of it. Additionally SSH tunnels are created on this device in order to reach/control the devices downstream of it, since those reside behind NAT. The NAT gateway device however needs to be accessible via specified IP/SSH-port combination from AC2 server directly.
IP-Range scan (or the lack of it)
Since AC2 possesses complete topology information, scanning IP ranges to discover devices normally becomes redundant (as opposed to AirControl 1.x). It is enough to add a Gateway or NAT-Gateway device manually and AC2 discovery/resolution task will gather all devices/topology information downstream of the gateway device automatically.
However, there are some cases when IP range-scan still has benefits: when adding a batch of devices/routers which are accessible via public IP and have large networks behind them. Range-scan task is on the road-map of AC2.
Adding devices to the topology tree
Adding devices automatically
Run Discover task by clicking on the circular arrow button below the AirControl2 logo at the top-left corner of the window.
If "Resolve topology" option is checked, the task will try to resolve topological relations among discovered devices. To do that it will need to login into each discovered device and extract network information by executing commands on it via SSH. User will be prompted to enter credentials for all the devices.
In the task window user can choose from which device in the topology discovery/resolution needs to be started. If "Topology Root" is chosen, discovery/resolution start from AC2 server by sending Layer-2 device-discovery broadcasts.
If discovery/resolution is started from a specific device in topology, the task will login into the device and execute discovery on that device via SSH 'discover' command. This approach is useful for discovering devices residing on subnets different from the ones that AC2 server running on.
Adding devices manually
If a device is not reachable through Layer-2 discovery, operator needs to add it manually by invoking context menu (using "right-click") on a "Topology root" or any device inside the topology tree and selecting "Add device manually" command. In the displayed add-device task panel operator needs to specify:
IP address of the device (DNS-name resolution currently not supported)
SSH port and SSH credentials
Membership type
Membership type defines how device discovery and topology resolution is performed with respect to this device. There are following types:
"Regular subnet member" - device resides on the same local subnet with respect to it's parent node
"Gateway to subnet" - device is on a different subnet with respect to it's parent. It is used as a "gateway" for discovering devices on it's subnet, as mentioned above the "discover" shell command will be executed by AC2 on the gateway device .
"NAT Gateway to Subnet" - similar to the "Gateway to subnet", such device is used as a gateway for discovering devices downstream of it. Additionally SSH tunnels are created on this device in order to reach/control the devices downstream of it, since those reside behind NAT. The NAT gateway device however needs to be accessible via specified IP/SSH-port combination from AC2 server directly.
IP-Range scan (or the lack of it)
Since AC2 possesses complete topology information, scanning IP ranges to discover devices normally becomes redundant (as opposed to AirControl 1.x). It is enough to add a Gateway or NAT-Gateway device manually and AC2 discovery/resolution task will gather all devices/topology information downstream of the gateway device automatically.
However, there are some cases when IP range-scan still has benefits: when adding a batch of devices/routers which are accessible via public IP and have large networks behind them. Range-scan task is on the road-map of AC2.
0 x
Kliknes pravym na root topology a tam das zadat ip ak nastavis defaultnu moznost tak hlada zariadenia na rovnakom subnete....neviem ci je moznost zadavat rozsah ale pravdepodobne nie.....
0 x
vam to nekomu jede na win? 2008 server x64 r2? konkretne kdyz se mi to povede nahodit tak se na to jenom jednou naloguji a to po instalaci. Ale jinak se newim jak na to dostat.. localjost:9080 mi ukazuje jenom vzaz ze web jede 
ale zadna administrace se tam provist neda? Jak to funguje? Dik

ale zadna administrace se tam provist neda? Jak to funguje? Dik
0 x
Ferenc Richard
info[at]RFservis[dot]cz
+420 774 164 886
Vystavba telek. reseni LTE, 3G, 2G [HUAWEI,NOKIA..]
Mikrovlny ericsson, huawei, ray, alcoma...
Vytyčování met. a opt. siti o2
Servis a udrzba mob. a fix stanic.
Poskytovani telek. sluzeb Olomoucky kraj.
info[at]RFservis[dot]cz
+420 774 164 886
Vystavba telek. reseni LTE, 3G, 2G [HUAWEI,NOKIA..]
Mikrovlny ericsson, huawei, ray, alcoma...
Vytyčování met. a opt. siti o2
Servis a udrzba mob. a fix stanic.
Poskytovani telek. sluzeb Olomoucky kraj.
-
- Příspěvky: 278
- Registrován: 13 years ago
Jak jsem pochopil, tak to uz nejede pres prohlizec ale pres kliose. Z prohlizece to pojede casem.
0 x
-----------------------------------------------------------
RBcka i UBNT mají své přednosti - využívám obojí
RBcka i UBNT mají své přednosti - využívám obojí