But I just connected to my Netrom k5di-1 and instead of that
useless to a human connection it gave me my Xfbb! I have no idea how that
is happening. It is clearly a problem. Yet another one...:-)
Do not blame you for getting tired Tomi. If you have some paper
that explains this stuff send it. I have the how-to but it doesn't talk to
the BPQ Look which most hams would like to have. In fact if I EVER learn
how to do this I will write a how-to...:-)
On Tue, 8 Sep 1998, Tomi Manninen wrote:
> I'm getting a bit tired of this pattern repeating over and over...
>
> > My Xfbb listens for k5di-3 and the DX Cluster listens for k5di-5.
>
> Are you SURE your FBB is listening on the callsign you say. That is what I
> wanted you to verify but of course you couldn't do that. Just give me a
> cut and paste of the output of "nlinks" on your own LinuxNode and I'll be
> happy.
>
> > The netrom call is k5di-1. The nodes I made show a proper node listing
> > except instead of calling, for Xffb k5di-3, it called k5di-1.
> >
> > That is the problem and I have not figured out how to change this.
>
> "... instead of calling, for k5di-3, it called k5di-1 ..."
>
> Ok. There are two possible causes. Your bug report is, as usual, very
> vague. If you just would respect us enough not to bother us with what you
> _think_ is happening but gave us just the facts this would be much easier.
> In this case a "listen" dump would have said it all.
>
> But: If you used your BBS' alias it could be that the neighbouring node
> hasn't yet learned that the alias should point to a new callsign and when
> you said "c lcbbs" it mapped the alias to a callsign k5di-1. If this was
> the case, a "n lcbbs" would reveal it as it would return with something
> like "routes to lcbbs:k5di-1 ..." This could be possible if lcbbs formerly
> indeed was k5di-1. In that case you should be able to connect with the
> callsign ie. "c k5di-3".
>
> The second, more probable cause is that you have mixed the protocol layers
> and everything is just fine except your FBB configuration. When you
> initiate the connect from the remote node you should see a connect frame
> resembling this:
>
> Port xxx: AX25: XXXXXX-X->K5DI-1 <I C S2 R3> pid=NET/ROM
> NET/ROM: XXXXXX-X->K5DI-3 ttl 12
> conn rqst: my ckt 01/A2 wnd 4 K5DI@XXXXXX-X
>
> Now if you don't have your FBB set up correctly you will see a reply
> looking something like this:
>
> Port 3: AX25: K5DI-1->XXXXXX-X <I C S1 R4> pid=NET/ROM
> NET/ROM: K5DI-3->XXXXXX-X ttl 15
> conn ack: ur ckt 01/A2 my ckt 00/00 wnd 4 CHOKE
>
> Note how in these examples the link layer (AX.25) callsign used is k5di-1
> just as it should be and the NET/ROM network layer callsign is k5di-3.
> See? If this really is not the problem then I stand corrected. But before
> you provide us with good bug report with real listen traces etc. I'm going
> to continue with my belief that you don't really have the slightest clue
> how these things work.
>
> --
> --... Tomi Manninen / gjlegsyd@varig.com.br / OH2BNS @ OH2RBI.FIN.EU ...--
>
>
Best wishes
- Karl F. Larsen, 3310 East Street, Las Cruces,NM (505) 524-3303 -