Hi All,

New node in net 114: ,10,Mystical_Realm_BBS,Tucson_AZ,Craig_Daters,-Unpublished-,300,CM,INA:mysticalrealmbbs.com,IBN
Connect with: BinkIT/2.41,JSBinkP/4,sbbs3.21a/Linux

Node 2:250/7 is no longer down. Connect with: BinkIT/2.41,JSBinkP/4,sbbs3.20a/Linux

Node 2:420/0 and /33 (aka), have an updated IVM flag (new IP). I get a connect with FrontDoor/2 2.32.mL/CS000362; MultiLine, and see an EMSI string.
Node 2:420/333 also got an updated IVM flag, but there is a timeout when trying to connect to the advertised port.


Regards, Wilfred

--- FMail-lnx64 2.3.2.4-B20240523
* Origin: NPC Station (2:280/464)

Hi All,

On 2025-04-18 12:04:37, I wrote to you:

2:420/333 also got an updated IVM flag, but there is a timeout when trying to connect to the advertised port.

Another IVM update for this node, and there is now a connect and an EMSI response.


Bye, Wilfred.

--- FMail-lnx64 2.3.2.4-B20240523
* Origin: NPC Station (2:280/464)

02 May 25 12:04, Wilfred van Velzen wrote to All:

2:420/333 also got an updated IVM flag, but there is a timeout
when trying to connect to the advertised port.

Another IVM update for this node, and there is now a connect and an
EMSI response.

How did you test? That's not IVM in port 2030, it's ITN.

'Tommi

--- FastEcho/2 1.46.1 Revival
* Origin: =========================>>>> (2:221/1.254)

Hi Tommi,

On 2025-05-02 15:12:02, you wrote to me:

2:420/333 also got an updated IVM flag, but there is a timeout
when trying to connect to the advertised port.

Another IVM update for this node, and there is now a connect and an
EMSI response.

How did you test? That's not IVM in port 2030, it's ITN.

I'm not testing the protocol. I just connect to the advertised port with telnet, and report on what I see. ;-)

What is IVM anyway? There are only a few minimal mentions of it in the FTSC docs:


FRL-1016:

1.1.8.4. IVM[:3141]
Vmodem protocol according to Ray Gwinn's SIO-package
for OS/2

FTS-5001:

IVM 3141 Vmodem connection using FTS-1 or any other protocol
designed for classic POTS and modem.


Wouldn't the node qualify for IVM under the FTS-5001 "definition" ?


Bye, Wilfred.

--- FMail-lnx64 2.3.2.4-B20240523
* Origin: NPC Station (2:280/464)

02 May 25 14:18, Wilfred van Velzen wrote to Tommi Koivula:

2:420/333 also got an updated IVM flag, but there is a timeout
when trying to connect to the advertised port.

Another IVM update for this node, and there is now a connect and
an EMSI response.

How did you test? That's not IVM in port 2030, it's ITN.

I'm not testing the protocol. I just connect to the advertised port
with telnet, and report on what I see. ;-)

You were lucky this time, you were using telnet to connect vmodem, but it was telnet server indeed. ;)

What is IVM anyway? There are only a few minimal mentions of it in the FTSC docs:

FRL-1016:

1.1.8.4. IVM[:3141]
Vmodem protocol according to Ray Gwinn's SIO-package
for OS/2

From the SIO v1.60 docs:

=== Cut ===

WHAT IS VMODEM

Vmodem is a software implementation of a modem, referred to as a
Virtual Modem. Basically, it attempts to fake out other software
(like terminal programs) into believing they are accessing a real
modem. Vmodem will turn any Terminal into a Telnet Client, and any
BBS into a Telnet Server.

Normal (real) modems provide an interface that allows terminal
programs to pass digital information across telephone lines. Vmodem
does the same thing from the application (terminal) program's point of
view. However, the other side of Vmodem is not a phone line, but a
digital network like Internet. Thus, Vmodem allows the hoards of
communications programs to pass information across Internet instead of
using phone lines.

In addition to acting as a Telnet server, Vmodem uses a newly designed
protocol for communications networks, called the Virtual Modem
Protocol (VMP). At this time, no other programs have implemented VMP,
thus Vmodem is required on both ends of the connection to use the VMP.
However, VMODEM.EXE will accept inbound Telnet connections from any
system, meaning a BBS under vmodem can be accessed by just about
anyone with an Internet connection.

Future implementations of Vmodem may access networks other than
Internet and use TCP/IP implementations other than IBM's. The current
implementation of Vmodem works only on Internet, using the Internet
Access Kit (IAK) that is included with OS/2 V3 and IBM's TCP/IP (for
OS/2) version 2.0, with the August 1994 CSD applied.

A single invocation of Vmodem can service all of the Internet ports
defined in the SIO command line.

=== Cut ===

FTS-5001:

IVM 3141 Vmodem connection using FTS-1 or any other protocol
designed for classic POTS and modem.

Wouldn't the node qualify for IVM under the FTS-5001 "definition" ?

Yes. SIO/VModem can accept telnet and vmodem calls. By default ports ITN:23 and IVM:3141.

'Tommi

--- FastEcho/2 1.46.1 Revival
* Origin: =========================>>>> (2:221/1.254)

Hi Tommi,

On 2025-05-02 17:52:18, you wrote to me:

How did you test? That's not IVM in port 2030, it's ITN.

I'm not testing the protocol. I just connect to the advertised port
with telnet, and report on what I see. ;-)

You were lucky this time, you were using telnet to connect vmodem, but it was
telnet server indeed. ;)

See below.

What is IVM anyway? There are only a few minimal mentions of it in
the FTSC docs:


FRL-1016:

1.1.8.4. IVM[:3141]
Vmodem protocol according to Ray Gwinn's SIO-package
for OS/2

From the SIO v1.60 docs:

=== Cut ===

WHAT IS VMODEM

Vmodem is a software implementation of a modem, referred to as a
Virtual Modem. Basically, it attempts to fake out other software
(like terminal programs) into believing they are accessing a real
modem. Vmodem will turn any Terminal into a Telnet Client, and any
BBS into a Telnet Server.

Normal (real) modems provide an interface that allows terminal
programs to pass digital information across telephone lines. Vmodem
does the same thing from the application (terminal) program's point of
view. However, the other side of Vmodem is not a phone line, but a
digital network like Internet. Thus, Vmodem allows the hoards of
communications programs to pass information across Internet instead of
using phone lines.

In addition to acting as a Telnet server, Vmodem uses a newly designed
protocol for communications networks, called the Virtual Modem
Protocol (VMP). At this time, no other programs have implemented VMP,
thus Vmodem is required on both ends of the connection to use the VMP.
However, VMODEM.EXE will accept inbound Telnet connections from any
system, meaning a BBS under vmodem can be accessed by just about
anyone with an Internet connection.

Future implementations of Vmodem may access networks other than
Internet and use TCP/IP implementations other than IBM's. The current
implementation of Vmodem works only on Internet, using the Internet
Access Kit (IAK) that is included with OS/2 V3 and IBM's TCP/IP (for
OS/2) version 2.0, with the August 1994 CSD applied.

A single invocation of Vmodem can service all of the Internet ports
defined in the SIO command line.

=== Cut ===

If I read that correctly IVM is just an extension of ITN with VMP. So IVM implies ITN by default.

FTS-5001:

IVM 3141 Vmodem connection using FTS-1 or any other protocol
designed for classic POTS and modem.


Wouldn't the node qualify for IVM under the FTS-5001 "definition" ?

Yes. SIO/VModem can accept telnet and vmodem calls. By default ports ITN:23
and IVM:3141.

So I wasn't lucky my simple telnet test worked... ;-)


Bye, Wilfred.

--- FMail-lnx64 2.3.2.4-B20240523
* Origin: NPC Station (2:280/464)

02 May 25 17:38, Wilfred van Velzen wrote to Tommi Koivula:

Yes. SIO/VModem can accept telnet and vmodem calls. By default
ports ITN:23 and IVM:3141.

So I wasn't lucky my simple telnet test worked... ;-)

That was because the server was answering in telnet mode at port 2030. Not in vmodem mode.

You should have tried to connect with VMODEM, which you may not have in linux :).

I can see the difference in my SIO/Vmodem. You can try to connect ports 32/telnet and 3141/vmodem here.

'Tommi

---
* Origin: rbb.fidonet.fi (2:221/360)

Hi Tommi,

On 2025-05-02 18:47:28, you wrote to me:

Yes. SIO/VModem can accept telnet and vmodem calls. By default
ports ITN:23 and IVM:3141.

So I wasn't lucky my simple telnet test worked... ;-)

That was because the server was answering in telnet mode at port 2030. Not in
vmodem mode.

Does it need to be configured before hand what to do on a specific port? Or can it detect if a IVM or ITN node is connecting when it happens.

You should have tried to connect with VMODEM, which you may not have
in linux :).

I certainly don't! ;-)

I can see the difference in my SIO/Vmodem. You can try to connect
ports 32/telnet and 3141/vmodem here.

The response is different indeed...

Bye, Wilfred.

--- FMail-lnx64 2.3.2.4-B20240523
* Origin: NPC Station (2:280/464)

Friday May 02 2025 18:21, Wilfred van Velzen wrote to Tommi Koivula:

Yes. SIO/VModem can accept telnet and vmodem calls. By default
ports ITN:23 and IVM:3141.

So I wasn't lucky my simple telnet test worked... ;-)

That was because the server was answering in telnet mode at port
2030. Not in vmodem mode.

Does it need to be configured before hand what to do on a specific
port? Or can it detect if a IVM or ITN node is connecting when it
happens.

No autodetection, separate ports for each protocol.

You should have tried to connect with VMODEM, which you may not
have in linux :).

I certainly don't! ;-)

;-D

I can see the difference in my SIO/Vmodem. You can try to connect
ports 32/telnet and 3141/vmodem here.

The response is different indeed...

19:21 Incoming Vmodem connection attempt from 45.83.243.76
19:21 The caller is not using a current VMODEM
19:21 Incoming Vmodem connection attempt from 45.83.243.76
19:21 The caller is not using a current VMODEM
19:24 Incoming Telnet connection attempt from 45.83.243.76
19:24 The incoming connect has been assigned to COM2
19:24 COM2 disconnected

'Tommi

---
* Origin: * RBB * Lake Ylo * Finland * (2:221/360)