Re: [Aprsd-devel] problem with messaging

[Hamish M. <ha...@cl...>]

I did find a real aprsd bug: in aprsString.cpp, the packet checking
code was throwing away messages if they were SHORTER than the maximum
length, not LONGER. There was one other type of packet it did that
too as well; both fixed and verified.

As well as that I was having Xastir problems. It's possible that
it's intentional; the stations I tried to message unsuccessfully
were on a different interface which I had then brought down.
ie I was trying to message them on one interface after hearing
them on another.

Hamish

On Sat, Dec 08, 2001 at 11:32:52PM -0600, Brian D Heaton wrote:
> Could this be an Xastir problem?  If Xastir's behavior varies based on
> whether or not the station is in the history list it sounds like
> something in Xastir is not working correctly.  I know that I used an
> older CVS snapshot on the aprsd 2.2.1 code and was able to send messages
> in/out to folks I had on my map.
> 
> 			THX/BDH
> 
> 
> On Sat, 2001-12-08 at 17:39, Hamish Moffatt wrote:
> > 
> > I'm trying to debug this messaging thing but I can't get Xastir
> > to send any messages!
> > 
> > I'm running 'nc -l -p 10151' on my debug machine, and connecting
> > to it with xastir. Xastir sends the login string OK, and sends
> > beacons, but never sends messages.
> > 
> > I was using 1.0.0 and I just got the 1208 snapshot from CVS
> > (1.0.5), same thing.
> > 
> > It seems that if I use the 'Send Message To' command to
> > send a message to an unknown callsign, it works. If I send
> > to somebody on the map, it never actually sends anything.
> > 
> > Can anyone help?
> > 
> > Hamish
> > -- 
> > Hamish Moffatt VK3SB <ha...@de...> <ha...@cl...>
> > 
> > _______________________________________________
> > Aprsd-devel mailing list
> > Apr...@li...
> > https://lists.sourceforge.net/lists/listinfo/aprsd-devel
> > 
> 
> 

-- 
Hamish Moffatt VK3SB <ha...@de...> <ha...@cl...>