When adding Brume2 (4.7.0-Stable OpenWrt 21.02-SNAPSHOT r15812+908-46b6ee7ffc) as drop-in gateway and enabling the Network Storage on both, I started seeing both trying to be the Domain Master:
Wed Dec 25 22:52:23 2024 daemon.err nmbd[18095]: Attempting to become domain master browser on workgroup WORKGROUP on subnet 192.168.6.1
Wed Dec 25 22:52:23 2024 daemon.err nmbd[18095]: [2024/12/25 22:52:23.338835, 0] ../../source3/nmbd/nmbd_become_dmb.c:306(become_domain_master_browser_bcast)
Wed Dec 25 22:52:23 2024 daemon.err nmbd[18095]: become_domain_master_browser_bcast: querying subnet 192.168.6.1 for domain master browser on workgroup WORKGROUP
Wed Dec 25 22:52:23 2024 daemon.err nmbd[18095]: [2024/12/25 22:52:23.339863, 0] ../../source3/nmbd/nmbd_become_dmb.c:237(become_domain_master_query_success)
Wed Dec 25 22:52:23 2024 daemon.err nmbd[18095]: become_domain_master_query_success:
Wed Dec 25 22:52:23 2024 daemon.err nmbd[18095]: There is already a domain master browser at IP 192.168.10.1 for workgroup WORKGROUP registered on subnet 192.168.6.1.
I'm not 100% sure this is the correct way to fix, but I went to /etc/config/samba4 (on Brume) and I changed:
From: option workgroup 'WORKGROUP'
To: option workgroup 'BRUME2'
@bruce, there are many reports of different bugs, but the last comment from GL-iNet here is from 2 weeks ago.
Policy based routing with WG is broken in this release. Closed source works this release does not route via domain. (hulu.com) ipv4 only stack. Went back to closed source until corrected
Hey, I am on an msc Cruise right now and can't get it to work. I have same installed firmware. Do you mind explaining in detail what you did to make it work? Thanks a lot
Hello Bruce, thanks for the reply and upcoming help as I am on a cruise right now.
Here the information requested ;
Setup : gl-mt3000
Firmware: version 4.7.0
Firmware type : release3
-Subscribed to internet with phone via portal.
-Mac address on phone is not randomized.
-Confirmed working on phone.
-deactivated wifi on phone and connected to router.
-activated repeater mode / cloned mac address / lock BSSID deactivated / manually set static ip activated and copied the one from phone as it appears I always have the same ip on phone. Gateway, DNS 1 and DNS 2 copies from phone.
Currently not working. I also tried without static ip and not working. I updated the firmware with keeping previous settings.
Do I need to change the firmware from my router as some managed to get to internet portal. Am I doing something wrong?
Please try upgrading the op24 firmware on the MT3000, this firmware version has supported this portal WiFi first, the stable firmware version merges the codes in next version, sorry about this:
NO NEED to cloned mac address / lock BSSID / manually set static ip (copied the one from phone as it appears I always have the same ip on phone. Gateway, DNS 1 and DNS 2 copies from phone.)
Just like you are going to repeat a normal WiFi on the MT3000, and the phone/laptop connects the MT3000 and access the portal page to login your info.
Thank you Bruce. I am now on v4.7.0-op24 and proceeded as you said.
Copied over from phone: ip, gateway, DNS, netmask 255.255.255.0. Disconnect phone from cruise wifi. The beryl is connected but I am not sent to portal. Manual entry to portal address is not working.
Do you have an MSC app on the phone? Perhaps they are picking up your iphone specifically via some other method and know that your router is not your iphone (user agent, device id, etc.).
I do have an msc app installed (msc for me) but it's not opening when connecting. I forced closed it. I believe right from the beginning with activating the internet account from phone it isolated the phone and blacklist any other device.
I have spent several hours trying to troubleshoot but I never get access to portal.
May be it differs from boat to boat. This ship is from 2022 (msc seascape using starlink). If someone has managed to get it working or bypass restrictions please advise.
Do not copy this info from the phone to GL router. Let the GL router repeater DHCP obtain the IP from MSC.
Just like you are going to repeat a normal WiFi on the MT3000, and the phone/laptop connects to the MT3000 and access the portal page to login your info.
AdGuard sudderlap doenst work anymore. After router boot, i try to connect to adguard on port 3000, in keeps loading, after 5 min i cant reach the adguard page at all. This happend since yesterday. I’m on release 3 of 4.7.0 for over 2 weeks i think.
Do not copy any network setting! You will receive all settings via DHCP.
Just make sure that you have a static MAC on your Beryl. If you are not redirected to the captive portal disconnect the device (mobile, laptop...) and reconnect the device.
Some of these MSC ships only work with non random MAC-Adresses. Then build yourself some iphone MAC: F0:D1:A9:XX:XX:XX
Maybe some feature: Generate iphone/samsung/whatever "random" MACs?
Issue: When AdGuard Home and VPN client is enabled, turning on or off the ‘ Allow Custom DNS to Override VPN DNS’ option on the DNS page does not take effect.
Thanks. I tried all possible variations. I has never worked. If anyone is sailing on msc seascape please report if you managed to make it work. Thank you