April 6, 20206 yr What are these "shim" gateways that have appeared in my unraid config? I can't find anything google
April 9, 20206 yr Author Any clue on this? please I can not delete them. Edited April 9, 20206 yr by L0rdRaiden
April 9, 20206 yr Community Expert They certainly aren't part of a default install, posting the diagnostics might give some clues, you can also try booting in safe mode without any dockers.
April 9, 20206 yr Author 5 minutes ago, johnnie.black said: They certainly aren't part of a default install, posting the diagnostics might give some clues, you can also try booting in safe mode without any dockers. Please find attached the diagnostics file. I will try to troubleshoot it tomorrow to see if I can delete them, but I would like to know what added them unraid-diagnostics-20200409-2253.zip
April 9, 20206 yr 44 minutes ago, L0rdRaiden said: what added them This will help: shim-br0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.1.200 netmask 255.255.255.255 broadcast 0.0.0.0 shim-br0.50: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 10.10.50.128 netmask 255.255.255.255 broadcast 0.0.0.0
April 9, 20206 yr Author It doesn't help me really, I am not a pro What I can tell you is that if I stop the array they disappear, but if I start it again they are created, but I don't know why yet
April 10, 20206 yr shim networks are created when the Docker setting "Host access to custom networks" is enabled. This allows Unraid to talk directly with docker containers, which are using macvlan (custom) networks. Docker does not allow this direct communication, and network trickery is done to bypass the restriction. Here is an example of my network Edited April 10, 20206 yr by bonienl
April 10, 20206 yr Author Yes, that must be, I was trying to setup wireguard, it worked but I was never able to see anything else than 192.168.1.200 which is my unraid machine. This one of the settings that had to be enable accoding to the guide. I will try again in a couple of months.
July 28, 20205 yr so i have enabled Host access to custom networks: Enabled yet no shim-br0 is added: (see photo) How can i add this?
July 28, 20205 yr 40 minutes ago, bonienl said: Post your diagnostics hpunraid-diagnostics-20200728-1637.zipThere you go!
July 28, 20205 yr I don't see anything going wrong in the log. Try to disable and enable the docker service again.
July 30, 20205 yr On 7/28/2020 at 7:35 PM, bonienl said: I don't see anything going wrong in the log. Try to disable and enable the docker service again. I did try that. no effect. Also restarting did nothing
February 23, 20215 yr On 8/24/2020 at 1:26 AM, Mirano said: hpunraid-diagnostics-20200824-0826.zip 81.14 kB · 0 downloads config! Did you ever figure out a solution to this? I have the same issue where the shim network isn't getting created.
February 23, 20215 yr 3 minutes ago, Raesche said: Did you ever figure out a solution to this? I have the same issue where the shim network isn't getting created.
February 23, 20215 yr 9 minutes ago, Mirano said: I've tried this multiple times, even rebooting in between, and its still not creating the shim network
May 17, 20215 yr I run into this same problem time and time again. Every so often my server suffers from a kernel panic. Once it reboots, the routing tables and docker networks are missing. Even if I disable/enable Docker the routing tables don't get added back. Usually a reboot fixes it, but not always. This is what the routing tables should be when correct # ip route show default via 192.168.1.1 dev br0 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 192.168.0.0/16 via 192.168.0.2 dev tun0 192.168.0.2 dev tun0 proto kernel scope link src 192.168.0.1 192.168.1.0/25 dev shim-br0 scope link 192.168.1.0/24 dev br0 proto kernel scope link src 192.168.1.100 192.168.1.128/25 dev shim-br0 scope link 192.168.3.0/25 dev shim-br0.3 scope link 192.168.3.128/25 dev shim-br0.3 scope link 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown And this is what it looks like when things are broken default via 192.168.1.1 dev br0 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 192.168.0.0/16 via 192.168.0.2 dev tun0 192.168.0.2 dev tun0 proto kernel scope link src 192.168.0.1 192.168.1.0/24 dev br0 proto kernel scope link src 192.168.1.100 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown Adding the route manually throws an error, as the device doesn't exist. For example # ip route add 192.168.3.0/25 dev shim-br0.3 Cannot find device "shim-br0.3" Any ideas how I can prevent this from happening? Or how I can correctly add these routing tables myself?
June 9, 20215 yr Just wanted to provide an update. I haven't gotten to the bottom of why the network (and routing tables) suddenly disappear, but when it happens I'm able to fix it with the following commands (I reverse engineered the /etc/rc.d/rc.docker script) ip link add shim-br0 link br0 type macvlan mode bridge ip link set shim-br0 up ip route add 192.168.1.0/25 dev shim-br0 ip route add 192.168.1.128/25 dev shim-br0 Hopefully this helps someone else fix the issue in the future. Edit: And for those using ipvlan ip link add shim-br0 link br0 type ipvlan mode l3 ip link set shim-br0 up ip route add 192.168.1.0/25 dev shim-br0 ip route add 192.168.1.128/25 dev shim-br0 Edited April 9, 20233 yr by acook
May 8, 20224 yr On 6/9/2021 at 5:29 AM, acook said: Just wanted to provide an update. I haven't gotten to the bottom of why the network (and routing tables) suddenly disappear, but when it happens I'm able to fix it with the following commands (I reverse engineered the /etc/rc.d/rc.docker script) ip link add shim-br0 link br0 type macvlan mode bridge ip link set shim-br0 up ip route add 192.168.1.0/25 dev shim-br0 ip route add 192.168.1.128/25 dev shim-br0 Hopefully this helps someone else fix the issue in the future. Thaaaaaaaaaaaaaaank Youuuu 🙂 I am so happy that you posted this.
September 28, 20223 yr On 6/8/2021 at 8:29 PM, acook said: Just wanted to provide an update. I haven't gotten to the bottom of why the network (and routing tables) suddenly disappear, but when it happens I'm able to fix it with the following commands (I reverse engineered the /etc/rc.d/rc.docker script) ip link add shim-br0 link br0 type macvlan mode bridge ip link set shim-br0 up ip route add 192.168.1.0/25 dev shim-br0 ip route add 192.168.1.128/25 dev shim-br0 Hopefully this helps someone else fix the issue in the future. Thank you, it works like a charm! is there anyway I can prevent this happen again; I have to manually type this in each time I restart the Unraid server. Wing
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.