Multicast addresses missing from the document are below.
EXEC "noaaportIngester -m 224.0.1.8"
EXEC "noaaportIngester -m 224.0.1.9"
EXEC "noaaportIngester -m 224.0.1.10"
http://www.nws.noaa.gov/noaaport/html/GOES_R.shtml
On Sat, Apr 29, 2017 at 2:27 PM, <admin@xxxxxxxx> wrote:
> I did and its running, but not getting the NOTHER products on the new
> GOES-16 feed.
>
>
>
> I see them with tcpdump
>
>
>
> Ray
>
>
>
> On Saturday, April 29, 2017 3:39pm, "Ryan Hickman" <ryan@xxxxxxxxxxxxxxxx>
> said:
>
> https://www.unidata.ucar.edu/software/ldm/ldm-current/utilit
> ies/noaaport/index.html
> I assume you've followed the above documentation? Make sure your
> configurations match the above link and you should see data coming over
> "ldmadmin watch." There's no need for a "request."
>
> On Sat, Apr 29, 2017 at 1:33 PM, <admin@xxxxxxxx> wrote:
>
>> Sent to poor Gilbert instead of the list.
>>
>>
>>
>> Long time since we did noaaport ingest direct, finally dish back up.
>>
>>
>>
>> in the ldmd.conf I have the exec noaaportIngester commands, and confirmed
>> with tcpdump all kinds of data on the eth1 port connected to the S300.
>>
>>
>>
>> Put the exec readnoaaport lines in too, not sure If I need them.
>>
>>
>>
>> What to I put in for a request line to request it from my own machine?
>> LOL.
>>
>> I think that's the only issue.
>>
>>
>>
>> ldmadmin watch shows nothing hitting LDM, despite the multicast data
>> showing on the Ethernet with tcpdump.
>>
>>
>>
>> Ray Weber
>>
>> MA Skywarn
>>
>>
>>
>> _______________________________________________
>> NOTE: All exchanges posted to Unidata maintained email lists are
>> recorded in the Unidata inquiry tracking system and made publicly
>> available through the web. Users who post to any of the lists we
>> maintain are reminded to remove any personal information that they
>> do not want to be made public.
>>
>>
>> ldm-users mailing list
>> ldm-users@xxxxxxxxxxxxxxxx
>> For list information or to unsubscribe, visit:
>> http://www.unidata.ucar.edu/mailing_lists/
>
>
