Release Notes v3.0.2

Release Date: Apr 8, 2022

Update Considerations

This update addresses the following issues:

  • Service restarts on Conductor
  • Service restarts on Airwall Gateway
  • Cloud Airwall Gateway auto-config overriding custom settings
  • Security update for an OpenSSL vulnerability (CVE-2022-0778) - OpenSSL version has been updated.

Fixes

ID Applies to Description
DEV-17432 Conductors Fixed an issue where bypass Airwall Gateways with local devices may not be configured properly in overlay networks that have bypass devices.
DEV-17398 Airwall Gateways Fixed get_iface_mtu_by_name ioctl SIOCGIFMTU: No such device warning on Airwall relay.
DEV-17388 Cloud Airwall Gateways Fixed an issue where the Conductor failed to properly provision older Airwall Gateways.
DEV-17376 Conductors Fixed an issue that could crash the metadata service on the Conductor.
DEV-17375 Conductors Fixed a race condition that could cause a crash of the Airwall control plane daemon.
DEV-17334 Airwall Gateways Fixed a backhaul bypass warning: "PortGroupImpl::syncInterfaceRoutes unable to add route on backhaul bypass gateway and Agents without an overlay IP have bypass policy."
DEV-17327 Airwall Gateways Fixed an issue that could cause Airwall Agents configured with a NAT IP to become unreachable on 3.0.0 and 3.0.1 Conductors.
DEV-17315 Conductors Fixed an issue where Airwall Edge Services using the default bypass gateway may have not been given the correct configuration to fully access it.
DEV-17296 Airwall Gateways Fixed an issue that could cause a service crash on the Conductor immediately after reboot.
DEV-17269 Airwall Gateways Fixed an issue that could cause service interruption when executing several long-lasting diagnostic or device discovery requests.
DEV-17267 Airwall Gateways Fixed an issue that could deadlock the Airwall control daemon causing service restarts and Conductor reconnects.
DEV-17255 Airwall Gateways Fixed an issue that could cause control plane service restarts because of heartbeat starvation during the overlay route summation.
DEV-17082 OpenHIP Fixed a bug where HIP continually exchanges UPDATE packets with a peer.
DEV-17016 Cellular Airwall Gateways Fixed an issue that may affect certain SIM swaps on cellular Airwall Gateways.
DEV-16963 Airwall Gateways Fixed an issue where the AW-250 SFP (combo port) PHY settings were reset to default when you updated the firmware. The PHY mode settings will now be reset during factory reset. Use Diag Mode to change these settings.
DEV-16638 OpenHIP Airwall Gateways acting as a Relay may now initiate tunnels to peers that are behind a NAT, using the address of that peer learned via received relay probes.
DEV-16374 Airwall Gateways Diagnostic mode no longer prevents long hostnames in the "Airwall Conductor Hostname or IP" section

Known Issues

ID Applies to Description
DEV-17450 Airwall Gateways If you are upgrading an AWS cloud Airwall Gateway with NVMe, the update from v2.2.12 to v3.0.1 fails.

Workaround -- Skip the v3.0.1 release and update to v3.0.2.

DEV-17178 Cellular Airwall Gateways Cellular details show "unavailable" on the Conductor Ports tab after you update the Airwall Gateway to v3.0.1.

Workaround -- Reboot the Airwall Gateway.

DEV-16999 Airwall Gateways AW-150 port 5 SFP LEDs are non-functional when the port may be actually linked and active.
DEV-16503 macOS Airwall Agents Deleting a profile does not immediately delete the associated private key.

Workaround – Switch to a different profile before creating a profile after deleting one.

DEV-16431 Conductor When specifying a port mirror destination IP address, ensure that it doesn't conflict with any of the Airwall Gateway's local device IPs
DEV-16397 Conductor If you change the LSI prefix and have port mirroring configured, you need to either reboot the Conductor, or go to Settings > Diagnostics and select Restart metadata cache to update the LSI prefix.
DEV-16068 Amazon Web Services Conductor To enable enhanced networking for a cloud Amazon Web Services Airwall Gateway or Conductor, use the custom images instead of the marketplace image.
DEV-16067 Cloud, Conductor, Airwall Gateways If you are adding a new interface to an existing cloud Airwall Gateway, you must set the source and destination check to false (see your cloud provider for the terminology they use for source and destination checks).
DEV-16059 Airwall Gateways When HA-pairing two Airwall Gateways that don't have the HA link plugged in correctly, the Conductor displays no actionable error message and the HA setup never completes.
DEV-15982 Conductor Traffic stats reporting graphs generally show a smooth curve between data points. However, over time the graph can show up with sharper angles. The data is still correct, but this is a known issue with the graphing library used by the Conductor.
DEV-15945 Airwall Gateways If you configure port mirroring using a remote destination local device, GRE/ERSPAN traffic from remote Airwall Gateways will arrive with a source IP in the LSI prefix (defaults to 1.0.0.0/8).
DEV-15923 Airwall Gateways When you run Check secure tunnels on a v3.0 Airwall Gateway, the check falsely reports a bad tunnel status for any peer airwall running a firmware version that is v2.2.8 or lower.
DEV-15887 Airwall Gateways You cannot currently add VLAN interfaces to the Ruggedcom platform.
DEV-15808 Google Cloud Airwall Gateways Google Cloud Airwall Gateways with the same VM name have the same device serial number, which can result in a failure when you make a license request in the Conductor.

Workaround – In Google Cloud, use unique deployment names (VM names) for Airwall Gateways.

DEV-15791 Airwall Gateways On the Airwall Gateway 100, Port 2 might be inactive after a factory-reset.

Workaround – After a factory reset, manually reboot the Airwall Gateway 100.

DEV-15787 macOS Airwall Agents If a person who already has a profile makes a Request to Connect from the Remote Access User portal on the same Conductor, no profile is created.

Workaround – If the user wants a second profile, they can use an invite code or enter the Conductor information manually.

DEV-15705 macOS Airwall Agents Establishing a tunnel TO a mobile Airwall Agent (iOS or Android) fails when there is no Airwall Relay involved.

Workaround – Establish the tunnel FROM the mobile Airwall Agent.

DEV-15572 Airwall Gateways If you don't specify a gateway in the DHCP server configuration, the DHCP client cannot configure a default gateway.

Workaround – Unless you want to configure a single isolated subnet, always specify a gateway. For example, a subnet for networked PDUs that should not have any outside connectivity aside from remote access through an Airwall Gateway, and used in conjunction with SNAT over the overlay port group. See https://tempered.force.com/TemperedSupportCenter/s/article/DHCP-server-isn-t-serving-as-a-gateway.

DEV-15489 Windows Airwall Agents and Servers Windows 7 sends an extra Windows system popup when the Windows Airwall Agent UserAuth prompt appears. You can safely ignore this popup, or can disable the Windows 7 service as described in this article from Broadcom: https://knowledge.broadcom.com/external/article/153693/interactive-services-detection-a-progra.html
DEV-15357 macOS Airwall Agents If you update the macOS Airwall Agent to a release later than v2.2.11 on macOS Mojave using a Conductor-based update package, it may not report the updated version to the Conductor.

Workaround – Restart the Airwall Agent or reapply the update.

DEV-15338 Linux Airwall Servers If using a recent systemd-based Linux distribution including Fedora 33 and Debian 11, disable systemd-networkd MAC address randomization of the hip1 interface.
DEV-15302 macOS Airwall Agents The profile for a macOS Airwall Agent does not work correctly when restored to a new computer using Time Machine.

Workaround – Create a new profile on the Airwall Agent, and then on the Conductor, replace the old profile with the new one.

DEV-15219 Cellular 110g Airwall Gateways The Airwall Gateway 110g does not on the Bell Mobility (Canada) cellular provider because they require the use of a http/https proxy.
DEV-15031 Airwall Gateways Remote syslog over TLS doesn't work when using keys stored in TPM.
DEV-14860 Conductor Airwall Gateways on older firmware (pre v2.2.0) may send passively-discovered device events to the Conductor even when the feature is off.
DEV-14835 Conductor Airwall Gateway 150 serial numbers look like exponentiated numbers to Windows Excel, so the column displaying the Serial number shows xxxEyyy instead of the full serial number.
DEV-14739 Airwall Gateways If you set IPv4 to DHCPv4 and set a static IP address for IPv6, the setting that you set second doesn't get saved.

Workaround – If you need both IPv4 and IPv6, set static IP addresses for both.

DEV-14736 Cellular Airwall Gateways Cellular details may display as "unavailable" on the first boot after you update anAirwall Gateway. The cellular connections are not affected.

Workaround – Reboot the Airwall Gateway again to correctly display the cellular details.

DEV-14726 Conductor If you're viewing an Android Airwall Agent Ports tab and the Airwall Agent changes how it's connected to the Conductor (for example, from WiFi to cellular), the display doesn't update correctly.

Workaround – Refresh the page.

DEV-14715 macOS Airwall Agents Big Sur ARM64 Macs are not supported in this release
DEV-14610 Conductor After changing the Reporting traffic stats reporting time, the CPU graph does not display.

Workaround – Refresh your browser page.

DEV-14584 Cellular Airwall Gateways Hot-swapping the SIM on an Airwall Gateway 110 with firmware version v2.2.11 may not work.

Workaround – Reboot the Airwall Gateway after installing a new SIM card.

DEV-14551 Conductor The Android Airwall Agent lets you press the Edit Settings button on the Ports page; however, submitting any changes to the page results in an error message.
DEV-14426 Conductor, Airwall Gateways Bypass destinations with a hostname do not show device activity in the Conductor.
DEV-14308 OpenHIP Initial packets are dropped while building a new tunnel to a new peer Airwall Gateway.
DEV-14249 iOS Airwall Agents Check Secure TunnelsTunnel Status may show as unavailable on iOS.

Workaround – You can determine tunnel status by checking packets sent or received.

DEV-14223 Google Cloud Add an overlay IP to agent in order to talk to device behind Google 300v.
DEV-14218 Airwall Gateways NAT broadcast applied to traffic between ports within a single port group. Use an external switch if you need to connect multiple devices to a single port group and use the NAT broadcast feature and require IP broadcast un-NATed between those local devices.
DEV-14045 Android and iOS Airwall Agents iOS does not currently support overlay ping.
DEV-14015 OpenHIP If an Airwall Relay is also used as a bypass gateway, Airwall Edge Services behind the relay are not able to use that relay.

Workaround – Deploy multiple relays so at least one relay is usable by each pair of Airwall Edge Services that need to communicate.

DEV-13775 Azure Cloud Airwall Gateways The Conductor might rarely give a "Net::ReadTimeout" error when you try to deploy an Azure Airwall Gateway 300v or server. This error doesn't indicate that the deployment has failed. If you get this error message, go to Azure portal and check the actual deployment result.
DEV-13699 Windows Airwall Agents and Servers The initial ping from the Windows Airwall Agent can be misleading since it currently includes the time to initially set up the connection.

Workaround – Ping a second time to see actual ping time.

DEV-13650 Conductor SoIP device activity is not being reported on an Airwall Gateway Local Devices tab.
DEV-13640 Conductor Airwall Relay diagnostics don't work on a Standby Conductor.
DEV-13633 Conductor A standby Conductor shows available firmware downloads, but they cannot be downloaded.

Workaround – Download firmware from the active Conductor.

DEV-13620 Conductor In Airwall > Ports > Failover settings, the failover ping occurs only every "ping rate" + "ping timeout" seconds, somewhat unexpectedly.
DEV-13607 Conductor, Airwall Gateways Creating a link failover group (Airwall > Ports > Failover settings) does not apply the settings to any port groups. You must also assign the failover group to port groups on the Ports page.
DEV-13588 Conductor Opening the Conductor on Internet Explorer 11 can be very slow for medium to large deployments.

Workaround – Use the latest version of Chrome, Firefox, or Edge instead.

DEV-13536 Windows Airwall Agents and Servers When you uninstall the Windows Airwall Agent, it does not remove the tun-tap driver.

Workaround – Delete the driver from C:\Windows\System32\drivers\tnw-tap.sys.

DEV-13531 Cloud Conductor Automatically creating Cloud HA Conductors only works if you use the same cloud provider for both active and standby Conductors. For example, AWS HA Active and AWS HA Standby.

Workaround – You can manually set up different cloud providers as HA pair Conductors.

DEV-13474 Airwall Gateways If you configure multiple overlay port groups with the same overlay IP subnet (same or different IP addresses) and then create a local device equal to the entire subnet with port affinity set, it may not lead to the expected result.
DEV-13331 Alibaba Cloud Airwall Gateways The Alibaba Cloud Conductor system time is incorrect.

Workaround – Change the Conductor system time to browser time: In Conductor Settings, under System time, select Edit Settings, select Set browser time, and then select Update Settings.

DEV-13195 Conductor, Airwall Gateways When you upgrade a Cellular Airwall Gateway-150 from 2.2.3 to 2.2.5, the cellular details all become "Unavailable."

Workaround – Reboot and the details return.

DEV-13194 Conductor Check Connectivity > Ping Local Devices for an Airwall Gateway fails in Internet Explorer 11 if one of the devices is defined as a CIDR.

Workaround – Use one of the latest versions of Chrome, Firefox, Safari or Edge.

DEV-12852 Windows Airwall Agents Windows by default doesn't allow multiple 'active' interfaces. It prefers ethernet over cellular whenever possible.

Workaround – Set Windows to keep multiple interfaces open by editing the fMinimizeConnections registry value:

  1. Hold the Windows Key and press R.
  2. On the Run page, type regedit and click OK.
  3. Navigate to the following path in Registry Editor: HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WcmSvc\
  4. See if the GroupPolicy subkey exists. If not, right-click on WcmSvc and select New > Key and name it GroupPolicy.
  5. Right-click GroupPolicy and choose New > DWORD (32-bit) > Create value.
  6. Name the value fMinimizeConnections and select OK. (The value should be 0, or false).
  7. Reboot and test.
DEV-11710 macOS Airwall Agents If you change the LSI prefix on the Conductor, the macOS Airwall Agent doesn't update the routes correctly.

Workaround – Close and reopen the macOS Airwall Agent.

DEV-10590 Cloud Airwall Gateways The Conductor does not display an error when adding a route that would exceed the maximum number of allowed routes in the cloud provider.
DEV-10039 Airwall Gateways An Airwall Gateway-150 can show "could not detect attached switch" intermittently.
DEV-9546 Airwall Gateways, Airwall Gateways 150 The Airwall Gateway-150 serial connection has an intermittent issue when large amounts of data are sent over the console.
DEV-9429 Windows Airwall Agents When you update the Overlay Device IP address for a Windows Airwall Server in the Conductor, it doesn't always update the first time. Workaround -- Open and update the address a second time.