Hi all. Wondering if anyone has had an issue with this. My server & clients are on the same subnet and my server has stopped being able to detect the clients. I haven’t changed any firewall configurations. Tried disabling firewalls on the server/client and also adding client IPs via hint. I believe the network is able to handle UDP broadcast packets (it was doing that before without an issue and I haven’t changed the config). I’ve only been able to get this to work by setting the clients up as Internet clients. Any suggestions for other things I can try?
Thanks!
1 Like
I should mention that the server is a Hyper-V client. Not sure if that has anything to do with it. It’s been working fine for years.
OK figured it out. That was painful. This was not a urbackup issue. Hyper-V was dropping UDP broadcast packets at the level of the adapter. No idea why. Running the server natively fixed the issue.
Commending here to say we are seeing the same thing. A packet capture inside the HyperV VM shows the broadcasts, but captures outside do not.
To follow up on this, we were able to work around the issue by using a HyperV “legacy network adapter” instead of the regular network adapter. It appears that a recent HyperV update broke broadcast traffic for regular network adapters (at least for generation 1 VMs).
1 Like
Had the same problem, after uninstalling KB5015811 on the Hyper-V server it works again.
1 Like
Can you share with us full experience:
Hyper-V host OS version and build?
Hyper-V VM generation, net adapter version legacy or new, Hyper-V switch version?
Do you disable offloading and VMQ in Hyper-V VM net adapter settings, NIC teaming?
Do you disable GRO, LRO for UDP/TCP in guest OS, and what guest OS you use?
UrBackup server and client versions, installation sources?
Useful commands and resources:
Disable-NetAdapterVmq *
Disable-NetAdapterChecksumOffload *
Disable-NetAdapterIPsecOffload *
Disable-NetAdapterLso *
Thank you!
Had the same problem, after uninstalling KB5015808 (Hyper-V 2016) and KB5015874 (Hyper-V 2012R2) on the Hyper-V server it works again. Now I’m looking for Hyper-V 2022 (the problem remains). You have to look for the parameter to be fixed so as not unistalling KB in all server version.
Does anybody know exactly what is being restored by uninstalling KB5015808? What “parameter” are you looking for to be fixed? I’ve been struggling to find any other recent reports of this behavior more broadly, want to avoid installing on bare metal to fix the issue, and want to avoid having to hold back certain updates.
maropr
August 11, 2022, 5:08pm
10
Hello.
After the August Windows Server updates, the problem persists. UrBackup servers are Debian or Ubuntu based virtual machines. This probably has to do with the size of the UDP packet:
opened 10:33AM - 13 Jul 22 UTC
closed 07:11PM - 20 Jul 22 UTC
integration: shelly
### The problem
Hi there
This morning i had to reboot my PC for updated whic… h is running hypervisor and HA on a VM, once restarted i noticed all of my Generation 1 shelly devices unavailable (i have about 30 of them), all Generation 2 devices were still online, after rebooting a number of times, i then rebooted all shelly devices with no luck, then rebooted everything from Switches, Wifi, Gateway, VM Host, and still no luck
i first verified all of my gen 1 devices are running the current firmware of 20220209-094317/v1.11.8-g8c7bb8d and all also have the Colo it enabled pointing back to my HA server which is 192.168.X.X:5683
i then deleted onc shelly device and tried to re-add and got the following message
<img width="320" alt="2" src="https://user-images.githubusercontent.com/24925789/178708478-e4cc0f83-b347-40f0-a6f7-0da8ae7e2b5a.png">
note that if i delete a shelly device and then reboot, HA does auto discover it
i then factory reset the shelly unit, and still did the same issue as above . i then tried adding to configration.yaml a line to change the ColoIT port and then set it to the new port on a shelly, and no luck there either
i then decided to install a new install of HA on my VM (using the same hyper-v instance but with a new virtual disk,) meaning it kept the same IP, and then restored from a backup which was done two days ago when these were working with no luck, i then done another fresh install and starting a new HA system, which also done the same, and then reverted back to a older HA image i had with 8.1 and this also failed. i also tried changing IP addresses of the HA but keeping the same MAC of the VM and also no help there
after the tests above i believe i have ruled out the shellys and HA but the issue is still there, i can log into the units via web and control them with no issues and also i can confirm there is no firewall or blocking on the network as all these devices are on the same subnet
any help here would be greatly appreciated
Thanks
### What version of Home Assistant Core has the issue?
core-2022.7.3
### What was the last working version of Home Assistant Core?
core-2022.7.3
### What type of installation are you running?
Home Assistant OS
### Integration causing the issue
Shelly
### Link to integration documentation on our website
https://www.home-assistant.io/integrations/shelly
### Diagnostics information
logs turned off
### Example YAML snippet
```yaml
N/A as its an integrated setup
```
### Anything in the logs that might be useful for us?
```txt
2022-07-13 20:26:40 WARNING (MainThread) [homeassistant.config] Key whitelist_external_dirs has been replaced with allowlist_external_dirs. Please update your config
2022-07-13 20:26:41 WARNING (Recorder) [homeassistant.components.recorder.util] Ended unfinished session (id=630 from 2022-07-13 10:23:05)
2022-07-13 20:26:49 ERROR (MainThread) [snitun.client.client_peer] Challenge/Response error with SniTun server (0 bytes read on a total of 32 expected bytes)
2022-07-13 20:26:49 ERROR (MainThread) [hass_nabucasa.remote] Connection problem to snitun server
2022-07-13 20:26:52 WARNING (MainThread) [homeassistant.config_entries] Config entry 'SHELLY-PL1PM-DISHWASHER' for shelly integration not ready yet: Cannot connect to host 192.168.199.174:80 ssl:default [Connect call failed ('192.168.199.174', 80)]; Retrying in background
2022-07-13 20:26:58 WARNING (MainThread) [homeassistant.config_entries] Config entry 'SHELLY-EM' for shelly integration not ready yet: Timeout during device setup; Retrying in background
2022-07-13 20:26:58 WARNING (MainThread) [homeassistant.config_entries] Config entry 'SHELLY-UNI-SOLAR2' for shelly integration not ready yet: Timeout during device setup; Retrying in background
2022-07-13 20:26:58 WARNING (MainThread) [homeassistant.config_entries] Config entry 'SHELLY-UNI-SOLAR1' for shelly integration not ready yet: Timeout during device setup; Retrying in background
2022-07-13 20:26:58 WARNING (MainThread) [homeassistant.config_entries] Config entry 'SHELLY-2.5-KITCHEN' for shelly integration not ready yet: Timeout during device setup; Retrying in background
2022-07-13 20:26:58 WARNING (MainThread) [homeassistant.config_entries] Config entry 'SHELLY-DIM2-LOUNGE' for shelly integration not ready yet: Timeout during device setup; Retrying in background
2022-07-13 20:26:58 WARNING (MainThread) [homeassistant.config_entries] Config entry 'SHELLY-2.5-LAUNDRY' for shelly integration not ready yet: Timeout during device setup; Retrying in background
2022-07-13 20:26:58 WARNING (MainThread) [homeassistant.config_entries] Config entry 'SHELLY-2.5-MASTER' for shelly integration not ready yet: Timeout during device setup; Retrying in background
2022-07-13 20:26:58 WARNING (MainThread) [homeassistant.config_entries] Config entry 'SHELLY-1PM-BEDSIDE' for shelly integration not ready yet: Timeout during device setup; Retrying in background
2022-07-13 20:26:58 WARNING (MainThread) [homeassistant.config_entries] Config entry 'SHELLY-1PM-HALLWAY' for shelly integration not ready yet: Timeout during device setup; Retrying in background
2022-07-13 20:26:58 WARNING (MainThread) [homeassistant.config_entries] Config entry 'SHELLY-1PM-BEDROOM2' for shelly integration not ready yet: Timeout during device setup; Retrying in background
2022-07-13 20:26:58 WARNING (MainThread) [homeassistant.config_entries] Config entry 'SHELLY-1PM-SPRINT' for shelly integration not ready yet: Timeout during device setup; Retrying in background
2022-07-13 20:26:58 WARNING (MainThread) [homeassistant.config_entries] Config entry 'SHELLY-1PM-BEDROOM1' for shelly integration not ready yet: Timeout during device setup; Retrying in background
2022-07-13 20:26:58 WARNING (MainThread) [homeassistant.config_entries] Config entry 'SHELLY-1PM-ROBE' for shelly integration not ready yet: Timeout during device setup; Retrying in background
2022-07-13 20:26:58 WARNING (MainThread) [homeassistant.config_entries] Config entry 'SHELLY-2.5-FRONTDOOR' for shelly integration not ready yet: Timeout during device setup; Retrying in background
2022-07-13 20:26:58 WARNING (MainThread) [homeassistant.config_entries] Config entry 'SHELLY-1PM-BATHROOM' for shelly integration not ready yet: Timeout during device setup; Retrying in background
2022-07-13 20:26:58 WARNING (MainThread) [homeassistant.config_entries] Config entry 'SHELLY-2.5-BATHROOM' for shelly integration not ready yet: Timeout during device setup; Retrying in background
2022-07-13 20:26:58 WARNING (MainThread) [homeassistant.config_entries] Config entry 'SHELLY-2.5-ENSUITE2' for shelly integration not ready yet: Timeout during device setup; Retrying in background
2022-07-13 20:26:58 WARNING (MainThread) [homeassistant.config_entries] Config entry 'SHELLY-2.5-ENSUITE1' for shelly integration not ready yet: Timeout during device setup; Retrying in background
2022-07-13 20:26:58 WARNING (MainThread) [homeassistant.config_entries] Config entry 'SHELLY-1PM-WASHING' for shelly integration not ready yet: Timeout during device setup; Retrying in background
2022-07-13 20:26:58 WARNING (MainThread) [homeassistant.config_entries] Config entry 'SHELLY-UNI-ROLLER TRIGGER' for shelly integration not ready yet: Timeout during device setup; Retrying in background
2022-07-13 20:26:58 WARNING (MainThread) [homeassistant.config_entries] Config entry 'SHELLY-1PM-BATHROOM-ALEXA' for shelly integration not ready yet: Timeout during device setup; Retrying in background
2022-07-13 20:26:58 WARNING (MainThread) [homeassistant.config_entries] Config entry 'SHELLY-1PM-GARAGE-ALEXA' for shelly integration not ready yet: Timeout during device setup; Retrying in background
2022-07-13 20:26:58 WARNING (MainThread) [homeassistant.config_entries] Config entry 'SHELLY-2.5-TOILET' for shelly integration not ready yet: Timeout during device setup; Retrying in background
2022-07-13 20:26:58 WARNING (MainThread) [homeassistant.config_entries] Config entry 'SHELLY-2.5-GARAGE-TV' for shelly integration not ready yet: Timeout during device setup; Retrying in background
2022-07-13 20:26:58 WARNING (MainThread) [homeassistant.config_entries] Config entry 'SHELLY-UNI-AUTOMATION-4' for shelly integration not ready yet: Timeout during device setup; Retrying in background
2022-07-13 20:26:58 WARNING (MainThread) [homeassistant.config_entries] Config entry 'SHELLY-UNI-AUTOMATION-3' for shelly integration not ready yet: Timeout during device setup; Retrying in background
2022-07-13 20:26:58 WARNING (MainThread) [homeassistant.config_entries] Config entry 'SHELLY-UNI-AUTOMATION-2' for shelly integration not ready yet: Timeout during device setup; Retrying in background
2022-07-13 20:26:58 WARNING (MainThread) [homeassistant.config_entries] Config entry 'SHELLY-UNI-AUTOMATION-1' for shelly integration not ready yet: Timeout during device setup; Retrying in background
2022-07-13 20:26:58 WARNING (MainThread) [homeassistant.config_entries] Config entry 'SHELLY-UNI-COMMS FAN' for shelly integration not ready yet: Timeout during device setup; Retrying in background
2022-07-13 20:26:58 WARNING (MainThread) [homeassistant.config_entries] Config entry 'SHELLY-UNI-LIZARD' for shelly integration not ready yet: Timeout during device setup; Retrying in background
2022-07-13 20:27:04 ERROR (MainThread) [snitun.client.client_peer] Challenge/Response error with SniTun server (0 bytes read on a total of 32 expected bytes)
2022-07-13 20:27:04 ERROR (MainThread) [hass_nabucasa.remote] Connection problem to snitun server
2022-07-13 20:27:06 WARNING (MainThread) [aioshelly.block_device] device 192.168.199.210 initialize error - TimeoutError()
2022-07-13 20:27:20 WARNING (MainThread) [aioshelly.block_device] device 192.168.199.157 initialize error - TimeoutError()
2022-07-13 20:27:20 WARNING (MainThread) [aioshelly.block_device] device 192.168.199.167 initialize error - TimeoutError()
2022-07-13 20:27:20 WARNING (MainThread) [aioshelly.block_device] device 192.168.199.231 initialize error - TimeoutError()
2022-07-13 20:27:21 WARNING (MainThread) [aioshelly.block_device] device 192.168.199.164 initialize error - TimeoutError()
2022-07-13 20:27:21 WARNING (MainThread) [aioshelly.block_device] device 192.168.199.210 initialize error - TimeoutError()
2022-07-13 20:27:21 WARNING (MainThread) [aioshelly.block_device] device 192.168.199.170 initialize error - TimeoutError()
2022-07-13 20:27:21 WARNING (MainThread) [aioshelly.block_device] device 192.168.199.175 initialize error - TimeoutError()
2022-07-13 20:27:22 WARNING (MainThread) [aioshelly.block_device] device 192.168.199.234 initialize error - TimeoutError()
2022-07-13 20:27:23 WARNING (MainThread) [aioshelly.block_device] device 192.168.199.203 initialize error - TimeoutError()
2022-07-13 20:27:25 WARNING (MainThread) [aioshelly.block_device] device 192.168.199.204 initialize error - TimeoutError()
2022-07-13 20:27:25 WARNING (MainThread) [aioshelly.block_device] device 192.168.199.160 initialize error - TimeoutError()
2022-07-13 20:27:25 WARNING (MainThread) [aioshelly.block_device] device 192.168.199.171 initialize error - TimeoutError()
2022-07-13 20:27:25 WARNING (MainThread) [aioshelly.block_device] device 192.168.199.233 initialize error - TimeoutError()
2022-07-13 20:27:25 WARNING (MainThread) [aioshelly.block_device] device 192.168.199.172 initialize error - TimeoutError()
2022-07-13 20:27:26 WARNING (MainThread) [aioshelly.block_device] device 192.168.199.165 initialize error - TimeoutError()
2022-07-13 20:27:27 WARNING (MainThread) [aioshelly.block_device] device 192.168.199.228 initialize error - TimeoutError()
2022-07-13 20:27:28 WARNING (MainThread) [aioshelly.block_device] device 192.168.199.226 initialize error - TimeoutError()
2022-07-13 20:27:28 WARNING (MainThread) [aioshelly.block_device] device 192.168.199.168 initialize error - TimeoutError()
2022-07-13 20:27:36 WARNING (MainThread) [aioshelly.block_device] device 192.168.199.210 initialize error - TimeoutError()
2022-07-13 20:27:39 WARNING (MainThread) [aioshelly.block_device] device 192.168.199.226 initialize error - TimeoutError()
2022-07-13 20:27:39 WARNING (MainThread) [aioshelly.block_device] device 192.168.199.217 initialize error - TimeoutError()
2022-07-13 20:27:39 WARNING (MainThread) [aioshelly.block_device] device 192.168.199.234 initialize error - TimeoutError()
2022-07-13 20:27:39 WARNING (MainThread) [aioshelly.block_device] device 192.168.199.233 initialize error - TimeoutError()
2022-07-13 20:27:39 WARNING (MainThread) [aioshelly.block_device] device 192.168.199.232 initialize error - TimeoutError()
2022-07-13 20:27:39 WARNING (MainThread) [aioshelly.block_device] device 192.168.199.207 initialize error - TimeoutError()
2022-07-13 20:27:40 WARNING (MainThread) [aioshelly.block_device] device 192.168.199.204 initialize error - TimeoutError()
2022-07-13 20:27:40 WARNING (MainThread) [aioshelly.block_device] device 192.168.199.160 initialize error - TimeoutError()
2022-07-13 20:27:40 WARNING (MainThread) [aioshelly.block_device] device 192.168.199.171 initialize error - TimeoutError()
2022-07-13 20:27:40 WARNING (MainThread) [aioshelly.block_device] device 192.168.199.172 initialize error - TimeoutError()
2022-07-13 20:27:41 WARNING (MainThread) [aioshelly.block_device] device 192.168.199.165 initialize error - TimeoutError()
2022-07-13 20:27:42 WARNING (MainThread) [aioshelly.block_device] device 192.168.199.228 initialize error - TimeoutError()
2022-07-13 20:27:43 WARNING (MainThread) [aioshelly.block_device] device 192.168.199.168 initialize error - TimeoutError()
2022-07-13 20:27:44 WARNING (MainThread) [aioshelly.block_device] device 192.168.199.203 initialize error - TimeoutError()
2022-07-13 20:27:44 WARNING (MainThread) [aioshelly.block_device] device 192.168.199.173 initialize error - TimeoutError()
2022-07-13 20:27:44 WARNING (MainThread) [aioshelly.block_device] device 192.168.199.211 initialize error - TimeoutError()
2022-07-13 20:27:44 WARNING (MainThread) [aioshelly.block_device] device 192.168.199.197 initialize error - TimeoutError()
2022-07-13 20:27:46 WARNING (MainThread) [aioshelly.block_device] device 192.168.199.206 initialize error - TimeoutError()
2022-07-13 20:27:46 WARNING (MainThread) [aioshelly.block_device] device 192.168.199.166 initialize error - TimeoutError()
2022-07-13 20:27:47 WARNING (MainThread) [aioshelly.block_device] device 192.168.199.159 initialize error - TimeoutError()
2022-07-13 20:27:47 WARNING (MainThread) [aioshelly.block_device] device 192.168.199.213 initialize error - TimeoutError()
2022-07-13 20:27:47 WARNING (MainThread) [aioshelly.block_device] device 192.168.199.169 initialize error - TimeoutError()
2022-07-13 20:27:48 WARNING (MainThread) [aioshelly.block_device] device 192.168.199.161 initialize error - TimeoutError()
2022-07-13 20:27:48 WARNING (MainThread) [aioshelly.block_device] device 192.168.199.231 initialize error - TimeoutError()
2022-07-13 20:27:49 WARNING (MainThread) [aioshelly.block_device] device 192.168.199.232 initialize error - TimeoutError()
2022-07-13 20:27:50 WARNING (MainThread) [aioshelly.block_device] device 192.168.199.157 initialize error - TimeoutError()
2022-07-13 20:27:50 WARNING (MainThread) [aioshelly.block_device] device 192.168.199.167 initialize error - TimeoutError()
2022-07-13 20:27:50 WARNING (MainThread) [aioshelly.block_device] device 192.168.199.204 initialize error - TimeoutError()
2022-07-13 20:27:50 WARNING (MainThread) [aioshelly.block_device] device 192.168.199.226 initialize error - TimeoutError()
2022-07-13 20:27:50 WARNING (MainThread) [aioshelly.block_device] device 192.168.199.217 initialize error - TimeoutError()
2022-07-13 20:27:50 WARNING (MainThread) [aioshelly.block_device] device 192.168.199.234 initialize error - TimeoutError()
2022-07-13 20:27:50 WARNING (MainThread) [aioshelly.block_device] device 192.168.199.233 initialize error - TimeoutError()
2022-07-13 20:27:51 WARNING (MainThread) [aioshelly.block_device] device 192.168.199.164 initialize error - TimeoutError()
2022-07-13 20:27:51 WARNING (MainThread) [aioshelly.block_device] device 192.168.199.210 initialize error - TimeoutError()
2022-07-13 20:27:51 WARNING (MainThread) [aioshelly.block_device] device 192.168.199.170 initialize error - TimeoutError()
2022-07-13 20:27:51 WARNING (MainThread) [aioshelly.block_device] device 192.168.199.175 initialize error - TimeoutError()
2022-07-13 20:27:52 WARNING (MainThread) [aioshelly.block_device] device 192.168.199.207 initialize error - TimeoutError()
2022-07-13 20:27:55 WARNING (MainThread) [aioshelly.block_device] device 192.168.199.160 initialize error - TimeoutError()
2022-07-13 20:27:55 WARNING (MainThread) [aioshelly.block_device] device 192.168.199.171 initialize error - TimeoutError()
2022-07-13 20:27:55 WARNING (MainThread) [aioshelly.block_device] device 192.168.199.172 initialize error - TimeoutError()
2022-07-13 20:27:56 WARNING (MainThread) [aioshelly.block_device] device 192.168.199.165 initialize error - TimeoutError()
2022-07-13 20:27:57 WARNING (MainThread) [aioshelly.block_device] device 192.168.199.228 initialize error - TimeoutError()
2022-07-13 20:27:58 WARNING (MainThread) [aioshelly.block_device] device 192.168.199.168 initialize error - TimeoutError()
2022-07-13 20:27:59 WARNING (MainThread) [aioshelly.block_device] device 192.168.199.203 initialize error - TimeoutError()
2022-07-13 20:28:06 WARNING (MainThread) [aioshelly.block_device] device 192.168.199.210 initialize error - TimeoutError()
2022-07-13 20:28:09 WARNING (MainThread) [aioshelly.block_device] device 192.168.199.217 initialize error - TimeoutError()
2022-07-13 20:28:09 WARNING (MainThread) [aioshelly.block_device] device 192.168.199.234 initialize error - TimeoutError()
2022-07-13 20:28:09 WARNING (MainThread) [aioshelly.block_device] device 192.168.199.233 initialize error - TimeoutError()
2022-07-13 20:28:09 WARNING (MainThread) [aioshelly.block_device] device 192.168.199.231 initialize error - TimeoutError()
2022-07-13 20:28:09 WARNING (MainThread) [aioshelly.block_device] device 192.168.199.232 initialize error - TimeoutError()
2022-07-13 20:28:09 WARNING (MainThread) [aioshelly.block_device] device 192.168.199.207 initialize error - TimeoutError()
2022-07-13 20:28:10 WARNING (MainThread) [aioshelly.block_device] device 192.168.199.160 initialize error - TimeoutError()
2022-07-13 20:28:10 WARNING (MainThread) [aioshelly.block_device] device 192.168.199.171 initialize error - TimeoutError()
2022-07-13 20:28:10 WARNING (MainThread) [aioshelly.block_device] device 192.168.199.226 initialize error - TimeoutError()
2022-07-13 20:28:10 WARNING (MainThread) [aioshelly.block_device] device 192.168.199.172 initialize error - TimeoutError()
2022-07-13 20:28:11 WARNING (MainThread) [aioshelly.block_device] device 192.168.199.165 initialize error - TimeoutError()
2022-07-13 20:28:12 WARNING (MainThread) [aioshelly.block_device] device 192.168.199.204 initialize error - TimeoutError()
2022-07-13 20:28:12 WARNING (MainThread) [aioshelly.block_device] device 192.168.199.228 initialize error - TimeoutError()
2022-07-13 20:28:13 WARNING (MainThread) [aioshelly.block_device] device 192.168.199.168 initialize error - TimeoutError()
```
### Additional information
## System Health
version | core-2022.7.3
-- | --
installation_type | Home Assistant OS
dev | false
hassio | true
docker | true
user | root
virtualenv | false
python_version | 3.10.5
os_name | Linux
os_version | 5.15.45
arch | x86_64
timezone | Australia/Sydney
config_dir | /config
<details><summary>Home Assistant Cloud</summary>
logged_in | true
-- | --
subscription_expiration | 15 July 2022 at 10:00
relayer_connected | true
remote_enabled | true
remote_connected | true
alexa_enabled | false
google_enabled | false
remote_server | ap-southeast-1-0.ui.nabu.casa
can_reach_cert_server | ok
can_reach_cloud_auth | ok
can_reach_cloud | ok
</details>
<details><summary>Home Assistant Supervisor</summary>
host_os | Home Assistant OS 8.2
-- | --
update_channel | stable
supervisor_version | supervisor-2022.07.0
agent_version | 1.2.1
docker_version | 20.10.14
disk_total | 30.8 GB
disk_used | 3.8 GB
healthy | true
supported | true
board | ova
supervisor_api | ok
version_api | ok
installed_addons | Samba share (10.0.0), File editor (5.3.3), MariaDB (2.4.0), Check Home Assistant configuration (3.11.0)
</details>
<details><summary>Dashboards</summary>
dashboards | 1
-- | --
resources | 0
views | 5
mode | storage
</details>
<details><summary>Recorder</summary>
oldest_recorder_run | 7 July 2022 at 09:10
-- | --
current_recorder_run | 13 July 2022 at 20:26
estimated_db_size | 207.78 MiB
database_engine | mysql
database_version | 10.4.19
</details>
For me, it was temporarily helpful to turn off the virtual machine for outgoing checksum traffic:
ethtool -K eth0 tx off
Regards
Thanks for sharing that command. Works like a charm with
ethtool -K eth0 tx off
You have to execute it after every reboot but I see that as a plus as the changes are gone after a reboot.
I fixed in Ubuntu 20.04.4 by editing the .yaml configuration file used by netplan.
Example:
network:
ethernets:
eth0:
addresses: [192.168.1.167/24]
gateway4: 192.168.1.254
nameservers:
addresses: [4.2.2.2, 8.8.8.8]
tcp-segmentation-offload: false
tcp6-segmentation-offload: false
receive-checksum-offload: false
transmit-checksum-offload: false
generic-segmentation-offload: false
generic-receive-offload: false
large-receive-offload: false
version: 2
You must have netplan.io updated to version 0.104, previous versions have a bug that does not disable offloading.
View article… https://bugs.launchpad.net/netplan/+bug/1956264
Updated Ubuntu …
Regards
2 Likes
Sorry to necro an old thread, but I just wanted to put this out there. This week I experienced an issue where my native ubuntu server suddenly stopped being able to discover a native windows client. Did some troubleshooting and found out that the UDP packets were being dropped at the level of the windows firewall. Very strange considering that the default urbackup allow ingress rules are all there. Anyway, issue was resolved by adding a manual ingress rule for the proper port.