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.
Patrick, I guess I'm not sure what you're asking because port numbers aren't relevant to the problem caused by having multiple downstream LDM-s that are behind a NAT device and requesting overlapping feeds from the same upstream LDM. The problem is that the upstream LDM sees the requests as coming from the same downstream computer (which has the IP address of the NAT device) and will disallow overlapping or identical requests. If this is a problem, then one workaround is to disable this anti-DOS feature by modifying the LDM registry on the upstream LDM. Another workaround is to make the requests appear to be non-overlapping or not identical by surrounding the regular expressions in the REQUEST entries with different levels of parentheses. For example, on one system REQUEST NEXRAD3 .* upstream.ldm.server and on another system REQUEST NEXRAD3 (.*) upstream.ldm.server > Um steve.. that wasn’t the question > > The question was, would assigning specific ports to each downstream box solve > LDM’s issue of assigning random ports if the noaaport ingester is behind a > NAT? I.e. currently 388 is defined, but as shown, random ports pop up. > > -- > ---------------------------------------- > Patrick L. Francis > Vice President of Research & Development > Media Logic Group > > http://www.medialogicgroup.com > http://www.hamweather.com > http://www.alertsbroadcaster.com > http://www.modelweather.com > > FB: http://www.facebook.com/wxprofessor > > ---- Regards, Steve Emmerson Ticket Details =================== Ticket ID: RBX-213298 Department: Support NOAAPORT Priority: Normal Status: Closed