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

Stuck at Bringing WireGuard up #25

Open
SerJaimeLannister opened this issue Sep 13, 2024 · 12 comments
Open

Stuck at Bringing WireGuard up #25

SerJaimeLannister opened this issue Sep 13, 2024 · 12 comments

Comments

@SerJaimeLannister
Copy link

Hello I was thinking of creating a multi platform application on wush (just thinking , I liked magic wormhole but its golang library was a bit rough and I really liked golang and like your project's approach)
On offtopic I was the author to (https://news.ycombinator.com/item?id=38876954) so I have had a keen interest in this space

Since wush uses wireguard and wireguard needs root access , I found that there is this wireguard compliant non root alternative called wiretap (https://github.com/sandialabs/wiretap)which could allow the server to run rootlessly and also wireproxy (https://github.com/pufferffish/wireproxy)
which could connect to clients rootlessly (or maybe wiretap can do that as well)

Anyhow adding this support could be really interesting
I did somewhere hear that tailscale can be configured in a non rootless device as when I was looking at wireproxy and the likes. some people said that something like this could work directly in headscale , so please look into that as well..

I hope that you could look into these matters.

@SerJaimeLannister SerJaimeLannister changed the title Allow Wush to run on non root devices Allow Wush to run on non root devices (Also allow the use of wiretap , a non root wireguard compliant solution) Sep 13, 2024
@coadler
Copy link
Contributor

coadler commented Sep 13, 2024

Hey! wush doesn't actually require root. We use wireguard-go, which is entirely user space. The part of Taiscale requires root is the TUN device, which we don't currently implement.

@SerJaimeLannister
Copy link
Author

SerJaimeLannister commented Sep 13, 2024

I am not exactly sure.
First of all your script requires root to run (maybe to put it in bin path on linux)
but then I just went to the releases page and no worries I installed it and added to a non root vps (which is behind a nat)

and then I did ./wush serve and it gave me an auth key and when I tried to add a random file to , using wush cp if I remember correctly (Edit: edited the errors into comment below for better clarity)

@SerJaimeLannister
Copy link
Author

then it just said bringing wireguard up on my device from which I was trying to send file from as a trial (it has root access)

On my non rooted device behind nat on which I ran wush serve
Use this key to authenticate other wush commands to this instance.
WireGuard is ready
SSH server enabled
File transfer server enabled
15:11:34 Received connection request over DERP from example@test

and on my device it showed (I have changed some data since I was not sure if that has personal information or not but still)

On my rooted device from which I was trying to send file it
showed

wush cp random.file
Auth information:
> Server overlay STUN address: XYZ
> Server overlay DERP home: XYZ
> Server overlay public key: [XYZ]
> Server overlay auth key: [XYZ]
Bringing WireGuard up..

and then it just keeps on loading (> 5 -10 minutes) and it doesn't show up any errors but its clearly not working)

@SerJaimeLannister SerJaimeLannister changed the title Allow Wush to run on non root devices (Also allow the use of wiretap , a non root wireguard compliant solution) Stuck at Bringing WireGuard up Sep 14, 2024
@SerJaimeLannister
Copy link
Author

hey any updates regarding this ?

@coadler
Copy link
Contributor

coadler commented Sep 30, 2024

Hey @SerJaimeLannister, are you able to run wush cp in verbose mode?

wush cp -v random.file

This should let us know where it's hanging

@SerJaimeLannister
Copy link
Author

yes this -v command does absolutely nothing in terms of additional logs.
image
image

@coadler
Copy link
Contributor

coadler commented Oct 3, 2024

Thanks for the additional info. Could you confirm what os/architecture wush is stuck on? I'm currently digging into something similar on win11/arm64.

@coadler
Copy link
Contributor

coadler commented Oct 3, 2024

I may have fixed this in #47. Going to push a new release. Let me know if you're still seeing issues with the new version.

@SerJaimeLannister
Copy link
Author

Thanks for the additional info. Could you confirm what os/architecture wush is stuck on? I'm currently digging into something similar on win11/arm64.

Both the devices are on linux
(also I think x86_64)

One of the devices is behind a nat

@SerJaimeLannister
Copy link
Author

Hello I have tried it again on multiple servers behind nats and I have also installed the latest version and its unfortunately still not working.

@SerJaimeLannister
Copy link
Author

To me it seems that tailscale servers are blocked on the servers , though this is only a hypothesis

@SerJaimeLannister
Copy link
Author

Hey any updates , this means rather lot to me

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

3 participants