can't add network route for Iphone #1821

Closed
opened 2025-11-20 06:07:22 -05:00 by saavagebueno · 5 comments
Owner

Originally created by @tomkoi on GitHub (Apr 17, 2025).

Maybe it's related to https://github.com/netbirdio/netbird/pull/3511, but i didn't understand if there is an update that fix it:
I’m new here :)

I bring-up today a self-host server of netbird.
I wanted to test my first peer — my iPhone.

I downloaded the app from App Store > logged in > back to my dashboard:

Image

I wanted to try to route my internal lan via netbird and make it working on iPhone when I outside.

As the picture shows, I need to do some update, BUT I downloaded the latest version from App Store. My backend version on pi is 0.41.3
So what I’m doing wrong here? The iPhone version is not getting any updates?

Originally created by @tomkoi on GitHub (Apr 17, 2025). Maybe it's related to https://github.com/netbirdio/netbird/pull/3511, but i didn't understand if there is an update that fix it: I’m new here :) I bring-up today a self-host server of netbird. I wanted to test my first peer — my iPhone. I downloaded the app from App Store > logged in > back to my dashboard: ![Image](https://github.com/user-attachments/assets/a3ee7299-a15f-4956-89b4-cba52f2e4a6d) I wanted to try to route my internal lan via netbird and make it working on iPhone when I outside. As the picture shows, I need to do some update, BUT I downloaded the latest version from App Store. My backend version on pi is 0.41.3 So what I’m doing wrong here? The iPhone version is not getting any updates?
saavagebueno added the bugios labels 2025-11-20 06:07:22 -05:00
Author
Owner

@nazarewk commented on GitHub (Apr 17, 2025):

You do not need to match the backend and client versions exactly, they should be gracefully handling specific mechanisms supported by both peers & management versions involved.

Still the App Store version should not contain a -dev suffix. I cannot find the reference, but I think this was reported & fixed already and seems to be a regression.

@nazarewk commented on GitHub (Apr 17, 2025): You do not need to match the backend and client versions exactly, they should be gracefully handling specific mechanisms supported by both peers & management versions involved. Still the App Store version should not contain a `-dev` suffix. I cannot find the reference, but I think this was reported & fixed already and seems to be a regression.
Author
Owner

@tomkoi commented on GitHub (Apr 17, 2025):

You do not need to match the backend and client versions exactly, they should be gracefully handling specific mechanisms supported by both peers & management versions involved.

Still the App Store version should not contain a -dev suffix. I cannot find the reference, but I think this was reported & fixed already and seems to be a regression.

if so, why it's didn't give me to add network route via the dashboard?
if i installing on my pi (docker version for the self-host) also client and running netbird route add 192.168.x.x/24 --peer-id this should work fine instead of the dashboard?

@tomkoi commented on GitHub (Apr 17, 2025): > You do not need to match the backend and client versions exactly, they should be gracefully handling specific mechanisms supported by both peers & management versions involved. > > Still the App Store version should not contain a `-dev` suffix. I cannot find the reference, but I think this was reported & fixed already and seems to be a regression. if so, why it's didn't give me to add network route via the dashboard? if i installing on my pi (docker version for the self-host) also client and running netbird route add 192.168.x.x/24 --peer-id <your-pi-peer-id> this should work fine instead of the dashboard?
Author
Owner

@mlsmaycon commented on GitHub (Apr 18, 2025):

@tomkoi can you share your network or network route configuration and your policies?

@mlsmaycon commented on GitHub (Apr 18, 2025): @tomkoi can you share your network or network route configuration and your policies?
Author
Owner

@nazarewk commented on GitHub (Apr 18, 2025):

I would highly suggest to use Network Resources instead of Routes and following the guide to figure out what can be wrong.

Feel free to get back to me if you still have questions after doing that.

@nazarewk commented on GitHub (Apr 18, 2025): I would highly suggest to use Network Resources instead of Routes and following [the guide](https://docs.netbird.io/how-to/troubleshooting-client#access-from-peer-a-to-srv-c) to figure out what can be wrong. Feel free to get back to me if you still have questions after doing that.
Author
Owner

@tomkoi commented on GitHub (Apr 18, 2025):

I did something, maybe if it's kind of workaround:
installed on pi (which acts as the server via docker) a netbird client, I went to dashboard and create network route to my home LAN, I chose the pi as the assign peer for this route, now when I use my iPhone with netbird VPN outside home I'm able to access to my LAN.

@tomkoi commented on GitHub (Apr 18, 2025): I did something, maybe if it's kind of workaround: installed on pi (which acts as the server via docker) a netbird client, I went to dashboard and create network route to my home LAN, I chose the pi as the assign peer for this route, now when I use my iPhone with netbird VPN outside home I'm able to access to my LAN.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SVI/netbird#1821