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

[LDM #RKK-379892]: LDM logging and operation issues

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 #RKK-379892]: LDM logging and operation issues
  • Date: Thu, 05 Jul 2007 12:58:37 -0600
Evan,

> The firewall rules to 129.82.225.8 have been changed, but I am still
> unable to gain access to the computer.<br>
> <br>
> The rule was changed to allow ANY computer to access 129.82.225.8 on
> tcp/111 and tcp/388.&#65533;  There is an LDM running on that computer now and
> like I said, I shut off the iptables and included an "ALLOW&#65533; &#65533; 
> &#65533;
> NEXRAD2&#65533; &#65533; &#65533;  ^(.*$)" line in ldmd.conf to test the 
> connection through the
> firewall.&#65533;  Could you attempt to access it now and tell me what
> happens?&#65533;  If possible, could you also tell me the time you tried to
> access 129.82.225.8?&#65533;  We have set up a sniff on the firewall to see 
> who
> tries to access 129.82.225.8 from the outside.<br>

Host 129.82.225.8 exists and appears to be running an LDM:

$ date && ldmping -vl- -i 0 129.82.225.8
Thu Jul  5 12:57:26 MDT 2007
Jul 05 18:57:26 INFO:      State    Elapsed Port   Remote_Host           
rpc_stat
Jul 05 18:57:26 INFO: RESPONDING   0.041466  388   129.82.225.8  

This was not the case 5 minutes ago.

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: RKK-379892
Department: Support LDM
Priority: Normal
Status: Closed