Hey DM,ããNot sure if you recall, but earlier this year I was having some problems with SVDM where after a while it would no longer connect.ããNot sure if this is related, but I discovered a repeatable issue today.ããIn my svdm.ini file, I have an alias ofãã010003001=c-8-2.dege.lan:11179ããThat host resolves to both an IPv4 and IPv6 address. I think windows is prefering the IPv6 address when the resolver present both (although I'm not 100% sure if that is correct), but when I replace the hostname with an IPv4 address - the problem below does *not* occur. (So its either an IPv6 thing, or a resolver thing.)ããAnyway, if when my (dos) mailer is calling to my uplink, and it gets a connection refused, the mailer (via SVDM) reports "NO CARRIER" (which I think is expected).ããHowever, the next attempt results in SVDM reporting "ERROR" - regardless of whether the uplink is back online or not. If I try and call in to the mailer, I get SVDM responding "Sorry, not available right now".ããUsing dbgview, I can see each attempt.ããThe first failure:ã00000049 5:08:15 PM [3472] SBBSVDM: RX command: ' ATD010003001 ' at 3035779ã00000050 5:08:15 PM [3472] SBBSVDM: dial(010003001)ã00000051 5:08:15 PM [3472] SBBSVDM: Connecting to port 11179 at host 'c-8-2.dege.lan' via Rawã00000052 5:08:15 PM [3472] SBBSVDM: C:\GitLab-Runner\builds\4S9KMgUy\2\main\sbbs\src\vdmodem\vdmodem.c 640 calling getaddrinfoã00000053 5:08:15 PM [3472] SBBSVDM: C:\GitLab-Runner\builds\4S9KMgUy\2\main\sbbs\src\vdmodem\vdmodem.c 662 calling connectã00000054 5:08:15 PM [3472] SBBSVDM: Setting socket optionsã00000055 5:08:15 PM [3472] SBBSVDM: Socket send buffer length: 8192 bytesã00000056 5:08:15 PM [3472] SBBSVDM: Socket receive buffer length: 8192 bytesã00000057 5:08:15 PM [3472] SBBSVDM: Socket TCP_NODELAY: 0ã00000058 5:08:15 PM [3472] SBBSVDM: C:\GitLab-Runner\builds\4S9KMgUy\2\main\sbbs\src\vdmodem\vdmodem.c 710 socket_recvdoneã00000059 5:08:15 PM [3472] SBBSVDM: Modem response: NO CARRIERããThe subsequent failure:ãã00000070 5:08:23 PM [3472] SBBSVDM: RX command: ' ATD010003001 ' at 3043682ã00000071 5:08:23 PM [3472] SBBSVDM: Can't dial: Already connectedã00000072 5:08:23 PM [3472] SBBSVDM: Modem response: ERRORããIE: It is reporting "already connected" (when it isnt).ããThe only way I can clear this is unload SVDM and reload it and then I'm good to go until next time the uplink (only 1 uplink tested) is offline.ããThought you might like to know.ãã(This is SVDM from 2a6d9983)ããã...ëîåïãã---ã þ Synchronet þ AnsiTEX bringing back videotex but with ANSIã

Re: SVDM - strange issue "already connected"ã By: deon to Digital Man on Fri Aug 04 2023 05:23 pmãã > Hey DM,ã >ã > Not sure if you recall, but earlier this year I was having some problemsã > with SVDM where after a while it would no longer connect.ã >ã > Not sure if this is related, but I discovered a repeatable issue today.ã >ã > In my svdm.ini file, I have an alias ofã >ã > 010003001=c-8-2.dege.lan:11179ã >ã > That host resolves to both an IPv4 and IPv6 address. I think windows isã > prefering the IPv6 address when the resolver present both (although I'm notã > 100% sure if that is correct), but when I replace the hostname with an IPv4ã > address - the problem below does *not* occur. (So its either an IPv6 thing,ã > or a resolver thing.)ã >ã > Anyway, if when my (dos) mailer is calling to my uplink, and it gets aã > connection refused, the mailer (via SVDM) reports "NO CARRIER" (which Iã > think is expected).ã >ã > However, the next attempt results in SVDM reporting "ERROR" - regardless ofã > whether the uplink is back online or not. If I try and call in to theã > mailer, I get SVDM responding "Sorry, not available right now".ã >ã > Using dbgview, I can see each attempt.ã >ã > The first failure:ã > 00000049 5:08:15 PM [3472] SBBSVDM: RX command: ' ATD010003001 'ã > at 3035779ã > 00000050 5:08:15 PM [3472] SBBSVDM: dial(010003001)ã > 00000051 5:08:15 PM [3472] SBBSVDM: Connecting to port 11179 atã > host 'c-8-2.dege.lan' via Rawã > 00000052 5:08:15 PM [3472] SBBSVDM:ã > C:\GitLab-Runner\builds\4S9KMgUy\2\main\sbbs\src\vdmodem\vdmodem.c 640ã > calling getaddrinfoã > 00000053 5:08:15 PM [3472] SBBSVDM:ã > C:\GitLab-Runner\builds\4S9KMgUy\2\main\sbbs\src\vdmodem\vdmodem.c 662ã > calling connectã > 00000054 5:08:15 PM [3472] SBBSVDM: Setting socket optionsã > 00000055 5:08:15 PM [3472] SBBSVDM: Socket send buffer length:ã > 8192 bytesã > 00000056 5:08:15 PM [3472] SBBSVDM: Socket receive bufferã > length: 8192 bytesã > 00000057 5:08:15 PM [3472] SBBSVDM: Socket TCP_NODELAY: 0ã > 00000058 5:08:15 PM [3472] SBBSVDM:ã > C:\GitLab-Runner\builds\4S9KMgUy\2\main\sbbs\src\vdmodem\vdmodem.c 710ã > socket_recvdoneã > 00000059 5:08:15 PM [3472] SBBSVDM: Modem response: NO CARRIERã >ã > The subsequent failure:ã >ã > 00000070 5:08:23 PM [3472] SBBSVDM: RX command: ' ATD010003001 'ã > at 3043682ã > 00000071 5:08:23 PM [3472] SBBSVDM: Can't dial: Alreadyã > connected 00000072 5:08:23 PM [3472] SBBSVDM: Modem response:ã > ERRORã >ã > IE: It is reporting "already connected" (when it isnt).ããThank you! That is very helpful.ãã > The only way I can clear this is unload SVDM and reload it and then I'm goodã > to go until next time the uplink (only 1 uplink tested) is offline.ããLooking at the code, this is a bug, but I also think an "ATH0" would have cleared this condition.ãã > Thought you might like to know.ã >ã > (This is SVDM from 2a6d9983)ããThanks. I'll commit a fix in a second here, but nothing specifically for IPv6. Let me know if there remains some issue with the IPv6 support and I'll look into that.ã-- ã digital man (rob)ããThis Is Spinal Tap quote #11:ãNigel Tufnel: No. no. That's it, you've seen enough of that one.ãNorco, CA WX: 81.2øF, 49.0% humidity, 5 mph E wind, 0.00 inches rain/24hrsã---ã þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.netã

Re: SVDM - strange issue "already connected"ã By: Digital Man to deon on Fri Aug 04 2023 12:17 pmããHey DM,ãã > Thanks. I'll commit a fix in a second here, but nothing specifically forã > IPv6. Let me know if there remains some issue with the IPv6 support and I'llã > look into that.ããThanks, that seems to have fixed it (using a full hostname at least). I'll leave it running and see how it goes. I havent tested separating out IPv4/IPv6 hostnames (not really sure why that would be an issue) - but if I have problems, I'll try and get a repeatable problem.ããã...ëîåïãã---ã þ Synchronet þ AnsiTEX bringing back videotex but with ANSIã