Updated the Ocedo Agent for Windows (Beta)
The Ocedo Agent (for Windows) has been updated and a new installer is available for first-time users. The installer package is branded for your Organization and can be downloaded from the Agent tab within the Organization menu. Existing installations will be updated automatically. Changes:
- Improved location awareness on multi-homed systems.
- Fix display error in Monitor when on-site.
- Fix Monitor application high CPU usage.
- Add robust IPC communication between Monitor and Service.
- Add crash-dump generation.
- Improved Service logging.
Improved table row rendering for specific appliance classes (Gateways/Switches/APs)
There are now individual row templates for each appliance type. The “Overview” menu entry shows a generic view with the serial numbers. Specific templates are used for the “Gateways”, “Access Points” and “Switches” tables:
- In the “Gateways” table, the rows now show STP status, uplinks, connected zones and number of ports (with link to the ports page).
- In the “Access Points” table, the rows now show radio donut graphics, along with the number of clients on each radio.
- In the “Switches” table, the rows now show STP status and number of ports (with link to ports page).
Better control of IP protocol in custom apps
Custom apps can now properly differentiate between TCP and UDP. It is still possible to specify a TCP/UDP combination. In addition, explicit support for GRE and IPSEC (ESP/AH) protocols was added. These will also work for DNAT.
Preparation to display subscription expiry at the Appliances “Overview” table as well as corresponding notifications/alerts (selected CCs only). Please note that – as of now – there’s no kind of license enforcement whatsoever.
Extended Hotspot/Portal support
Support for employee and guest captive portals has been greatly enhanced in this release.
- Support for customized ToS (Terms of Service).
- Customizable logo (image) as well as title, greeting and welcome texts.
- Final redirect now sends clients to original URL.
- Guest device table shows cumulative guest device traffic (since device was registered by the guest)
- Uncluttered portal pages design
- Multiple portals can be configured and used, each with distinctive types, options and customization. The following portal types are available:
- User Portal (BYOD support): Portal used to register employee devices via email or SMS loopback authentication.
- Guest Portal (ToS only): A simple click-through portal that just requires guests to accept the ToS.
- Guest Portal (Authenticated): Portal that requires guests to leave an authenticated identity token (email address, mobile number or social network ID). For social media apps, please check your redirect (callback) URL to be https://eagle.ocedo.cc/portal-social-in. For Google, please activate Google+ API. See http://blog.ocedo.com/social-media-apps/ for details.
- Guest Portal (Voucher): Portal using voucher codes for access. Vouchers can be managed in batches (and exported as CSV lists) or be managed on-the-fly in an extra GUI with separate access credentials. Vouchers support setting the number of devices (MAC addresses), runtime in calendar days and an upper traffic limit.
Automatic VLAN trunking when connecting Ocedo appliances
All LAN ports on Ocedo appliances will now automatically negotiate multizone (aka VLAN trunk or AutoTrunk) ethernet connections when connected to another Ocedo appliance LAN port. This enables true plug-and-play across OcedoGateways, Switches and Access Points. No more brain-wrangling manual tagging of ports. XLAN will be automatically disabled if one or more ports are automatically trunked. While this will be active for all new appliances, existing Gateways and Access Points will have AutoTrunk turned off by default. Check the ports section for Switches and Gateways or the Wired tab for Access Points to enable/disable AutoTrunk.
Smaller Additions, Improvements and Bugfixes
- Added shadow support for upcoming S12 switch model
- Compatibility improvements with third party STP implementations by switching from MSTP (802.1s) to RSTP (802.1w) frame format.
- Dashboard map: Fix a bug that prevented many cities from being correctly located
- Fix appliance reconnect after CC maintenance downtime
- Fix non-working DHCP server if additional IPs are configured
- Fixed handling of VLAN 1 in S24
- Improved accuracy of reporting link layer information gathered via LLDP.
- Improved CC backend performance
- Improved fan control on S24 to prevent the fan from spinning up and down in short succession.
- MTU of uplink interfaces can be adjusted.
- Reduce S24 reconfiguration downtime.
- Registered and unregistered device tables now show the cumulative traffic for each device since midnight (Organization time zone)
Thank you, your comment successfully submitted
your comment has been submited, it might take a while to be moderated.