Subj : One entry point, multiple destination points.
To : Eric Renfro
From : mark lewis
Date : Wed Sep 16 2015 09:04 pm
16 Sep 15 10:21, you wrote to All:
ER> Alrighty. It's been ages since I've used FastEcho, and though I'm not
ER> personally using it, instead trying to help someone else whom already
ER> has it use it, whom is not very savvy with it all.
ok...
ER> Here's the situation. One of my downlinks wants to setup their IRex
ER> and FastEcho on thheir system to receive mail, one from me, one from
ER> another link.
should be a pretty standard setup...
ER> They run multiple BBS systems at the same time using some telnet2bbs
ER> link tool of some kind, I'm not entirely sure about that, but their
ER> BBS's support includes JAM message bases so..
ok... hummm... are they sharing the same JAM bases between those BBSes?? do
they all use the same FTN address? if not then they will need a FE setup for
each BBS instance... even if they are all on the same machine... that means
either copying packets destined for the others to their inbounds or using some
mailer to send to them as normal... i have 4 or 5 systems here all using their
own mailers for this but they all also have their own FTN addresses as
required...
ER> Can anyone help me come up with a reasonably logical idea of how to
ER> set up this link to receive mail from me and internally relay it to
ER> several point point nodes for their multiple BBS systems they have
ER> running?
other than the above ""hints"" for multiple BBSes behind one IP, the setup
should be no different than any other distribution hub system... the specific
points being that each system has its own FTN address (full node or points) and
that there is a proper entry in the nodelist pointing to each domain and/or IP
address...
)\/(ark
... We have no need for ancient ways, our world is doing fine.: Rush
---
* Origin: (1:3634/12.73)
