On Fri, 5 Mar 1999, Jose Angel Amador Fundora wrote:
> On 2 Mar 99 at 14:12, Jonathan NAYLOR wrote:
>
> > The problem with users connecting to the NET/ROM callsign is that
> > the NET/ROM doesn't know whether the person connecting is a user or
> > another node, this is the reason why real NET/ROMs, BPQ, et al,
> > don't generate any connect text in that case.
>
> I would like to see BPQ's BEHAVIOR reproduced in the Linux nodes.
> I have not been able to replicate such connects since I moved to
> Linux.
I seriously doubt this will be changed at least anytime soon. The reason
for all this lies in the AX.25 protocol it self and while the ugly
workarounds in BPQ et al _could_ be included also in linux, I don't think
the developers want to break the current clean code.
> I am running a "pseudo BPQ" set up, even when I do not understand
> fully the reasons for installing several nodes, and I would really
> like to understand WHY it must be that way with Linux. I copied it,
> it does work, in spite I don't understand all the reasons involved,
> but I don't feel comfortable that way. Could someone enligthen me on
> this matter ?
Well if you have run BPQ in the past, you actually run several nodes! You
just didn't necessarily realise it. But If you had NODE=1 and BBS=1 in
bpqcfg.txt then you actually had _two_ nodes. The only difference in Linux
is that you need one additional node in addition to that. And the reason
for that is the ambiguity in incoming AX.25 connections Jonathan
mentioned.
> PS: I am running FBB, JNOS and DXNET along with a linux node. I am
> trying to mimic an old MSDOS setup that worked fairly well under
> DesqView. I have gotten fairly close, but it is not exactly the
> same...and the users were used to access to services THAT way.
I don't see any reason you couldn't have exactly the same setup as before
except for the one additional netrom interface (or node if you want).
--
--... Tomi Manninen / [EMAIL PROTECTED] / OH2BNS @ OH2RBI.FIN.EU ...--
