Hello,
I'm using Gargoyle 1.3.16
I've notice a problem, that ddns_gargoyle is leaving CLOSE_WAIT connections.
As I can see the libewget.c (used by ddns_gargoyle) has a bug in destroy_connection_http function.
Shouldn't be there close(socket) before free(socket)?
Best Regards,
MJ
ddns_gargoyle leaves sockets in CLOSE_WAIT status
Moderator: Moderators
Re: ddns_gargoyle leaves sockets in CLOSE_WAIT status
What all does this bug affect?
Re: ddns_gargoyle leaves sockets in CLOSE_WAIT status
ddns-gargoyle leaves open sockets, so you have to restart it to free resources.
Re: ddns_gargoyle leaves sockets in CLOSE_WAIT status
So it's only a problem with dynamic DNS? Just wanted to know since I noticed it's been fixed in repository and wanted to know if it was worth compiling.
Re: ddns_gargoyle leaves sockets in CLOSE_WAIT status
I noticed the problem with dynDNS only.
However root of the bug is in ewget lib, and I'm not sure if this is even noticeable in ewget.
However root of the bug is in ewget lib, and I'm not sure if this is even noticeable in ewget.
Re: ddns_gargoyle leaves sockets in CLOSE_WAIT status
It seems Eric has fixed this issue in the repo so it should be correct in the next release of Gargoyle. You can see yourself at http://www.gargoyle-router.com/gargoyle rev:6c66f0cf
Thanks for your investigation and report.
Thanks for your investigation and report.
Linksys WRT1900ACv2
Netgear WNDR3700v2
TP Link 1043ND v3
TP-Link TL-WDR3600 v1
Buffalo WZR-HP-G300NH2
WRT54G-TM
Netgear WNDR3700v2
TP Link 1043ND v3
TP-Link TL-WDR3600 v1
Buffalo WZR-HP-G300NH2
WRT54G-TM