You can subscribe to this list here.
2001 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(7) |
Jul
(33) |
Aug
(21) |
Sep
(8) |
Oct
(21) |
Nov
(33) |
Dec
(21) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2002 |
Jan
(3) |
Feb
(31) |
Mar
(11) |
Apr
(56) |
May
(7) |
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
(15) |
Dec
|
2003 |
Jan
(1) |
Feb
|
Mar
|
Apr
(5) |
May
(34) |
Jun
(20) |
Jul
(5) |
Aug
(6) |
Sep
(9) |
Oct
|
Nov
|
Dec
|
2004 |
Jan
(9) |
Feb
(2) |
Mar
(2) |
Apr
(1) |
May
(1) |
Jun
(4) |
Jul
|
Aug
(2) |
Sep
(1) |
Oct
|
Nov
|
Dec
|
2005 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(11) |
Jun
|
Jul
(7) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2006 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
(8) |
Jun
(6) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2007 |
Jan
|
Feb
(1) |
Mar
|
Apr
(1) |
May
(7) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2008 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(2) |
Nov
(13) |
Dec
|
2009 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(3) |
Dec
|
2010 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
From: Hamish M. <ha...@cl...> - 2001-09-19 22:26:56
|
On Wed, Sep 19, 2001 at 12:49:17PM -0400, Mike James Wolthuis wrote: > 2.1.4 version so I am confused why I don't see some of this on 14580 even > though it is digied by a local digi according to my D7a. So the packets even > make it back to the IGATE, but our never relayed back onto any of the ports. > I understand it should not go back to the Internet or you get a loop, but it > should go to clients on port 14579,14580 for sure I would think? > > Any help would be GREAT! Maybe I am just missing a setting or am missing a > brain dead solution, besides putting up a local receiver. Seems that the raw TNC port (14580) is just giving you data received on air, not also data that was transmitted. I'm not sure that that's the wrong behavior. Dennis said it's the same in 2.1.4; are you sure that it works for you on that version? Hamish -- Hamish Moffatt VK3SB <ha...@de...> <ha...@cl...> |
From: Hamish M. <ha...@cl...> - 2001-09-19 22:26:01
|
On Wed, Sep 19, 2001 at 01:42:45PM -0400, Dennis Hudson, N2LBT wrote: > I guess the answer is to use ax.25 tools on a kiss TNC and connect the IGate > and a compatible client to share a TNC. I would also like to adjust my path > within the client instead of the default of the aprsd IGate from gate2rf. Well, that's possible with a kiss TNC, but aprsd doesn't allow it yet. I'll consider it for the future. Hamish -- Hamish Moffatt VK3SB <ha...@de...> <ha...@cl...> |
From: Dennis H. N. <n2...@n2...> - 2001-09-19 17:42:53
|
On 9/19/01 12:49 PM, "Mike James Wolthuis" <wol...@pi...> wrote: > Everyone, > Quick questions, possible problem? New user confusion?? > > I have CVS APRSd running, latest build. > > I connect to it via APRS+SA on port 14580 for all my own APRS needs. > Since I have only the IGATE with live RF access. > > Here is what I am confused by. > > When we have NWS Weather Alerts come through or calls that are in gate2rf they > make it to RF with the default UNPROTO path. I can see all this with my > TH-D7a > and copy it perfectly, so I am glad to see all the gating to RF works GREAT in > latest build I have installed. > > Problem is that my client on 14580 never sees the information. It never gets > the NWS alerts or the packets from stations in gate2rf. This worked in the > old > 2.1.4 version so I am confused why I don't see some of this on 14580 even > though it is digied by a local digi according to my D7a. So the packets even > make it back to the IGATE, but our never relayed back onto any of the ports. > I understand it should not go back to the Internet or you get a loop, but it > should go to clients on port 14579,14580 for sure I would think? I am running release 2.1.4 and I see the same issue. I assumed it was the norm. I tried changing the igateMyCall to "yes" and I didn't see any change. I guess the answer is to use ax.25 tools on a kiss TNC and connect the IGate and a compatible client to share a TNC. I would also like to adjust my path within the client instead of the default of the aprsd IGate from gate2rf. Dennis, N2LBT |
From: Mike J. W. <wol...@pi...> - 2001-09-19 16:49:38
|
Everyone, Quick questions, possible problem? New user confusion?? I have CVS APRSd running, latest build. I connect to it via APRS+SA on port 14580 for all my own APRS needs. Since I have only the IGATE with live RF access. Here is what I am confused by. When we have NWS Weather Alerts come through or calls that are in gate2rf they make it to RF with the default UNPROTO path. I can see all this with my TH-D7a and copy it perfectly, so I am glad to see all the gating to RF works GREAT in latest build I have installed. Problem is that my client on 14580 never sees the information. It never gets the NWS alerts or the packets from stations in gate2rf. This worked in the old 2.1.4 version so I am confused why I don't see some of this on 14580 even though it is digied by a local digi according to my D7a. So the packets even make it back to the IGATE, but our never relayed back onto any of the ports. I understand it should not go back to the Internet or you get a loop, but it should go to clients on port 14579,14580 for sure I would think? Any help would be GREAT! Maybe I am just missing a setting or am missing a brain dead solution, besides putting up a local receiver. Mike Wolthuis kb8zgl President MSU Amateur Radio Club |
From: Bruno Q. <que...@ve...> - 2001-08-26 00:51:44
|
Hi to all, Just as a taught for this parameter. I'm working on providing multiple serial port support to the program. I've actually done the config change the following : tncport device_file device_speed config_file The first parameter is the same from the original config file, then the device file to open (not changed) then the speed associated to the device and the config file associated to the TNC or device on the serial port. In that way, one line can configure the serial port the proper way with all you need and to support as many as you want. This is just to think for the possible futur of multiple serial device support.... Again, this is just as a suggestion and I'm sure they're is many way to do it. (Note : Doing some catching up because of a week's vacation....) KC7ZRU - Tate wrote: > Thanks Hamish! > > Do'n the CVS update thing now... > > 73 > > Hamish Moffatt wrote: > > > > I've just checked into CVS support for setting your TNC port speed > > in aprsd.conf. > > -- > Casper, WY | CARC Repeater > DN62tt | 146.940 > "The Dungeon" online at http://go.to/kc7zru > "RTFM" is NOT a 'four letter' word! > > _______________________________________________ > Aprsd-devel mailing list > Apr...@li... > http://lists.sourceforge.net/lists/listinfo/aprsd-devel -- Bruno Quesnel va...@vi... Genie Electrique que...@ve... Electrical Engineering VA2BMG Ecole de Technologies Superieure http://www.findu.com/cgi-bin/find.cgi?va2bmg |
From: KC7ZRU - T. <kc...@ar...> - 2001-08-25 17:43:14
|
Thanks Hamish! Do'n the CVS update thing now... 73 Hamish Moffatt wrote: > > I've just checked into CVS support for setting your TNC port speed > in aprsd.conf. -- Casper, WY | CARC Repeater DN62tt | 146.940 "The Dungeon" online at http://go.to/kc7zru "RTFM" is NOT a 'four letter' word! |
From: Hamish M. <ha...@cl...> - 2001-08-25 13:57:06
|
I've just checked into CVS support for setting your TNC port speed in aprsd.conf. The new configuration command is "tncbaud", followed by the baud rate. The default (if you don't specify that command at all) is 9600, as per 2.14. Hamish -- Hamish Moffatt VK3SB <ha...@de...> <ha...@cl...> |
From: Hamish M. <ha...@cl...> - 2001-08-25 01:33:34
|
On Fri, Aug 24, 2001 at 04:25:18PM -0400, Michael J. Wolthuis - KB8ZGL wrote: > I have already changed the TNC baud to match the TNC, before it was receving no data when I first installed CVS. Now it matches and I see data from the TNC, data just appears to not make it to the TNC or is not being sent in the right mode. > > Sorry, I can't help diagnose more. serial.cpp has separate speeds for input and output. Did you change both? I can't really debug any further, as it seems to work correctly here. Hamish -- Hamish Moffatt VK3SB <ha...@de...> <ha...@cl...> |
From: Chuck B. <cb...@vi...> - 2001-08-24 20:21:23
|
I have activated the Bug and Feature Request links on the APRSd Source Forge Site. If you feel there is a bug (reproducible or not) submit the problem with a complete description. I hope this will better help prioritize how things get fixed. All developers have rights to assign or modify these reports. ---- Chuck Byam, KG4IJB |
From: Michael J. W. - K. <kb...@mf...> - 2001-08-24 20:17:46
|
I have already changed the TNC baud to match the TNC, before it was = receving no data when I first installed CVS. Now it matches and I see = data from the TNC, data just appears to not make it to the TNC or is not = being sent in the right mode. Sorry, I can't help diagnose more. Mike kb8zgl |
From: Hamish M. <ha...@cl...> - 2001-08-24 14:47:34
|
On Fri, Aug 24, 2001 at 10:39:17AM -0400, Michael J. Wolthuis wrote: > I run my CVS version of APRSd off and on without -d as well. I also see the dump to console saying Sending to TNC when I add VK* or any of my other gate2rfs for that matter. > > However, watching the TNC light for transmit, or watching with a Laptop and another receiver 1mile away I never see it go. > > The TNC does not go into transmit mode at all during this point. > > Any other thoughts? I have my TNC (KPC-3) set into CONV mode via the K command as the last command in APRSd TNC files. Like Tate, check your serial port speed. The default in the CVS version is 1200, NOT 9600 which was the default in 2.14. You might need to edit serial.cpp and change it back. I'll try to find time to add this to the configuration file over the weekend. Hamish -- Hamish Moffatt VK3SB <ha...@de...> <ha...@cl...> |
From: Michael J. W. <kb...@mi...> - 2001-08-24 14:39:11
|
I run my CVS version of APRSd off and on without -d as well. I also see = the dump to console saying Sending to TNC when I add VK* or any of my = other gate2rfs for that matter. However, watching the TNC light for transmit, or watching with a Laptop = and another receiver 1mile away I never see it go. The TNC does not go into transmit mode at all during this point. Any other thoughts? I have my TNC (KPC-3) set into CONV mode via the K = command as the last command in APRSd TNC files. Mike kb8zgl |
From: Hamish M. <ha...@cl...> - 2001-08-23 05:03:56
|
On Wed, Aug 22, 2001 at 04:46:42PM -0600, KC7ZRU - Tate wrote: > Ah HA!! > > Yup - 9600 to 1200 would sure do what I'm seeing. Thanks Hammish! That'll likely fix it for me. OK, glad to hear this should fix it. I don't know why it has changed in the code. All the more reason to make it configurable, with the default being 9600 (as in 2.14). By the way, Hamish has only one 'm'. :-) Cheers, Hamish -- Hamish Moffatt VK3SB <ha...@de...> <ha...@cl...> |
From: KC7ZRU - T. <kc...@ar...> - 2001-08-22 22:47:07
|
Ah HA!! Yup - 9600 to 1200 would sure do what I'm seeing. Thanks Hammish! That'll likely fix it for me. FWIW, I am running it as a program (no -d). And yes, the "Sending to TNC:" lines all look fine. Even further evidence of the 1k2 and 9k6 mixup. Thanks again - I'll have to wait till after work to go 'play', I'll let ya know how it goes. 73! Hamish Moffatt wrote: > > No, nothing has changed there compared to .vk3sb.2. What if you run > aprsd without the -d parameter? It will send status messages to > the screen, including "Sending to TNC: " messages which show what > it is transmitting. Do you see anything funny there? > > With my test setup I don't seem to get an rf.log at all, so you're > one up on me. But my test setup doesn't have any real ports, only > a dummy serial TNC. > > Actually, just looking at the changes to serial.cpp in CVS, I see > that the baud rate on the serial port has changed from 9600 (in > .vk3sb.2) to 1200 (in CVS). You can edit serial.cpp yourself > to change it back for your installation. It should probably > go into the configuration file. > > Hamish -- /\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\ | CARC Repeater 146.940 DN62 | | http://groups.yahoo.com/group/RM-APRS | | "The Dungeon" at http://go.to/KC7ZRU | +++++++++++++++++++++++++++++++++++++++++++++++ |
From: Hamish M. <ha...@cl...> - 2001-08-22 22:39:28
|
On Wed, Aug 22, 2001 at 09:27:22AM -0600, KC7ZRU - Tate wrote: > Upon execution (/home/aprsd2/aprsd) and watching rf.log with tail -f, I get: > ::snipped:: > Tue Aug 21 20:44:39 2001 BEACON was EVERY 0 (disabled) > Tue Aug 21 20:44:39 2001 cmd: > Tue Aug 21 20:45:07 2001 }KD7TA-7>APRS,TCPIP*,KC7ZRU-15*:!4118.75NN10534.78W#PHG2460/R,WY,Wn,Tn digi > Tue Aug 21 20:45:35 2001 ÿÿÿÿÿÕÿÿýÿõÿýÿÿÿýÿÿõÿßõÿ½ÿýÿõÿÿÝÿÕÿÿÿ¿¿«ÿõ > Does the CVS version use a different port speed/setting that's not matched in the TNC? Did running the executable in the 'old' location break something? Is 'normal' serial mode being changed and something is pending? No, nothing has changed there compared to .vk3sb.2. What if you run aprsd without the -d parameter? It will send status messages to the screen, including "Sending to TNC: " messages which show what it is transmitting. Do you see anything funny there? With my test setup I don't seem to get an rf.log at all, so you're one up on me. But my test setup doesn't have any real ports, only a dummy serial TNC. Actually, just looking at the changes to serial.cpp in CVS, I see that the baud rate on the serial port has changed from 9600 (in .vk3sb.2) to 1200 (in CVS). You can edit serial.cpp yourself to change it back for your installation. It should probably go into the configuration file. Hamish -- Hamish Moffatt VK3SB <ha...@de...> <ha...@cl...> |
From: KC7ZRU - T. <kc...@ar...> - 2001-08-22 15:27:45
|
Asked this once before, but I think I've lost the reply. 2.1.4.vk3sb.2 runs very nicley here (Tarball from Hamish's web site). I do the ./configure, make, make install on the CVS version and then copy= the aprsd executable over to /home/aprsd2 from /usr/local/bin (keeps thi= ngs organized for me - may be where my problem is?). Upon execution (/home/aprsd2/aprsd) and watching rf.log with tail -f, I g= et: ::snipped:: Tue Aug 21 20:44:39 2001 BEACON was EVERY 0 (disabled) Tue Aug 21 20:44:39 2001 cmd: Tue Aug 21 20:45:07 2001 }KD7TA-7>APRS,TCPIP*,KC7ZRU-15*:!4118.75NN10534= .78W#PHG2460/R,WY,Wn,Tn digi Tue Aug 21 20:45:35 2001 =FF=FF=FF=FF=FF=D5=FF=FF=FD=FF=F5=FF=FD=FF=FF=FF= =FD=FF=FF=F5=FF=DF=F5=FF=BD=FF=FD=FF=F5=FF=FF=AD=DD=FF=D5=FF=FF=FF=BF=BF=AB= =FF=F5 Tue Aug 21 20:45:36 2001 }=FB=FF=FF=FF=FF=FD=FF=FF=FFU=FF=FF=FD=FF=F5=F5= k=ED=DD=FD=FF=FF=FF=BF=BF=AB=FF=FF Tue Aug 21 20:45:39 2001 }=FB=FF=FF=FF=FD=FF Tue Aug 21 20:45:39 2001 =D5=FF=FF=F5=F5=FB=FF=FB=FD=FD=FD=FF Tue Aug 21 20:45:41 2001 }=FB=FF=FF=F5=FF=FD=FF=FD=FF=BD]=F5=FD=FF=FF=F5= =FF=FF=FF=FF=FF=FF=FF=FF=FF=FF=DD=DD=BF=FD=BF=BF=AB=FF=BD=ED=FF=BD]=FF=F5 Tue Aug 21 20:45:42 2001 =FF Tue Aug 21 20:45:43 2001 =FD Tue Aug 21 20:45:43 2001 =FD Tue Aug 21 20:45:44 2001 =F5 Tue Aug 21 20:45:44 2001 =FF Tue Aug 21 20:45:45 2001 }=FB=FF=FF=F5=FF=FD=FF=FF=FF=FF=FF=FF=D5=FD=FF=FF= =FF=FF=FF=FD=FD=FFW=D7=F5=F5=FD Tue Aug 21 20:45:50 2001 }=FF=F5=FF=FF=FD=FF=FF=FF=FF=D5=EB=FB=FF=FD=FF=F5= =FF=F5=FF=FD=FD=F5=FF=FFU=F5=F5=FD=FD=BD=BF=FD Tue Aug 21 20:46:15 2001 KC7ZRU-15>APRS,WIDE3-3:!4251.19N/10619.20WI/A=3D= 005156 Casper's aprsd server/I-gate - kc...@ar... ::snipped:: The first 3 and last lines were generated with 2.1.4.vk3sb.2 (not running= concurantly) Nothing is atually going out the TNC (listening with a 2nd radio). The 'S= ent to TNC' lines look fine. Running as a 'normal' serial TNC - no KISS or kernel AX.25 support. Does the CVS version use a different port speed/setting that's not matche= d in the TNC? Did running the executable in the 'old' location break some= thing? Is 'normal' serial mode being changed and something is pending? Ideas? In the interim - I'm running 2.1.4.vk3sb.2 - keep things on the air 73 --=20 /\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\ | CARC Repeater 146.940 DN62 | | http://groups.yahoo.com/group/RM-APRS | | "The Dungeon" at http://go.to/KC7ZRU | +++++++++++++++++++++++++++++++++++++++++++++++ |
From: Hamish M. <ha...@cl...> - 2001-08-22 12:18:05
|
I just tested aprsd CVS with a single callsign listed in gate2rf, VK3SB-2, and it seemed to work fine. Hamish -- Hamish Moffatt VK3SB <ha...@de...> <ha...@cl...> |
From: Hamish M. <ha...@cl...> - 2001-08-22 06:45:11
|
On Tue, Aug 21, 2001 at 07:26:16PM -0400, Michael J. Wolthuis - KB8ZGL wrote: > You see them going out to the TNC? Are you watching live RF or via one of > the ports(14580?) > Just wondering how you are seeing this. I'm seeing "Sending to TNC:" messages in the aprsd output (when it's run without -d). I also modified it to send TNC output to a file instead of to the serial port and saw the output there too. > I will try some with adding a * as you did to test further on my IGATES. I don't think a wildcard should be necessary (if so it's a bug) but I'll check. Hamish -- Hamish Moffatt VK3SB <ha...@de...> <ha...@cl...> |
From: Michael J. W. - K. <kb...@mf...> - 2001-08-21 23:17:19
|
You see them going out to the TNC? Are you watching live RF or via one of the ports(14580?) Just wondering how you are seeing this. I will try some with adding a * as you did to test further on my IGATES. Thanks! Mike kb8zgl ----- Original Message ----- From: <apr...@li...> To: <apr...@li...> Sent: Tuesday, August 21, 2001 3:12 PM Subject: Aprsd-users digest, Vol 1 #16 - 1 msg > Send Aprsd-users mailing list submissions to > apr...@li... > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.sourceforge.net/lists/listinfo/aprsd-users > or, via email, send a message with subject or body 'help' to > apr...@li... > > You can reach the person managing the list at > apr...@li... > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Aprsd-users digest..." > > > Today's Topics: > > 1. gate2rf in CVS aprsd (Hamish Moffatt) > > --__--__-- > > Message: 1 > Date: Tue, 21 Aug 2001 23:22:51 +1000 > From: Hamish Moffatt <ha...@cl...> > To: apr...@li... > Subject: [Aprsd-users] gate2rf in CVS aprsd > > > I'm testing gate2rf with the current CVS aprsd code right now > and it seems to work fine. I put "gate2rf VK*" and I can see > packets from VK stations going out to the TNC. > > Can anyone who has seen this problem give me some more information? > > > thanks, > Hamish > -- > Hamish Moffatt VK3SB <ha...@de...> <ha...@cl...> > > > > --__--__-- > > _______________________________________________ > Aprsd-users mailing list > Apr...@li... > http://lists.sourceforge.net/lists/listinfo/aprsd-users > > > End of Aprsd-users Digest > |
From: Hamish M. <ha...@cl...> - 2001-08-21 13:23:00
|
I'm testing gate2rf with the current CVS aprsd code right now and it seems to work fine. I put "gate2rf VK*" and I can see packets from VK stations going out to the TNC. Can anyone who has seen this problem give me some more information? thanks, Hamish -- Hamish Moffatt VK3SB <ha...@de...> <ha...@cl...> |
From: Hamish M. <ha...@cl...> - 2001-08-20 09:17:00
|
On Sun, Aug 19, 2001 at 06:30:13PM -0400, Michael J. Wolthuis - KB8ZGL wrote: > Here is the piece of info that is interesting, posit2rf works fine. Only gate2rf does not send data. Well that's probably a good lead. I'll look into it, since I worked on that part of the code most recently I think. > Someone emailed me and said I should go back to 2.1.4, but I feel this is not in the best interests of IGATE operators. v2.2.0 has been much more stable for me, but is only functioning one-way. This is a huge problem that we need to get resolved before others begin switching to this version. Yes, that was me.. > Has anyone tried v2.2.0 with Internet to live RF and a live TNC? Is this not the ACTUAL functionallity behind an IGATE? Last time I had time to try it, it didn't work that well, so I took my own advice and downgraded! I haven't had time to debug it since then. Also, I'm only using posit2rf here, so I'll check with gate2rf asap. By the way, as I've said many times before, PLEASE don't call it "2.2.0". "2.2.0" is a future release. The code we have now is not that final release. It is best called the "CVS version" or similar. Since it can change from minute-to-minute, it is confusing to put a version number to it. Hamish -- Hamish Moffatt VK3SB <ha...@de...> <ha...@cl...> |
From: Michael J. W. - K. <kb...@mf...> - 2001-08-19 22:21:30
|
Everyone, Just a quick piece of info I found on my michigan.aprs.net v2.2.0 = Internet to RF problem. I still have been unable to find the exact problem, we are still = reviewing the code. I have verified all settings in the serial.cpp file and it is correct. Here is the piece of info that is interesting, posit2rf works fine. = Only gate2rf does not send data. Someone emailed me and said I should go back to 2.1.4, but I feel this = is not in the best interests of IGATE operators. v2.2.0 has been much = more stable for me, but is only functioning one-way. This is a huge = problem that we need to get resolved before others begin switching to = this version. Has anyone tried v2.2.0 with Internet to live RF and a live TNC? Is = this not the ACTUAL functionallity behind an IGATE? Please HELP! I have 4 coders reviewing the code, but we have all been = unable to find the problem yet. Mike kb8zgl |
From: Chuck B. <cb...@vi...> - 2001-08-16 14:27:13
|
On Wednesday 15 August 2001 09:25 pm, Michael J. Wolthuis - KB8ZGL wrote: :: Has anyone experienced a problem with 2.2.0 not sending messages to RF? :: Make sure your port settings are correct in serial.cpp (AsyncSetupPort), this code will eventually find its way to a config file. Chuck |
From: Hamish M. <ha...@cl...> - 2001-08-16 03:25:06
|
On Wed, Aug 15, 2001 at 09:25:55PM -0400, Michael J. Wolthuis - KB8ZGL wrote: > This is a MAJOR problem, as both my IGATEs are thus receive only, please advise and HELP! Same happens on all three implementations of 2.2.0. I did not see this problem back when I ran 2.1.4 Unless you have the time and skills to debug the problem I would suggest that you just run 2.1.4 then. Hamish -- Hamish Moffatt VK3SB <ha...@de...> <ha...@cl...> |
From: Michael J. W. - K. <kb...@mf...> - 2001-08-16 01:16:57
|
Has anyone experienced a problem with 2.2.0 not sending messages to RF? I have a serious problem on igate.miaprs.net and elansing.miaprs.net, = both IGATEs have latest 2.2.0 compiled on them and michigan.aprs.net has = two copys for two TNCs running on it. =20 Problem is that when ever anything comes in to go to RF it is appended = correctly to rf.log, but watching local RF it NEVER goes out!=20 I sat in my driveway as messages and NWS weather warnings came through = and watched RF.log grow via 802.11b connection, but I watched APRS on RF = with an HT and it never saw any of the messages sent. I also watched the transmitter, NOTHING. To test that TNC was correctly set to convers mode, I stopped APRSd and = used a terminal program to test, it was in covers mode, first thing I = typed went to RF. This is a MAJOR problem, as both my IGATEs are thus receive only, please = advise and HELP! Same happens on all three implementations of 2.2.0. I = did not see this problem back when I ran 2.1.4 Mike Wolthuis kb8zgl kb...@mi... |