osvinenko 0 Posted ... I am trying to use a 3rd party Wireguard client. It seems to work, but spams these lines in the log a lot. I am not asking for help with troubleshooting, I only want to know if it is OK to continue using it as is. It does not break something, does it? 2023/09/06 14:12:50 read tcp 127.0.0.1:25345->127.0.0.1:55969: use of closed network connection 2023/09/06 14:12:50 read tcp 127.0.0.1:25345->127.0.0.1:55968: use of closed network connection 2023/09/06 14:13:33 read tcp 127.0.0.1:25345->127.0.0.1:55971: use of closed network connection 2023/09/06 14:15:09 read tcp 127.0.0.1:25345->127.0.0.1:55973: use of closed network connection 2023/09/06 14:15:41 read tcp 127.0.0.1:25345->127.0.0.1:55980: use of closed network connection 2023/09/06 14:15:44 read tcp 127.0.0.1:25345->127.0.0.1:55975: use of closed network connection 2023/09/06 14:16:19 read tcp 127.0.0.1:25345->127.0.0.1:55976: use of closed network connection 2023/09/06 14:16:29 read tcp 127.0.0.1:25345->127.0.0.1:55906: use of closed network connection 2023/09/06 14:16:43 read tcp 127.0.0.1:25345->127.0.0.1:55946: use of closed network connection 2023/09/06 14:17:06 read tcp 127.0.0.1:25345->127.0.0.1:55941: use of closed network connection 2023/09/06 14:17:16 read tcp 127.0.0.1:25345->127.0.0.1:55951: use of closed network connection 2023/09/06 14:17:20 read tcp 127.0.0.1:25345->127.0.0.1:55881: use of closed network connection 2023/09/06 14:17:38 read tcp 127.0.0.1:25345->127.0.0.1:56005: use of closed network connection 2023/09/06 14:17:38 read tcp 127.0.0.1:25345->127.0.0.1:56006: use of closed network connection 2023/09/06 14:19:08 read tcp 127.0.0.1:25345->127.0.0.1:55875: use of closed network connection 2023/09/06 14:19:40 read tcp 127.0.0.1:25345->127.0.0.1:56010: use of closed network connection 2023/09/06 14:22:50 read tcp 127.0.0.1:25345->127.0.0.1:56021: use of closed network connection 2023/09/06 14:22:50 read tcp 127.0.0.1:25345->127.0.0.1:56022: use of closed network connection 2023/09/06 14:26:51 read tcp 127.0.0.1:25345->127.0.0.1:56043: use of closed network connection 2023/09/06 14:27:06 read tcp 127.0.0.1:25345->127.0.0.1:56041: use of closed network connection 2023/09/06 14:27:27 read tcp 127.0.0.1:25345->127.0.0.1:56050: use of closed network connection 2023/09/06 14:27:27 read tcp 127.0.0.1:25345->127.0.0.1:56051: use of closed network connection 2023/09/06 14:27:52 read tcp 127.0.0.1:25345->127.0.0.1:56045: use of closed network connection 2023/09/06 14:27:53 read tcp 127.0.0.1:25345->127.0.0.1:56046: use of closed network connection 2023/09/06 14:27:53 read tcp 127.0.0.1:25345->127.0.0.1:56049: use of closed network connection 2023/09/06 14:27:53 read tcp 127.0.0.1:25345->127.0.0.1:56048: use of closed network connection 2023/09/06 14:28:28 read tcp 127.0.0.1:25345->127.0.0.1:56053: use of closed network connection 2023/09/06 14:28:28 read tcp 127.0.0.1:25345->127.0.0.1:56054: use of closed network connection 2023/09/06 14:28:28 read tcp 127.0.0.1:25345->127.0.0.1:56052: use of closed network connection 2023/09/06 14:29:49 read tcp 127.0.0.1:25345->127.0.0.1:56059: use of closed network connection 2023/09/06 14:30:38 read tcp 127.0.0.1:25345->127.0.0.1:56071: use of closed network connection 2023/09/06 14:31:03 read tcp 127.0.0.1:25345->127.0.0.1:56060: use of closed network connection 2023/09/06 14:31:03 read tcp 127.0.0.1:25345->127.0.0.1:56062: use of closed network connection 2023/09/06 14:31:04 read tcp 127.0.0.1:25345->127.0.0.1:56069: use of closed network connection 2023/09/06 14:31:04 read tcp 127.0.0.1:25345->127.0.0.1:56070: use of closed network connection 2023/09/06 14:31:04 read tcp 127.0.0.1:25345->127.0.0.1:56068: use of closed network connection 2023/09/06 14:31:04 read tcp 127.0.0.1:25345->127.0.0.1:56061: use of closed network connection 2023/09/06 14:31:39 read tcp 127.0.0.1:25345->127.0.0.1:56065: use of closed network connection 2023/09/06 14:31:39 read tcp 127.0.0.1:25345->127.0.0.1:56064: use of closed network connection 2023/09/06 14:31:39 read tcp 127.0.0.1:25345->127.0.0.1:56072: use of closed network connection 2023/09/06 14:31:39 read tcp 127.0.0.1:25345->127.0.0.1:56063: use of closed network connection 2023/09/06 14:31:39 read tcp 127.0.0.1:25345->127.0.0.1:56066: use of closed network connection 2023/09/06 14:31:39 read tcp 127.0.0.1:25345->127.0.0.1:56067: use of closed network connection 2023/09/06 14:32:31 read tcp 127.0.0.1:25345->127.0.0.1:56087: use of closed network connection 2023/09/06 14:32:31 read tcp 127.0.0.1:25345->127.0.0.1:56086: use of closed network connection 2023/09/06 14:33:15 read tcp 127.0.0.1:25345->127.0.0.1:56090: use of closed network connection 2023/09/06 14:34:02 read tcp 127.0.0.1:25345->127.0.0.1:56085: use of closed network connection 2023/09/06 14:37:14 read tcp 127.0.0.1:25345->127.0.0.1:56042: use of closed network connection Quote Share this post Link to post
OpenSourcerer 1435 Posted ... I think the config is missing KeepAlive. Did you import an AirVPN-generated config, or did you fill out some GUI with the settings? Quote Hide OpenSourcerer's signature Hide all signatures NOT AN AIRVPN TEAM MEMBER. USE TICKETS FOR PROFESSIONAL SUPPORT. LZ1's New User Guide to AirVPN « Plenty of stuff for advanced users, too! Want to contact me directly? All relevant methods are on my About me page. Share this post Link to post
osvinenko 0 Posted ... I used the generated config. It has both KeepAlive and MTU. Quote Share this post Link to post
OpenSourcerer 1435 Posted ... Oh, wait… right, Wireguard. I don't understand the TCP connections, then; Wireguard is UDP-only. Basen on that, I think these errors have nothing to do with the connection to AirVPN, it's something happening locally. Can you tell what third-party client you're using? Quote Hide OpenSourcerer's signature Hide all signatures NOT AN AIRVPN TEAM MEMBER. USE TICKETS FOR PROFESSIONAL SUPPORT. LZ1's New User Guide to AirVPN « Plenty of stuff for advanced users, too! Want to contact me directly? All relevant methods are on my About me page. Share this post Link to post
osvinenko 0 Posted ... This one: https://github.com/pufferffish/wireproxy Quote Share this post Link to post
OpenSourcerer 1435 Posted ... I see. That's where the TCP spam is coming from. Yes, it's definitely a local problem. Moving to off-topic.This issue looks similar. I'd say, please file your issue with upstream. Quote Hide OpenSourcerer's signature Hide all signatures NOT AN AIRVPN TEAM MEMBER. USE TICKETS FOR PROFESSIONAL SUPPORT. LZ1's New User Guide to AirVPN « Plenty of stuff for advanced users, too! Want to contact me directly? All relevant methods are on my About me page. Share this post Link to post