netbirdio / netbird

Connect your devices into a secure WireGuard®-based overlay network with SSO, MFA and granular access controls.
https://netbird.io
BSD 3-Clause "New" or "Revised" License
10.55k stars 473 forks source link

ios show connected, but still same old ip #2274

Open mobilelifeful opened 1 month ago

mobilelifeful commented 1 month ago

Describe the problem trying to use ios client app to connect, so we can use the vpn feature.

A clear and concise description of what the problem is.

To Reproduce Download the ios app from store, then change the sever to a selfhosted one. after ios first initial setup, (reseting password and added auth)

Steps to reproduce the behavior:

  1. Download the ios app from store
  2. Change the sever to a selfhosted one.
  3. login
  4. show connected, but the same old IP.

Expected behavior ios netbird client can act as a vpn client

A clear and concise description of what you expected to happen.

Are you using NetBird Cloud? No

Please specify whether you use NetBird Cloud or self-host NetBird's control plane. self-hosted

NetBird version

0.28.4

NetBird status -d output: Working ok on mac client app, and I can connect to github now. If applicable, add the `netbird status -d' command output.

Screenshots

If applicable, add screenshots to help explain your problem.

Additional context

Add any other context about the problem here.

Everything woking fine, but not when ios client app is used.

pascal-fischer commented 1 month ago

Hi @mobilelifeful,

can you explain a bit more what exactly is not working? First of are you having the same issue on wifi as on mobile networks? So management shows connected? Does the peer overview show connected peers? If not what state is showing on the peers? If you have peers shown whats not working? does pinging the netbird ip work? Do you have issues with routes?

mobilelifeful commented 1 month ago

Hi @mobilelifeful,

can you explain a bit more what exactly is not working? First of are you having the same issue on wifi as on mobile networks? So management shows connected? Does the peer overview show connected peers? If not what state is showing on the peers? If you have peers shown whats not working? does pinging the netbird ip work? Do you have issues with routes?

using the ios client app for the ios device to connect. both (ios and macos) are one the same wifi network. after updating the sever endpiont on the ios client, then hit connect, it asks for user name and password, when I entered the same information as on the mac os client.

on the peer overview (), also showed connected with timestamp as:

  iPhone-adminadmin@www.mydomainusedWithNetbird.com iphone-admin.netbird.selfhosted110.194.23.198 All 1 hours ago   v0.27.8


"does pinging the netbird ip work" should be ok, since it asked me to log in, which I did. "Do you have issues with routes?" not sure since doesn't have any option on the ios client app. Thank you again.

mobilelifeful commented 1 month ago

The only config difference that I can confirm is that: I limit only one exit node on mac os client, but can't have the option to limit only one on the ios client app.

pascal-fischer commented 1 month ago

I mean this overview on you iOS device: 400x800bb-2

This should show your other peers as connected. Alternatively you can run netbird status -d on macOS to get a similar overview.

How do you define that the VPN functionality is not given?

mobilelifeful commented 1 month ago

I mean this overview on you iOS device: 400x800bb-2

This should show your other peers as connected. Alternatively you can run netbird status -d on macOS to get a similar overview.

How do you define that the VPN functionality is not given?

There should never be the case that the vpn functionality is not given because I am the only user(admin) of the selfhost netbird and all exit node is appied to all group.

pascal-fischer commented 1 month ago

So the issue is that the exit node is not working for you on iOS? Can you take a screenshot from the routes and the peers tab from your app while connected? I need to know what exactly is not working to figure out why the exit node does not work. You neet do thave the route set in the app and the connection to the routing peer must be available