n00b42

just as a note: even though it does not have to mean anything, a month passed without problems. we will see.

For once I changed "Settings > docker > Docker custom network type" to "ipvlan" as suggested. Furthermore I removed the "br0" network and moved the corresponding container to the default bridge network for now.

> docker network ls NETWORK ID NAME DRIVER SCOPE 69d9ba12e3ba br0 macvlan local b3c086cd02ba bridge bridge local ef0efa310ce6 cdocknet bridge local 9f5a5e61419c host host local d85a3c71fba0 none null local > docker network inspect br0 bridge cdocknet host none [ { "Name": "br0", "Id": "xxx", "Created": "2024-05-28T12:30:30.178193348+02:00", "Scope": "local", "Driver": "macvlan", "EnableIPv6": false, "IPAM": { "Driver": "default", "Options": {}, "Config": [ { "Subnet": "192.168.0.0/24", "Gateway": "192.168.0.1", "AuxiliaryAddresses": { "server": "192.168.0.200" } } ] }, "Internal": false, "Attachable": false, "Ingress": false, "ConfigFrom": { "Network": "" }, "ConfigOnly": false, "Containers": { "xxx": { "Name": "xxx", "EndpointID": "xxx", "MacAddress": "02:42:c0:a8:00:02", "IPv4Address": "192.168.0.2/24", "IPv6Address": "" } }, "Options": { "parent": "br0" }, "Labels": {} }, { "Name": "bridge", "Id": "xxx", "Created": "2024-05-28T12:30:27.200004702+02:00", "Scope": "local", "Driver": "bridge", "EnableIPv6": false, "IPAM": { "Driver": "default", "Options": null, "Config": [ { "Subnet": "172.17.0.0/16", "Gateway": "172.17.0.1" } ] }, "Internal": false, "Attachable": false, "Ingress": false, "ConfigFrom": { "Network": "" }, "ConfigOnly": false, "Containers": { "xxx": { "Name": "xxx", "EndpointID": "xxx", "MacAddress": "02:42:ac:11:00:03", "IPv4Address": "172.17.0.3/16", "IPv6Address": "" }, "xxx": { "Name": "xxx", "EndpointID": "xxx", "MacAddress": "02:42:ac:11:00:02", "IPv4Address": "172.17.0.2/16", "IPv6Address": "" } }, "Options": { "com.docker.network.bridge.default_bridge": "true", "com.docker.network.bridge.enable_icc": "true", "com.docker.network.bridge.enable_ip_masquerade": "true", "com.docker.network.bridge.host_binding_ipv4": "0.0.0.0", "com.docker.network.bridge.name": "docker0", "com.docker.network.driver.mtu": "1500" }, "Labels": {} }, { "Name": "cdocknet", "Id": "xxx", "Created": "2021-03-03T15:58:08.470260897+01:00", "Scope": "local", "Driver": "bridge", "EnableIPv6": false, "IPAM": { "Driver": "default", "Options": {}, "Config": [ { "Subnet": "172.18.0.0/16", "Gateway": "172.18.0.1" } ] }, "Internal": false, "Attachable": false, "Ingress": false, "ConfigFrom": { "Network": "" }, "ConfigOnly": false, "Containers": { "xxx": { "Name": "xxx", "EndpointID": "xxx", "MacAddress": "02:42:ac:12:00:07", "IPv4Address": "172.18.0.7/16", "IPv6Address": "" }, "xxx": { "Name": "xxx", "EndpointID": "xxx", "MacAddress": "02:42:ac:12:00:02", "IPv4Address": "172.18.0.2/16", "IPv6Address": "" }, "xxx": { "Name": "xxx", "EndpointID": "xxx", "MacAddress": "02:42:ac:12:00:05", "IPv4Address": "172.18.0.5/16", "IPv6Address": "" }, "xxx": { "Name": "xxx", "EndpointID": "xxx", "MacAddress": "02:42:ac:12:00:03", "IPv4Address": "172.18.0.3/16", "IPv6Address": "" }, "xxx": { "Name": "xxx", "EndpointID": "xxx", "MacAddress": "02:42:ac:12:00:08", "IPv4Address": "172.18.0.8/16", "IPv6Address": "" }, "xxx": { "Name": "xxx", "EndpointID": "xxx", "MacAddress": "02:42:ac:12:00:06", "IPv4Address": "172.18.0.6/16", "IPv6Address": "" }, "xxx": { "Name": "xxx", "EndpointID": "xxx", "MacAddress": "02:42:ac:12:00:04", "IPv4Address": "172.18.0.4/16", "IPv6Address": "" } }, "Options": {}, "Labels": {} }, { "Name": "host", "Id": "xxx", "Created": "2021-03-03T14:41:07.112591038+01:00", "Scope": "local", "Driver": "host", "EnableIPv6": false, "IPAM": { "Driver": "default", "Options": null, "Config": [] }, "Internal": false, "Attachable": false, "Ingress": false, "ConfigFrom": { "Network": "" }, "ConfigOnly": false, "Containers": {}, "Options": {}, "Labels": {} }, { "Name": "none", "Id": "xxx", "Created": "2021-03-03T14:41:06.621475741+01:00", "Scope": "local", "Driver": "null", "EnableIPv6": false, "IPAM": { "Driver": "default", "Options": null, "Config": [] }, "Internal": false, "Attachable": false, "Ingress": false, "ConfigFrom": { "Network": "" }, "ConfigOnly": false, "Containers": {}, "Options": {}, "Labels": {} } ] Is the problem that there are networks with different drivers (macvlan and bridge) at the same time? Or that there are any bridges while "Docker custom network type" is set to "macvlan"? My most important (and reverse proxied) containers are in cdocknet, I probably could move all other containers there and delete the other networks, would that help? (I also read about bonding, and as I will not use it I could deactivate it to reduce complexity) I actually only access my docker containers via exposed ports on the server IP (or via reverse proxy), i.e. as far as I understand it, currently I neither rely on macvlan nor ipvlan, right?

I see, the docker containers stuck around for a long time and there might be some legacy stuff (or "recommended" stuff from old tutorials I used back then), will look into that. I am not sure about all the reasoning and which tutorials I used, however this one looks close to what I have/had: (emby + swag in a custom network) https://forums.unraid.net/topic/101969-guide-setup-emby-with-hw-transcoding-on-unraid-remote-access-through-reverse-proxy-using-swag/ The server only uses one of its NIC (the others are never connected), and there is no VLAN tagging on the server side (only done internally by the Router on a port basis) The router runs OpenWRT, which allowed me to easily move the devices (on a port basis) from one VLAN to another, and to get tcpdumps on a VLAN basis. I have several tcpdumps, however I feel uncomfortable posting them publicly, but I am happy to provide them temporarily via PM, if that might help and is ok for you?

setterm -blank 0 This is an attempt to disable the screen to turn off (which might be a problem when accessing it via BMC/KVM), there are several posts about that command in the forum, e.g. https://forums.unraid.net/topic/104711-solved-looking-for-the-command-to-disable-screen-blanking/?do=findComment&comment=986789

I aggree that this is the most probable reason and I would totally agree if it would happen more often (within days) However the time between the last two incidents was way more than a month... Not a reasonable time to wait and not use it productively. I will check my docker containers and think about suspending some of them for now, or at least change some docker settings of the remaining (bridged or priviledged).

Setup: Both my Unraid server as well as my PC are in the same LAN (and even in the same VLAN) Situation: If the problem occurs, I can not reach any other device in my LAN from my PC, however, as soon as I either disconnect the server OR put it (or the PC) in another VLAN (even if routed in the same subnet) then I am able to access any remaining LAN devices from my PC (as well as my Router/WAN). Diagnostic Problem (unrelated to the actual issue): When the problem occurs, I am unable to access the headless server (and connecting a monitor and keyboard in that state has no effect), therefore I never was able to access the device when the issue happened. However I am working on solving that in the future (using a dummy vga to keep it alive so that my BMC can access it) Thanks for the hint at NetProbe, not sure if it will help here, but sure is an interesting tool I will look into. I appended a diagnostics file, however as I needed to restart the server to access it, there is obviously no log about the incident... (or before) xxx-diagnostics-20240529-0107.zip

When I was asked to provide a diagnostics file I went throught the files and would like to propose some more anonymization: - Remove the serial numbers of devices (e.g. from the SMART reports, config/pools, vars.txt) - Maybe change some LAN/Docker/.. IPs - share names (smb-extra.conf)

I have a very weird networking issue and I was not able to reproduce it, it just happens unregulary between once a week and once in months... Out of the blue my LAN devices are not able to access WAN anymore, and some time after, I am unable to access any other device in my LAN. (Other LAN-VLANs and WLAN continue to work) First, I suspected some of my network infrastructure, but one after one I restarted and/or temporaily replaced them, until I observed that when I unplug my Unraid instance from the network, all other devices will come back to work. Also reconnecting the Unraid instance will raise the problems once more. As the Unraid instance runs headless and for whatever (unrelated) reasons my BMC/KVM view is not able to get any output (maybe wake it), my only option is to trigger a server reset, after which I savely can reconnect the instance to my network. I did not notice anything really obvious logged, and I even tried to tcpdump the network traffic - however I just was looking if there was some obvious flooding. I run several docker instancens and services, and I thought about turning some off for testing, however as I could not find a reliable way to trigger this issue, I do not want to keep my services disabled for weeks.... I am well aware, that this issue sounds very unbelievable, or at least as it "has to be something else", and due to the difficulty analysing the problem I would not have made a post here if I wouldn't have read some posts with similar issues (without solutions) elsewhere: https://www.reddit.com/r/unRAID/comments/13becyn/unraid_takes_down_my_internet_at_the_wan_level/