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

[NOAAPORT #GGP-872890]: New Noaaport server with ldm

Hi Heather,

re:
> Okay, I was wrong, big mistake.  My novra is on eth1:
> [root@npingest ~]# ip addr
> 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group 
> default qlen 1000
> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
> inet 127.0.0.1/8 scope host lo
> valid_lft forever preferred_lft forever
> inet6 ::1/128 scope host
> valid_lft forever preferred_lft forever
> 2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP 
> group default qlen 1000
> link/ether 00:25:90:e7:0f:ba brd ff:ff:ff:ff:ff:ff
> inet 10.2.15.252/24 brd 10.2.15.255 scope global noprefixroute eno1
> valid_lft forever preferred_lft forever
> inet6 fe80::225:90ff:fee7:fba/64 scope link
> valid_lft forever preferred_lft forever
> 3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP 
> group default qlen 1000
> link/ether 00:25:90:e7:0f:bb brd ff:ff:ff:ff:ff:ff
> inet 192.168.0.10/24 brd 192.168.0.255 scope global eth1
> valid_lft forever preferred_lft forever
> inet6 fe80::225:90ff:fee7:fbb/64 scope link
> valid_lft forever preferred_lft forever
> 
> So I did the tcpdump -i eth1 and I have attached the output.  But it is just 
> this:
> mtp.mcast.net.ipcd3: UDP, bad length 4032 > 1472

This shows that UDP packets from the Novra are making it to eth1,
but the 'bad length' messages on so many packets indicates that
there is something wrong.  At this point, I would try rebooting
the Novra to see if the 'bad length' messages go away.

Question:

- can you use 'cmcs' to talk to the Novra?

  If yes, what are the outputs of:

  show traffic       <- this will show DVB packets accepted and # uncorrectable 
errors

  show device        <- this will show the firmware version

  show pids          <- this will show the PIDs that the Novra is configured for

  show lan           <- this will show how the Novra is configured for LAN

re:
> I modified the iptables to include eth1 NOT eno2:
> 
> [root@npingest ~]# iptables -nvL
> Chain INPUT (policy ACCEPT 0 packets, 0 bytes)
> pkts bytes target     prot opt in     out     source               destination
> 1161 82006 ACCEPT     all  --  *      *       0.0.0.0/0            0.0.0.0/0  
>           state RELATED,ESTABLISHED
> 0     0 ACCEPT     icmp --  *      *       0.0.0.0/0            0.0.0.0/0
> 44  2904 ACCEPT     all  --  lo     *       0.0.0.0/0            0.0.0.0/0
> 0     0 ACCEPT     tcp  --  *      *       0.0.0.0/0            0.0.0.0/0     
>        state NEW tcp dpt:22
> 897  142K REJECT     all  --  *      *       0.0.0.0/0            0.0.0.0/0   
>          reject-with icmp-host-prohibited
> 0     0 ACCEPT     all  --  eth1   *       0.0.0.0/0            0.0.0.0/0
> 
> Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
> pkts bytes target     prot opt in     out     source               destination
> 0     0 REJECT     all  --  *      *       0.0.0.0/0            0.0.0.0/0     
>        reject-with icmp-host-prohibited
> 
> Chain OUTPUT (policy ACCEPT 750 packets, 121K bytes)
> pkts bytes target     prot opt in     out     source               destination
> 
> I restarted iptables and the ldm and am still not getting data coming through.

The easiest way to test to see if the firewall is blocking traffic is to
turn it off; restart the LDM.

re:
> Any suggestions?

The errors shown in your tcpdump.out listing are troubling.  I think we need
to figure these out first then move on to the next step.

re:
> Thanks!!!

No worries.

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: GGP-872890
Department: Support NOAAPORT
Priority: Normal
Status: Closed
===================
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.