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.
Ryan, > We're trying to limit what a downstream LDM can pull from us. For > example, we had these two allow statements: > > allow WMO 10.2.1.93 ^(FT|SA) > allow WMO 10.2.1.93 ^(YLXB|YLXC) > > Unfortunately the second line appears to get ignored and we're only able > to successfully send ^FT and ^SA products. After I combined all of the > allows on to one line: > > allow WMO 10.2.1.93 ^(FT|SA|YLXB|YLXC) > > it started working. However, this becomes a problem when you have a lot > of WMO headers to put on one line. > > Do we have to use only one line? Because the first entry that matches the feedtype and host controls what the host can receive, I'm afraid that you must have all the "OK patterns" together. Note, however, that you can use the "not pattern" to disallow certain data-products. Regards, Steve Emmerson Ticket Details =================== Ticket ID: YIG-564077 Department: Support LDM Priority: Normal Status: Closed