[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[NOAAPORT #ZLV-851048]: LDM misses data on NOAAPORT via satellite
- Subject: [NOAAPORT #ZLV-851048]: LDM misses data on NOAAPORT via satellite
- Date: Mon, 21 Dec 2020 14:38:17 -0700
Hi Jim,
My apologies for not being able to get back to you before now!
As far as your situation goes, I have not experienced this problem
before in any setup that I have been involved in troubleshooting.
That being said, however, I happened to notice that the configuration
listings for both of your Ethernet interfaces have the following
entry:
DEFROUTE=yes
The first exchange listed in a Google search using this as the search key
suggested that this is only used by 'networkmanager'. So the question to
you is if your systems are using 'networkmanager'?
Beyond this, I will need to get our system administrator involved to
see if he can spot anything in the listings you provided.
Cheers,
Tom
re:
> To give you feedback on what I did. After plugging in the new NIC I used the
> GUI in
> Centos to assign a 192.168.1.203 address with Net 255.255.255.0 and gateway of
> 192.168.1.1 onto the card.
>
> I opened a terminal and went to /etc/sysconfig/network-scripts. As "su" I
> created
> route-eno1 and put this into the file:
>
> ADDRESS0=224.0.1.1
> NETMASK0=255.255.255.255
> ADDRESS1=224.0.1.2
> NETMASK1=255.255.255.255
> ADDRESS2=224.0.1.3
> NETMASK2=255.255.255.255
> ADDRESS3=224.0.1.4
> NETMASK3=255.255.255.255
> ADDRESS4=224.0.1.5
> NETMASK4=255.255.255.255
> ADDRESS5=224.0.1.6
> NETMASK5=255.255.255.255
> ADDRESS6=224.0.1.7
> NETMASK6=255.255.255.255
> ADDRESS7=224.0.1.8
> NETMASK7=255.255.255.255
> ADDRESS8=224.0.1.9
> NETMASK8=255.255.255.255
> ADDRESS9=224.0.1.10
> NETMASK9=255.255.255.255
> ADDRESS10=224.1.1.1
> NETMASK10=255.255.255.255
>
> and saved it. I rebooted the computer for good measure and when I started ldm
> I was
> not getting any data. I opened the GUI and notice it had a routing section
> under
> that interface. I noticed it had red on the gateway for all the routes I had
> entered.
> So I entered 192.168.1.1 for each and noticed the route-eno1 file then
> contained
> this:
>
> ADDRESS0=224.0.1.1
> NETMASK0=255.255.255.255
> ADDRESS1=224.0.1.2
> NETMASK1=255.255.255.255
> ADDRESS2=224.0.1.3
> NETMASK2=255.255.255.255
> ADDRESS3=224.0.1.4
> NETMASK3=255.255.255.255
> ADDRESS4=224.0.1.5
> NETMASK4=255.255.255.255
> ADDRESS5=224.0.1.6
> NETMASK5=255.255.255.255
> ADDRESS6=224.0.1.7
> NETMASK6=255.255.255.255
> ADDRESS7=224.0.1.8
> NETMASK7=255.255.255.255
> ADDRESS8=224.0.1.9
> NETMASK8=255.255.255.255
> ADDRESS9=224.0.1.10
> NETMASK9=255.255.255.255
> ADDRESS10=224.1.1.1
> NETMASK10=255.255.255.255
> GATEWAY0=192.168.1.1
> GATEWAY1=192.168.1.1
> GATEWAY2=192.168.1.1
> GATEWAY3=192.168.1.1
> GATEWAY4=192.168.1.1
> GATEWAY5=192.168.1.1
> GATEWAY6=192.168.1.1
> GATEWAY7=192.168.1.1
> GATEWAY8=192.168.1.1
> GATEWAY9=192.168.1.1
> GATEWAY10=192.168.1.1
>
> I now get data if I do a ldmadmin watch. If I am on another computer on the
> LAN and
> go to http://10.133.205.246 I get the webpage on wxengine4, but if I am at
> home and
> log into our corporate VPN I used to be able to go to http://10.133.205.246
> and get
> the same page. Now it cannot connect to the web page. It seems as if it is
> not
> responding to request coming across the gateway.
>
> the results for netstat -rn for wxengine4:
>
> [ldm@wxengine4 network-scripts]$ netstat -rn
> Kernel IP routing table
> Destination Gateway Genmask Flags MSS Window irtt Iface
> 0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 eno1
> 0.0.0.0 10.133.207.217 0.0.0.0 UG 0 0 0
> enp1s0
> 10.133.204.0 0.0.0.0 255.255.252.0 U 0 0 0
> enp1s0
> 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eno1
> 192.168.122.0 0.0.0.0 255.255.255.0 U 0 0 0
> virbr0
> 224.0.1.1 192.168.1.1 255.255.255.255 UGH 0 0 0 eno1
> 224.0.1.2 192.168.1.1 255.255.255.255 UGH 0 0 0 eno1
> 224.0.1.3 192.168.1.1 255.255.255.255 UGH 0 0 0 eno1
> 224.0.1.4 192.168.1.1 255.255.255.255 UGH 0 0 0 eno1
> 224.0.1.5 192.168.1.1 255.255.255.255 UGH 0 0 0 eno1
> 224.0.1.6 192.168.1.1 255.255.255.255 UGH 0 0 0 eno1
> 224.0.1.7 192.168.1.1 255.255.255.255 UGH 0 0 0 eno1
> 224.0.1.8 192.168.1.1 255.255.255.255 UGH 0 0 0 eno1
> 224.0.1.9 192.168.1.1 255.255.255.255 UGH 0 0 0 eno1
> 224.0.1.10 192.168.1.1 255.255.255.255 UGH 0 0 0 eno1
> 224.1.1.1 192.168.1.1 255.255.255.255 UGH 0 0 0 eno1
> [ldm@wxengine4 network-scripts]$
>
>
> >>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.
>
> Yes, when i am at my desk computer in the office which is on the same
> 10.133... LAN I
> can ssh to wxengine3 and wxengine4 but when I am on the VPN I cannot and
> could before
> and if I turn off the second NIC I can do it again...so something I have done
> on that
> second NIC has upset things.
>
> As a side note...I just turned the firewall off completely with a systemctl
> stop
> firewalld just to remove that from the equation and that has not helped.
>
> Here is the config for the private LAN on wxengine4:
>
> [ldm@wxengine4 network-scripts]$ cat ifcfg-eno1
> HWADDR=24:BE:05:E1:98:55
> TYPE=Ethernet
> PROXY_METHOD=none
> BROWSER_ONLY=no
> BOOTPROTO=none
> DEFROUTE=yes
> IPV4_FAILURE_FATAL=no
> IPV6INIT=yes
> IPV6_AUTOCONF=yes
> IPV6_DEFROUTE=yes
> IPV6_FAILURE_FATAL=no
> IPV6_ADDR_GEN_MODE=stable-privacy
> NAME=eno1
> UUID=3fa83fe4-fca7-328b-b33a-0d4318fa9e1e
> DEVICE=eno1
> ONBOOT=yes
> AUTOCONNECT_PRIORITY=-999
> IPADDR=192.168.1.203
> PREFIX=24
> GATEWAY=192.168.1.1
> [ldm@wxengine4 network-scripts]$
>
> And the main interface on wxengine4:
>
> [ldm@wxengine4 network-scripts]$ cat ifcfg-enp1s0
> TYPE=Ethernet
> PROXY_METHOD=none
> BROWSER_ONLY=no
> BOOTPROTO=none
> DEFROUTE=yes
> IPV4_FAILURE_FATAL=no
> IPV6INIT=yes
> IPV6_AUTOCONF=yes
> IPV6_DEFROUTE=yes
> IPV6_FAILURE_FATAL=no
> IPV6_ADDR_GEN_MODE=stable-privacy
> NAME=enp1s0
> UUID=6838598a-ce0f-4f6c-8589-45550a4052a7
> DEVICE=enp1s0
> ONBOOT=yes
> IPADDR=10.133.205.246
> PREFIX=22
> GATEWAY=10.133.207.217
> DNS1=10.133.207.210
> DNS2=10.133.199.5
> IPV6_PRIVACY=no
> [ldm@wxengine4 network-scripts]$
>
>
> --------------------------------------------------------------------
> from wxengine3:
>
> [ldm@wxengine3 ~]$ netstat -rn
> Kernel IP routing table
> Destination Gateway Genmask Flags MSS Window irtt Iface
> 0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0
> ens3f0
> 0.0.0.0 10.133.207.217 0.0.0.0 UG 0 0 0
> enp63s0
> 10.133.204.0 0.0.0.0 255.255.252.0 U 0 0 0
> enp63s0
> 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0
> ens3f0
> 192.168.122.0 0.0.0.0 255.255.255.0 U 0 0 0
> virbr0
> 224.0.1.1 192.168.1.1 255.255.255.255 UGH 0 0 0
> ens3f0
> 224.0.1.2 192.168.1.1 255.255.255.255 UGH 0 0 0
> ens3f0
> 224.0.1.3 192.168.1.1 255.255.255.255 UGH 0 0 0
> ens3f0
> 224.0.1.4 192.168.1.1 255.255.255.255 UGH 0 0 0
> ens3f0
> 224.0.1.5 192.168.1.1 255.255.255.255 UGH 0 0 0
> ens3f0
> 224.0.1.6 192.168.1.1 255.255.255.255 UGH 0 0 0
> ens3f0
> 224.0.1.7 192.168.1.1 255.255.255.255 UGH 0 0 0
> ens3f0
> 224.0.1.8 192.168.1.1 255.255.255.255 UGH 0 0 0
> ens3f0
> 224.0.1.9 192.168.1.1 255.255.255.255 UGH 0 0 0
> ens3f0
> 224.0.1.10 192.168.1.1 255.255.255.255 UGH 0 0 0
> ens3f0
> 224.1.1.1 192.168.1.1 255.255.255.255 UGH 0 0 0
> ens3f0
> [ldm@wxengine3 ~]$
>
> [ldm@wxengine3 network-scripts]$ cat ifcfg-ens3f0
> HWADDR=00:1B:21:C3:E9:54
> TYPE=Ethernet
> PROXY_METHOD=none
> BROWSER_ONLY=no
> BOOTPROTO=none
> IPADDR=192.168.1.202
> PREFIX=24
> DEFROUTE=yes
> IPV4_FAILURE_FATAL=no
> IPV6INIT=yes
> IPV6_AUTOCONF=yes
> IPV6_DEFROUTE=yes
> IPV6_FAILURE_FATAL=no
> IPV6_ADDR_GEN_MODE=stable-privacy
> NAME=ens3f0
> UUID=89ba67a7-a51a-3e24-a5f0-c952d8bc4b28
> DEVICE=ens3f0
> ONBOOT=yes
> AUTOCONNECT_PRIORITY=-999
> GATEWAY=192.168.1.1
> [ldm@wxengine3 network-scripts]$
>
> [ldm@wxengine3 network-scripts]$ cat route-ens3f0
> ADDRESS0=224.0.1.1
> NETMASK0=255.255.255.255
> ADDRESS1=224.0.1.2
> NETMASK1=255.255.255.255
> ADDRESS2=224.0.1.3
> NETMASK2=255.255.255.255
> ADDRESS3=224.0.1.4
> NETMASK3=255.255.255.255
> ADDRESS4=224.0.1.5
> NETMASK4=255.255.255.255
> ADDRESS5=224.0.1.6
> NETMASK5=255.255.255.255
> ADDRESS6=224.0.1.7
> NETMASK6=255.255.255.255
> ADDRESS7=224.0.1.8
> NETMASK7=255.255.255.255
> ADDRESS8=224.0.1.9
> NETMASK8=255.255.255.255
> ADDRESS9=224.0.1.10
> NETMASK9=255.255.255.255
> ADDRESS10=224.1.1.1
> NETMASK10=255.255.255.255
> GATEWAY0=192.168.1.1
> GATEWAY1=192.168.1.1
> GATEWAY2=192.168.1.1
> GATEWAY3=192.168.1.1
> GATEWAY4=192.168.1.1
> GATEWAY5=192.168.1.1
> GATEWAY6=192.168.1.1
> GATEWAY7=192.168.1.1
> GATEWAY8=192.168.1.1
> GATEWAY9=192.168.1.1
> GATEWAY10=192.168.1.1
> [ldm@wxengine3 network-scripts]$
>
> [ldm@wxengine3 network-scripts]$ cat ifcfg-enp63s0
> TYPE=Ethernet
> BOOTPROTO=none
> DEFROUTE=yes
> IPV4_FAILURE_FATAL=no
> IPV6INIT=yes
> IPV6_AUTOCONF=yes
> IPV6_DEFROUTE=yes
> IPV6_FAILURE_FATAL=no
> NAME=enp63s0
> UUID=d23abbc1-9e37-449f-b86d-7d415862864f
> ONBOOT=yes
> HWADDR=00:24:81:8F:7B:22
> DNS1=10.133.199.5
> DNS2=10.133.140.250
> MACADDR=00:24:81:8F:7B:22
> PROXY_METHOD=none
> BROWSER_ONLY=no
> IPADDR=10.133.205.247
> PREFIX=22
> GATEWAY=10.133.207.217
> [ldm@wxengine3 network-scripts]$
>
> Thanks for all your help Tom!
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.