SV: [Dxspider-support] SSID -6 problems (again?)

[Rene Olsen]

Hi.

> Thanks for answers so far. To Rene, well we are not using Linux, we use
> WIN98 so can't fix it in ax25d.conf.

Sri. I found that out after sending the mail, and reading your message again. Should 
have read it carefully the first time :-)

> I have to study the AX25 protocoll more to understand how AX25 handels SSID.
> But what I know is that this problem started when we changed our
> clustersoftware  from AK1A to Spider so it's not the links between the clusters
> that converts SSID, it must be in the Spider software. Of course we can solve
> it by configuring both -6 and -9 as nodes but as -6 is common for DXC nodes in
> Sweden so it is confusing for users that SM6XX-6 is suddenly called SM6XX-9 in
> the next cluster node list.... Else I think Spider is really super, we have had
> our node up for 3 months without any reboot running under WIN98 !

Are you sure that you did not have the nodes in question defined as -6 and -9 in the 
nodes.dat in AK1A ?. I know many sysops that run AK1A who has the nodes defined 
like "OZ5BBS-7 OZ5BBS-7, OZ5BBS-8" because the node can come in as both -7 and 
-8 when it is on a L2 link.

Sri if the format is not correct. It has been a looong time since I have done anything 
with AK1A. Actually have never used it myself, but just helped a few sysops once in a 
while.

If you connect to a node that only runs L2, and you connect with SM6XX-2 and then ask 
the node to connect to SM7YY, then you will see a SABM frame with SM6XX-13 to 
SM7YY. That is just how L2 works. So two L2 hops will get you back to your original 
SSID.

I am still convinced that it has nothing to do with spider, and that it is a pure ax25 thing.

Since I have never used the AGW engine I have no idea how Dirk shoul fix this. He 
could of course do like the old AK1A and have a file that defines what will be accepred 
as SM6XX-6.

Vy 73 de Rene / OZ1LQH