netbirdio
Android Client Update
Since the netbird kernel version on the Android app is too old, it can't support the Networks feature and custom DNS. Do you know when it’s going to get an update? @nazarewk
what version of Android are we talking about? we should be supporting anything from Android 8 and up
I found out that the Android Netbird kernel version is 0.34.0 in the console. Just wondering, when will this kernel be upgraded?
@Cikaros
The kernel version has been updated to 0.42.0 now.
What and where? Last commit to main branch of android-client is 5 months ago. Only Java branch is getting updates, but no release-info that I can find.
When is the new client coming? Or how can I use it?
@olanystrom Sorry, I did not describe it clearly. At the time I raised this issue, the version of the netbirdio/netbird project was 0.42.0. So I was also asking the official developers about the upgrade plans for the android-client.
Just FYI, there is an unofficial native NetBird client called JetBird available on Codeberg. They are currently on NetBird version v0.35.2 but cannot upgrade further due to NetBird client code bugs which make the client crash. The main dev is in contact with the NetBird team about this but as yet the team has not fixed the issue.
FYI: We have just released the first version of the rewritten client as open test on Google Play, you can sign up for this at https://play.google.com/apps/testing/io.netbird.client
Hi, I was having the same problem with custom DNS servers not working on Android (was fine on Windows and Linux) and I gave the testing Android client a go, but now I can't log in at all, getting through the SSO flow fine on Entra then coming back to the "Login successful" page on localhost:53000
From there closing the page has me coming back to a Disconnected status on the app and when I click on the connection button I go through the same flow previously described, indefinetely.
If i can be of any help in debugging this issue, would be happy to provide whatever is needed!
PS: Important detail, I am on a self-hosted version, in case this might be the issue here, every other platform other than Android is working as intended on that part however.
With a rollback to the main stable client I am able to log in.
Little workaround for the custom DNS not working as intended on Android :
If like me your usage of the DNS was via the Networks functionnality and defining a ressource there, interestingly enough, defining the IP of the ressource rather than their DNS name in Netbird works
(Charon is my internal DNS server here, also defined as a custom DNS on netbird)
As you can see this works, and I tried the multiple ways that should clear the DNS cache on Android including :
But the resolving still happens, even though I am on mobile data just to make sure my DNS server is not reachable by any other means than Netbird