[Thread Ufficiale] Ubiquiti UniFi - Piattaforma multiuso - routing/switching/wireless

[PsychoWood]

Originariamente inviato da emax81

Me se sono accorto dopo....solo che avevo quasi finito e non avevo voglia di rifarla da capo

Credo succeda praticamente a tutti (presente!).

Per quanto riguarda il firmware 4.3.54dev:

• Added back end for custom host-uniq for PPPoE.

Confermo la fix sullo host-uniq, ora riesco a collegarmi direttamente all'ONT della FFTH senza usare la Vodafone station (per la connessione dati).

Ora devo solo capire come fare un bridge sulla VLAN voce verso la WAN2 così da poter usare la connessione voce, ma siamo a metà dell'opera.

[emax81]

Domanda per gli utilizzatore di Cloud Key : ci si può installarci sopra Pi-Hole ?

[PsychoWood]

Originariamente inviato da Pigr8

ma le opzioni dell'usg son tutte li? O_o

Intendi dell'interfaccia web? Quella WebUI serve in pratica solamente per poter configurare lo USG con l'indirizzo IP giusto prima di inserirlo in rete locale (cosa un po' rognosa nel caso si avesse una LAN non su 192.168.1.x). Da lì in avanti viene fatto tutto tramite lo UniFi Controller.

[emax81]

UniFi 5.5.21 Stable Candidate has been released

Notes:

• As always, make a backup prior to upgrading.
• Windows users must have x64 Java installed as we only support 64 bit webRTC library. Please see HERE and download the missing version (64bit offline Windows install package).
• You cannot re-use a VLAN ID for dynamic VLAN if it is set as a static value for another SSID on the same AP. So, if I have a SSID set to use VLAN 10, I cannot use VLAN ID 10 for RADIUS controlled VLAN users as those users will not get an IP.
• Smart Queue QoS is similar to the implementation as in EdgeOS (see HERE). Please note that DPI will not work when using QoS, as traffic will not be offloaded. It's also worth noting that maximum throughput will be affected when using QoS, as traffic is not offloaded. There are some rough guidelines in the article linked above.
• DFS channels can not be used for wireless uplink in the US. Please use non-DFS channels if you need to use wireless uplink on dual band UAPs.
• Official UniFi MIBs can be downloaded from HERE and HERE (those are 2 different files).
• We no longer support Java version 6, it needs to be 7 or later. We recommend Java version 8.
• Features like airtime fairness, bandsteering, load balancing and minimum RSSI are default disabled. If you need them you need to go to Settings>Site and check Enable advanced features.
• If you previously used Google Maps for a site map, then you have to enable this feature again by adding an API key. This is done under Settings>Controller. There is a linked guide with instructions.

Important Notes:
The initial database migration will take longer than normal. It is expected to see mongo using most, if not all, of the available CPU cycles during this process. Please be patient, this process could easily take 15+ minutes, depending on the amount of historical stats, as well as the system specs. As always, err on the side of caution, and make a backup before upgrading.

Known Issues
Manual site-to-site VPN status is not reflected on the UniFi dashboard widget. Currently it will look like it's offline, even when the tunnel is up.

Controller bugfixes/changes from 5.5.20:

• MAC address input validation improvements (reported HERE).
• Fix a provisioning issue which would clear USG WAN settings.
• Improvements for Ethernet bonding support on UAPs (on supported devices).
• Improve topology view when using wireless uplinks.
• Allow setting device credentials during setup and new site wizards.
• Security improvements.
• Various backend fixes and improvements.

Firmware changes from 3.8.2/4.3.41:

• [UAPG3] Enable DFS on UAP-AC-SHD.
• [UAPG2] Fix a STA connectivity issue, when a 2nd gen AP is the wireless downlink AP to a wired 3rd gen AP.
• [UAPG2] Fix an issue causing less than expected throughput in recent releases.
• [UAP] Fix a bug in uplink-monitor.
• [USW] Add 802.1X MAC auth bypass support.*
• [USL2] Add PSU fail detection support.*
• [USG] Update numerous subsystems to the latest EdgeRouter 1.9.7. This includes a number of bug fixes made in EdgeRouter in the past 2-3 years, though largely not relevant to USG use cases. IPv6 related fixes the primary area where people have encountered relevant problems.
• UPnP, PPTP client, DHCP server, Quagga, PPPoE and PPP handling, DHCP client, conntrack, configuration subsystem, operational commands subsystem, IPv6 router advertisement service, keepalived, NAT configuration and handling, OpenVPN configuration subsystem
• [USG] Increased maximum NDP and ARP cache table sizes, and added back end controls for ARP and NDP timeouts.
• [USG] Guest control bug fixes and improvements - added locking and rewrote the back end functions to greatly improve performance and reliability. Fixes all known guest control issues on USG, including "too many redirects" issues.
• [USG] Fix memory leak in VPN status reporting, eventually leading to disconnects of USG from controller.
• [USG] DPI improvements
• Back end additions for DPI blocking.
• Stats clearing fix
• Signature update improvements
• [USG] Added contiguous option for firewall schedules (for coming controller feature).
• [USG] RADIUS server permissions fix for log files, certificates and accounting data.
• [USG] Update additional load-balance components from latest EdgeRouter.
• [USG] Fix source NAT over-matching from port-forward hairpin-nat. Previously all traffic sourced from the LAN subnet leaving the LAN interface would be translated, now appropriately narrowed to match only port forward hairpin traffic.
• [USG] Send PADT on PPPoE disconnect, fixing edge case PPPoE reconnect failures where ISP is using a buggy PPPoE relay that doesn't detect loss of PPP session.
• [USG] Add contiguous option to back end for firewall rule schedules.
• [USG] Remove unnecessary character restrictions on site to site IPsec pre-shared keys.
• [USG] Fix "dpi.dpi_pktinfo_send(): failed to send UGW wevent" log spam.
• [HW] Fix the issue preventing SSH login when the interface IP changed.
  *controller support pending

For USG we recommend using 4.3.54dev

link

[vanel86]

Info dal thread beta su 4.3.54dev

Doktornotor wrote:
@UBNT-cmb*- any ETA on IPv6?

5.7.x controller (5.6.x is feature frozen now).*

Quindi possiamo smettere di pregare per ipv6 via gui, prima di ottobre non ci sono speranze per 5.7

psychowood wrote:
*
Wondering if we should expect a new USG sooner or later (and I've just bought the 3P -_-' )
*
USG-XG-8 will be available in beta*store soon.*

USG-XG-8 a breve

-----

Come rilevato da @silibum sul forum UBNT il webmgmt viene esposto SU TUTTI GLI IP del vostro USG. Impostate blocchi via firewall o eventualmente vi sgamano la pass via bruteforce.

[emax81]

none

[emax81]

UniFi 5.6.14 Testing has been released

Notes:
As always, make a backup prior to upgrading.
Windows users must have x64 Java installed as we only support 64-bit WebRTC library. Please see HERE and download the missing version (64bit offline Windows install package).
You cannot re-use a VLAN ID for dynamic VLAN if it is set as a static value for another SSID on the same AP. So, if I have a SSID set to use VLAN 10, I cannot use VLAN ID 10 for RADIUS controlled VLAN users as those users will not get an IP.
Smart Queue QoS is similar to the implementation as in EdgeOS (see HERE). Please note that DPI will not work when using QoS, as traffic will not be offloaded. It's also worth noting that maximum throughput will be affected when using QoS, as traffic is not offloaded. There are some rough guidelines in the article linked above.
DFS channels can not be used for wireless uplink in the US. Please use non-DFS channels if you need to use wireless uplink on dual band UAPs.
Official UniFi MIBs can be downloaded from HERE and HERE (those are 2 different files).
We no longer support Java version 6, it needs to be 7 or later. We recommend Java version 8.
Features like airtime fairness, bandsteering, load balancing and minimum RSSI are default disabled. If you need them you need to go to Settings>Site and check Enable advanced features.
If you previously used Google Maps for a site map, then you have to enable this feature again by adding an API key. This is done under Settings>Controller. There is a linked guide with instructions.

Important Notes:
The initial database migration will take longer than normal. It is expected to see mongo using most, if not all, of the available CPU cycles during this process. Please be patient, this process could easily take 15+ minutes, depending on the amount of historical stats, as well as the system specs. As always, err on the side of caution, and make a backup before upgrading.
The controller will not start if it is set to bind to a privileged port (<1024), as it now runs as a non-root user. There are various ways you can fix this immediately, like authbind, although there may be better ways. We're considering options here.
If your controller is running on a UniFi Cloud Key (UCK), make sure it is on firmware 0.6.4 or later, otherwise the controller will not start. This firmware is available via the normal upgrade mechanism found in the controller or it's local management page. Make sure to make a backup before upgrading the UCK firmware, as you'll need it to restore after, and it's good to have a backup on hand before any controller upgrade.

Known Issues:
AirTime will not work if a radio is disabled and/or there isn't any SSID present. This will be fixed in a future release. If you enable it, and it still isn't working, then you may need to force a refresh without cache.
If you start both a 2.4GHz and 5GHz scan in quick succession, then it will fail.
Manual site-to-site VPN status is not reflected on the UniFi dashboard widget. Currently it will look like it's offline, even when the tunnel is up.

New Features:
Add Switch Port Profiles.
Add USG Performance Graphs.

Controller bugfixes/changes from 5.6.12:
Allow user to set default SSH device password in Wizard.
Display board revision in Property Panel.
Display fixed IP only for clients with enabled fixed IP option.
Add sorting to Admin table.
Add VAP BSSID filter to devices page.
Allow network to change purpose between corporate and guest.
Change default DHCP mode to DHCP Server.
Show advanced DHCP options only for DHCP Server mode.
Fix cloning destination ports form forward ports in Port Forwarding settings.
Do not validate WAN VLAN if VLAN is not enabled.
Disable AirTime tool when no SSID is configured.
Disable RF Scan tool for AP with wireless uplink.
Fix opening Property Panel after reloading a page.
Fix messages that USG is required.
Enable VPN client pull DNS by default.
Add missing Outdoor section for UAP-IW, UAP-AC-IW, and UAP-AC-IW-PRO.
Add support for MS-CHAPv2 to Hotspot RADIUS.
Improve Facebook WiFi redirection settings.
Add Beta tag to Facebook WiFi.
Don't show the "not using configured channel" icon when the radio is disabled.
Extend "Use Secure Portal" tooltip message to display info about OS X Captive Network Assistant limitation.
Improve validation of admin name in Invite Admin form.
Fix number of active clients in clients filter on Clients page.
MAC address input validation improvements (reported HERE).
Do not allow for duplicates in firewall's groups.
Fix empty select boxes.
Fix select boxes in FireFox.
Rename "Automatically upgrade firmware" label to "Automatically upgrade AP firmware".
Renamed "Logging" to "Notifications" Settings.
Improvements for Ethernet bonding support on UAPs (on supported devices).
Update and improve translations.
Various backend fixes and improvements.

Firmware changes from 3.8.7:
[UAPG2] Initial improvements to Mesh V3.*
[UAP] Add support for multiple WLAN schedule blocks per day.*
[UAP] Various 802.11r fixes, including the crash when enabled on an open VAP.
[UAP] Various backend changes and bugfixes.
[USL2] Various backend changes.
*controller support either varies or is pending.

For USG we recommend using 4.3.54dev

link

[emax81]

8/15

[PsychoWood]

Originariamente inviato da emax81

8/15

Eh?

[emax81]

Ubiquiti's next platform

[vanel86]

Tut tut, smettetela con ste minchiate

https://www.ubnt.com/edgemax/edgerouter-infinity/

Ecco lo scheletro del prossimo usgpro, 1.6k $

La finestrella comparativa tra ERL3 e ERXG fa molto "ti piace vincere facile" soprattutto visto che uno costa 1600$ e l'altro ne costa 100$

[PsychoWood]

Originariamente inviato da emax81

Ubiquiti's next platform

In che contesto? Altra roba oltre a UNMS?

[vanel86]

ER‑8‑XG passa da beta a produzione. Normalmente fintanto che gli ER sono in beta non esce il corrispettivo USG, quindi possiamo aspettarci USG-8-XG a breve nel beta store

[emax81]

Originariamente inviato da PsychoWood

In che contesto? Altra roba oltre a UNMS?

Dovrebbe essere qualcosa in stile AmpliFi :cubetto camera con WiFi classe AC e bluetooth

[vanel86]

Originariamente inviato da emax81

Dovrebbe essere qualcosa in stile AmpliFi :cubetto camera con WiFi classe AC e bluetooth

Basta che non sia come amplifi per la banda, ci sta gente sui vari smallnet e reddit con le fiaccole e i forconi in quanto non riesce a superare i 400-500mbps di traffico esterno

[emax81]

Originariamente inviato da vanel86

Tut tut, smettetela con ste minchiate

mi piace "stimolare" il Thread

[PsychoWood]

Originariamente inviato da vanel86

ER‑8‑XG passa da beta a produzione. Normalmente fintanto che gli ER sono in beta non esce il corrispettivo USG, quindi possiamo aspettarci USG-8-XG a breve nel beta store

Speriamo vada meglio dello US-24-XG...

[PsychoWood]

Originariamente inviato da vanel86

La finestrella comparativa tra ERL3 e ERXG fa molto "ti piace vincere facile" soprattutto visto che uno costa 1600$ e l'altro ne costa 100$

Tra poco confronteranno con ER4 e ER6. Non che cambi poi molto...

[emax81]

Originariamente inviato da emax81

Grazie a tutti per la pazienza...io con le righe di comando non ci vado molto a genio

Copiato comunque il config.gateway.json che mi ha passato il tecnico del supporto UBNT,


ma sto maledetto modem non lo raggiungo ; questo è il contenuto :

{
        
        "interfaces": {
                "ethernet": {
                        "eth0": {
                                "firewall": {
                                        "in": {
                                                "name": "WAN_IN"
                                        },
                                        "local": {
                                                "name": "WAN_LOCAL"
                                        },
                                        "out": {
                                                "name": "WAN_OUT"
                                        }
                                }
                               
                        }
                        
                }
               
        },
       
        "protocols": {
                "static": {
                        "interface-route": {
                                "192.168.0.0/24": {
                                        "next-hop-interface": {
                                                "eth0": {
                                                        "distance": 1
                                                }
                                        }
                                }
                        }
                }
        },
        "service": {
               
                "nat": {
                        "rule": {
                                "6001": {
                                        "description": "MASQ Modem",
                                        "log": "disable",
                                        "destination": {
                                        },
                                        "outbound-interface": "eth0",
                                        "protocol": "all",
                                        "source": {
                                               
                                        },
                                        "type": "masquerade"
                                }
                               
                        }
                }
                
        }
       
        
}

Vi aggiorno su questo fronte : nuovo config.gateway.json (si è collegato in remoto il supporto di UBNT sulla mia macchina)

{
        
        "interfaces": {
                "ethernet": {
                        "eth0": {
						        "address": [
                                        "192.168.0.2/24"
                                ],
                                "firewall": {
                                        "in": {
                                                "name": "WAN_IN"
                                        },
                                        "local": {
                                                "name": "WAN_LOCAL"
                                        },
                                        "out": {
                                                "name": "WAN_OUT"
                                        }
                                }
                               
                        }
                        
                }
               
        },
       
        "protocols": {
                "static": {
                        "interface-route": {
                                "192.168.0.0/24": {
                                        "next-hop-interface": {
                                                "eth0": {
                                                        "distance": 1
                                                }
                                        }
                                }
                        }
                }
        },
        "service": {
               
                "nat": {
                        "rule": {
                                "6000": {
                                        "description": "MASQ Modem",
                                        "log": "disable",
                                        "outbound-interface": "eth0",
                                        "protocol": "all",
                                        "type": "masquerade"
                                }
                               
                        }
                }
                
        }
       
        
}

ed ora raggiungo il modem TIM

[PsychoWood]

Comunque con l'ultimo firmare dello USG qualche ottimizzazione delle performance (di routing?) c'è stata: dove prima mi fermavo (con lo Speed Test del controller) a 120up/120down, ho riprovato poco fa e con mia sorpresa è arrivato a 170up/190down.