Plus, we're able to get data from wisc.edu just fine (except that their
data feed is giving us corrupt data and it's about an hour behind).
On Tue, Oct 14, 2014 at 11:32 PM, Blair Trosper <blair.trosper@xxxxxxxxx>
wrote:
> No change.
>
> On Tue, Oct 14, 2014 at 10:43 PM, Gilbert Sebenste <
> sebenste@xxxxxxxxxxxxxxxxxxxxx> wrote:
>
>> On Tue, 14 Oct 2014, Blair Trosper wrote:
>>
>> Here's the iptables config we have on startup (as root):
>>>
>>> iptables -A INPUT -p tcp -m tcp --dport 388 -j ACCEPT
>>>
>>>> iptables -A INPUT -p udp -m udp --dport 388 -j ACCEPT
>>>> iptables -A INPUT -p tcp --dport 111 -j REJECT
>>>> iptables -A INPUT -p udp --dport 111 -j REJECT
>>>> iptables-save
>>>>
>>>
>>>
>>> ...and here's how it looks right now on the server:
>>>
>>
>> Blair,
>>
>> What happens when you turn off iptables on your end?
>>
>> Gilbert
>>
>> ************************************************************
>> *******************
>> Gilbert Sebenste
>> ********
>> (My opinions only!)
>> ******
>> Staff Meteorologist, Northern Illinois University
>> ****
>> E-mail: sebenste@xxxxxxxxxxxxxxxxxxxxx
>> ***
>> web: http://weather.admin.niu.edu **
>> Twitter: http://www.twitter.com/NIU_Weather **
>> Facebook: http://www.facebook.com/niu.weather *
>> ************************************************************
>> *******************
>>
>> _______________________________________________
>> ldm-users mailing list
>> ldm-users@xxxxxxxxxxxxxxxx
>> For list information or to unsubscribe, visit:
>> http://www.unidata.ucar.edu/mailing_lists/
>
>
>
