Rocksolid Light

Welcome to novaBBS (click a section below)

mail  files  register  newsreader  groups  login

Message-ID:  

6 May, 2024: The networking issue during the past two days has been identified and appears to be fixed. Will keep monitoring.

computers / alt.bbs.synchronet / SVDM - strange issue "already connected"

SubjectAuthor
* SVDM - strange issue "already connected"deon
`* SVDM - strange issue "already connected"Digital Man
 `- SVDM - strange issue "already connected"deon

1
SVDM - strange issue "already connected"

<64CCA769.47209.dove-syncdisc@bbs.dege.au>

  copy mid

https://www.novabbs.com/computers/article-flat.php?id=18938&group=alt.bbs.synchronet#18938

  copy link   Newsgroups: alt.bbs.synchronet
Path: i2pn2.org!i2pn.org!weretis.net!feeder8.news.weretis.net!feeder1-2.proxad.net!proxad.net!feeder1-1.proxad.net!193.141.40.65.MISMATCH!npeer.as286.net!npeer-ng0.as286.net!peer01.ams1!peer.ams1.xlned.com!news.xlned.com!peer02.iad!feed-me.highwinds-media.com!news.highwinds-media.com!fx09.iad.POSTED!not-for-mail
From: deo...@ALTERANT.remove-u7z-this (deon)
Subject: SVDM - strange issue "already connected"
Message-ID: <64CCA769.47209.dove-syncdisc@bbs.dege.au>
X-Comment-To: Digital Man
Organization: Alterant
Newsgroups: alt.bbs.synchronet
X-FTN-PID: Synchronet 3.20a-Linux master/0cf8e4b18 Jun 27 2023 GCC 10.2.1
X-FTN-MSGID: 47209.dove-syncdisc@12:1/2 293295d2
X-FTN-CHRS: CP437 2
WhenImported: 20230804172321+1000 1258
WhenExported: 20230804172536+1000 1258
ExportedFrom: ALTERANT dove-syncdisc 47209
Content-Type: text/plain; charset=IBM437
Content-Transfer-Encoding: 8bit
X-Gateway: vert.synchro.net [Synchronet 3.20a-Linux NewsLink 1.114]
Lines: 53
X-Complaints-To: https://www.astraweb.com/aup
NNTP-Posting-Date: Fri, 04 Aug 2023 07:26:02 UTC
Date: Fri, 4 Aug 2023 17:23:21 +1000
X-Received-Bytes: 3833
 by: deon - Fri, 4 Aug 2023 07:23 UTC

To: Digital Man
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
--- Synchronet 3.20a-Linux NewsLink 1.114
* Vertrauen - Riverside County, California - telnet://vert.synchro.net

SVDM - strange issue "already connected"

<64CD4EB4.50213.sync@vert.synchro.net>

  copy mid

https://www.novabbs.com/computers/article-flat.php?id=18939&group=alt.bbs.synchronet#18939

  copy link   Newsgroups: alt.bbs.synchronet
Path: i2pn2.org!i2pn.org!usenet.blueworldhosting.com!diablo1.usenet.blueworldhosting.com!peer03.iad!feed-me.highwinds-media.com!news.highwinds-media.com!fx14.iad.POSTED!not-for-mail
From: digital....@vert.synchro.net.remove-5mi-this (Digital Man)
Subject: SVDM - strange issue "already connected"
Message-ID: <64CD4EB4.50213.sync@vert.synchro.net>
X-Comment-To: deon
Organization: Vertrauen
Newsgroups: alt.bbs.synchronet
In-Reply-To: <64CCA769.47209.dove-syncdisc@bbs.dege.au>
References: <64CCA769.47209.dove-syncdisc@bbs.dege.au>
X-FTN-PID: Synchronet 3.20a-Linux master/118133307 Jun 28 2023 GCC 12.2.0
X-FTN-MSGID: 50213.sync@1:103/705 293348d9
X-FTN-REPLY: 47209.dove-syncdisc@12:1/2 293295d2
Content-Type: text/plain; charset=IBM437
Content-Transfer-Encoding: 8bit
X-Gateway: vert.synchro.net [Synchronet 3.20a-Linux NewsLink 1.114]
Lines: 84
X-Complaints-To: https://www.astraweb.com/aup
NNTP-Posting-Date: Fri, 04 Aug 2023 19:17:09 UTC
Date: Fri, 4 Aug 2023 12:17:08 -0700
X-Received-Bytes: 4532
 by: Digital Man - Fri, 4 Aug 2023 19:17 UTC

To: deon
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 3.20a-Linux NewsLink 1.114
* Vertrauen - Riverside County, California - telnet://vert.synchro.net

SVDM - strange issue "already connected"

<64CDED29.47217.dove-syncdisc@bbs.dege.au>

  copy mid

https://www.novabbs.com/computers/article-flat.php?id=18946&group=alt.bbs.synchronet#18946

  copy link   Newsgroups: alt.bbs.synchronet
Path: i2pn2.org!i2pn.org!eternal-september.org!news.eternal-september.org!feeder1.feed.usenet.farm!feed.usenet.farm!peer02.ams4!peer.am4.highwinds-media.com!peer03.iad!feed-me.highwinds-media.com!news.highwinds-media.com!fx05.iad.POSTED!not-for-mail
From: deo...@ALTERANT.remove-k38-this (deon)
Subject: SVDM - strange issue "already connected"
Message-ID: <64CDED29.47217.dove-syncdisc@bbs.dege.au>
X-Comment-To: Digital Man
Organization: Alterant
Newsgroups: alt.bbs.synchronet
In-Reply-To: <64CD4EB4.50213.sync@vert.synchro.net>
References: <64CD4EB4.50213.sync@vert.synchro.net>
X-FTN-PID: Synchronet 3.20a-Linux master/0cf8e4b18 Jun 27 2023 GCC 10.2.1
X-FTN-MSGID: 47217.dove-syncdisc@12:1/2 2933db9a
X-FTN-REPLY: 50213.sync@1:103/705 293348d9
X-FTN-CHRS: CP437 2
WhenImported: 20230805163313+1000 1258
WhenExported: 20230805172536+1000 1258
ExportedFrom: ALTERANT dove-syncdisc 47217
Content-Type: text/plain; charset=IBM437
Content-Transfer-Encoding: 8bit
X-Gateway: vert.synchro.net [Synchronet 3.20a-Linux NewsLink 1.114]
Lines: 19
X-Complaints-To: https://www.astraweb.com/aup
NNTP-Posting-Date: Sat, 05 Aug 2023 07:26:12 UTC
Date: Sat, 5 Aug 2023 16:33:13 +1000
X-Received-Bytes: 1879
 by: deon - Sat, 5 Aug 2023 06:33 UTC

To: Digital Man
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
--- Synchronet 3.20a-Linux NewsLink 1.114
* Vertrauen - Riverside County, California - telnet://vert.synchro.net

1
server_pubkey.txt

rocksolid light 0.9.81
clearnet tor