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

[LDM #RTQ-862032]: Internal Server to External issue

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: [LDM #RTQ-862032]: Internal Server to External issue
  • Date: Mon, 26 Oct 2020 14:35:17 -0600
Hi Tiffany,

> After alot of time invested I have it figured this out, but I am not sure WHY 
> this was not working for me.
> 
> In the ldmd.conf (and all of our other LDM machine configs (x5)) we have the 
> ALLOW lines as so:
> ALLOW ANY     10.1.142.77
> 
> This has always worked just fine and those are on version (6.13.1).
> However, with this new SRPHYLDM (on current version) I had to do:
> ALLOW ANY     10.1.142.77 .*
> 
> Which has me stumped because in the config file it mentions this is already a 
> default if not added and optional unless of course you want to specify.
> 
> Do you guys have any ideas of why this would not work without that optional 
> field or have you seen this before?

Wow! No, we've never see this before and none of our operational LDM-s use that 
field. Also, the relevant code hasn't changed in years.

Does the SRPHYLDM LDM differ from the Unidata LDM?

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: RTQ-862032
Department: Support LDM
Priority: Normal
Status: Closed
===================
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.