Hi Chuck,
It is all fairly easy to get going. Conpile your kernel with AX25 support as
per the howto. I then created a simple shell script to setup the interfaces
etc. Put your TNC in kiss mode and connect it to the port. Then use kissattach
to create the ax0 device.
The only thing to remember is you must assign an IP to the port after you use
kissattach. This can be done with the ifconfig command. If you would like me
to send you a copy of my script file let me know and I will sent it to you ...
it is very basic though.
I would recommend using the HOWTO to get started. Just remember to use the
packages below to get going...
SNIP " for 2.2 kernels, you should download ax25-apps, ax25-tools libax25 from
ftp://ftp.hes.iki.fi/pub/ham/linux/ax25/ and install them as instructed.
The ax25-howto is a bit outdated on the ax25 installation when you are
using 2.2 kernels. "
Anyway, hope this helps
Richard
VK2HDJ
________________________________________________________________________________________
>From "Hast, Chuck" <[EMAIL PROTECTED]> on 5 January 2000
To : "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]>
Copy To : (bcc: Richard Talbot)
Subject : RE: AX25 and Redhat 6.1
Richard:
I am new to this part of linux, I have run TNOS for quite some time
but have never putzed around with the AX.25 stuff in LINUX.
I have RH 6.1 and am getting ready to install it, I pulled down the
AX25 how to and tried to follow it for RH 6.0 (which I also have) and
appeared to have made a misserable mess out of it. I was able to
compile a kernel and I also did the modules thing but that is as
far as I got, I would like to find a good set of steps for doing this
under the 6.0 or 6.1 rev.
I can see that you are having problems but are much farther down
the road than I am. I really just want to set up a linux box to handle
IP (UDP) in AX.25 frames. But I also in the end want to keep track
of mobiles off of several towers and figure out which tower a mobile
is on and route the packets to that tower. Right now I just want to
get to where you are with your second problem (assigning IP addr
to a port and sending ax25 frames) then I can press on.
I am assuming that there is a load of differences between the HOW
TO and the way you do it with the newer RH versions...
Tnx in advanced
Chuck
Kp4djt.
> -----Original Message-----
> From: [EMAIL PROTECTED] [SMTP:[EMAIL PROTECTED]]
> Sent: Tuesday, January 04, 2000 17:52
> To: linux-hams
> Subject: AX25 and Redhat 6.1
>
>
>
> Greetings everyone,
>
> Over the last couple of weeks I have been trying to get AX25 going on
> Redhat
> 6.1. I am unable to comple ax25-utils-2.1.42a.tar.gz on the base system.
> I get
> all sorts of compile errors. In the end I gave up after manually editing
> most
> of the files and including the errno.h file where needed. It also appears
> that
> the sockets.h file included by default was not the correct one to use. I
> got
> most of it to compile but just gave up eventually.
>
> I have also tried installing from the RPM's. (ax25-utils-2-1-42a-3 and
> ax25-utils-2-1-42a-9) This resulted in a different problem. No matter
> what I
> did the call program would give me an error to say that none of my ports
> were
> active. Well the TNC was in Kiss mode and receiving packets. When I did
> an
> ifconfig | more I was able to see ax0 was receiving frames and it was
> reported
> by the kernel as up. In my book this is active.
>
> In the end I tried to give the port an IP address with the ifconfig
> command. I
> could not believe it when everything flashed, the TNC went into TX etc. I
> am
> now able to call my local BBS and everything is great....
>
> However, one problem remains. I have an IP address assigned to each of my
> ax
> ports. This is a problem as I run Samba and a whole host of other
> packages on
> my Linux box and I do not wish to see them appear on RF. I cannot delete
> them
> from the routing table as they are interfaces, not routes and I do not
> really
> want to firewall the machine. If I mark the interface as down, I will not
> be
> able to use AX25 either.... My security policy was to be so simple - No IP
> transport...
>
> The ideal solution is to somehow remove IP from the interface and leave
> ax25 up.
> Has anyone worked out how to solve this problem? I notice there are a few
> other
> people who have got AX25 running with an IP address.
>
> Thanks
> Richard
> VK2HDJ
>
