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

Is it possible to add automatic reconnection after disconnection? #69

Open
pizixi opened this issue Apr 26, 2024 · 6 comments
Open

Is it possible to add automatic reconnection after disconnection? #69

pizixi opened this issue Apr 26, 2024 · 6 comments
Labels
accepted The new feature request is accepted new feature This is a new feature
Milestone

Comments

@pizixi
Copy link

pizixi commented Apr 26, 2024

Describe the new feature you'd like
Is it possible to add automatic reconnection after disconnection?

Describe the reason why you want to add the feature
I need this feature because Often disconnected

@pizixi pizixi added the new feature This is a new feature label Apr 26, 2024
@mkckr0 mkckr0 added this to the v0.0.21 milestone Apr 26, 2024
@mkckr0 mkckr0 added the accepted The new feature request is accepted label Apr 26, 2024
@pizixi
Copy link
Author

pizixi commented Apr 26, 2024

Often after the program has been running for a period of time, an error message is reported: "accept_udp_loop cannot connect because the target computer actively refused it." At this time, the only solution is to restart the server and then reconnect. I hope the program can automatically reconnect.

@mkckr0
Copy link
Owner

mkckr0 commented Apr 26, 2024

This error message shouldn't happen. Can you post the log with more details?

@pizixi
Copy link
Author

pizixi commented Apr 27, 2024

I used the command line server program (as cmd. exe) and launched the command: 'as cmd.exe - b 0.0.0.0:9989'. There is no more useful information in the log except for the error message sent above

@pizixi
Copy link
Author

pizixi commented Apr 28, 2024

I switched to a server with UI, but the problem persists. The log is as follows:

[2024-04-28 08:30:51.662] [server] [info] endpoint_id: {0.0.0.00000000}.{20d5007d-721a-4afc-bc20-6476d185344b}
[2024-04-28 08:30:51.662] [server] [info] tcp listen success on 192.168.1.130:9989
[2024-04-28 08:30:51.662] [server] [info] udp listen success on 192.168.1.130:9989
[2024-04-28 08:30:51.662] [server] [info] server started
[2024-04-28 08:30:51.662] [server] [info] select audio endpoint: Digital Audio (S/PDIF) (High Definition Audio Device)
[2024-04-28 08:30:51.665] [server] [info] WAVEFORMATEX: wFormatTag: 65534, nBlockAlign: 8
[2024-04-28 08:30:51.666] [server] [info] AudioFormat:
format_tag: 3
channels: 2
sample_rate: 48000
bits_per_sample: 32

[2024-04-28 08:30:51.694] [server] [info] buffer size: 480000
[2024-04-28 08:30:51.695] [server] [info] device period: 2ms
[2024-04-28 08:31:24.096] [server] [info] accept 192.168.1.31:46962
[2024-04-28 08:40:51.434] [server] [info] accept_udp_loop 由于目标计算机积极拒绝,无法连接。
[2024-04-28 08:41:41.041] [server] [info] server stopped
[2024-04-28 08:41:42.230] [server] [info] tcp listen success on 192.168.1.130:9989
[2024-04-28 08:41:42.230] [server] [info] udp listen success on 192.168.1.130:9989

@mkckr0
Copy link
Owner

mkckr0 commented Apr 28, 2024

The port 9989 may be unavailable, you can change a port greater than 50000.

@pizixi
Copy link
Author

pizixi commented Apr 28, 2024

08:31:24 normal use, 08:40:51 sudden exception, restart service still using port 9989, still able to use normally for a period of time

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
accepted The new feature request is accepted new feature This is a new feature
Projects
None yet
Development

No branches or pull requests

2 participants