Community Discussions
Explore the latest discussions and community conversations related to this domain.
what is network 8 on my ethernet connection?
Main Post: what is network 8 on my ethernet connection?
/8 vs /24
Main Post:
I have been using some raspberry pi's for program transfer devices for some out of date cnc equipment(can't have windows xp on the network) I am just using the usb otg as a thumb drive then using samba to move files on and off of them. The network is windows based.
I have found that when I set the IP to /8 on the raspberry pi I can only access the devices when connected to the the network with a physical ethernet connection, and when I set it to /24 it becomes accessible to the wireless as well. I was under the impression that the network was in control of this, not the Pi, but apparently I was mistaken.
EDIT: This device has a static ip address and only the /8 or /24 on the end is changed. and this device is connected over a wifi that was set up for shop floor equipment and not the wifi I typically run on.
In the simplest terms, what's going on here? Sorry to ask what is probably a very basic question without enough background info, but I typically do automation with very simple networking and no security to speak of. Thank you
Top Comment: Slash notation is formally called CIDR notation, and is a type of subnet mask notation. Your Pi probably has the DHCP pool set to work in a /24 range, meaning the final octet of the IP address. When you set it to /8, the usable IP range goes from 254 addresses to (254^2)^2 (this math may be wrong) because of the usable IP range being the final 3 octets. The reason that you can connect with a wired connection is probably due to the LAN port being pre-assigned by the DHCP server, but the wireless won't be aware of the rest of the address range.
UniFi Network Application 8.6.9
Main Post:
Announcement Post from Ubiquiti
Overview
UniFi Network Application 8.6.9 increases the VLAN limit on the EFG and UXG- Enterprise and includes the improvements and bugfixes listed below.
Improvements
- Added the ability to filter the AP Density widget in the Dashboard by Radio Bands.
- Added French, Italian, and Portuguese as languages.
- Added Enhanced IoT Connectivity option in the advanced WiFi settings.
- Improved connectivity for IoT devices.
- Requires firmware version 6.6.78 and 7.0.66 or newer.
- Added support for packet captures on WAN ports.
- Improved the latency for loading the Dashboard.
- Improved the user experience for the Dashboard.
- Improved the user search experience within Hotspot Manager.
- Improved searching within Settings.
- Improved feedback in Port Manager when a device exceeds the Tagged VLAN Management limits.
- Renamed AP Analyzer to Radio Manager and improved the user experience.
- Renamed RF Scanning to AirTime Scan and is now available under Radios > Environment.
- Updated validation for WiFi Settings when MLO is enabled. It now requires WPA3/WPA3 Enterprise.
- Updated VLAN limit to 500 for the EFG and UXG-Enterprise.
- Requires UniFi (Cloud) Gateway firmware version 4.1 or newer.
Bugfixes
- Fixed the inability to load the Dashboard after restoring backups in rare cases.
- Fixed an issue where some devices showed the AirTime scan but didn't support it.
- Fixed the inability to upload images in the Hotspot Portal designer in rare cases.
- Fixed an issue where users could configure NetFlow while the adopted Gateway didn't support it.
- Fixed an issue where MAC ACLs didn't function correctly when using any as source or destination.
- Fixed an issue where the Site-to-Site VPN status could be inaccurate on the Viewer page under Insights.
- Fixed the inability to open Settings in rare cases.
- Fixed an issue where some devices didn't list their signal strength in the AP Meshing settings.
- Fixed Packet Capture issues for Access Points using MLO.
- Fixed ISP Speed Test History on setups with a PPPoE connection.
- Fixed the inability to set SFP28 ports with FEC configured to auto-negotiation.
Additional information
- Create a backup before upgrading your UniFi Network Application in the event any issues are encountered.
- See the UniFi Network Server Help Center article for more information on self-hosting a server.
- UniFi Network Application 7.5 and newer requires MongoDB 3.6 and Java 17.
- Version 7.5 till 8.0 supports up to MongoDB 4.4.
- Version 8.1 and newer supports up to MongoDB 7.0.
- UniFi Network Application updates may cause your adopted devices to be re-provisioned.
- Existing UniFi Network Applications must be on one of the following versions to upgrade directly to this version: 8.6.9 and earlier 8.6.x versions. 8.5.6 and earlier 8.5.x versions. 8.4.62 and earlier 8.4.x versions. 8.3.32 and earlier 8.3.x versions. 8.2.93 and earlier 8.2.x versions. 8.1.127 and earlier 8.1.x versions. 8.0.28 and earlier 8.0.x versions. 7.5.187 and earlier 7.5.x versions. 7.4.162 and earlier 7.4.x versions. 7.3.84 and earlier 7.3.x versions. 7.2.97 and earlier 7.2.x versions. 7.1.68 and earlier 7.1.x versions. 7.0.26 and earlier 7.0.x versions. 6.5.55 and earlier 6.5.x versions. 6.4.54 and earlier 6.4.x versions. 6.3.51 and earlier 6.3.x versions. 6.2.26 and earlier 6.2.x versions. 6.1.71 and earlier 6.1.x versions. 6.0.45 and earlier 6.0.x versions. 5.14.25 and earlier 5.14.x versions. 5.13.33 and earlier 5.13.x versions. 5.12.72 and earlier 5.12.x versions. 5.11.52 and earlier 5.11.x versions. 5.10.27 and earlier 5.10.x versions. 5.9.33 and earlier 5.9.x versions. 5.8.30 and earlier 5.8.x versions. 5.7.28 and earlier 5.7.x versions. 5.6.42 and earlier 5.6.x versions. Most earlier versions are also supported for a direct upgrade, going back to 3.1.0.
UniFi Network Native Application for UniFi OS
A specific application version that is only compatible with the UDM, UDR, Express, UCG-Ultra and UCG-Max (running UniFi OS 3.1.6 or newer).
- The UniFi OS update uses the application version that is required for your console.
- The manual update process via SSH requires you to use the compatible package. Incompatible packages will be rejected on installation.
- Older UniFi OS versions (before UniFi OS 3.1.6) on the UDM and UDR still use regular UniFi Network Application for UniFi OS.
Checksums
e98f7bf5fccc0fda819a7e0029df03e1 *UniFi-installer.exe 972db1ff4de8dbbe129f0ea4f862eda3 *UniFi-Network-Server.dmg 30e727c782f27ce566081f1ce4f1501c *UniFi.unix.zip 57a2c35f825ade65a3c65ccded5c7d50 *unifi_sysvinit_all.deb fc8921178f431573d52c69855eebdc51 *unifi-uos_sysvinit.deb e1e612ec5add5d878c359a6c500cf170 *unifi-native_sysvinit.deb 601df32736f41e40a80a3e472450a3e1 *unifi_sh_api ------------------------------------------------------------------------------------------------------------------------ SHA256(UniFi-installer.exe)= 5fc51467fc3225cfe5b0d39d6bd053bc028270b1cceaf6937c3ff5f102d318fe SHA256(UniFi-Network-Server.dmg)= b4f3531e4a7d5a139c9b7b5c36e725bc0eac999f805e66f5fa6ca2f6c55f6b6f SHA256(UniFi.unix.zip)= 8bc8d780327fbdad72d340f3819b1ef71031170ea5e8b2910ebaaffc21c02e7c SHA256(unifi_sysvinit_all.deb)= d34e19244a23db71721440739eaae93f343d13a0d8a43ee00716b77b04ae9c8a SHA256(unifi-uos_sysvinit.deb)= 358cc36f4396e91195bb6f4ca09c154ff8043fe1d0e35f04e27f53a977a5c874 SHA256(unifi-native_sysvinit.deb)= bd6bc01347f9073f29a46cc6c9352b47bb6e1f5688ab15bd484ceb91c8c4cc23 SHA256(unifi_sh_api)= 1791685039ea795970bcc7a61eec854058e3e6fc13c52770e31e20f3beb622ebWould you recommend this release?
- Upvote this post if you recommend this version
- If you'd like, leave a comment about your setup so others can upgrade with confidence
- Downvote this post if you experienced significant issues with it
- Leave a comment (or upvote an existing one) about the issues
- If you have a workaround, please share here
- Remember to file bugs with Ubiquiti
Top Comment: It would be nice if you referenced that the RF scan has moved in app. I had to spend a long time to figure it our on my own. For the people in my shoes, you now go to Radios - The AP you wish to scan - and Airtime scan
New network application release: UniFi Network Application 8.5.6. What's new? (summary)
Main Post: New network application release: UniFi Network Application 8.5.6. What's new? (summary)
Top Comment: Can we please get CNAME support already? What the hell is the hold up?
UniFi Network Application 8.5.6
Main Post:
Announcement Post from Ubiquiti
Overview
UniFi Network Application 8.5.6 adds support for support for NetFlow and Packet Capture on Gateways, and an improved Dashboard user experience including customizable widgets.
Improved Dashboard
Improved the Dashboard experience to provide immediate insight into critical issues, as well as allowing widgets and time ranges to be customized.
- Customize the Dashboard and widgets to focus on the information that is important for you.
- Widgets include Active Channels, AP Radio Overview and Deployment Density and Most Active APs, Clients and Apps.
More widgets will be added in future releases.
NetFlow
Allows capturing and exporting traffic information to a collector.
- Versions 10, 9 and 5 are supported.
- Customize the collector address, port and rates.
- Requires a UniFi (Cloud) Gateway firmware version 4.1 or newer.
NetFlow is not supported on the UniFi Express and UXG-Lite models.
SIEM Activity Logging
Export all or specific System Logs shown on the Network Application to SIEM Servers (remote Syslog) such as Splunk, Microsoft Sentinel, IBM QRadar, and others.
Packet Capture
Capture packets on Gateways and directly download the capture file.
- Capture on specific networks and for a specified duration.
- Requires a UniFi (Cloud) Gateway firmware version 4.1 or newer.
Packet Capture is not supported on the UniFi Express and UXG-Lite models.
Improvements
- Added support for IPsec and OpenVPN Site-to-Site VPNs to Policy Based Routing.
- IPsec requires UniFi (Cloud) Gateway firmware version 4.1 or newer.
- Added SNMP location and contact in the Gateway side panels.
- Added support for configuring multiple CA certificates for RADIUS TLS Profiles.
- Added System Logs for Ports that are dropping large amounts of traffic.
- Added support for WPA2/WPA3 Enterprise mode in the WiFi Settings.
- Added Egress Rate limit option to UniFi (Cloud) Gateways.
- Added support for adjusting WAN DNS verification (internet reachability monitor) in the Gateway side panel.
- Added Integrations section in System Settings.
- Added a Stats section for AP Analyzer.
- Review different performance metrics over time - CPU, Memory, Channel Utilization, TX Retries, and more.
- Added the ability to expand the 2.4GHz channel list.
- Added ability to view the RADIUS Secret.
- Added AP status in Broadcasting APs list in the WiFi settings.
- Added recommendation to disable Ping Conflict Detection for large networks.
- Added neighbors table to the OSPF section.
- Requires UniFi (Cloud) Gateway firmware version 4.0 or newer.
- Improved the Dashboard user experience.
- Improved the AP Analyzer Stats section.
- Improved validation for SNMP settings.
- Allow APs that are adopted to an Express to have more than 3 SSIDs.
- Allow configuring the NAS ID field when RADIUS MAC is enabled in the WiFi settings.
- Improved Site Magic VPN validation.
- Improved remote connections for Network Servers.
- Improved PassPoint settings user experience.
- Improved Channel List settings to prevent blocking all channels in each WiFi band.
- Moved device update settings to Advanced Settings when Control Plane integration is available.
- Renamed the "Inspection" section to "Flows".
- Renamed NeXT AI to Critical in System Logs.
- Updated the left navigation bar.
Bugfixes
- Fixed an issue where some channels were not properly marked as DFS.
- Fixed an issue where VLAN Magic was not available on EFGs.
- Fixed an issue where Masquerade/SNAT/DNAT rules weren't working on EFG, Express, UXG-Lite, and UXG-Pro Gateways.
- Fixed an issue where Auto-scale wasn't accounting for conflicts with WAN interfaces.
- Fixed an issue where the Port Forwarding interface value might not be displayed in rare cases.
- Fixed an issue where the Client settings may not open in rare cases.
- Fixed false System Logs regarding duplicated leases for 0.0.0.0.
- Fixed unexpected provisions for Express devices in rare cases.
- Fixed an issue where the Topology page could lose the configured Display Options.
Additional information
- Create a backup before upgrading your UniFi Network Application in the event any issues are encountered.
- See the UniFi Network Server Help Center article for more information on self-hosting a server.
- UniFi Network Application 7.5 and newer requires MongoDB 3.6 and Java 17.
- Version 7.5 till 8.0 supports up to MongoDB 4.4.
- Version 8.1 and newer supports up to MongoDB 7.0.
- UniFi Network Application updates may cause your adopted devices to be re-provisioned.
- Existing UniFi Network Applications must be on one of the following versions to upgrade directly to this version: 8.5.6 and earlier 8.5.x versions. 8.4.62 and earlier 8.4.x versions. 8.3.32 and earlier 8.3.x versions. 8.2.93 and earlier 8.2.x versions. 8.1.127 and earlier 8.1.x versions. 8.0.28 and earlier 8.0.x versions. 7.5.187 and earlier 7.5.x versions. 7.4.162 and earlier 7.4.x versions. 7.3.84 and earlier 7.3.x versions. 7.2.97 and earlier 7.2.x versions. 7.1.68 and earlier 7.1.x versions. 7.0.26 and earlier 7.0.x versions. 6.5.55 and earlier 6.5.x versions. 6.4.54 and earlier 6.4.x versions. 6.3.51 and earlier 6.3.x versions. 6.2.26 and earlier 6.2.x versions. 6.1.71 and earlier 6.1.x versions. 6.0.45 and earlier 6.0.x versions. 5.14.25 and earlier 5.14.x versions. 5.13.33 and earlier 5.13.x versions. 5.12.72 and earlier 5.12.x versions. 5.11.52 and earlier 5.11.x versions. 5.10.27 and earlier 5.10.x versions. 5.9.33 and earlier 5.9.x versions. 5.8.30 and earlier 5.8.x versions. 5.7.28 and earlier 5.7.x versions. 5.6.42 and earlier 5.6.x versions. Most earlier versions are also supported for a direct upgrade, going back to 3.1.0.
UniFi Network Native Application for UniFi OS
A specific application version that is only compatible with the UDM, UDR, Express and UCG-Ultra (running UniFi OS 3.1.6 or newer).
- The UniFi OS update uses the application version that is required for your console.
- The manual update process via SSH requires you to use the compatible package. Incompatible packages will be rejected on installation.
- Older UniFi OS versions (before UniFi OS 3.1.6) on the UDM and UDR still use regular UniFi Network Application for UniFi OS.
Checksums
378f6e8d0076d24aad31280618a3ab98 *UniFi-installer.exe 8852b6c8a8139ea2c200d05dbc212ce0 *UniFi-Network-Server.dmg 1d40fc5108d4ae73826a3fc2dd502112 *UniFi.unix.zip 5a4677cd44822ac99cff0f40552a51fa *unifi_sysvinit_all.deb ae9c05c82ff29b78ff2be96827ea514a *unifi-uos_sysvinit.deb b2b0ef292c44ecd8f3be82e52b72ceda *unifi-native_sysvinit.deb 601df32736f41e40a80a3e472450a3e1 *unifi_sh_api ------------------------------------------------------------------------------------------------------------------------ SHA256(UniFi-installer.exe)= b0f550aaaf0d177dcdbc5d1ee3ea70483b52a809580bac218ce7ee933356055a SHA256(UniFi-Network-Server.dmg)= b08c4d79b6438a7797c6331123a53f006c9b55d84cccea75615e672844107b2c SHA256(UniFi.unix.zip)= be66c21ee60dfc3940b1b251a80eeef386f751dfba27fba687b76b063854d070 SHA256(unifi_sysvinit_all.deb)= 6690a813c38f6f715c2b37fb36eadff6afa0d81a5b8d9729d4bbd63ac57fb690 SHA256(unifi-uos_sysvinit.deb)= f15cd91294f0275cfe321e367b107c16f90ae5847819efb58d6d2fafc8149c03 SHA256(unifi-native_sysvinit.deb)= 1da18dba3e0a635cd8dbc323c26fbe08654dc7182f50759463baba08a653984f SHA256(unifi_sh_api)= 1791685039ea795970bcc7a61eec854058e3e6fc13c52770e31e20f3beb622ebWould you recommend this release?
- Upvote this post if you recommend this version
- If you'd like, leave a comment about your setup so others can upgrade with confidence
- Downvote this post if you experienced significant issues with it
- Leave a comment (or upvote an existing one) about the issues
- If you have a workaround, please share here
- Remember to file bugs with Ubiquiti
Top Comment: My working theory is that this update is responsible for the increase in packet loss & latency I've been having on my UDM Pro.
Moraes fines X in R$ 8 million after network refuses to provide account data attributed to blogger
Main Post: Moraes fines X in R$ 8 million after network refuses to provide account data attributed to blogger
Top Comment:
Each day for this man lasts 72 hours, it's not possible to find time for all of this.