search

n42n / n3n

Peer to Peer VPN
51 stars 6 forks source link

Investigate "edge: *** bit out of range 0 - FD_SETSIZE on fd_set ***: terminated" errors #28

Closed hamishcoleman closed 1 month ago

hamishcoleman commented 1 month ago

There have been some reports (https://github.com/ntop/n2n/issues/1168#issuecomment-2098388293) of people getting this error.

hamishcoleman commented 1 month ago

@nkxingxh, are you able to provide some details about what configuration you are using when you get this error?

The error suggests to me that a file descriptor has been used without being initialised, so there is probably some combination of configuration that leads to this happening.

nkxingxh commented 1 month ago

I installed n3n_3.3.3-1_amd64.deb on debian11 (Linux Robin 5.10.0-28-cloud-amd64 #1 SMP Debian 5.10.209-2 (2024-01-31) x86_64 GNU/Linux) and debian12 (Linux debian 6.1.0-18-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.76-1 (2024-02-01) x86_64 GNU/Linux) using dpkg -i ....

Both machines use the following config file, and I'm having this problem with debian12

I then tried installing n3n-3.3.3-1.x86_64.rpm on RockyLinux8. But my low glibc version caused the installation to fail, so I compiled n3n on rockylinux8. It also works fine with the following configuration.

Here is my configuration file

[tuntap]
name=n3n0
# address=10.6.6.3/22
# address_mode=static
[community]
name=xxxx
supernode=xx.xxx.xxx.xxx:7777
key=xxxxxxxxxxxxxxxx
cipher=Speck
[auth]
password=xxxxxxxxxxxxxxxx
pubkey=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
[connection]
bind=50001
description=xxxxx
allow_p2p=false
connect_tcp=true

The output looks like this

......
...... sessiondir: /run/n3n/edge
...... automatically assign IP address by supernode
*** bit out of range 0 - FD_SETSIZE on fd_set ***: terminated
Aborted

Sorry, I didn't keep a log from that time, but I'm sure that's what it looked like.

After that, I uploaded the compiled binary to my debian12 and this time I didn't have the problem

hamishcoleman commented 1 month ago

Thanks for those details - I'm guessing that this might be related to the "allow_p2p=false connect_tcp=true" options as the TCP mode has had less testing.

I will see if that information lets me reproduce the issue here

hamishcoleman commented 1 month ago

Just wanted to confirm that I can reproduce this on Debian 12 with the https://github.com/n42n/n3n/releases/download/3.3.3/n3n-3.3.3-1.x86_64.rpm binary, but not with locally compiled versions.

While it is clearly influenced by the build environment, I'm still assuming it is pointing at an actual code bug

nkxingxh commented 1 month ago

Just wanted to confirm that I can reproduce this on Debian 12 with the https://github.com/n42n/n3n/releases/download/3.3.3/n3n-3.3.3-1.x86_64.rpm binary, but not with locally compiled versions.

While it is clearly influenced by the build environment, I'm still assuming it is pointing at an actual code bug

Yes, this situation is the same as mine. The locally compiled version is working fine

hamishcoleman commented 1 month ago

I found a couple of bugs related to TCP mode - 3.3.4 has these fixes and I couldnt make it crash.

hamishcoleman commented 1 month ago

I've been running this new version for a day and a bit and could not trigger this error again.

Please feel free to re-open if you can reproduce the issue again with a newer version.