On Wed, 5 May 1999, Arno Verhoeven wrote:
> Hi,
>
>
--snip--
> The symptoms are as follows. While retrieving data from the BBS (via
> digipeater) and the link quality is good, the user suddenly receives a
> D frame.
> See trace below.
>
--
Arno,
You have more than one instance of the same callsign-ssid. At least, the
netrom port and FBB BBS both are configured to use same callsign-ssid. Your
FBB is responding to PI8ZAA-0 and begins login procedure. NRport PI8ZAA-0
notices packets addressed to its callsign (also PI8ZAA-0), wakes up, and
knowing that it is not connected, sends out a DM Frame. There is perhaps
another callsign of the same SSID in your ax25 config setup in your
/etc/rc.d/rc.ham file, but not sure that is used anywhere else.
This problem can also exist where the inverted ssid and another callsign
matching the inverted ssid are both visible on the same port.
You must use a different ssid for either the bbs or the nrport.
> As you can see also other users get disconnected at the same time.
>
> If I then reconnect to the BBS, and give the ! command, I see my call
> sign in the list twice.
> Apparently FBB thinks that I'm still connected.
>
Yes, it is not FBB that is disconnecting the link.
> Is it a coniguration error?
> If so, do you see anything wrong in the files below?
Yes.
> #/etc/ax25/nrports
> #
> #name call alias paclen description
> nr_ZAA PI8ZAA-0 EHVBBS 235 PI8ZAA NetRom Switch Port
>
^^^^^^ PI8ZAA-0 also listed as BBS callsign-ssid
--
> #!/bin/sh
> #
> # /etc/rc.d/rc.ham: Local system initialization script.
> #
> # Put any ham-radio related setup commands in here:
> # Edit for your setup.
> CALLSIGN="PI8ZAA"
> IPADDR=${IPADDR:-"44.137.24.1"} # pi8zaa
This may or may not be a problem, as I don't see an example of the Callsign
String used in this configuration (which was snipped to save space)
--
> # FBB7.00
> #
> # Set-up file
> #
> #
> # Callsign of BBS
> PI8ZAA.#NBO.NLD.EU
> #
> # SSID of BBS
> 0
--
73, Ronnie.
[EMAIL PROTECTED]
