Thanks for the heads up, unfortunately your proposed workaround also doesn't work. I am still getting a loop of DHCPDISCOVER and DHCPOFFER and the speaker doesnt get an IP.
Having the exact same issue with my Symfonisk speaker not accepting DCHP and it has been driving me insane. Is there any new info on a definitive fix other than using an external DCHP server or turning off guest network?
Didnt notice any issues so far. Both my deployment variants have headscale running on a host thats also a member of the tailnet. I dont really use magicdns and exit nodes that much, but from my limited testing it all seemd to work as intended. Basic routing definitely works without problems, as...
Official documentation under https://headscale.net/, I didn't need anything else. Deployed the latest available version with docker and put it behind a reverse proxy. Has been running flawlessly for some days now.
Since the only way to manage headscale is through the CLI, I wouldn't recommend it...
Thanks for taking the time answer and explain the reasoning behind it. :)
Just for reference, got tailmon working together with headscale without any problems. Multiple asus routers (with tailmon ;)), site2site networking and several client devices. All working flawlessly. Big upgrade over my...
Would it be possible to add the option to set the "--login-server" parameter through the gui instead of having to use "Custom Operation Mode"? (Just like Exitnode, advertise and accept routes options) Would make it much easier to use it toegther with a selfhosted headscale server.
GT-AX6000 as router and AX56U as node both on 388.6-beta1. I had them on 388.5_0 and 388.2_2 before and had the same issue.
It is set to off right now and the devices can definitely talk to each other. They cannot access main network though.
I'm am trying to use guest network 1 for all my IOT devices to have them seperated from the main network by setting"intranet access" to off. I also have the guest network 1 synced the my AI mesh nodes to get good coverage of my whole flat. Now I have the issue that the clients connected to guest...
Upgraded my GT-AX6000 from 388.2_2 to 3004.388.4 beta1 and noticed that my ddns-start script now gets called non-stop, several times a minute. Definitely was not the case with 388.2_2. Everything else looks good.
Thanks for the help. Could figure the issue. It was actually my raspberry pi that was going crazy, more specifically the program Pi-Somfy that kept sending those queries, for whatever reason. Disabled it and now its back to normal. Sorry for the false alarm.
Since installing 386.7 on my AX88U it keeps hammering my DNS with queries for "192.168.1.x" several dozen times a second. Tried a factory reset and reinstallation to no avail. Since installing it a few days ago, the router sent over 22 million queries!!!
Tried with dnsfilter on and off, with...
iirc it's an issue with TrendMicro services being enabled and not a cpu bottleneck. I think you need to withdraw all permissions from TrendMicro services under Administration -> Privacy to make it work properly.
After updating m AX88U from beta4b to beta5 both my XT8's refused to use the dedicated 5GHz backhaul and always used 2.4GHz. Resetting and adding the nodes again did not help. Did a factory reset of the AX88U without importing a settings backup and everything is working now.
(I know AiMesh is...