Hi All.

I have tried to setup FD as Telnet Mailer, but without luck.

I'm using Netserial, and have set it up for Com2.

I'm using ADF as fossil, and I can connect with it. I have tried Netfoss too, but that did'nt work at all!

If any of you guys or girl out there, are using FD as your primary mailer with Telnet, so please give me some response.
Thank you.

Sincerely,
Elmo.

--- FMail 1.60W+
* Origin: DDI BBSystem * BinkP Mail/Freq * Telnet BBS (5123) * 24h (2:230/35)

10 Oct 15 08:27, you wrote to All:

I have tried to setup FD as Telnet Mailer, but without luck.

:(

the main thing to remember is that there needs to be a virtual modem for FD to talk to...

I'm using Netserial, and have set it up for Com2.

I'm using ADF as fossil, and I can connect with it.

:)

i gotta ask, based on your next statement, what do you mean that you could connect... you could connect outbound? others could connect inbound? connections worked both ways? is there a problem with this setup? have you tried using X00 or BNU? they pretty set the standard for FOSSIL drivers when they came on the PC scene...

I have tried Netfoss too, but that did'nt work at all!

in what way didn't it work at all? may be because there's no virtual modem?

If any of you guys or girl out there, are using FD as your primary
mailer with Telnet, so please give me some response. Thank you.

i do but i don't do it on winwhatever... i still use OS/2 with ray gwinn's SIO serial driver package...

)\/(ark

... It's the net: the use of common curtesy is totally out of place.
---
* Origin: (1:3634/12.73)

Hello mark

On Sat 10 Oct 2015 11.02, mark wrote to Elmo Jensen:

the main thing to remember is that there needs to be a
virtual modem for FD to talk to...

I'm using Netserial, and have set it up for Com2.

Netserial _is_ the windows virtual modem from PCMicro, and is configured as preferred.

i gotta ask, based on your next statement, what do you
mean that you could connect... you could connect
outbound? others could connect inbound? connections
worked both ways? is there a problem with this setup?

Yes, for example I can connect to Janis, and get correct mail session answer, but she denied filerequest on her 1:1/0 address, so it was refused. I have tried too to 2:230/152, Gert, and I can connect, but I can see on the screen, I
startup his BBS, before I get redirected to his mailer. When I get redirected to the mailer, it think a lot, and then drop the carrier. The same on 2:230/0, Benny - my uplink! So i'm not sure if it is my setup there is okay, and theres there is wrong, or different.

have you tried using X00 or BNU? they pretty set the
standard for FOSSIL drivers when they came on the PC
scene...

Yes, I used BNU in the start of my modem days, but then I try ADF, and get better performance with that, and since then I have used ADF.

i do but i don't do it on winwhatever... i still use OS/2
with ray gwinn's SIO serial driver package...

I have tried to install OS/2, but get errordump when the system restart after install :( Maybe the HD or the pc is too fast!

Have you filerequest on some of your lines? Where FD is online? So I could try to request from your system, and see how it work against you. Okay?

But for now - thanks for the help!

-=[Best regards]=-
-=[Elmo]=-

--- FMail 1.60W+
* Origin: DDI BBSystem * BinkP Mail/Freq * Telnet BBS (5123) * 24h (2:230/35)

11 Oct 15 06:33, you wrote to me:

the main thing to remember is that there needs to be a
virtual modem for FD to talk to...

I'm using Netserial, and have set it up for Com2.

Netserial _is_ the windows virtual modem from PCMicro, and is configured

as

preferred.

ok... i don't use winwhatever for anything mission critical... ever... so i've also never played with mike's offerings from pcmicro :?

i gotta ask, based on your next statement, what do you
mean that you could connect... you could connect
outbound? others could connect inbound? connections
worked both ways? is there a problem with this setup?

Yes, for example I can connect to Janis, and get correct mail session answer, but she denied filerequest on her 1:1/0 address, so it was

refused.

ok... so use her normal address ;)

I have tried too to 2:230/152, Gert, and I can connect, but I can see
on the screen, I startup his BBS, before I get redirected to his
mailer. When I get redirected to the mailer, it think a lot, and then
drop the carrier.

hunh? he must have his bbs running first and then shelling to the mailer instead of the mailer answering and then passing to the bbs... that's the way it seems to read from what you wrote...

The same on 2:230/0, Benny - my uplink! So i'm not sure if it is my
setup there is okay, and theres there is wrong, or different.

you can try connecting to my system via telnet... frontdoor answers... freqs are welcome... if you telnet with a standard terminal then you will pass through frontdoor (hit esc twice) to my remoteaccess system...

have you tried using X00 or BNU? they pretty set the
standard for FOSSIL drivers when they came on the PC
scene...

Yes, I used BNU in the start of my modem days, but then I try ADF, and get better performance with that, and since then I have used ADF.

ok... i was just suggesting them in case you were having a problem with adf talking to netserial...

i do but i don't do it on winwhatever... i still use OS/2
with ray gwinn's SIO serial driver package...

I have tried to install OS/2, but get errordump when the system restart after install :( Maybe the HD or the pc is too fast!

it depends on which OS/2 you've tried... i have eCS on a system now but i don't
think it is 1ghz or more... and only 384meg of ram, too :)

Have you filerequest on some of your lines? Where FD is online? So I
could try to request from your system, and see how it work against
you. Okay?

my system's address is listed in the nodelist... that's one of the main reasons
for the nodelist... but if you don't have a nodelist since some systems don't need them (but they should!) then you can contact my system via ftn.wpusa.dynip.com... telnet on standard port... be careful that you don't try
too many times too fast... i have an IDS (Intrusion Detection System) that will
block your IP if it thinks you are trying to attack the system... you'll have to contact me via fidonet to have the block removed or wait until the block times out after some days ;)

But for now - thanks for the help!

you are quite welcome :)

)\/(ark

... Just remember, being dead is no excuse for getting behind in your mail.
---
* Origin: (1:3634/12.73)

Re: Who is running FD as Telnet Mailer?
By: Elmo Jensen to All on Sat Oct 10 2015 08:27 am

I have tried to setup FD as Telnet Mailer, but without luck.

What's the problem ?

I'm using Netserial, and have set it up for Com2.

I'm using ADF as fossil, and I can connect with it. I have tried Netfoss too, but that did'nt work at all!

The reason why NetFoss will not work is because it is a FOSSIL for telnet connections. FrontDoor is expecting a FOSSIL for serial ports.

If any of you guys or girl out there, are using FD as your primary mailer with Telnet, so please give me some response.

I have done preliminary testing with NetSerial, FrontDoor and RemoteAccess. Everything works as expected.

Re: Who is running FD as Telnet Mailer?
By: Elmo Jensen to mark lewis on Sun Oct 11 2015 06:33 am

Yes, for example I can connect to Janis, and get correct mail session answer, but she denied filerequest on her 1:1/0 address, so it was refused. I have tried too to 2:230/152, Gert, and I can connect, but I can see on the screen, I
startup his BBS, before I get redirected to his mailer. When I get redirected to the mailer, it think a lot, and then drop the carrier. The same on 2:230/0, Benny - my uplink! So i'm not sure if it is my setup there is okay, and theres there is wrong, or different.

You said you connect to Gert's BBS, which then redirects you to the mailer ? -- that does not sound right. Usually it is the mailer that answers first.

If you are using a virtual modem with FrontDoor, then the system you are connecting to should also be using a virtual modem. The rule is: a virtual modem connects to another virtual modem - and a telnet 'client' connects to a telnet 'server'.

If you are using a virtual modem to connect to a BinkP server, then it will not work. If you use FrontDoor to connect to another frontend mailer that is not FTN compatible, then it will not work. You should ask Benny what mailer he's using -- the safest frontend mailers to use with FrontDoor are D'Bridge and BinkleyTerm (because they are oldschool like FrontDoor).

Yes, I used BNU in the start of my modem days, but then I try ADF, and get better performance with that, and since then I have used ADF.

ADF is all you need these days. I only use BNU for nostalgia reasons. Also, no point using X00 or anything that requires 'config.sys'(unless you're running DOS/w3.x/w9x).

I have tried to install OS/2, but get errordump when the system restart after install :( Maybe the HD or the pc is too fast!
Have you filerequest on some of your lines? Where FD is online? So I could try to request from your system, and see how it work against you. Okay?

Bleh. Do not waste your time with OS/2 :)

01 Apr 16 23:35, you wrote to Elmo Jensen:

I have tried to setup FD as Telnet Mailer, but without luck.

What's the problem ?

I'm using Netserial, and have set it up for Com2.

I'm using ADF as fossil, and I can connect with it. I have tried
Netfoss too, but that did'nt work at all!

The reason why NetFoss will not work is because it is a FOSSIL for telnet connections. FrontDoor is expecting a FOSSIL for serial ports.

actually, frontdoor is expecting a FOSSIL, period... what is on the other side of that FOSSIL frontdoor doesn't care about... frontdoor does send the standard
analogue modem AT commands, though, so the FOSSIL should either eat them or convert them to whatever the other side needs... in the same manner that the FOSSIL will send a "RING" to frontdoor so that it knows there is an incoming connection...

If any of you guys or girl out there, are using FD as your primary
mailer with Telnet, so please give me some response.

I have done preliminary testing with NetSerial, FrontDoor and RemoteAccess. Everything works as expected.

i think the biggest thing is to have either an all in one FOSSIL/telnet shim or
at least a working FOSSIL that can talk to a telnet shim... i'm saying telnet shim but it could be any shim... these same type things were used back in the day when ISDN first came around so that frontdoor could talk to the ISDN device
;)

BTW: what's your real name? this is a fidonet echo... you should use your real name in the header or at least sign your messages with your real name... eye of
the beholder 2 is over there on the other side of the park ;)

)\/(ark

Always Mount a Scratch Monkey

... Cats have fur coats because they look silly in raincoats
---
* Origin: (1:3634/12.73)

01 Apr 16 23:56, you wrote to Elmo Jensen:

Yes, for example I can connect to Janis, and get correct mail session
answer, but she denied filerequest on her 1:1/0 address, so it was
refused. I have tried too to 2:230/152, Gert, and I can connect, but I
can see on the screen, I startup his BBS, before I get redirected to
his mailer. When I get redirected to the mailer, it think a lot, and
then drop the carrier. The same on 2:230/0, Benny - my uplink! So i'm
not sure if it is my setup there is okay, and theres there is wrong,
or different.

You said you connect to Gert's BBS, which then redirects you to the
mailer ? -- that does not sound right. Usually it is the mailer that answers first.

it depends, really... some bbses can operate in shell-to-mailer mode... they either answer the connection and shell to the mailer or they shell to the mailer straight away and then accept a hot line after the mailer answers the line and exits back to the bbs... pcboard and other similar bbses answer the line and then switch to the mailer when they realize the connection is not a human user...

If you are using a virtual modem with FrontDoor, then the system you
are connecting to should also be using a virtual modem. The rule is: a virtual modem connects to another virtual modem - and a telnet
'client' connects to a telnet 'server'.

telnet-to-telnet, yes... but one could have a virtual modem that does ssh or rlogin so they'll also need to connect to the proper end on the other side... a
virtual modem is just a shim between software that is expecting to talk to an analogue modem and a different connection type that speaks another language/protocol... kinda like a media convertor (aka cable modem, dsl modem, fiber optic to cat5)...

If you are using a virtual modem to connect to a BinkP server, then it will not work. If you use FrontDoor to connect to another frontend
mailer that is not FTN compatible, then it will not work. You should
ask Benny what mailer he's using -- the safest frontend mailers to use with FrontDoor are D'Bridge and BinkleyTerm (because they are
oldschool like FrontDoor).

very true...

Yes, I used BNU in the start of my modem days, but then I try ADF, and
get better performance with that, and since then I have used ADF.

ADF is all you need these days. I only use BNU for nostalgia reasons. Also, no point using X00 or anything that requires 'config.sys'(unless you're running DOS/w3.x/w9x).

if you rename x00.sys to x00.exe, you can load it from the command line... no config.sys necessary... x00 was specifically written to be able to do this ;)

I have tried to install OS/2, but get errordump when the system restart
after install :( Maybe the HD or the pc is too fast! Have you
filerequest on some of your lines? Where FD is online? So I could try
to request from your system, and see how it work against you. Okay?

Bleh. Do not waste your time with OS/2 :)

why not? it works perfectly well over here... it has done so since OS/2 Warp 3 Connect came out... we also don't have a bunch of scridiots trying to tear it down ;)

)\/(ark

Always Mount a Scratch Monkey

... Then, quite suddenly, and all at once, nothing happened.
---
* Origin: (1:3634/12.73)

Re: Who is running FD as Telnet Mailer?
By: mark lewis to Dran Draggore on Sat Apr 02 2016 09:24 am

The reason why NetFoss will not work is because it is a FOSSIL for telnet connections. FrontDoor is expecting a FOSSIL for serial ports.

actually, frontdoor is expecting a FOSSIL, period... what is on the other side of that FOSSIL frontdoor doesn't care about... frontdoor does send the standard
analogue modem AT commands, though, so the FOSSIL should either eat them or convert them to whatever the other side needs... in the same manner that the FOSSIL will send a "RING" to frontdoor so that it knows there is an incoming connection...

I guess in that case, the problem with NetFoss might be that it is not a TSR.

I suppose the problem Elmo's having might be mailer compatibility. He did not specify whether he was connecting between two FrontDoor mailers. In any case, I have my doubts about connecting any oldschool mailer to a post-BBS era mailer (eg. safely assume anything created after 2000).

i think the biggest thing is to have either an all in one FOSSIL/telnet shim or
at least a working FOSSIL that can talk to a telnet shim... i'm saying telnet shim but it could be any shim... these same type things were used back in the day when ISDN first came around so that frontdoor could talk to the ISDN device

I think using a virtual modem is the safest approach. Let the virtual modem and FOSSIL do their separate jobs as originally intended by the software.

BTW: what's your real name? this is a fidonet echo... you should use your real name in the header or at least sign your messages with your real name... eye of
the beholder 2 is over there on the other side of the park ;)

My name being used in an old computer game is purely coincidental. I should sue, but the developers already took care of that in their ending credits legal notice - "Any characters in this game who bear resemblance to persons living or dead are purely coincidental".

"Elmo Jensen" - now that sounds like a suspicious name to me.

Re: Who is running FD as Telnet Mailer?
By: mark lewis to Dran Draggore on Sat Apr 02 2016 09:35 am

You said you connect to Gert's BBS, which then redirects you to the mailer ? -- that does not sound right. Usually it is the mailer that answers first.

it depends, really... some bbses can operate in shell-to-mailer mode... they either answer the connection and shell to the mailer or they shell to the mailer straight away and then accept a hot line after the mailer answers the line and exits back to the bbs... pcboard and other similar bbses answer the line and then switch to the mailer when they realize the connection is not a human user...

Ah yes. RemoteAccess does shell-to-mailer mode to speed up the process. I forgot about this.

If you are using a virtual modem with FrontDoor, then the system you are connecting to should also be using a virtual modem. The rule is: a virtual modem connects to another virtual modem - and a telnet
'client' connects to a telnet 'server'.

telnet-to-telnet, yes... but one could have a virtual modem that does ssh or rlogin so they'll also need to connect to the proper end on the other side... a
virtual modem is just a shim between software that is expecting to talk to an analogue modem and a different connection type that speaks another language/protocol... kinda like a media convertor (aka cable modem, dsl modem, fiber optic to cat5)...

My point was to use an approach that minimised potential compatibility issues by sticking as closely as possible to how things were meant to run. The virtual modem's purpose is to substitute for an actual modem. The separation of the modem, FOSSIL and BBS software has been rigorously tested, so deviating from this paradigm is asking for trouble.

SSH/rlogin were added afterwards, probably during a time when companies were transitioning from legacy systems. These new features are not relevant to FrontDoor or what it expects from other mailers.

ADF is all you need these days. I only use BNU for nostalgia reasons. Also, no point using X00 or anything that requires 'config.sys'(unless you're running DOS/w3.x/w9x).

if you rename x00.sys to x00.exe, you can load it from the command line... no config.sys necessary... x00 was specifically written to be able to do this ;)

Wow, I did not know this. But in the spirit of authenticity, X00 belongs in config.sys :)

Bleh. Do not waste your time with OS/2 :)

why not? it works perfectly well over here... it has done so since OS/2 Warp 3 Connect came out... we also don't have a bunch of scridiots trying to tear it down ;)

From a BBS perspective, because most doors are made for DOS. From a business perspective, because OS/2 is dead. Does that make you feel like you have been stabbed in the heart ? Heh.

Hello Dran

On Fri 1 Apr 2016 23.35, Dran wrote to Elmo Jensen:

Re: Who is running FD as Telnet Mailer?
By: Elmo Jensen to All on Sat Oct 10 2015 08:27 am

I have tried to setup FD as Telnet Mailer, but without luck.

What's the problem ?

[....]

Nothing anymore ;)

Thanks for the reply!

-=[Best regards]=-
-=[Elmo]=-

--- FMail 1.60W+
* Origin: DDI BBSystem * BinkP Mail/Freq * Telnet BBS (5123) * 24h (2:230/35)

Hello Dran

On Fri 1 Apr 2016 23.56, Dran wrote to Elmo Jensen:

Re: Who is running FD as Telnet Mailer?
By: Elmo Jensen to mark lewis on Sun Oct 11 2015 06:33am

You said you connect to Gert's BBS, which then redirects

[....]

Thanks for the reply.

-=[Best regards]=-
-=[Elmo]=-

--- FMail 1.60W+
* Origin: DDI BBSystem * BinkP Mail/Freq * Telnet BBS (5123) * 24h (2:230/35)

Re: Who is running FD as Telnet Mailer?
By: mark lewis to Dran Draggore on Sat Apr 02 2016 09:24 am

[....]

"Elmo Jensen" - now that sounds like a suspicious name to me.

Suspicious??? In what way? It's my birthname, thank you!

-=[Best regards]=-
-=[Elmo]=-

--- FMail 1.60W+
* Origin: DDI BBSystem * BinkP Mail/Freq * Telnet BBS (5123) * 24h (2:230/35)

Re: Who is running FD as Telnet Mailer?
By: Elmo Jensen to Dran Draggore on Thu Apr 07 2016 07:03 am

I have tried to setup FD as Telnet Mailer, but without luck.

What's the problem ?

[....]

Nothing anymore ;)

Out of curiosity, what setup are you running now ?

Re: Who is running FD as Telnet Mailer?
By: Elmo Jensen to Dran Draggore on Thu Apr 07 2016 07:09 am

"Elmo Jensen" - now that sounds like a suspicious name to me.

Suspicious??? In what way? It's my birthname, thank you!

Why are you named after a Sesame Street puppet ?

On 10/11/2015 08:26 PM, mark lewis -> Elmo Jensen wrote:

11 Oct 15 06:33, you wrote to me:

the main thing to remember is that there needs to be a
virtual modem for FD to talk to...

I know this thread is ancient... but I am curious about this...

Lets just pretend I am crazed.. ok.. so its not so much pretend...

So I sudo apt-get install dosbox

Then lets say... you put this in the dosbox conf

[serial]
serial1=modem listenport:3141


Then you mount up a C drive with FD etc... installed

XOO loaded up for a FOSSIL and point FD at that FOSSIL with COM1 and dosbox doing its virtual modem thing...

And thus **** potentially *** FD would run via net versus DU???

Have you done this???

I might try it after I rectify some things, due to the idea that is swirling in
my brain.. this is why you should not read echos late at night! :) ;)

I find this very interesting... although I think there are some huge problems in getting FD to actually do this ie: dial something like: fidonet.me.domain


* Origin: news://news.wpusa.dynip.com | acct req'd to post (1:3634/12)

24 Sep 16 19:33, you wrote to me:

the main thing to remember is that there needs to be a virtual
modem for FD to talk to...

I know this thread is ancient... but I am curious about this...

i'm sure you're not the only one ;)

Lets just pretend I am crazed.. ok.. so its not so much pretend...

hahahahaha...

So I sudo apt-get install dosbox

Then lets say... you put this in the dosbox conf

[serial]
serial1=modem listenport:3141

that's the vmodem port... it is generally used for the vmodem protocol which is
a slightly tweaked telnet...

Then you mount up a C drive with FD etc... installed

XOO loaded up for a FOSSIL and point FD at that FOSSIL with COM1 and

dosbox

doing its virtual modem thing...

And thus **** potentially *** FD would run via net versus DU???

that sounds about right... no clue if anyone has actually done it, though...

Have you done this???

no... my main system (still) runs OS/2 with the original SIO/VModem stuff...

I might try it after I rectify some things, due to the idea that is swirling in my brain.. this is why you should not read echos late at night! :) ;)

hahaha... the only thing i'm not sure about is being able to do true multinode with multiple DOSBOXes... i don't know of their file locking stuff will work across the divisions between them...

I find this very interesting... although I think there are some huge problems in getting FD to actually do this ie: dial something like: fidonet.me.domain

FD doesn't have a problem dialing domains... i actually set mine up to dial some with telnet and others with vmodem ;)

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDP/IPS yer doin' it wrong...
... A loaf of bread, a jug of wine, and my offline mail reader.
---
* Origin: (1:3634/12.73)

On 09/24/2016 10:38 PM, mark lewis -> rick christian wrote:

that's the vmodem port... it is generally used for the vmodem protocol which is a slightly tweaked telnet...

Hmmm.. I figured that might be the best choice... that VMODEM protocol came along after I moved on from FTN...

Any pointers to info... what I am finding just keeps going to all that OS2 stuff for drivers.

So best to have this on a differing port then.(?) I guess I will have to flesh out some more things but AFTER I see that this thing is even installable under DOSBOX....

no... my main system (still) runs OS/2 with the original SIO/VModem stuff...

Hmm... well..I guess I will be finding out... VM's are CHEAP! :) ;)

I need tp dig up some more docs on this DOSbox thing.. never played with it...

hahaha... the only thing i'm not sure about is being able to do true multinode with multiple DOSBOXes... i don't know of their file locking stuff will work across the divisions between them...

Never played with it before... so I can't speak to it either.. Right now the noise that is in my head... about using TLB (The Last Byte Memory Manager) in there for EMS/XMS stuff... like I said it really is a bad idea to read echos at
night!!!! My imagination runs away with ideas on things! :) ;)

FD doesn't have a problem dialing domains... i actually set mine up to dial some with telnet and others with vmodem ;)

Really??? I would have expected that the input would parse for 0-9 and reject anything and especially puke on . in there let alone letters..hmm....

HMMM.. interesting....


* Origin: news://news.wpusa.dynip.com | acct req'd to post (1:3634/12)

26 Sep 16 17:57, you wrote to me:

that's the vmodem port... it is generally used for the vmodem
protocol which is a slightly tweaked telnet...

Hmmm.. I figured that might be the best choice... that VMODEM protocol came along after I moved on from FTN...

that must have been before Ray Gwinn (yes, the x00 fossil author) released SIO for OS/2... SIO brought the entire virtual modem thing to the market... it was the first, best and most reliable virtual modem implementation... winwhatever users suffered for many years before a proper one for the NT kernel stuff was available... most of them, however, only did telnet... SIO brought telnet and vmodem at the same time and two SIOs with the same registration number cannot connect with each other... piracy prevention, ya know ;)

Any pointers to info... what I am finding just keeps going to all that
OS2 stuff for drivers.

yup... AFAIK SIO on OS/2 is the only way one can use the vmodem protocol...

So best to have this on a differing port then.(?) I guess I will have
to flesh out some more things but AFTER I see that this thing is even installable under DOSBOX....

to avoid the scanner bots on port 23, choose any other port... you can use 3141
if you like... i was just pointing out that vmodem normally runs on that port...

no... my main system (still) runs OS/2 with the original SIO/VModem
stuff...

Hmm... well..I guess I will be finding out... VM's are CHEAP! :) ;)

so they say ;)

I need tp dig up some more docs on this DOSbox thing.. never played
with it...

hahaha... the only thing i'm not sure about is being able to do true
multinode with multiple DOSBOXes... i don't know of their file
locking stuff will work across the divisions between them...

Never played with it before... so I can't speak to it either.. Right
now the noise that is in my head... about using TLB (The Last Byte
Memory Manager) in there for EMS/XMS stuff... like I said it really is
a bad idea to read echos at night!!!! My imagination runs away with
ideas on things! :) ;)

hahahaha... i'd probably fall back to QEMU from quarterdeck because i know it... no clue if it would even work with today's stuff, though...

FD doesn't have a problem dialing domains... i actually set mine up to
dial some with telnet and others with vmodem ;)

Really??? I would have expected that the input would parse for 0-9 and reject anything and especially puke on . in there let alone letters..hmm....

joho was very forward thinking... frontdoor was the first to offer this capability...

===== fdnode.ctl =====
[snip]
DIAL / 011-
# internet
0000- internet/:115
000- internet
V internet#
[snip local calling replacements]
END
===== end =====

then phone numbers can look like this in the nodelist or the overrides...


#filegate.net
#74.167.111.188
Vquinnspost.nodelist.net
000-192.168.99.23


the '#' signals for a telnet connection... the 'V' for a vmodem connection... '000-' is also telnet... '0000-' is telnet to port 115... in retrospect, using 'V' for the vmodem protocol is not a very good idea because of the confusion of
the meaning of the character... probably better to use another character that is not allowed in domain names... '@', '%', or '^' seem to be better choices for the 'V' in fdnode.ctl and in the phone numbers in the nodelist and overrides...

frontdoor development stopped before the nodelist INA flag was put into use so a lot of stuff has to be done manually instead of reading from the nodelist unless someone wants to write a tool to convert the distributed nodelist to the
form that frontdoor can read directly... it is easy enough to do and there are still examples using '000-' as their areacode to signal that the following numbers are an IPv4 number... IPv6 is different and requires additional conversions... SIO doesn't do IPv6 and frontdoor shouldn't care because it thinks it is talking to a modem...

NOTE that the above numbers and domains are just examples... nothing more...

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDP/IPS yer doin' it wrong...
... Every time I say the word "Exercise" I wash my mouth out with chocolate. ---
* Origin: (1:3634/12.73)

On 09/27/2016 11:14 AM, mark lewis -> rick christian wrote:

that must have been before Ray Gwinn (yes, the x00 fossil author)
released SIO for OS/2...

Ummm.. I left in late '99 due to job relocation and some other things...

yup... AFAIK SIO on OS/2 is the only way one can use the vmodem

protocol...

Well that probably is part of why I never really paid much attention I didn't do OS2! I was dragged kicking and screaming from my DOS world heavily customized with 4DOS and FANSI-CONSOLE to winstupper...in the ~ 5 years or so from that to eXtremely stuPidows.. then I moved to Linux full time via Knoppix with KDE 3 right before that one went down the Linux Holy Roller route ie: "It must be open! ! ! "

to avoid the scanner bots on port 23, choose any other port... you can
use 3141 if you like... i was just pointing out that vmodem normally
runs on that port...

Well I was thinking that putting it there might be "correct" since this is some
sort of "VMODEM" but from what it appears this is probably not the same protocol.

And dosxbox would need to be run as root to get below 1024! And that ain't happening!

I get plenty of scans on stuff... but since SSH and a select few are the only ones passed through.. they get bubckious... I chose to leave SSH v. something else in the off chance I run into things blocking non standard ports which I have with some VPN services and LAN's.

so they say ;)

I spend alot of time using them... If I blow up a VM.. no biggie... I go back to the base image, and go on from there after I triage what went wrong..

Thats why I despise compiling since it takes 3-4-5-x-x- times to try get it work when the instructions mostly leave out the key things, namely dependencies..

I don't install anything till I read, read, read, read, then read read read again, and thats for a DEB!

I need to know what it is going to do to things that could potentially muck up things.

Once I get things to a stable level, then I will install to physical hardware if applicable or create a VM and repeat installs from my notes to get error free operations.

hahahaha... i'd probably fall back to QEMU from quarterdeck because i
know it... no clue if it would even work with today's stuff, though...

I am not sure if you need it as DOSbox I think tries to provide a lot of this...like EMS/XMS etc..there is a lack of info, or info at the level I prefer
on setup and use.

I used QEMU for a long time then TLB came along.. and it ran rings around QEMU.
I got more memory, I think because one of the newer units I built had one of the needed chipsets that would do some of the extra magic that QEMU couldn't I was getting like 760K free DOS or something silly and thats with FANSI-CONSOLE loaded, 4DOS etc...

I think it and Terminate were about the only thing at that time I actually paid
registrations for.. the rest was shareware and lived with its limits like Silver Xpress and SLMR.

joho was very forward thinking... frontdoor was the first to offer this capability...

That definitely happened after '99 then... or if not I didn't pay attention to it in the updates.. I used uucp to get news and mail till then.. relocation brought ISDN, and then finally cable based internet.

#filegate.net
#74.167.111.188
Vquinnspost.nodelist.net
000-192.168.99.23

frontdoor development stopped before the nodelist INA flag was put into use so a lot of stuff has to be done manually instead of reading from
the nodelist unless someone wants to write a tool to convert the distributed nodelist to the form that frontdoor can read directly... it
is easy enough to do

Is there something that outlines what conversions need to be done for FD.. I think I've found 2.26 and a 2.12 SL's or basically read in the domain names in the one field and move them to the phone # location in the nodelist sort of like a FDNODE.txt similar to the binkd list that its little script makes from the raw nodelist.

I can possibly write a BASH or python script to take nodelist.999 in and spit out something for FD to read... maybe even PHP as an option..

and there are still examples using '000-' as their
areacode to signal that the following numbers are an IPv4 number...

Yeah.. I read that in reading the nodelist notes...but I see mostly "unpublished" for nearly 90+% of things.. so this conversion would need to be done.

That clue probably saved me from dropping the experiment when it barfed on the node list...

IPv6 is different and requires additional conversions... SIO doesn't do

IPv6

I don't do IPv6 either... that is proof that engineers should not be allowed to
set standards without supervision! :) ;)

And honestly does EVERYTHING on the planet need an IP???? ;)


* Origin: news://news.wpusa.dynip.com | acct req'd to post (1:3634/12)

27 Sep 16 17:39, you wrote to me:

that must have been before Ray Gwinn (yes, the x00 fossil author)
released SIO for OS/2...

Ummm.. I left in late '99 due to job relocation and some other
things...

yeah, we had SIO with telnet and vmodem protocols before win95 came out... likely you just don't remember or didn't know about the vmodem protocol at that
time :)

yup... AFAIK SIO on OS/2 is the only way one can use the vmodem
protocol...

Well that probably is part of why I never really paid much attention I didn't do OS2! I was dragged kicking and screaming from my DOS world heavily customized with 4DOS and FANSI-CONSOLE to winstupper...in the
~ 5 years or so from that to eXtremely stuPidows.. then I moved to
Linux full time via Knoppix with KDE 3 right before that one went down
the Linux Holy Roller route ie: "It must be open! ! ! "

yep, that explains it :lol: i went from DOS/DESQview to OS/2 and never looked back at anything else for that system... yeah, i ran the various winwhatevers but not for mission critical stuff...

to avoid the scanner bots on port 23, choose any other port... you
can use 3141 if you like... i was just pointing out that vmodem
normally runs on that port...

Well I was thinking that putting it there might be "correct" since
this is some sort of "VMODEM" but from what it appears this is
probably not the same protocol.

well, remember, vmodem is the protocol... virtual modem is the artificial device (modem) that is the shim between analogue FOSSIL comms and telnet or vmodem protocols...

And dosxbox would need to be run as root to get below 1024! And that
ain't happening!

it really doesn't matter since you can forward your WAN side port 23 to any other port internally so set your BBS up on 2023 for instance and forward port 23 to that... the BBS doesn't have to know that it isn't talking to port 23 all
the way...

I get plenty of scans on stuff... but since SSH and a select few are
the only ones passed through.. they get bubckious... I chose to leave
SSH v. something else in the off chance I run into things blocking non standard ports which I have with some VPN services and LAN's.

i always configure my SSH to use a non-standard port anyway... that allows me to do silly things like running SBBS and let it provide SSH on port 22 ;)

so they say ;)

I spend alot of time using them... If I blow up a VM.. no biggie... I
go back to the base image, and go on from there after I triage what
went wrong..

yep...

Thats why I despise compiling since it takes 3-4-5-x-x- times to try
get it work when the instructions mostly leave out the key things,
namely dependencies..

sadly that's because developers code and don't always remember the individual steps or additional requirements...

I don't install anything till I read, read, read, read, then read read read again, and thats for a DEB!

screw that shite :lol:

I need to know what it is going to do to things that could potentially muck up things.

agree there... for me, that goes for most anything, though... not just DEB...

Once I get things to a stable level, then I will install to physical hardware if applicable or create a VM and repeat installs from my
notes to get error free operations.

sometimes it is too much busy work, too...

hahahaha... i'd probably fall back to QEMU from quarterdeck because i
know it... no clue if it would even work with today's stuff,
though...

I am not sure if you need it as DOSbox I think tries to provide a lot
of this...like EMS/XMS etc..there is a lack of info, or info at the
level I prefer on setup and use.

i was thinking that DOXBOX was the virtual machine and you could use your own DOS on it...

I used QEMU for a long time then TLB came along.. and it ran rings
around QEMU.

i've never heard of TLB... if i have, it was for a very brief passing moment back in the '90s...

I got more memory, I think because one of the newer units I built had
one of the needed chipsets that would do some of the extra magic that
QEMU couldn't I was getting like 760K free DOS or something silly and thats with FANSI-CONSOLE loaded, 4DOS etc...

I think it and Terminate were about the only thing at that time I
actually paid registrations for.. the rest was shareware and lived
with its limits like Silver Xpress and SLMR.

joho was very forward thinking... frontdoor was the first to offer
this capability...

That definitely happened after '99 then... or if not I didn't pay attention to it in the updates.. I used uucp to get news and mail till then.. relocation brought ISDN, and then finally cable based internet.

i am/was a frontdoor beta tester so i had access to additional capabilities that were not available to the mainstream users ;)

#filegate.net
#74.167.111.188
Vquinnspost.nodelist.net
000-192.168.99.23

frontdoor development stopped before the nodelist INA flag was put
into use so a lot of stuff has to be done manually instead of reading
from the nodelist unless someone wants to write a tool to convert the
distributed nodelist to the form that frontdoor can read directly...
it is easy enough to do

Is there something that outlines what conversions need to be done for
FD..

not really... just a matter of creating a slightly older format of nodelist and
moving the domain from the INA flag or the system name field to the phone field
and prefixing it with 000- BUT only doing this with nodes flying the ITN or IVM
flags... remember, the nodelist is for mailers so it doesn't matter if there's a BBS or not... only that there's a mailer on the listed ports... that's one reason why so many have embraced binkd and the binkp protocol... they fly on another port and leave 23 alone for the BBS to ride on... kinda like having two
phone lines... one for the BBS and one for the mailer so the two don't interfere with each other and the mailer rides beside the BBS instead of in front of it...

I think I've found 2.26 and a 2.12 SL's or basically read in the
domain names in the one field and move them to the phone # location in
the nodelist sort of like a FDNODE.txt similar to the binkd list that
its little script makes from the raw nodelist.

yeah, kinda similar to that...

I can possibly write a BASH or python script to take nodelist.999 in
and spit out something for FD to read... maybe even PHP as an option..

the script that creates the distributed binkd.txt is written in perl...

and there are still examples using '000-' as their areacode to signal
that the following numbers are an IPv4 number...

Yeah.. I read that in reading the nodelist notes...but I see mostly "unpublished" for nearly 90+% of things.. so this conversion would
need to be done.

yeah, we've split "PVT" and "-Unpublished-" from each other... one does not require the other these days... this because some could not agree that the "phone number field" is really a "contact field" and allow IP numbers and/or domains to be listed there... frontdoor, if it had been able to remain in development would have helped to force that option and pedantic arseholes would
not have complicated things like they have... "it says phone field so phone numbers are all that's allowed there. we'll have to find somewhere else to put IP numbers and domain names. then you folks using other software that can't handle the new format will have to write yourselves a nodelist shim to move things where you need them to be." :grumble: [/rant]

That clue probably saved me from dropping the experiment when it
barfed on the node list...

TBH, i really don't even need to be running FD any more... very rarely do i get
any mailer connections over telnet... tobias (from fastecho) still polls me on telnet but he's using some winwhatever mailer instead of frontdoor like he used
to do... sometimes i get a FREQ or two but most of my traffic is now using binkp on port 24554... me using frontdoor has, however, allowed me to detect and write some IDS/IPS rules for a recent round of skiddiots and their infestation bots ;)

IPv6 is different and requires additional conversions... SIO doesn't
do IPv6

I don't do IPv6 either... that is proof that engineers should not be allowed to set standards without supervision! :) ;)

hahahahahahahahaha...

And honestly does EVERYTHING on the planet need an IP???? ;)

that's my thing, too... it is no one's business how many machines i have on my network and you're surely not going to charge me for each one that uses the internet... we won't even mention that 640k is enough for anyone and the number
of available IPs is no more or less shortsighted than IPv4 is/was... available IPv6 numbers will run out one day...

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDP/IPS yer doin' it wrong...
... Famous Last Words: "It hurts." - Chas. DeGaulle
---
* Origin: (1:3634/12.73)

On 09/28/2016 03:31 AM, mark lewis -> rick christian wrote:

yeah, we had SIO with telnet and vmodem protocols before win95 came
out... likely you just don't remember or didn't know about the vmodem protocol at that time :)

If it wasn't in DOS at the time.. I was pretty good at sticking my head in the sand and ignoring it..

I only used wfwg for 2 reasons

1) My ICLID program forced it... there really was no good ICLID program for DOS
which would forward to a pager

2) LAN, I used 10Base2 longer than probably any one on the planet! :)

So I was dragged kicking and screaming to it.. but spent most of the time in a DOS console.

yep, that explains it :lol: i went from DOS/DESQview to OS/2 and never looked back at anything else for that system... yeah, i ran the various winwhatevers but not for mission critical stuff...

DOS -> wfwg -> 98 -> xp -> Linux

Linux was running along side things for a long time as I was used to it from my
VAX, VMS, and other main frame stuff, and we had a XENIX (yeah I know where it came from! :( ) at work for stuff...

I was really more preoccupied with uucp and FTN stuff to look too far outside it..

And I never had OS2 capable hardware.

it really doesn't matter since you can forward your WAN side port 23 to any other port internally so set your BBS up on 2023 for instance and forward port 23 to that... the BBS doesn't have to know that it isn't talking to port 23 all the way...

Yeah, it can... but I've run across a few places of wifi and VPN's that hork up
non standard ports...

I can VPN into my own server to eliminate things most times...

sadly that's because developers code and don't always remember the individual steps or additional requirements...

That, and theres a lot of stuff that they don't notate... in ONE, and ONLY ONE instance have I seen instructions that work... that is to compile Darkice on Raspian, since I need MP3 support and Debians DFSG removes it! :( urrrrgghhh...

About the only other thing I've seen work as well is the VMWare Player installer which if you let them catch up to the release of *Buntu & Kernel, you
just chmod +x the installer, sudo sh installit.sh and it compiles the kernel stuff it needs...

If you get too bleeding edge with it.. prepare for the pain! :) ;)

screw that shite :lol:

I was more rogue like that.. I learned my lesson the HARD WAY by screwing up some stuff! No more!

Nope... Read, read, read, compare notes... ok... read, read... put it in a VM..
success?? OK... COPIOUS AND RUTHLESS NOTES via TEE and by hand....

That lead to my VM Guru'ness! :)

agree there... for me, that goes for most anything, though... not just DEB...

When I can repeat my 99.9% success rate with DEBS and/or apt-get via regular repos' or PPA's... then I will change my opinion of RPM... and it is unlikely that will ever, EVER happen!

Same package of stuff for CentOS.. FAIL, FAIL, FAIL.. I think the first time I did it on my own it took 2-3 hours over 2 days to find the various EXACT versions of other RPM's it needed to get it to compile/install from that RPM

versus

sudo apt-get install mystuff

Setup up, and moved on in less than 30 minutes.

When its my own time it even still not going to devote that kind to that kind of hunt... When its company time.. well then... I ain't paying for that kind of
nonsense.

sometimes it is too much busy work, too...

It is/can be... but SAFETY is a key portion of my job. Myself and my team have
become quite good at turning up VM's playing with them, getting what we need to
install setup and go...

I always take a base image for each ESR release that is the standard image for

Server
Desktop
LTSP Server
Thin clients

Outside my direct department they use nothing by LTSP thin setups... The little
cubites just point and clickey on things.. they can't really screw it up, too much! :) ;)

When the distro doesn't include basic things like nslookup in the ISO's something is wrong... We/I have some other personal things....

Like the pile of dead ones I have to try to:

purge systemd
install upstart
install lightdm or KDM to get an XDMCP capable DM...

All die! 16.04 just won't revert.. or well I should say they revert back to upstart, but with out an XDMCP capable DM,... useless. so 16.04 is banned... and Devuan well is fouled due to DFSG.. and it really is not got a lot of steam
to get things going.. last I looked it didn't have anything to even install.. but the fact I would need to do huge amounts of compiling of stuff... no thanks...I am not sure what my plan is yet for post 2019... but things look bleak. systemd, mir/wayland... all solutions to problems which, well don't exist. And BREAK in MAJOR WAYS things I do, daily, like XDMCP!

i was thinking that DOXBOX was the virtual machine and you could use
your own DOS on it...

DOSBox sort of takes it all on... there is some HOWTO's about putting DRDOS etc
in...the docu sucks for this, and it seems aimed more at a group, gamers, which
is another area I am not inline with, and alot of emphasis on putting junky software into things. :) ;)

DOSemu needs installs of full DOSetc..

i've never heard of TLB...

You probably had to be big into shareware and the various chipsets out there..TLB took advantage of advanced features that alot of the other memory managers didn't. Based on going the OS2 route I doubt there was a need for some
of the shenanigans of TLB etc.. Don't know, never looked at OS2 as more than, oh great, another GUI thingy...

Since I've built all my own boxes since.. well a long time... I was into all the various tricks that some MB's incorporated to get more RAM for DOS.

I also got HUGE PILES of disks each month with shareware on them, plus I was connected to various FDN's to get stuff, and DL'd tons of stuff too.

i am/was a frontdoor beta tester so i had access to additional capabilities that were not available to the mainstream users ;)

So??? I take it this never made it into a "release" version that us mere mortals saw? Ie: V2.25SL or something???

If not I guess I won't bother playing with it...if it did, which one?

That way I grab the right one to play with... or stop if that feature never made it to the public.

not really... just a matter of creating a slightly older format of nodelist and moving the domain from the INA flag or the system name
field to the phone field and prefixing it with 000- BUT only doing this

I figure I can use Python or PHP to do the conversions.. I deal with those daily.

the script that creates the distributed binkd.txt is written in perl...

Yeah.. never was into PERL...

yeah, we've split "PVT" and "-Unpublished-" from each other... one does not require the other these days... this because some could not agree
that the "phone number field" is really a "contact field" and allow IP numbers and/or domains to be listed there... frontdoor, if it had been able to remain in development would have helped to force that option and

Yeah I figured that that whole thing was a mess from the various iterations it appears things went through.

That clue probably saved me from dropping the experiment when it
barfed on the node list...

TBH, i really don't even need to be running FD any more... very rarely
do i get any mailer connections over telnet... tobias (from fastecho) still polls me on telnet but he's using some winwhatever mailer instead

I have a couple of reasons for trying this...

1) Pet project
2) Nostalgia
3) Another idea for something, I don't want to blurt out just yet..

1 & 2 really more for my own fun... So I am amused by simple things! :) ;)

I honestly would be quite amused to just see FD run under Linux! I know its not
really natively running, but I can live with the DOSbox shim whereas I can't the mono virus and its cousin WINE. BLECH! PWETTTW!

To be honest I really would have thought that this Fido stuff would have been more ported to Linux to begin with since its more like "DOS" but with out some of the hassles. Yes it might have few different hassles say X if you want GUI. And binaries can be distributed if you just package up things in DEB, and you don't have to give the source out... Yeah the whiner wieners will whine, but I ignore them... I could care less about the source! 95% of the users could care less. They are like me install it get things done, move on in life!

And honestly does EVERYTHING on the planet need an IP???? ;)

that's my thing, too... it is no one's business how many machines i have on my network and you're surely not going to charge me for each one that uses the internet... we won't even mention that 640k is enough for
anyone and the number of available IPs is no more or less shortsighted than IPv4 is/was... available IPv6 numbers will run out one day...

My gripe with IP6 is the total stupid, and STUPID interface!


HEX v. 127.0.0.1 so we need more.. come up with IPvX and just add more like 127.0.0.0.0.1 or something... or 0.0.0.127.0.0.1 . Then add in all the nonsesne
on how IPv6 can be shrunk for repeating stuff... OH PUHLEASE! That is the kind of crap that happens when engineers are left unsupervised and some one who doesn't understand it ratifies it via rubber stamp as a "standard."

Then I like all the schmucks who are just going to start running around connecting any and everything to the net because it has v6 and they think it makes them more secure v. a proper firewall.... and the railing against NAT.. Meh... I don't see the big deal.. I've yet to see a situation where being directly on the internet behind a firewall versus NAT really made that big a difference except when you want tons of apache servers running on port 80...Myabe I jusst have not found the right prickly hardware/software... but I really don't want to be hosting httpd servers locally for my stuff that the public is traversing into my network.. I'd rather they be out there in a DC where there is no connection to my network in a way they could access things they don't need... Backups yeah.. I can spin up some in an emergency... but the
routine stuff is in DC's elsewhere.

Much like being dragged into windumber, I will go kicking and screaming into IPv6 only when forced... I just don't see the need... The world has not come to
an end.. servers come online all the time with IP4 without a big deal...


* Origin: news://news.wpusa.dynip.com | acct req'd to post (1:3634/12)

I have tried to setup FD as Telnet Mailer, but without luck.
I'm using Netserial, and have set it up for Com2.

I'm using ADF as fossil, and I can connect with it. I have tried
Netfoss too, but that did'nt work at all!

If any of you guys or girl out there, are using FD as your
primary mailer with Telnet, so please give me some response.
Thank you.

On the reboot development environment, I'm currently running NetSerial and NetFoss, and I can connect to just about any system via Internet. This is done under VirtualBox and a Windows XP "CMD Window".

FrontDoor talks to NetFoss, NetFoss talks to NetSerial, and NetSerial talks to the world.

You first checkpoint should be to see if you can load up the FrontDoor Terminal
and talk to the "modem" (which is actually NetSerial).



-joho

---
* Origin: FrontDoor | defsol.com | reboot.defsol.com | Sweden (2:20/4609)

I have tried to setup FD as Telnet Mailer, but without luck.
I'm using Netserial, and have set it up for Com2.

I'm using ADF as fossil, and I can connect with it. I have tried
Netfoss too, but that did'nt work at all!

If any of you guys or girl out there, are using FD as your
primary mailer with Telnet, so please give me some response.
Thank you.

I must be the only one doing this, but I am doing just what the original poster
is trying to do, but only under ArcaOS 5.0.1 (aka OS/2 Warp 5).

--- Maximus/2 3.01
* Origin: Neptune's Lair * Olive Branch MS * os2bbs.org (1:116/17)

* On Sun 17 Sep 2017 10.51, <Robert Wolfe> wrote:

I must be the only one doing this, but I am doing just what the
original poster is trying to do, but only under ArcaOS 5.0.1 (aka
OS/2 Warp 5).

Indeed. Good to see it's working :) I too, may venture down th eOS2/ArcaOS path if I find the time, but perhaps it's (time) better spent coding instead :)

Though with NetSerial (and possibly NetFoss) it should work in many Windows environments.


-joho

---
* Origin: reboot.defsol.com (2:20/4609)

I must be the only one doing this, but I am doing just what the original poster is trying to do, but only under ArcaOS 5.0.1 (aka OS/2 Warp 5).

I had one setup... no-one to poll. FD/2 ... There are a few out there just hunt around. Something happend to my InterNET REX so it's down for now. I also setup Mystic BBS, and for the most part they have the mail thing wrapped up.

with JoHo back in the saddle I'd like to see where he goes with a windows or linux version. As much as I think/thought OS2 was/is cool.... Windows or
Linux is where it's at.

I have a big wish for the future of FrontDoor... I'd like it to be able to spawn a telnet session off a modem line. There are a few applications out there... dialup2telnet.... and Synchronet, or Digital Man, has made one as well. There was never an OS2 version of those programs, know nothing about programming so I have no clue how to port said code...

Anyway, FD is going to be bigger and better...

Just saying...

IB JOE
AKA Joe Schweier
SysOp of Joe's Computer & BBS
Telnet: joesbbs.com

--- Mystic BBS v1.12 A35 (Raspberry Pi/32)
* Origin: Joe's Computer & BBS -=joesbbs.com=- (1:342/200)

I have a big wish for the future of FrontDoor... I'd like it to
be able to spawn a telnet session off a modem line. There are
a few applications out there... dialup2telnet.... and Synchronet,
or Digital Man, has made one as well. There was never an OS2
version of those programs, know nothing about programming so I
have no clue how to port said code...

What is the use case?



-joho

---
* Origin: reboot.defsol.com (2:20/4609)

On 09/18/17, Joaquim Homrighausen said the following...

I have a big wish for the future of FrontDoor... I'd like it to
be able to spawn a telnet session off a modem line. There are
a few applications out there... dialup2telnet.... and Synchronet,
or Digital Man, has made one as well. There was never an OS2
version of those programs, know nothing about programming so I
have no clue how to port said code...

What is the use case?

Okay, not sure of your question... So I'll answer the one I think you're asking. There are a few programs out there... Synchronnet has one called sexpots... the pots part of this word is exactly what you're
thinking... P.O.T.S. ... the sex part was added on by Digital Man... Apparently, like the powers to be in FidoNET, Rob should have rubbed one out before naming software.

All that aside, If you have a dialup line and have a mailer, sexpots has a windows flavor, the mailer answers the call... people press twice to gain access to the BBS... Where themailer errors out to pull up the BBS
commandline to exicute the BBS it pulls up sexpots.

Sexpots then telnets you to your BBS through a modem connection, since most BBSes are telnet systems, if they don't support that internaly they have
access to it.

Sexpots is a stand a lone product, can be ran without a mailer. It can
answer calls and send a user to said telnet address. There is an other
product called dialuptotelnet...

These only come in windows flavors, not sure if Duce has ported Sexpots to Linux.

The mailer choices we have access to are slim, I mean if you are using native 32Bit software in an other platform other than DOS... there are options, but none like FrontDoor.

Long live FrontDoor, all hale %JoHo%

:)

IB JOE
AKA Joe Schweier
SysOp of Joe's Computer & BBS
Telnet: joesbbs.com

--- Mystic BBS v1.12 A35 (Raspberry Pi/32)
* Origin: Joe's Computer & BBS -=joesbbs.com=- (1:342/200)

What is the use case?

Okay, not sure of your question... So I'll answer the one I think
you're asking. There are a few programs out there... Synchronnet
has one called sexpots...

Fair enough. I'll have to look a bit deeper into this once I get that far. I'm sure you'll remind me again when the time comes :)

Thanks.




-joho

---
* Origin: reboot.defsol.com (2:20/4609)

Fair enough. I'll have to look a bit deeper into this once I get that
far. I'm sure you'll remind me again when the time comes :)

Are we there yet??
HAHA

Thanx...

Look forward to see what's going on with FD

IB JOE
AKA Joe Schweier
SysOp of Joe's Computer & BBS
Telnet: joesbbs.com

--- Mystic BBS v1.12 A35 (Raspberry Pi/32)
* Origin: Joe's Computer & BBS -=joesbbs.com=- (1:342/200)