RE: aprsd config problem?
OK. Enough head banging! Move to aprsd 2.2.5-13. 2.1.4 is hopelessly broken
on kernel 2.4.22 | .24. After looking at the source trees\code for aprsd
2.1.4 & 2.2.5-15, there's no way anyone is gonna bother to touch 2.1.4 code.
The problem may have centered around\within TCPSessionThread().
Here's update method I used (assuming you have inet access to debian
packages (testing).
1) Shutdown aprsd.
2) dpkg -P aprsd
(purges aprsd install. Some aprsd.conf stuff has changed, so I recommend a
purge)
3) Create\edit /etc/apt/apt.conf and add the lines:
APT::Default-Release "testing";
APT::Cache-Limit "25000000";
4) Edit /etc/apt/sources.list and add the lines:
deb ftp://ftp.us.debian.org/debian/ testing main non-free contrib
deb-src ftp://ftp.us.debian.org/debian/ testing main non-free contrib
5) do a "apt-get update"
6) try a dry run with "apt-get -s install aprsd"
confirm that the aprsd version will be 2.2.5-13
NOTE: installing this will update a number of packages including gcc...
(which is OK for me cause I need 3.3 to build 2.6.x kernels)
7) if feeling brave and lucky...
"apt-get install aprsd"
with luck, aprsd will be running once completed.
8) if you normally install "stable" packages, may want to edit
/etc/apt/apt.conf:
APT::Default-Release "stable";
9) Reconfig /etc/aprsd/INIT.TNC, RESTORE.TNC, welcome.txt, aprsd.conf
...you should be good to go!
Been running 30 mins+, aprsd dumps history and streams rf feed from 10151
continuously and no orphaned procs yet!
Good luck,
Rick
> -----Original Message-----
> From: Nate Duehr [mailto:nate@natetech.com]
> Sent: Thursday, March 11, 2004 6:31 PM
> To: Rick Bolen
> Cc: Debian Hams; John Maxwell
> Subject: Re: aprsd config problem?
>
>
> Rick ,
>
> I think we're seeing similar problems with a woody-based install here
> and a KPC-3 in KISS mode.
>
> I'll have to forward this on to the guy who's actually working on the
> machine directly, but reading your posting was kinda eerie in that it
> matched symptoms almost perfectly.
>
> One question -- why the kernel rebuild? As best I could tell, the
> stock Woody kernel has ax25 stuff working in it? (Perhaps not? Maybe
> that's our problem... heh.)
>
> We also see data fine with "listen" and can do connections and
> what-not, but aprsd seems totally and hopelessly confused.
>
> One thought for package maintainers/authors... since Debian's known for
> "just works out of the box"... some effort to standardize the port
> names and other examples in the conf files would be nice (not
> necessary, just "nice") so that after a standard "apt-get install
> <foo>" things will generally "work" for KISS-mode TNC's. Not a big
> deal.
>
> Also, I found very little documentation on what would go in
> /etc/network/interfaces for AX.25 support. So far we're still in "test
> mode" so we're just manually starting mkiss and other stuff up.
>
> Here's the really "weird" part (I say weird in quotes because I'm sure
> there's a logical explanation for it...) -- he loaded the same machine
> with MEPIS and it worked FB. Hmmm... now the game of hunting down
> what's different between Debian Woody and MEPIS (probably version
> numbers and maybe newer ax25-lib?) to figure out why one works and the
> other doesn't.
>
> Nate WY0X
>
> On Mar 10, 2004, at 4:36 PM, Rick Bolen wrote:
>
> > Hello all,
> >
> > I wrote regarding this awhile back, but my install was too cobbled to
> > tshoot. I've since re-installed Woody, compiled a custom kernel with
> > AX.25
> > protocol support, reinstalled the libax25, ax25-tools, ax25-apps and
> > reinstalled aprsd.
> >
> > I still suffer the same problem I had with the previous install, i.e.,
> > aprsd
> > won't stream output to it's ports (as config'd in aprsd.conf).
> >
> > -If I telnet (from localhost or remote) to the non-history and raw
> > ports, I
> > get only my server's beacon returned once only.
> >
> > -If I telnet (from localhost or remote) to ports w/history, I get the
> > history dump as of the time of socket connect, but no further data
> > streams
> > out.
> >
> > -My aprs client sw, UI-View32, is config'd to mainport (10151). When it
> > connects, it gets the history dump, but no further data until its'
> > timout,
> > and then it reconnects (same behavior whether the client officially
> > "logs
> > in" or not). This reconnect results in another "aprsd -d" process being
> > spawned (as indicated by ps -aux). The STAT of all "aprsd -d" processes
> > remain "S" (Sleeping). The number of aprsd processes will increase
> > into the
> > hundreds as re\connections occur).
> >
> > -All the while, "listen" displays a constant incoming stream of aprs
> > data
> > from the port.
> >
> > Hardware config:
> > Via Eden 5000
> > 10\100 NIC
> > TNC X(kiss only)->/dev/ttyS0
> >
> > Relevent config data is as follows:
> >
> > axports:
> > aprs2m KG4OFO-13 9600 255 2 144.390 MHz (APRS
> > 1200bps on
> > air)
> >
> > ax25.init (per www.febo.com):
> > /usr/sbin/kissattach /dev/ttyS0 aprs2m 44.71.36.65
> > /usr/sbin/kissparms -p aprs2m -f no -l 50 -r 32 -s 320 -t 320
> > /sbin/ifconfig ax0 broadcast 44.71.36.127 netmask 255.255.255.192
> > /sbin/ifconfig ax0 arp mtu 256 up
> > /sbin/route add -net 44.71.36.64 irtt 4000 ax0
> >
> > /etc/ax25# ifconfig
> > ax0 Link encap:AMPR AX.25 HWaddr KG4OFO-13
> > inet addr:44.71.36.65 Bcast:44.71.36.127
> > Mask:255.255.255.192
> > UP BROADCAST RUNNING MTU:256 Metric:1
> > RX packets:558 errors:0 dropped:0 overruns:0 frame:0
> > TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
> > collisions:0 txqueuelen:10
> > RX bytes:41439 (40.4 KiB) TX bytes:254 (254.0 b)
> >
> > eth0 Link encap:Ethernet HWaddr 00:40:63:CC:0A:CE
> > inet addr:192.168.1.5 Bcast:255.255.255.255
> > Mask:255.255.255.0
> > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> > RX packets:1141 errors:0 dropped:0 overruns:0 frame:0
> > TX packets:1196 errors:0 dropped:0 overruns:0 carrier:0
> > collisions:0 txqueuelen:1000
> > RX bytes:115839 (113.1 KiB) TX bytes:136042 (132.8 KiB)
> > Interrupt:11 Base address:0xe800
> >
> > lo Link encap:Local Loopback
> > inet addr:127.0.0.1 Mask:255.0.0.0
> > UP LOOPBACK RUNNING MTU:16436 Metric:1
> > RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> > TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
> > collisions:0 txqueuelen:0
> > RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
> >
> > /etc/ax25# route
> > Kernel IP routing table
> > Destination Gateway Genmask Flags Metric Ref Use
> > Iface
> > 44.71.36.64 * 255.255.255.192 U 0 0
> > 0 ax0
> > 192.168.1.0 * 255.255.255.0 U 0 0
> > 0 eth0
> > default 192.168.1.1 0.0.0.0 UG 0 0
> > 0 eth0
> >
> >
> > Anyone understand what the problem and solution is to this? It's
> > driving me
> > crazy.
> >
> > Thanks,
> > Rick - kg4ofo
> >
> >
> >
> > --
> > To UNSUBSCRIBE, email to debian-hams-request@lists.debian.org
> > with a subject of "unsubscribe". Trouble? Contact
> > listmaster@lists.debian.org
> >
>
>
Reply to: