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

[LDM #EWC-270147]: LDM

Hi Mike,

re:
> Our backup server is receiving NexRad2 data from unidata, but our primary
> ingest sever is not receiving this data.
> 
> Please allow NR2 data to flow to borg1.ncdc.noaa.gov
> 
> REQUEST NEXRAD2 "^L2-BZIP2/.*" idd.unidata.ucar.edu

This machine is already ALLOWed to REQUEST NEXRAD2 from our top level IDD relay
cluster, idd.unidata.ucar.edu.

Comments:

- a machine's IP address is included in the REQUEST sent to upstream LDMs

- a reverse DNS lookup on the received IP address is made, and then
  the name, if resolution is successful, is used to compare ALLOW
  rules in the upstream's LDM configuration file, ~ldm/etc/ldmd.conf

- we have a rule that ALLOWs machines that resolv to .gov to REQUEST
  feeds from our top level IDD relay, idd.unidata.ucar.edu

- we are not seeing any indication that any of the real server backends
  of our relay cluster are denying connection attempts from borg1's
  IP address, 205.167.25.129 or including its name

Question:

- is it possible that there is a firewall rule at NCDC that is not allowing
  outbound traffic to port 388 on remote machines for borg1?

Cheers,

Tom
--
****************************************************************************
Unidata User Support                                    UCAR Unidata Program
(303) 497-8642                                                 P.O. Box 3000
address@hidden                                   Boulder, CO 80307
----------------------------------------------------------------------------
Unidata HomePage                       http://www.unidata.ucar.edu
****************************************************************************


Ticket Details
===================
Ticket ID: EWC-270147
Department: Support IDD
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.