Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Wireless tunnel connection #532

Open
karthikgbbristol opened this issue Dec 13, 2024 · 2 comments
Open

Wireless tunnel connection #532

karthikgbbristol opened this issue Dec 13, 2024 · 2 comments

Comments

@karthikgbbristol
Copy link

This might be a feature request and not a bug!

I have noticed that on some iOS devices, the tunnel stays open and connected when disconnected. Assuming the device and PC are on the same network, I'd still be able to use the tunnel details when the device is disconnected from PC.

This behaviour is not consistent though.

I have an iPhone 15 Pro Max running 18.2, on which the tunnel drops when the cable is disconnected. On an iPhone 16 device running 18.1.1, the tunnel remains open when disconnected.

Can I force the tunnel to stay on when the cable is disconnected?

@karthikgbbristol
Copy link
Author

When I disconnect the device I get this error in the console

{"level":"info","msg":"C:\windows\system32\netsh.exe interface ipv6 set address tun0 fd80:9c5d:7085::2/64","time":"2024-12-13T13:15:55Z"}
{"level":"info","msg":"batch size: 1 mtu:1280","time":"2024-12-13T13:15:55Z"}
{"error":"failed to read IPv6 header: EOF","level":"error","msg":"failed to forward data to tunnel interface","time":"2024-12-13T13:17:17Z"}
{"error":"could not write packet. write tcp 127.0.0.1:54935-\u003e127.0.0.1:27015: wsasend: An established connection was aborted by the software in your host machine.","level":"error","msg":"failed to forward data to the device","time":"2024-12-13T13:17:18Z"}

@karthikgbbristol
Copy link
Author

After doing some experiments he following sequence works.

1)Start tunnel using ios.exe tunnel start --userspace
2)Disconnect device
3)Kill and start tunnel using same command
4)Now able to connect

I think upon disconnection a new tunnel needs to be created (ater stopping the old one).

Is there a way to do this without killing ios.exe?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant