If you've changed the callsign/SSID associated with your nodes, it'll
take some time for the new information to propagate through the local
network. Until then, netrom connects will probably fail.
In our environment, it took a good 12 hours plus for things to settle
down (since we have several nodes all able to hear each other through a
repeater, there's a "ping-pong" effect that makes it take a while for
node changes to propagate).
73,
John
> Hello guys,
> I spent all day today trying to set up my ax25 systen like paper I
> got from the web site that just got their Gateway working. It looked real
> good to me and I modified my ac25d.conf and nrports and startup bash file
> as the W8APR group suggested.
>
> When I rebooted it was wonderful. I have the old netrom called
> #cruce and the new alias's lcbbs:k5di-3 and lcdx:k5di-5 and cruces:k5di-4
> nodes everywhere. #cruce:k5di-1 is the actual netrom that you never want
> to call. LCBBS:k5di-3 is a XFBB packet bbs, lcdx:k5di-5 is a DX-Cluster
> and cruces:k5di-4 is the node.
>
> But when I connected to my distant node and called lcbbs it
> returned "lcbbs:k5di-3 Busy". When I did a node lcbbs it said the route to
> lcbbs:k5di-3 was to k5di-1!!!!
>
> I did the usual ifconfig nr0 through 3 and they were perfect. Now
> I see there is still something wrong with the old setup I just put back.
> So need to see what that is.
>
> With out question ax25-util setup is the pits. It is so easy to
> make a single tiny error and the whole thing goes bonkers!
>
> Best wishes
>
> - Karl F. Larsen, 3310 East Street, Las Cruces,NM (505) 524-3303 -