Is the UISP Switch-S discontinued, or being phased out?

Nowhere seems to have stock in UK, or further afield, and no restock date...

We need to source standby spares for an existing install.

Or, are we being pushed down the c.4x ££ UISP Switch Plus route, and need to purchase new UISP Box Plus too?

At the moment we use AF60 LR.

Link distance 8Km (clean)

throughput 800Mbps

The issue we have in rainy days it drops drastically to 100 - 200 Mbps or just lose link.

We want to swap to AF60 XR.

Does this model will have the same problem? is there a way to solve this?

Thanks in advance.

We are a Swiss ISP using a UISP Router Pro for CGNAT and are trying to understand the intended way to properly log NAT translations.

Setup:

* CGNAT subnet: 100.64.0.0/23

* SNAT to public IPv4 (e.g. 63.129.137.2)

* Remote Syslog configured

* NetFlow enabled

For regulatory requirements (Swiss BÜPF/VÜPF), we need to retain enough information to determine:

private IP:port ↔ public IP:port

at a specific timestamp.

I enabled logging on the SNAT/Postrouting rule. The Router Pro creates an NFLOG rule and ulogd writes the events to /var/log/iptables.

However, I found two issues:

1. These logs are not forwarded to the configured remote Syslog server.

2. More importantly, they only show the connection before SNAT, e.g.:

SRC=100.64.1.196 SPT=62780 DST=52.98.x.x DPT=443

The translated public source port is missing.

Interestingly, using:

conntrack -E -e NEW -s 100.64.0.0/23 -o timestamp

does provide the complete mapping, including the translated public IP and port.

So my question is: What is the intended/supported way to do proper CGNAT logging on UISP Router Pro?

Does NetFlow v9 export the NAT translation fields somewhere, or is there another supported method to export and retain the complete NAT mappings externally?

I would expect this to be a standard requirement for an ISP gateway, so I assume I may be missing something.

Thanks for your reply!

@UI-Team

What's confusing is that we aren't seeing capacity drops during those periods, which is what I would normally expect of the signal was actually having problems. Is this just a generic error whenever the radio has to change channels; or is something malfunctioning?

I’ve also tested with direct line of sight and achieved around 300mbps I’ll upload more later. I’m also going to test where I have the units on the closest side of the house at approx 20m to see what results I achieve with the distance being so close but at 40 inside the house I’m stoked and at 40m outside the house I think it’s fantastic.

I recently installed a pair of Ubiquiti UBB-XG to cover a 250m link with perfect line of sight and no obstacles at all.

I’ve been trying to align them for about two weeks now, but I can’t get more than around 37% link quality on the 60GHz link. It’s also quite unstable and often falls back to the 5GHz radio, where I consistently get 100% link quality.

I’ve tried using the built-in alignment tool and both antenna circles are fully green. I also checked the alignment with a laser and they seem perfectly aligned. On top of that, I tried doing small manual adjustments while waiting for the link quality to refresh, but I was never able to go beyond 37%.

As for the configuration, I’m basically using the default settings with channel set to auto and channel width at 2160 MHz.

I don’t think interference is the problem, since this exact same link was previously covered by a MikroTik 60GHz bridge without any issues. I upgraded to the UBB-XG to achieve higher throughput above 1 Gbps.

Has anyone experienced something similar with the UBB-XG or has any suggestions on what I could try next? I couldn’t find much information online about this specific model.

Thanks in advance!

I want to share with a you a recent issue that i was trying to solve with a connectivity issue between Wave AP and AF60-LR .

Even though that through ui it was beign written that AF60-LR support connectivity with a Wave AP , the case is not so straight forward .

After a lot of digging and searching in the community and the Early Access i tried to find the correct Firmware for the AF60-LR that allowed for the connection to be established successfully .

I didn't find any related post that described

My AF60-LR was at the latest firmware V2.6.8 which allows only for PtP. The Wave AP was with the latest firmware V4.1I had first to firmware upgrade it to GMP.v3.0.2-beta.45990.210831.1151.bin (https://ui.com/downloads/wave-fw-internal/v3.0.2/GMP.v3.0.2-beta.45990.210831.1151.bin) which can allow you to use the AF60-LR to be used as a PtMP Station. Warning, after performing this upgrade i couldn't connect to the antenna with my credentials , so i had to factory reset via the button next to the ethernet port.

When i re-configure the location and password, i gain access and went to the firmware configuration . I was prompt by a message to upgrade to V4.1 ,i tried several times to upgrade it wihout any luck. Somehow it was starting to download and then the window was automatically closing.

I manaully upgrade it to the GMP.v3.0.2-beta5.46866.220413.1251.bin(https://www.ui.com/downloads/wave-fw-internal/v3.0.2/GMP.v3.0.2-beta5.46866.220413.1251.bin) and again i had issue to upgrade it to V4.1 . Somewhere in the community i have found that i had first to upgrade to V3.1 (https://ui.com/downloads/wave-fw-internal/v3.1.1/GMP.ipq806x.v3.1.1.3b546807.230308.1329.bin) . After the AF60-LR went to V3.1 then i again tried to press the download firmware button to V4.1 and it worked.

After successfully being on V4.1 , i configured the SSID/password and the link has been successfully established . With the previous version i tried configuring each time the SSID/password but the link couldn't be established .

I hope if anyone of you is dealing with a similar issue and couldn't find a solution maybe my post will might help you.

P.S (some of the links above may not work and you might have to enable Early Access though your account profile)

It randomly disconnects.

WaveAI feature is DISABLED and both radios are on fixed channel and width.

Firmware 2.6.8

AP side:

```

Mar 12 08:43:36 ulogger[549]: [PRS][wlan0] [DBSC STATUS]: current state [Wait for Connect], previous state[Unknown]
Mar 12 08:43:36 ulogger[549]: [PRS][wlan0] [DBSC STATUS]: current state [Wait for Connect], previous state[Wait for Connect]
Mar 12 08:43:36 ulogger[549]: [PRS][wlan0] [DBSC STATUS]: current state [Wait for Connect], previous state[Wait for Connect]
Mar 12 08:43:36 ulogger[549]: [PRS][wlan0]: Disconnected from  24:5a:4c:f0:96:22
Mar 12 08:43:36 hostapd: wlan0: STA 24:5a:4c:f0:96:22 IEEE 802.11: disassociated
Mar 12 08:43:36 ubondd-lr[552]: event: DISCONNECTED, peer: 24:5a:4c:f0:96:22
Mar 12 08:43:36 ubondd-lr[552]: ubond peer mac changed to: 00:00:00:00:00:00
Mar 12 08:43:41 hostapd: wlan0: STA 24:5a:4c:f0:96:22 IEEE 802.11: associated
Mar 12 08:43:41 ulogger[549]: [PRS][wlan0]: Connected to  24:5a:4c:f0:96:22
Mar 12 08:43:41 ulogger[549]: [PRS][wlan0] [DBSC STATUS]: current state [Unknown], previous state[Wait for Connect]
Mar 12 08:43:41 hostapd: wlan0: STA 24:5a:4c:f0:96:22 RADIUS: starting accounting session BC43A5F1889D7824
Mar 12 08:43:41 hostapd: wlan0: STA 24:5a:4c:f0:96:22 WPA: pairwise key handshake completed (RSN)
Mar 12 08:43:41 ubondd-lr[552]: event: CONNECTED, peer: 24:5a:4c:f0:96:22
Mar 12 08:43:41 ubondd-lr[552]: ubond peer mac changed to: 24:5a:4c:f0:96:22

```

STA side:

```

Mar 12 08:43:36 ulogger[555]: [PRS][wlan0]: Disconnected from  24:5a:4c:f6:40:2a
Mar 12 08:43:36 wireless: wlan0    New Access Point/Cell address:Not-Associated
Mar 12 08:43:36 ulogger[555]: [SYS] Regulatory domain change: initiator [REGDOM_SET_BY_CORE], REG_TYPE [NL80211_REGDOM_TYPE_WORLD], alpha2 [N/A]
Mar 12 08:43:36 ulogger[555]: [SYS] Regulatory domain change: initiator [REGDOM_SET_BY_USER], REG_TYPE [NL80211_REGDOM_TYPE_COUNTRY], alpha2 [XL]
Mar 12 08:43:36 ubondd-lr[558]: event: DISCONNECTED, peer: 24:5a:4c:f6:40:2a
Mar 12 08:43:36 ubondd-lr[558]: ubond peer mac changed to: 00:00:00:00:00:00
Mar 12 08:43:36 ulogger[555]: [PRS][wlan0] [DBSC STATUS]: current state [Rotating], previous state[Unknown]
Mar 12 08:43:36 ulogger[555]: [PRS][wlan0] [DBSC STATUS]: current state [Wait for Connect], previous state[Rotating]
Mar 12 08:43:37 ulogger[555]: [PRS][wlan0] [DBSC STATUS]: current state [Wait for Connect], previous state[Wait for Connect]
Mar 12 08:43:37 ulogger[555]: [PRS][wlan0] [DBSC STATUS]: current state [Wait for Connect], previous state[Wait for Connect]
Mar 12 08:43:37 ulogger[555]: [PRS][wlan0] [DBSC STATUS]: current state [Wait for Connect], previous state[Wait for Connect]
Mar 12 08:43:37 ulogger[555]: [PRS][wlan0] [DBSC STATUS]: current state [Wait for Connect], previous state[Wait for Connect]
Mar 12 08:43:37 ulogger[555]: [PRS][wlan0] [DBSC STATUS]: current state [Wait for Connect], previous state[Wait for Connect]
Mar 12 08:43:37 ulogger[555]: [PRS][wlan0] [DBSC STATUS]: current state [Wait for Connect], previous state[Wait for Connect]
Mar 12 08:43:38 ulogger[555]: [PRS][wlan0] [DBSC STATUS]: current state [Wait for Connect], previous state[Wait for Connect]
Mar 12 08:43:38 ulogger[555]: [PRS][wlan0] [DBSC STATUS]: current state [Wait for Connect], previous state[Wait for Connect]
Mar 12 08:43:38 ulogger[555]: [PRS][wlan0] [DBSC STATUS]: current state [Wait for Connect], previous state[Wait for Connect]
Mar 12 08:43:38 ulogger[555]: [PRS][wlan0] [DBSC STATUS]: current state [Connected], previous state[Wait for Connect]
Mar 12 08:43:38 ulogger[555]: [PRS][wlan0] [DBSC STATUS]: current state [Wait for Connect], previous state[Connected]
Mar 12 08:43:38 ulogger[555]: [PRS][wlan0] [DBSC STATUS]: current state [Wait for Connect], previous state[Wait for Connect]
Mar 12 08:43:38 ulogger[555]: [PRS][wlan0] [DBSC STATUS]: current state [Wait for Connect], previous state[Wait for Connect]
Mar 12 08:43:39 ulogger[555]: [PRS][wlan0] [DBSC STATUS]: current state [Wait for Connect], previous state[Wait for Connect]
Mar 12 08:43:39 ulogger[555]: [PRS][wlan0] [DBSC STATUS]: current state [Wait for Connect], previous state[Wait for Connect]
Mar 12 08:43:39 wave_ai[559]: Peer 24:5A:4C:F6:40:2A disconnected with reason 1!
Mar 12 08:43:39 ulogger[555]: [PRS][wlan0] [DBSC STATUS]: current state [Wait for Connect], previous state[Wait for Connect]
Mar 12 08:43:39 ulogger[555]: [PRS][wlan0] [DBSC STATUS]: current state [Wait for Connect], previous state[Wait for Connect]
Mar 12 08:43:39 ulogger[555]: [PRS][wlan0] [DBSC STATUS]: current state [Wait for Connect], previous state[Wait for Connect]
Mar 12 08:43:39 ulogger[555]: [PRS][wlan0] [DBSC STATUS]: current state [Wait for Connect], previous state[Wait for Connect]
Mar 12 08:43:40 ulogger[555]: [PRS][wlan0] [DBSC STATUS]: current state [Wait for Connect], previous state[Wait for Connect]
Mar 12 08:43:40 ulogger[555]: [PRS][wlan0] [DBSC STATUS]: current state [Wait for Connect], previous state[Wait for Connect]
Mar 12 08:43:40 ulogger[555]: [PRS][wlan0] [DBSC STATUS]: current state [Wait for Connect], previous state[Wait for Connect]
Mar 12 08:43:40 ulogger[555]: [PRS][wlan0] [DBSC STATUS]: current state [Wait for Connect], previous state[Wait for Connect]
Mar 12 08:43:40 ulogger[555]: [PRS][wlan0] [DBSC STATUS]: current state [Wait for Connect], previous state[Wait for Connect]
Mar 12 08:43:41 ulogger[555]: [PRS][wlan0] [DBSC STATUS]: current state [Wait for Connect], previous state[Wait for Connect]
Mar 12 08:43:41 ulogger[555]: [PRS][wlan0] [DBSC STATUS]: current state [Wait for Connect], previous state[Wait for Connect]
Mar 12 08:43:41 ulogger[555]: [PRS][wlan0] [DBSC STATUS]: current state [Rotating], previous state[Wait for Connect]
Mar 12 08:43:41 wireless: wlan0    Scan request completed
Mar 12 08:43:41 ulogger[555]: [PRS][wlan0] [DBSC STATUS]: current state [Wait for Connect], previous state[Rotating]
Mar 12 08:43:41 ulogger[555]: [PRS][wlan0] [DBSC STATUS]: current state [Connected], previous state[Wait for Connect]
Mar 12 08:43:41 ulogger[555]: [PRS][wlan0] [DBSC STATUS]: current state [Unknown], previous state[Connected]
Mar 12 08:43:41 ulogger[555]: [PRS][wlan0]: Connected to  24:5a:4c:f6:40:2a
Mar 12 08:43:41 wireless: wlan0    Association Response IEs:0C12000003A3280027A4000042434000623210005A030500009411245A4CF6402A00014490C7000342117200970A000000F30020E8C8C820DD060418D601010
Mar 12 08:43:41 wireless: wlan0    New Access Point/Cell address:24:5A:4C:F6:40:2A
Mar 12 08:43:41 ubondd-lr[558]: event: CONNECTED, peer: 24:5a:4c:f6:40:2a
Mar 12 08:43:41 ubondd-lr[558]: ubond peer mac changed to: 24:5a:4c:f6:40:2a
Mar 12 08:43:42 wave_ai[559]: Peer 24:5A:4C:F6:40:2A re-connected!
Mar 12 08:43:42 crdd[560]: State change: [monitor] -> [dropped]
Mar 12 08:43:42 crdd[560]: Setting interface eth0 down
Mar 12 08:43:42 ulogger[555]: interface=eth0 link=DOWN
Mar 12 08:43:57 crdd[560]: State change: [dropped] -> [monitor]
Mar 12 08:43:57 crdd[560]: Setting interface eth0 up
Mar 12 08:44:00 ulogger[555]: interface=eth0 link=UP speed=1000Mbps duplex=FULL

```

I'm quite lost as to what's wrong here. It surely do most of the disconnects in the evening when there is peak traffic.

The 60 GHz is dropping and only 5 GHz remains on.

We need to swap the radio, neither resetting or rebooting takes it back online. We have replaced the Wave LR around 6 times for the last 6-8 months.

Important Note: The main Wave LR is mounted in a big tower with to many radios, 5GHz, 60 GHz and some others companies that we do not know which technology and frequencies they use.

Have any of you got the same problem? or any suggestions?

I want to transfer a 1Gbps fiber connection from one site to the other on a budget and looking at the Nanos as my best option.

The site is in the countryside (no interference) and clear LOS. According to the design center the link should work (spec says 5+ km).

Has anyone done something similar? My fear is that the Nanos aren't powerful enough for that distance with rainy weather. I know Wave LR would work better but my budget isn't that high.

You know if these devices have jumbo frames enabled by default or there's a hidden option that i need to enable for them?

I remember that airFiber AF-5X have jumbo frames enabled by default and the 5XHD version have an option to enable.

Thank you

I have a 1.4 km link, and channel 64800 gives −55 dBm. Channel 62640 gives −63 dBm. Channels 60480 and 58320 won’t link at all.

This is especially frustrating because Gigabeam doesn’t support 66960 or 69120. So in practice, there is only one channel that works properly.

I also noticed that these devices interfere with each other, at least when they are on adjacent channels.

So if anyone is planning to buy multiple devices and build a multilink trunk, don’t. It won’t work properly and it’s just a waste of money. At least you need to have multiple poles and endpoints so that you get different angles for those links.

for the 60 GHZ Wave-PRO

I updated the title and topic of this thread to be more about sharing screenshots of the alignment reached by installers in 60GHz devices. There is this question:

Have more people been able to reach the expected signal when aligning the link?

In the screenshots I shared in the comments, in 3 links I have, only 1 link is showed as excellent, with signal as expected. But the other 2, even though I tried my best in both ends to align spending a lot of time on it, I couldn't.

You can see my screenshots in the 4th comment of this thread.

So, have others being able to acquire the expected signal?

...

BEFORE THE TOPIC WAS ABOUT A LASER BEAM BUILT-IN IN NEWER WAVE DEVICES:

I got now a great idea for aligning Wave devices (for newer devices):

Before the great idea, I had another one idea: devices with a motor, so they autoalign to the best alignment/aiming, just as motorized Starlink antennas do. But it may mean, among others, considerable more cost for the device.

But how about if they could have built in a visible laser, it maybe wouldn't mean a lot of higher cost but few. So when 2 people are aligning at same time in each end and communicating in a phone call, they could tell the other if aligning to the right or left, up or down until the laser hits the Wave on each end. That could mean less cost for sure, and a good way for an excellent alignment/aiming.

First I thought it like an additional tool, removable tool, just as the sight aligner in the top, but interchangeable to a laser aligner. But better if it would be built in very well adjusted to aim to where it should aim, very solid. And the visible laser could be turned on and off either from the UISP app, from the Web GUI, or with a physical button - or even turned off with a timeout of 15 minutes for example, like the timeout of management WiFi in AirMAX.

And also it would be better a fixed built in sight-aimer instead of a removable one, don't you think?

I think on all this because I had it hard this last week in aligning and trying to get the best signal (known by expected signal) with current solution (I even hadn't got yet the best signal), even though it is of course a great solution the removable sight aimer and the alignment tool in the UI.

I've been replacing my AF60LR links with WaveLR and WavePro radios. Consequently, I have several AF60LR's laying around I thought I might use as client radios for up close customers. I run all of my customers in router mode on the radio (1-1 NAT bridge is for the special business customers) but it won't allow.

Any "OFFICIAL" reason why router mode is unavailable for the AF60LR when running the wave firmware? Or, could this be a feature request?

This is the log:

user.warn ustatsd[377]: radio main does not exist

user.warn ustatsd[377]: radio main does not exist

user.err wave_ai[559]: Failed to retrieve stats!

user.warn ustatsd[377]: radio main does not exist

user.warn ustatsd[377]: radio main does not exist

user.warn ustatsd[377]: radio main does not exist

user.err wave_ai[559]: Failed to retrieve stats!

user.warn ustatsd[377]: radio main does not exist

user.warn ustatsd[377]: radio main does not exist

user.warn ustatsd[377]: radio main does not exist

user.err wave_ai[559]: Failed to retrieve stats!

user.warn ustatsd[377]: radio main does not exist

user.warn ustatsd[377]: radio main does not exist

user.warn ustatsd[377]: radio main does not exist

user.err wave_ai[559]: Failed to retrieve stats!

The 60 GHz PtP link doesn't work even after changing the WaveAI settings, downgrading the firmware (currently the latest available version is active), and restarting the unit.

When i try to start 60GHz Site Survey a "Generic error" appear with indication to contact support.

Has anyone else experienced a similar issue? Ideas?

Thanks

Paolo