Arno Verhoeven wrote:
>
> Ronnie Hale wrote:
> >
> > 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.
> >
>
> I had read before that using the same ssid on different ports is not
> recomended, but I our case I don't know of another way to do it.
> I tried using PI8ZAA-1 on the netrom port but this means that the
> station announces itself as EHVBBS:PI8ZAA-1. And this is not what we
> need. We want the rest of the world to know that the BBS can be reached
> as PI8ZAA (without a suffix).
> Also If I use a different ssid on the netrom port than the BBS cannot be
> connected anymore. (The BBS can only be connected via netrom).
>
> Am I overlooking something?
> It must be possible to get this thing working...
>
> 73, Arno pe1icq
I forgot to mention that we found out that the disconnects happen at the
same moment that outgoing forwarding starts. (reproducable)
73, Arno pe1icq
