The BBS configs are out on an NFS drive mounted by each node and run
from there. This works fine for the BBS itself, but somehow breaks FrontDoor. So I need to find a way to get NFS working with FrontDoor,
or an alternate file sharing system. Lanmanager may work, but I've
never had any joy doing that under msdos, over tcp. It'll have to talk
to SAMBA 4.x
The second issue I have is, if I take all the NFS gear out the way I can have FrontDoor up and running, answering and generally doing its thing. I've looked at route.fd and the nodelist compiles alright, but the
system refuses to poll. The only thing of note that I've found is that the Terminal in FrontDoor believes all the listed systems in the
nodelist are PVT and so won't try to dial them from there. Does anyone else have this issue? And just out of interest how do you ensure FD
dials an IP address instead of looking for a Ph number.
I can't be of help here I am running FrontDoor, Remoteaccess and Fmail under Win 7 with Netserial.
I have had the same problem and could not find the correct way to make FD look for the IP so I just pasted the ip and port number into the area where the phone number is and it called out once a preset event was triggered. I know this is not the correct way to do it but it got me connecting to the 21:3/100 HUB and I have not really looked at it since.
I stuck with MS-SOD rather than win, but as I say I never had any joy
with
lanmanager over tcp.... does anyone have a driver load sequence they
might
share for that?
Spec
Hi,
On 08 May 2019, Spectre said the following ...
The BBS configs are out on an NFS drive mounted by each node and run
from there. This works fine for the BBS itself, but somehow breaks
FrontDoor. So I need to find a way to get NFS working with FrontDoor,
or an alternate file sharing system. Lanmanager may work, but I've
never had any joy doing that under msdos, over tcp. It'll have to talk
to SAMBA 4.x
I can't be of help here I am running FrontDoor, Remoteaccess and Fmail under
Win 7 with Netserial.
The second issue I have is, if I take all the NFS gear out the way I can
have FrontDoor up and running, answering and generally doing its thing.
I've looked at route.fd and the nodelist compiles alright, but the
system refuses to poll. The only thing of note that I've found is that
the Terminal in FrontDoor believes all the listed systems in the
nodelist are PVT and so won't try to dial them from there. Does anyone
else have this issue? And just out of interest how do you ensure FD
dials an IP address instead of looking for a Ph number.
I have had the same problem and could not find the correct way to make
FD
look for the IP so I just pasted the ip and port number into the area
where
the phone number is and it called out once a preset event was
triggered.
I know this is not the correct way to do it but it got me connecting
to the
21:3/100 HUB and I have not really looked at it since.
Hopefully someone with a bit more expertise in FD will be able to
comment and
we can both figure this out :^)
Re: Re: FrontDoor and DOS networking issues.
By: Crew to Spectre on Thu May 09 2019 06:57 pm
I can't be of help here I am running FrontDoor, Remoteaccess and Fmail
under Win 7 with Netserial.
That's cool. Back in the 90s, I also used FrontDoor, RemoteAccess,
and FMail
for my BBS setup.
On 05-10-19 07:49, Joacim Melin wrote to Nightfox <=-
I would love to setup a multi-node RA again but the PD version still
only supports two nodes and the PRO version never was released as free (and the current owner never replies to email so you can't really buy
it either I suppose...).
On 05-10-19 13:44, Spectre wrote to Crew <=-
I stumbled onto the same solution. As soon as FD sees -unlisted- it
seems to assume private and undiallable. I couldn't bypass that with a PVT number listing, but did get a result with putting the FQDN in the phone number space.
On 05-10-19 07:49, Joacim Melin wrote to Nightfox <=-
I would love to setup a multi-node RA again but the PD version still
only supports two nodes and the PRO version never was released as free
(and the current owner never replies to email so you can't really buy
it either I suppose...).
It's a pity, would be nice to have RA back up and running under a DOS
VM. I
like the idea of a Qemu VM running DOS. I can use tcpser and tty0tty
for
telnet access, and use the good old tosser, etc. Only difference is
I'd not
have to run a mailer, and simply have binkd running on the host OS,
and
communicating via semaphores. My old systems used BinkleyTerm, so I
know how
to use BSO with that generation software. What would be a bigger
issue is
scheduling mail sessions, I don't know how well the old software
shares the
messagebase with RA. My old system was single line, so it never had
to worry
about this, but the reincarnation would need to be able to handle
tossing and
BBS use at the same time.
Hardware could be an old netbook. :)
On 05-10-19 10:03, Joacim Melin wrote to Vk3jed <=-
AFAIK Frontdoor can write to and read from JAM messagebases that RA
also can use and it works fine with several nodes.
You could probably massage the nodelist with a Perl script or similar. :)
Also there's the issue of SMB protocols and the like from old software like that - what file server are you going to connect to?
On 05-10-19 22:27, Spectre wrote to Vk3jed <=-
You could probably massage the nodelist with a Perl script or similar. :)
Ahh no not me, maybe a bad bash script.. :P
On 05-10-19 10:03, Joacim Melin wrote to Vk3jed <=-
AFAIK Frontdoor can write to and read from JAM messagebases that RA
also can use and it works fine with several nodes.
Hmm, thought FD was a mailer, not a tosser. :) Besides, as I said, I
would be
using binkd (in the host OS), so I can run binkp sessions.
I have had the same problem and could not find the correct way to make FD
look for the IP so I just pasted the ip and port number into the area where
the phone number is and it called out once a preset event was triggered.
I know this is not the correct way to do it but it got me connecting to the
21:3/100 HUB and I have not really looked at it since.
Hopefully someone with a bit more expertise in FD will be able to comment and
we can both figure this out :^)
I'll check my Frontdoor setup tonight. I got it working with Netserial just fine but it requires some fair amount of voodoo in route.fd.
Also there's the issue of SMB protocols and the like from old software
like that - what file server are you going to connect to?
At this stage Ubuntu 14.04, so that'll be samba 4.x.... if I have to I
can
downgrade it.. or cripple it... or maybe even relay it through a
second
server :) Where theres a willy theres a wendy... erm whoops wrong
saying.
On 05-10-19 11:55, Joacim Melin wrote to Vk3jed <=-
Yeah, well FD can do a lot of things. Also it's cooler than Binkd
because it's SWEEEEEDISH.
Joacim Melin wrote to Spectre <=-
I say do it properly retro: Windows NT 4.0 Server. :)
On 05-10-19 11:55, Joacim Melin wrote to Vk3jed <=-
Yeah, well FD can do a lot of things. Also it's cooler than Binkd
because it's SWEEEEEDISH.
But it doesn't do binkp. :P
Joacim Melin wrote to Spectre <=-
I say do it properly retro: Windows NT 4.0 Server. :)
A friend of mine has a DEC Alpha box running NT 3.51, why not go all
the way?
On 05-13-19 06:14, Joacim Melin wrote to Vk3jed <=-
But it doesn't do binkp. :P
Well, that may change sometime in the future.
I would love to setup a multi-node RA again but the PD version still only supports two nodes and the PRO version never was released as free (and the current owner never replies to email so you can't really buy it either I suppose...).
Cä> eI have had the same problem and could not find the correct way to mak
FD
look for the IP so I just pasted the ip and port number into the area
where
the phone number is and it called out once a preset event was
triggered.
I know this is not the correct way to do it but it got me connecting
to the
21:3/100 HUB and I have not really looked at it since.
Hopefully someone with a bit more expertise in FD will be able to
comment and
we can both figure this out :^)
I'll check my Frontdoor setup tonight. I got it working with Netserial
just fine but it requires some fair amount of voodoo in route.fd.
It messed up the formatting a bit I think.
It's actually quite easy:
Phone <nodenumber as it exists in the nodelist> IP/hostname:port
;IBN
So making FD "dial" a hostname is done via fdroute.ctl. Mine looks like
this:
C:\fd\nodelist>more fdnode.ctl
Phone 2:221/360 rbb.fidonet.fi:32 ;IBN Phone 2:221/1 rbb.bbs.fi:32 ;IBN Phone 21:3/100 ipv4.agency.bbs.nz:24558 ;IBN
You then need to compile fdnode.ctl via fdnc.
It's actually quite easy:
Phone <nodenumber as it exists in the nodelist> IP/hostname:port
;IBN
Sysop: | echicken |
---|---|
Location: | Toronto, Ontario |
Users: | 2,224 |
Nodes: | 6 (0 / 6) |
Uptime: | 09:23:54 |
Calls: | 14,143 |
Files: | 295 |
Messages: | 551,261 |