I'd suggest that you patch with ax25-module-14f and recompile (or get
2.0.35, which doesn't need the patch). Also you should get
ax25-utils-2.1.42. If your system is glibc2, then check the archives of
this list regarding some header changes to get the utils to compile.
On Fri, 4 Sep 1998, K. David Prince wrote:
> First, thanks to all the hams that helped us get this AEA PK-12
> straightened out. Our solution was to pull the jumper that keeps the
> internal battery online. That forced the TNC to reset to the factory
> settings; the command prompt returned; and, we were able to put the TNC
> into KISS mode.
>
> But, nothing is perfect! Our next problem was to log into some bulletin
> boards. First, here is the setup we're using:
>
> Distribution: S.u.S.E. 5.2
> AX25 Utilities: ax25-utils-2.0.12
>
> Since this area (Seattle, WA) doesn't have that many sites using ROSE, we
> didn't patch and recompile the kernel (linux-2.0.33.SuSE) for ROSE support.
> The version of ax25-utils we installed came from the S.u.S.E. 5.2 CD-ROM
> distribution. Interestingly, the method for creating the ax25 port is to
> use the "axattach" command as opposed to the "kissattach" command
> documented in the current AX25-HOWTO.
axattach = old way
kissattach = new way
>
> Now, here's the wheeze: We could start the "listen" utility and see all
> sorts of ax25 activity. Then we used "call" while in KISS mode via the
> ax25 port we created. When we received a reply, we were immediately
> logged off, and "call" died. The "listen" utility showed the interaction,
> so there was a brief exchange of information. It seems that we can
> "call", keying the transmitter just fine (we monitored this using a
> handheld).
>
> Next, we took the PK-12 out of KISS mode and used "minicom" as a dumb
> terminal to access the TNC commands. No problem, we logged in and out
> successfully several times. This seems to eliminate any question of
> making a packet radio connection with this setup.
>
> So, our question is: Are there any gottchas concerning the use of the
> "call" program? Are there any parameters that we have to watch out for?
> Does "call" have to be configured somehow so that it opens its window and
> allows us to communicate both ways via the ax25 port?
>
> Again, I want to thanks all the hams out there helping us with this
> problem! The "we" in this message is myself (WB0RAZ) and Steve (N0FPF).
> Our project is to setup a Linux server on TCP-IP packet radio for the City
> of Seattle Emergency Management, Auxiliary Communications Service.
>
> Your help is greatly appreciated!
>
> Dave
>
----
Bob Nielsen Internet: pqxwtdo.mthi@sk-trier.de
Tucson, AZ AMPRnet: rew.ygluyrb@mx.dy.fi
DM42nh http://www.primenet.com/~nielsen