Skip to content

Update 7.1.0 release notes #245

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Mar 17, 2025
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
21 changes: 19 additions & 2 deletions docs/unraid-os/release-notes/7.1.0.md
Original file line number Diff line number Diff line change
Expand Up @@ -8,13 +8,17 @@ This release adds wireless networking, the ability to import TrueNAS and other f

### Known issues

For known issues, see the [7.0.0 release notes](7.0.0.md#known-issues).
#### VM Snapshots

After creating a VM snapshot, the spinning "please wait" indicator will not go away even though the snapshot is created correctly. Wait a minute, then reload the page.

For other known issues, see the [7.0.0 release notes](7.0.0.md#known-issues).

### Rolling back

If rolling back earlier than 7.0.1, also see the [7.0.1 release notes](7.0.1.md#rolling-back).

## Changes vs. [7.0.0](7.0.0.md)
## Changes vs. [7.0.1](7.0.1.md)

## Storage

Expand Down Expand Up @@ -47,6 +51,19 @@ Additional details
* Having both wired and wireless isn't really recommended for long term use, it should be one or the other. But if both connections use DHCP and you (un)plug a network cable while wireless is configured, the system should adjust within 45-60 seconds.
* Wireless chipset support: if your WiFi adapter can't connect to the network, please start a new forum thread and provide your diagnostics. We expect to have success with modern WiFi adapters, but we have seen an older Broadcom BCM4313 chipset fail to initialize.

Limitations: there are networking limitations when using wireless, as a wlan can only have a single mac address.

* Only one wireless NIC is supported, wlan0
* wlan0 is not able to participate in a bond
* Docker containers
* ***Settings → Docker***, **Docker custom network type** must be set to **ipvlan** (macvlan is not possible because wireless does not support multiple mac addresses on a single interface)
* ***Settings → Docker***, **Host access to custom networks** must be disabled
* Docker containers **Network Type** should use **Host** or **Bridge**
* VMs require some manual configuration
* Configure the VM with a static IP address
* Only one VM can be active at the time
* Configure the same IP address on the ipvtap interface, type: `ip addr add IP-ADDRESS dev shim-wlan0`

### Other networking changes

* When configuring multiple network interfaces, by default the additional interfaces will have their gateway disabled, this is a safe default that works on most networks where a single gateway is required. If an additional gateway is enabled, it will be given a higher metric than existing gateways so there are no conflicts. You can override as needed.
Expand Down