Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Routing issue with persistence problems after upgrade

Featured Replies

Hey All,

I've been running into an issue after upgrading to 6.7.2 . Where br2 becomes the default route.

image.thumb.png.01f6ed09669f7a0e6aefc99620b91685.png

The issue with this is that I don't have anything plugged into br2. I am currently only using br0, because it is my 10G link. br1, and br2 are only 1G links. So, I really don't want to use them. 

 

I was able to fix this by modifying the route table manually. However, if I modify it manually after a reboot it reverts right back. 

 

The weird thing is also if I downgrade back to 6.6.7 I don't have this issue. 

 

So, my primary question is what is the best option for making the br0 route persistent across reboots?

Post the content of the file "network.cfg" in the /config folder on your USB stick.

  • Author
# Generated settings:
IFNAME[0]="br0"
BRNAME[0]="br0"
BRSTP[0]="no"
BRFD[0]="0"
BRNICS[0]="eth0"
PROTOCOL[0]="ipv4"
USE_DHCP[0]="no"
IPADDR[0]="192.168.1.253"
NETMASK[0]="255.255.255.0"
GATEWAY[0]="192.168.1.1"
DNS_SERVER1="1.1.1.1"
DNS_SERVER2="192.168.1.1"
DNS_SERVER3="8.8.8.8"
USE_DHCP6[0]="yes"
DHCP6_KEEPRESOLV="no"
IFNAME[1]="br1"
BRNAME[1]="br1"
BRNICS[1]="eth1"
BRSTP[1]="no"
BRFD[1]="0"
PROTOCOL[1]="ipv4"
USE_DHCP[1]="no"
IPADDR[1]="192.168.1.252"
NETMASK[1]="255.255.255.0"
GATEWAY[1]="192.168.1.1"
IFNAME[2]="br2"
BRNAME[2]="br2"
BRNICS[2]="eth2"
BRSTP[2]="no"
BRFD[2]="0"
PROTOCOL[2]="ipv4"
USE_DHCP[2]="no"
IPADDR[2]="192.168.1.251"
NETMASK[2]="255.255.255.0"
GATEWAY[2]="192.168.1.1"
SYSNICS="3"

Here you go.

 

Like I said, the most baffling thing about it. Is that it worked just fine with the previous version of unraid when I downgraded. As well as naturally working before the upgrade.

Edited by Datapotomus

  • Author

Ok, so I sort of figured it out. If I turn off bridging on eth1, and eth2 then leave it on, on eth0, then bridge them all together it seems to work correctly. 

 

# Generated settings:
IFNAME[0]="br0"
BRNAME[0]="br0"
BRSTP[0]="yes"
BRFD[0]="0"
BRNICS[0]="eth0 eth1 eth2"
PROTOCOL[0]="ipv4"
USE_DHCP[0]="no"
IPADDR[0]="192.168.1.253"
NETMASK[0]="255.255.255.0"
GATEWAY[0]="192.168.1.1"
DNS_SERVER1="192.168.1.254"
DNS_SERVER2="192.168.1.1"
DNS_SERVER3="1.1.1.1"
USE_DHCP6[0]="yes"
DHCP6_KEEPRESOLV="no"
SYSNICS="1"

If someone has a better way to do this than bridging ports that aren't even plugged in I'm all ears. However, it does look like doing this does seem to persist after reboot.

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.