#!/bin/sh
#
# start file for the k5di ax25 system
#
echo " Erase the ifconfig nr0 entry.."
ifconfig nr0 down
#
echo "Attaching ax.25 interfaces..."
#
/usr/sbin/kissattach -i 44.30.2.5 -m 512 /dev/ttyS2 ax0
/usr/bin/sleep 1
/usr/sbin/kissattach -i 44.30.2.5 -m 512 /dev/ttyS3 ax1
#
echo "Start All Services..."
/usr/bin/sleep 1
/usr/sbin/nrattach -i 44.30.2.5 netrom
/usr/sbin/nrattach -i 44.30.2.5 netbbs
/usr/sbin/nrattach -i 44.30.2.5 netnod
/usr/sbin/nrattach -i 44.30.2.5 netdx
#/usr/sbin/nrattach -i 44.30.2.5 netunix
/usr/bin/sleep 1
/usr/sbin/ax25d > /dev/null 2> /dev/null &
/usr/sbin/netromd -i &
/usr/bin/sleep 1
echo " Form the IP route table "
#
ifconfig ax0 broadcast 44.30.2.255
/usr/bin/sleep 1
ifconfig ax1 broadcast 44.30.2.255
/usr/bin/sleep 1
ifconfig nr0 broadcast 44.30.2.255
#
route add -host 127.0.0.1 lo
route add -net 44.30.2.131 netmask 255.255.255.255 nr0
route add -net 44.77.0.100 netmask 255.255.255.255 ax0
route add -net 44.30.2.3 netmask 255.255.255.255 ax1
route add -net 44.30.2.34 netmask 255.255.255.255 ax0
route add -net 44.30.2.56 netmask 255.255.255.255 gw 44.30.2.3 ax1
route add -net 44.124.0.0 netmask 255.255.0.0 gw 44.30.2.131
route add -net 44.30.2.128 netmask 255.255.255.128 gw 44.30.2.131
route add -net 44.77.0.0 netmask 255.255.0.0 gw elp
route add -net 44.0.0.0 netmask 255.0.0.0 gw 44.30.2.34
#
echo " Form the ARP IP table "
arp -H netrom -s 44.30.2.131 wy5g-1
arp -H ax25 -s 44.77.0.100 k5elp-2
arp -H ax25 -s 44.30.2.34 w5gb-7
arp -H ax25 -s 44.30.2.3 k5di-2
#
echo " Set up the AX.25 paramters"
/usr/bin/sleep 1
echo 4 > /proc/sys/net/ax25/ax0/standard_window_size
echo 234 > /proc/sys/net/ax25/ax0/maximum_packet_length
echo 234 > /proc/sys/net/ax25/ax1/maximum_packet_length
echo 4 > /proc/sys/net/ax25/ax1/standard_window_size
echo 224 > /proc/sys/net/netrom/default_path_quality
#
echo "Load the old Node Table"
# /root/nodes.save
mheardd -f -n25 &
#
On Mon, 2 Nov 1998, Jason J Bachman wrote:
> Karl, Thanks for the reply, I followed the ax25-howto letter for letter,
> patched recompiled my 2.0.33 kernel, recompiled ax25-utils-2.1.42a-glibc,
> and got the same kmalloc errors.
> I tried it with a 2.0.35 kernel and it ran for a little while, then I was
> doing a ping test, the pinged station did an ARP request, my machine sent
> ARP response, then it stopped transmitting data to the tty port. The pings
> were going according to LISTEN, but nothing was getting to the tnc. I
> rebooted the machine, and now I get the kmalloc errors again.
> Could there posibally be a problem or interaction with the kernel's
> digiboard driver?
>
> Thanks for any help.
> Jason - N8WXZ
> xxf@mailit.tunk.net
>
> -----Original Message-----
> From: Karl F. Larsen [SMTP:gnc@jlab.org]
> Sent: Saturday, October 31, 1998 7:14 AM
> To: Jason J Bachman
> Cc: Linux-Hams Mailing List (E-mail)
> Subject: Re: kmalloc error when receiving a packet.
>
>
> Hi Jason, reboot the computer and as root type ifconfig <enter> and see if
> ax0 is loaded. If not then there is something wrong with the startup file
> or the ax25-util compiled binary files are not being called properly.
>
> Please read the ax25-HOWTO again and run with care the tests that Terry
> has in it.
>
>
>
> On Fri, 30 Oct 1998, Jason J Bachman wrote:
>
> > Hello all. I recently re-installed my RedHat 5.0 machine, and I am
> having
> > a problem with ax25 configuration.
> > The Redhat distrubution comes with a 2.0.31 kernel, but I patched a
> 2.0.33
> > kernel with ax25-module-14f , compiled, and ran, everything seemed ok
> until
> > I connected the radio and received the first data packet. CRASH! I got
> > the following error:
> > kmalloc called nonatomically from interrupt 0000000c
> > kmalloc called nonatomically from interrupt 00000030
> >
> > After these errors, I can no longer find the ax0 port. If I kill and
> > re-load kissattach, I still cannot get the ax0 port back.
> >
> > I have also tried compiling and running on a 2.0.35 kernel with the exact
> > same results.
> >
> > Hardware I am using is, intel 486DX2/66, serial card is a Digiboard
> > PC/Xeve, TNC is Kantronics KPC3 with 8.5 firmware.
> >
> > I verified that the serial port is working by connecting a modem, running
> > minicom, and calling another machine.
> >
> > I had this working before and it worked fine, now I'm stumped.
> >
> > Any help is greatly appreciated.
> >
> > Thanks! Jason
> >
> >
> >
>
> Best wishes
>
> - Karl F. Larsen, 3310 East Street, Las Cruces,NM (505) 524-3303 -
>
>
Best wishes
- Karl F. Larsen, 3310 East Street, Las Cruces,NM (505) 524-3303 -