September 27, 20169 yr unRAID OS Version: 6.2 Description: Master browser ends up on virbr0 interface with a VLAN added and the array restarted. How to reproduce: Add a VLAN to network and restart array. Expected results: Master Browser should be on the default interface and stay on the default interface. Actual results: Master Browser changes from default interface to the virbr0 interface. Other information: An ip route produces the following output: default via 192.168.1.1 dev br0 metric 212 127.0.0.0/8 dev lo scope link 169.254.0.0/16 dev br0.1 proto kernel scope link src 169.254.206.15 metric 213 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 192.168.1.0/24 dev br0 proto kernel scope link src 192.168.1.152 metric 212 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown And the command: /usr/bin/nmblookup -M -- - 2>/dev/null | /usr/bin/grep -Pom1 '^\S+' Shows 192.168.122.1 as the master browser. This is the wrong interface. It should be the default br0 interface at 192.168.1.1. Setting the SMB settings to: [global] interfaces = br0 lo bind interfaces only = yes Keeps the browser on the br0 interface at 192.168.1.1. Diagnostics attached. tower-diagnostics-20160927-0827.zip
October 8, 20169 yr I guess your server has become the master browser for your VLAN, which makes sense right, since there are no other smb servers on that network? When I set up same situation and type "nmblookup -M -- -" I get this: 192.168.1.9 __MSBROWSE__<01> 192.168.1.115 __MSBROWSE__<01> 192.168.1.9 is the IP address I assigned to VLAN1. 192.168.1.115 is another server on the network that happens to be the master browser. Is this not correct? Guess I'm wondering what the issue is...
October 8, 20169 yr Author I guess your server has become the master browser for your VLAN, which makes sense right, since there are no other smb servers on that network? No. My router is an smb server and I have the master browser set on the router. When I set up same situation and type "nmblookup -M -- -" I get this: 192.168.1.9 __MSBROWSE__<01> 192.168.1.115 __MSBROWSE__<01> 192.168.1.9 is the IP address I assigned to VLAN1. 192.168.1.115 is another server on the network that happens to be the master browser. Is this not correct? Guess I'm wondering what the issue is... It's a little tricky to catch, but there may be underlying gremlins. The issue is that samba attaches to all interfaces and the default interface (in my case br0) should be the one chosen for the master browser. When the array starts it is correct. It only becomes an issue if you stop the array, assign a new VLAN, and the start the array. Do this: 1) Set unRAID as the master browser. 2) Restart unRAID and check the master browser. It should be the ip address of the default interface (br0). 3) Stop the array. 4) Assign a new VLAN. 5) Start array. 6) Check the master browser. unRAID thinks it is the master browser for the virbr0 interface, not br0. Confirm ip addresses with 'ip route'.
October 8, 20169 yr 1) Set unRAID as the master browser. How are you forcing this? Normally an election takes place.
October 8, 20169 yr Author 1) Set unRAID as the master browser. How are you forcing this? Normally an election takes place. I don't force it. I only set it in the smb settings.
October 8, 20169 yr Ok I guess I'm wondering if this is wrong behavior that causes some kind of connectivity/name service issue? Meaning I can see that a server will become master browser on a VLAN but maybe that's correct, and in fact maybe desirable?
October 8, 20169 yr Author unRAID becomes the master browser on the virbr0 interface that is down, not on a VLAN. There is nothing there on virbr0! The master browser should be on the default interface - br0. unRAID is all alone on a non-functional interface. default via 192.168.1.1 dev br0 metric 212 127.0.0.0/8 dev lo scope link 169.254.0.0/16 dev br0.1 proto kernel scope link src 169.254.206.15 metric 213 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 192.168.1.0/24 dev br0 proto kernel scope link src 192.168.1.152 metric 212 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown
October 12, 20169 yr Author Putting the setting as suggested here: http://lime-technology.com/forum/index.php?topic=52698.msg506471#msg506471 in the smb-extra.conf file sets unRAID as the preferred master browser and prevents this problem.
October 12, 20169 yr Putting the setting as suggested here: http://lime-technology.com/forum/index.php?topic=52698.msg506471#msg506471 in the smb-extra.conf file sets unRAID as the preferred master browser and prevents this problem. Interesting, I wonder why that works?
October 12, 20169 yr Author Putting the setting as suggested here: http://lime-technology.com/forum/index.php?topic=52698.msg506471#msg506471 in the smb-extra.conf file sets unRAID as the preferred master browser and prevents this problem. Interesting, I wonder why that works? I'm guessing a bit here, but I think that unRAID is not winning the master browser election on the active interfaces and just sets itself as the master browser on the inactive interface because it wins the election there (no competition). Encouraging samba on unRAID to win the master browser election will insure it wins on all interfaces and the problem is resolved. Does that make sense?
October 19, 20169 yr Version 6.3.0-rc2 adds this tweak to samba config: if user sets “Local master” to “Yes”, in addition to telling samba to participate in browse master elections, we also configure it so that it will force an election each reboot and win over any windows/osx OS on the network. This was per request by dlandon and apparently solves issue where server becomes master browser on wrong I/F in VLAN-enabled config. I haven't notices any side-effects such as making network browse function faster or slower, but might be something to watch for.
Archived
This topic is now archived and is closed to further replies.