[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: 20050928: ldm ACCEPT

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: Re: 20050928: ldm ACCEPT
  • Date: Wed, 28 Sep 2005 09:10:12 -0600
Chris,

> To: address@hidden
> From: Chris Webster <address@hidden>
> Subject: ldm ACCEPT
> Organization: NCAR
> Keywords: 200509281220.j8SCKQYJ021115 LDM ACCEPT

The above message contained the following:

> In transmitting data from the airplane to the ground the aircraft server 
> dials into an ISP and gets a DHCP address.  This poses a ldmd.conf issue 
> on the ground.  We see two routes; the ACCEPT command or DDNS.
> 
> - Is there a configuration change on the airplane side?  Or is it
>    sufficient to have just this on the ground:
> 
>    ACCEPT EXP (sql_sequence\.*.gz) 12.111.57.*

I think the above entry would be more properly written as

    ACCEPT EXP sql_sequence.*\.gz ^12\.111\.57\.

This would allow the LDM to accept, via the HIYA mechanism,
data-products of feedtype EXP whose product-identifiers start with
"sql_sequence" and end with ".gz" from hosts whose IP addresses start
with "12.111.57.".

The HIYA mechanism is used to send data-products by the programs
rtstats(1), pqsend(1), and ldmsend(1).  It is not, however, used by
the LDM server (which uses the FEEDME mechanism) so you might have
difficulty setting up such a system.  I therefore suggest that you
investigate the DDNS solution (with which I'm unfamiliar).

> --Chris

Regards,
Steve Emmerson

> NOTE: All email exchanges with Unidata User Support are recorded in the
> Unidata inquiry tracking system and then made publicly available
> through the web.  If you do not want to have your interactions made
> available in this way, you must let us know in each email you send to us.