It doesn't make any meaningful difference if the port is going to be
used just for AX.25 work, since the AX.25 code or TNOS is going to be the
only interface with the port.
>Also, I have linux kernel 2.0.29 and ax25-utils2.0.12c. Both compiled
>with no problems on a 80386 and networked on to a larger home linux
>system.
>
>Is it better to use the ax25 system or use
>TNOS-2.22, which I also have ??
>
The kernel ax25 makes more sense for TCP/IP functionality. Since the port
will look like any other network device, anything that uses TCP/IP will be
able to use it. On the other hand, TNOS limits you a great deal, in that respec
t. The only major reason to use TNOS is if you have users who are too set in th
eir ways to use anything other than an early 1980's BBS interface. :-)
>I'm a real honest-to-god newbie with packet and do not even have a clue
>as to what I'm doing, although I'm fairly comfortable with linux. I've
>read all the applicable HOWTO's a couple of times but I'm still lost in
>the ozone.
>
Forget about trying to deal with any of the software right now. The first
thing you need to do it to establish communications with the TNC. Disable
*ALL* ax25 daemons, TNOS, etc. Start up minicom on your TNC's serial port,
with communications parameters as specified in your TNC manual. Hit
RETURN a few times. If you don't see anything at all, try doing a hardware
reset of the TNC, and start over. Make sure that your TNC isn't already in
KISS mode.
Of course, this assumes that you've already done basic diagnostics; i.e.
making sure that you have serial-device support built into the kernel in the
first place, ensuring that you have a good serial cable, etc.
If you still have problems, let us know with a *detailed* description of what
you've tried, and what, if anything, you're seeing in minicom.
- Rich
-- Rich Mulvey ehpfrj.rgvhioqqly@gov.eg Rochester, NY USA http://www.frontiernet.net/~mulveyr Amateur Radio: yzgzovrd.hnjz@passion-pictures.com, aa2ys@wb2wxq.#wny.ny.usa