[Xastir-dev] Broken "ST_DIRECT" flag?

[Tom Russo]

On Mon, Dec 27, 2004 at 09:05:45AM -0800, we recorded a bogon-computron collision of the <archer at eskimo.com> flavor, containing:
> On Mon, 27 Dec 2004, Tom Russo wrote:
> 
> > > Is this fixed now?
> >
> >
> > But I think the (null) path business for stations that have been gated
> > from Inet to RF is a result of the fix for the internet paths polluting rf
> > paths.
> 
> Yea, it's part of the ST_DIRECT fixes that I did.
> 
> We need to keep these igate stations in a different category from RF
> stations, as we don't want to be igating messages to RF for these
> stations as they don't exist there.
> 
> I can look at the code again w.r.t. these 3rd-party packets.  Most
> of the relevant code checks for that and doesn't process it past
> that stage.  Just need to snag the path and store it in the record.
> I assume we want the RF portion of the path and not the tcp/ip path
> that's in the 3rd-party portion?  That way we'll be able to tell
> what igate put it onto RF.

Not sure what I want other than that there not be null pointers in the
station record :-).

I think it would make sense if the path contain the path from the Igate to the 
xastir station, not the path from the originating station to the igate.  Not 
sure what the correct thing is.  

-- 
Tom Russo    KM5VY     SAR502  DM64ux         http://www.swcp.com/~russo/
Tijeras, NM  QRPL#1592 K2#398  SOC#236 AHTB#1 http://www.qsl.net/~km5vy/
 "When life gives you lemons, find someone with a paper cut."