Just updated my Spitz X3000 to 4.7 and everything seems to work fine.
In the develop plan, waiting for R&D resources to be arranged
@Alisa @bruce - I just checked out the link with the new features and have concern about this item:
- Enhanced Privacy and Security
With our randomized MAC address feature, your router generates a new MAC address upon each reboot, significantly increasing your privacy by protecting your identity online.
Many of my GL customers running self-hosted VPNs are doing so with the "server" router being behind an ISP router. When doing this we assign a static DHCP IP to the GL router so we can setup a stable port forwarding. Obviously if this MAC now changes, the static IP assignment will become invalid.
This could also impact customers using GL devices on networks that only allow a single device registration (e.g. cruise ships) that lock the usage to the initially registered MAC.
Can this "random MAC" feature be disabled for the WAN interface?
Thank you,
Ken
The MAC default setting for WAN is Factory.
Some users for safety reasons require to select manually to Random.
@bruce - Okay.. so it's just a new feature that replaces the previous "manual" option. Factory is still default. Great! Thank you.
Yes.
Before, MAC updates (changed) required manual updating.
Now, MAC can be updated (changed) automatically after each reboot.
@bruce - Thank you. I'll be interested to see how this works with ZeroTier enabled. In my experience ZT locks out a GL registered device if the MAC changes after an initial network join. You can't even rejoin the same network after changing the MAC back and deleting/re-adding the device. Might be worth testing (or making a note not to make any MAC changes if a device is already been ZT or Tailscale registered).
Downgraded to 4.6.4, Goodcloud site to site lists my Brume 2 as available.
This doesn't work on 4.7 and I'm going to have to stay on 4.6.4 until this is fixed.
This is still necessary. I tried the latest 4.7.0 beta, but still face the usual connection problems.
I doubt it. ZeroTier does not care about the MAC mostly since you can even pinpoint the client ID.
Never had any issues.
@admon - Good to know. I had an issue just yesterday where a MT3000 was disconnected from ZT when I changed MAC (from Factory to Manual > Random), and it would not reconnect.
I tried restarting ZT on the device with no luck, and then even tried deleting it from the ZT console and re-registering. It wouldn't re-register. I finally just recreated a new ZT network and switched the devices over, and it work right away. Maybe something else was going on. (Don't want to derail this thread. If I see it again I'll start a new one.)
Tried new beta, but still unable to access luci.
Trying the beta with NordVPN but the only servers it's showing for the USA are Seattle Washington.
People, this is a BETA version, every build should be installed without saving settings. You have weird problems that no one else has and you cry, you want the firmware to be perfect? ββDon't bother the developers with errors that are 70% your fault.
The issue is that the router is only showing Seattle servers when you choose the US, not that you can't choose other countries.
Related to the API provided by the VPN service companies.
May I know how about the error code or share some screenshots?
When Zerotier enabled, execute the command:
ls -lh /var/lib/zerotier-one
to see if it is the real path.
If it is a real path, you can delete it directly. If it is a soft connection, delete the real path which is pointing to.
Disable the Zeroter first when you delete it. The MAC (random created) will be regenerated after delete and re-enable.
That's how I've upgraded and downgraded, without saving settings, goodcloud is still bugged though on 4.7 for the Brume 2