Re: Multiple msgs, large msgs - Some Progress
Thanks Dana, I'll start using the SourceForge site for entering bugs. listen is a monitor for ax.25 traffic. There is also a listen program for monitoring connections on a socket. Go here to see a
By
Basil Gunn
·
#81
·
|
Re: Multiple msgs, large msgs - Some Progress
I don't really remember. It may have been that I was just following the lead of the code in the Windows paclink, or it may have just been a pointless snippet of code that should have been
By
Nicholas S. Castellano
·
#82
·
|
Re: Multiple msgs, large msgs - Some Progress
Thanks for committing the patch. Paclink-unix now has sufficient functionality for me to be used instead of Airmail3.exe. So whaa whoo! I'm using a serial port sniffer (slsnif) to look at traces from
By
Basil Gunn
·
#83
·
|
Re: Multiple msgs, large msgs - Some Progress
I take it that there is a kernel limit of 256 set somewhere else? OK
By
John Ronan - EI7IG
·
#84
·
|
Re: Multiple msgs, large msgs - Some Progress
The original send/receive buffer sizes for socket comm in wl2kax25.c were 256 bytes for each. I think the size requirement may be tied to the paclen size in /etc/ax25/axports. For buffering purposes I
By
Basil Gunn
·
#85
·
|
New project developer
Basil Gunn ke7kro has accepted my invitation to join the paclink-unix development team. Welcome aboard, Basil! -- 73 de Nick N2QZ FISTS #11469 - SKCC #1027
By
Nicholas S. Castellano
·
#86
·
|
Re: New project developer
Thanks Nick & Dana! /basil ke7kro
By
Basil Gunn
·
#87
·
|
Clean build problem when using CVS checked out code
I'm seeing some build problems with autoconf & automake when trying to do a build using code checked out with CVS. If you are able to do a successful build from a fresh CVS check-out could you please
By
Basil Gunn
·
#88
·
|
Re: Clean build problem when using CVS checked out code
Basil, I just updated my code from the repository and ran autogen.sh The first line in that script is a "make distclean" command. No issues here with configure after that. Hust to be suer, I ran
By
Dana
·
#89
·
|
Re: Clean build problem when using CVS checked out code
Dana, Thanks for the quick response! My error was I didn't run autogen.sh. I read the INSTALL file for the build procedure from a CVS check-out and didn't pick that up. From the autogen.sh script
By
Basil Gunn
·
#90
·
|
wl2ktelnet.
Hi, Just looking at this again. Could someone remind me of the command line options for wl2ktelnet. It's refusing to log in for me and I don't think I've changed anything. John
By
John Ronan - EI7IG
·
#91
·
|
Re: wl2ktelnet.
Hi John, mycall yourcall hostname port timeoutsecs password emailaddress So, for instance: wl2ktelnet ka1wpm wl2k server.winlink.org 8772 30 CMSTelnet me@myaddress This information is provided on the
By
Dana
·
#92
·
|
Re: wl2ktelnet.
Thanks Dana, I'm not loosing it (yet!) I just updated to latest CVS (to be sure) and I'm getting timeouts. root@ns1:~/src/paclink-unix# wl2ktelnet ei7ig wl2k server.winlink.org 8772 20 CMSTELNET
By
John Ronan - EI7IG
·
#93
·
|
Re: wl2ktelnet.
John, I'm getting a pretty quick response when I do it, but you might want to bump up the timeout. In the example from the Winlink FAQ, they are setting the timeout to 120 seconds. Do you get a
By
Dana
·
#94
·
|
Re: wl2ktelnet.
Too many messages it looks like (or maybe to large). John
By
John Ronan - EI7IG
·
#95
·
|
Re: wl2ktelnet.
I think I found the culprit.. a 500K message ... oops! John
By
John Ronan - EI7IG
·
#96
·
|
Patch for wl2kax25.c
Hi Attached is the patch I alluded to before. There is no longer a timeout in wl2kax25. This restores it. de John EI7IG .
By
John Ronan - EI7IG
·
#97
·
|
Re: Patch for wl2kax25.c [1 Attachment]
Patch applied and checked in. Thanks, John! -- Dana, KA1WPM
By
Dana
·
#98
·
|
QForms & paclink-unix
QForms is a Windows application written by Lee, K0QED, to format various messages including ARRL Radiograms and ICS-213 forms. After installing postfix as an MTA, I was able to generate and send
By
Dana
·
#99
·
|
Latency when retrieving msgs sent by paclink-unix
I've been checking out an anomaly where it looks like messages sent with paclink-unix using postfix are not immediately retrievable by the intended recipient. There are 2 scenarios where I've observed
By
Basil Gunn
·
#100
·
|