Subj : One entry point, multiple destination points.
To : mark lewis
From : Eric Renfro
Date : Sat Sep 19 2015 01:40 pm
Re: One entry point, multiple destination points.
By: mark lewis to Eric Renfro on Wed Sep 16 2015 09:04 pm
ML> 16 Sep 15 10:21, you wrote to All:
ER>> Alrighty. It's been ages since I've used FastEcho, and though I'm
ER>> not personally using it, instead trying to help someone else whom
ER>> already has it use it, whom is not very savvy with it all.
ML> 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.
ML> 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..
ML> ok... hummm... are they sharing the same JAM bases between those BBSes??
ML> do they all use the same FTN address? if not then they will need a FE
ML> setup for each BBS instance... even if they are all on the same machine...
ML> that means either copying packets destined for the others to their
ML> inbounds or using some mailer to send to them as normal... i have 4 or 5
ML> systems here all using their own mailers for this but they all also have
ML> their own FTN addresses as required...
No sharing or JAM message bases, all completely independant of each other.
Ideally, not sharing the same FTN address, but if that is possible, then it
could be viable, though I'd think a point node would be better personally. Have
one BinkD server act as the primary node for the whole list of internal BBS's,
and then serve out to each point from there acting as the gateway. That reduces
my redundant load, and puts them in proper control as a point-node should be,
since he only runs a mailer on one system and one mailer, IRex, and all on
Windows, which I haven't touched much for years. :)
So, here's the question of all questions then. How do you determine which PKT
is for which address, or can you easily? If that's reasonably plausible then,
hmmm.. I know sort of the concept, but I've never done this setup myself,
always had many different systems to work with, or these days, multiple systems
and multiple virtual machines. :)
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?
ML> other than the above ""hints"" for multiple BBSes behind one IP, the setup
ML> should be no different than any other distribution hub system... the
ML> specific points being that each system has its own FTN address (full node
ML> or points) and that there is a proper entry in the nodelist pointing to
ML> each domain and/or IP address...
Hmmm. Definitely a bit more difficult than I imagined. I keep wanting to
utilize his linux system, but he's not so keen on that. But, with it, I could
make it handle most everything fairly well, up until it has to still handle
mail tossing to the various Windows system's BBS systems, then that situation
comes right back to a system with multiple point nodes and BBSs to toss to.
heh.
Is it unreasonable to assign multiple nodelist entries to someone running
multiple BBS's even if they're behind a single IP/mailer, and just have my side
route all their IP's to their respective mailers? Coming from an NC perspective
on that question. hehe
