Re: status problems (in findu, too)
> The X-digi has a few problems. The one I saw the most when runningFair enough, but ... many many other packets get through this X-digi
> it was it completely trashed the path of the packet it was repeating
> every so often.
w/o being mangled.
- --- Chris Kantarjiev <cak@...> wrote:
>Ok, I was bored this afternoon so I thought I want to
> The setup here is that there's a WRT54 running
> arps4r acting as
> the digi/igate; it uses the T2 as a TNC. The T2
> generates the
> status packet directly; it gets digi'd by OKHRST,
> and comes back
> to be igate'd
duplicate your problem on my T2 that is acting as a
My T2 (actually a T2-135) is permanently installed as
a digi, and also doing as a WX station. So I hook this
board up to a ubuntu laptop running aprsd to do
perform as an igate .
The status packets from the T2 is digipeated by a
Kenwood D700 then comes back to the T2 and gets
I see no trailing garbage on TKUSIR's status packets,
unlike on yours.
Hope that helps,
73 de Paulus - N5SNN / YD0NXX
Luggage? GPS? Comic books?
Check out fitting gifts for grads at Yahoo! Search
- I haven't forgotten about this... do you have the config file for the
unit so I can try to duplicate it?
Chris Kantarjiev wrote:
> Scott and others looking at this,
> I'm out at CDRVLY this weekend, looking at the logs more carefully. I
> still see problems in APRS-IS with garbage at the end of the OT2
> status packets.
> The thing I notice, though, is that the garbage is there when the
> status packet arrives to be igated!
> The setup here is that there's a WRT54 running arps4r acting as
> the digi/igate; it uses the T2 as a TNC. The T2 generates the
> status packet directly; it gets digi'd by OKHRST, and comes back
> to be igate'd (there's a small problem in that pass, too, since
> the igate seems to be stripping part of the digipath).
> When the packet arrives here, it already has a string of nulls
> at the end, and the igate is passing that along faithfully.
> So ... that says to me that either the T2 is sending them, or,
> perhaps, OKHRST doesn't quite like the packet. OKHRST is an X-Digi/TNC-X,
> which adds another compontent to the puzzle :-)
> 73 de chris K6DBG