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

[NOAAPORT #ZLV-851048]: LDM misses data on NOAAPORT via satellite

Hi Jim,

re:
> Here is where we stand today and a lot of good news! 

I always like good news! :-)

re:
> This week an engineer installed
> new cabling to make a private network between the two Novra receivers and the 
> two
> computers on second NIC cards. 

Excellent!

re:
> I just got it moved over late afternoon yesterday and
> then they did some testing of the line in the satellite dish. So, I have not 
> had a
> full day of running without people unplugging cables or adjusting things. 
> What I have
> seen is since all hands have been off from about 8pm last night until this 
> morning I
> have seen zero Gap messages! This is even before they have done work on the 
> dish
> which will happen this weekend.

This is wonderful news, and it reinforces my notion that the data path between
the Novra S300Ns and your machines was suspect.

re:
> Now the question. Since I added the second NIC into the machines it makes 
> networking
> more confusing.

It shouldn't really.  All that was needed was to setup the second Ethernet
cards on a private network and then setup multicast routing so that the
UDP packets could be read from the standard system interface.

re:
> I added the routing-<iface> you said to do but here is my situation.

Can you describe exactly what you did?  Given your comments below, this may
be very important.

re:
> My primary NIC goes to the rest of the LAN and out to the internet. 

OK, this is the standard way of setting things up.

re:
> The second NIC
> talks only on a private network to the Novra. When I VPN onto the company 
> network I
> could ssh into the box or go to the web pages that I had running on the box 
> to view
> the data. Now with the addition of the NIC, I cannot ssh directly into the 
> box or
> go to the web page running on it. 

This suggests that more than multicast routing was changed.

re:
> I noticed when I was in the building, I was able
> to just fine. 

I am not sure I understand this statement.  Are you saying that you can
SSH to your machines from other machines when you are in your building?
If yes, I would suspect a firewall setting is blocking access from the
outside even though you are VPNed in.

re:
> So, the problem is the traffic is not going out the gateway on the
> primary NIC it appears. If I confirmed by turning off the second NIC and the 
> traffic
> flows correctly, and I can ssh and everything just like before. I believe 
> this gets
> into routing tables which I do not fully understand.

Again, we need to review all of the changes that were made to determine what was
(over) done.

re:
> Here is my setup on wxengine4(faster computer):
> 
> Primary NIC(enp1s0):
> IP = 10.133.205.246
> NET = 255.255.252.0
> GATEWAY = 10.133.207.217
> DNS = 10.133.207.210, 10.133.199.5
> 
> Second NIC(eno1):
> IP = 192.168.1.203
> NET = 255.255.255.0
> GATEWAY = 192.168.1.1
> DNS = (blank)

These look OK.  What is the output of:

netstat -rn

re:
> -----------------------
> wxengine3(slower computer):
> Primary NIC(enp63s0):
> IP = 10.133.205.247
> NET = 255.255.252.0
> GATEWAY = 10.133.207.217
> DNS = 10.133.207.210, 10.133.199.5
> 
> Second NIC(ens3f0):
> IP = 192.168.1.202
> NET = 255.255.255.0
> GATEWAY = 192.168.1.1
> DNS = (blank)

Thesee also look OK.  Like for the other machine, what is the output
of:

netstat -rn

re:
> Do you happen to know how to make the traffic flow correctly out the primary 
> NIC
> gateway?

The addition of the second Ethernet interface should not have changed
the routing for the main interface by itself.  The question is exactly
what was done?

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: ZLV-851048
Department: Support NOAAPORT
Priority: Normal
Status: Open
===================
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.