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

setup_udp_recv: bind: Address in use #12

Open
o-alquimista opened this issue Feb 24, 2024 · 2 comments
Open

setup_udp_recv: bind: Address in use #12

o-alquimista opened this issue Feb 24, 2024 · 2 comments

Comments

@o-alquimista
Copy link

o-alquimista commented Feb 24, 2024

# udptunnel -v -s 4096 127.0.0.1:55820
Listening for TCP connections on port 4096
setup_udp_recv: bind: Address in use

But netstat doesn't show any instance of port 4096. I'm not using it for anything.

So I tried many different ports, but still udptunnel thinks they're all in use.

Any idea?

OpenWrt 23.05.2 (ramips/mt7621 architecture)
udptunnel 1.1-1 installed with opkg.

@o-alquimista
Copy link
Author

o-alquimista commented Feb 24, 2024

Side note: the options parser is also misbehaving.

If I input

udptunnel -v -s 0.0.0.0:4096 127.0.0.1:55820

it outputs:

0.0.0.0:4096: invalid port number

It only seems to work with the port number alone (udptunnel -v -s 4096 127.0.0.1:55820)


UPDATE: Actually, it's documented in the usage and I didn't see it.

Usage: udptunnel -s TCP-port [-r] [-v] UDP-addr/UDP-port[/ttl]
    or udptunnel -c TCP-addr[/TCP-port] [-r] [-v] UDP-addr/UDP-port[/ttl]
     -s: Server mode.  Wait for TCP connections on the port.
     -c: Client mode.  Connect to the given address.
     -r: RTP mode.  Connect/listen on ports N and N+1 for both UDP and TCP.
         Port numbers must be even.
     -v: Verbose mode.  Specify -v multiple times for increased verbosity.

Strange, because on Linux it isn't like this. Or maybe the package version I have is older. I need to check that.

On Linux I compile from source. On OpenWrt I install the precompiled binary.

@o-alquimista
Copy link
Author

o-alquimista commented Feb 24, 2024

I figured out that the "port in use" refers to port 55820, the port I use for Wireguard traffic. Of course it's being used! I think this is a bug.

This is the same issue reported in #9 and #8

@o-alquimista o-alquimista changed the title Port in use (except it isn't) on OpenWrt setup_udp_recv: bind: Address in use Feb 24, 2024
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