NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
ncameron
Mar 31, 2022Aspirant
ReadyNAS says "No IP Address": I can connect to it, but it cannot connect to Internet
I was having trouble loading Spotty on LMS Web interface due to the outdated standard SSL version on this device. Following laborious instructions on this Forum I managed to update SSL, and now I ca...
ncameron
Apr 03, 2022Aspirant
I switched back to the other NIC; now I get this:
Link encap:Ethernet HWaddr e8:fc:af:e6:aa:f8
inet addr:192.168.1.32 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: 2603:7080:a403:6415:0:fc02:320:f87c/64 Scope:Global
inet6 addr: fe80::eafc:afff:fee6:aaf8/64 Scope:Link
inet6 addr: 2603:7080:a403:6415:eafc:afff:fee6:aaf8/64 Scope:Global
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:18428 errors:0 dropped:0 overruns:0 frame:0
TX packets:9198 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:3430479 (3.2 MiB) TX bytes:4358192 (4.1 MiB)
Interrupt:16 Memory:fea00000-fea20000
BUT; still get same error message with no outside access...
StephenB
Apr 03, 2022Guru - Experienced User
ncameron wrote:
I switched back to the other NIC; now I get this:
Link encap:Ethernet HWaddr e8:fc:af:e6:aa:f8
inet addr:192.168.1.32 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: 2603:7080:a403:6415:0:fc02:320:f87c/64 Scope:Global
inet6 addr: fe80::eafc:afff:fee6:aaf8/64 Scope:Link
inet6 addr: 2603:7080:a403:6415:eafc:afff:fee6:aaf8/64 Scope:Global
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:18428 errors:0 dropped:0 overruns:0 frame:0
TX packets:9198 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:3430479 (3.2 MiB) TX bytes:4358192 (4.1 MiB)
Interrupt:16 Memory:fea00000-fea20000
BUT; still get same error message with no outside access...
A lot of errors.
But did you try the other tests with the new NIC? Particularly
ping 8.8.8.8
nslookup dns.google.com
- ncameronApr 04, 2022Aspirant
They look OK:
--- 8.8.8.8 ping statistics ---
28 packets transmitted, 28 packets received, 0% packet loss
round-trip min/avg/max = 28.250/30.859/37.911 msroot@HAL9000:~# nslookup dns.google.com
Server: 209.18.47.62
Address 1: 209.18.47.62 dns-cac-lb-02.rr.comName: dns.google.com
Address 1: 2001:4860:4860::8844 dns.google
Address 2: 2001:4860:4860::8888 dns.google
Address 3: 8.8.4.4 dns.google
Address 4: 8.8.8.8 dns.googleBut STILL I get the comms error when the ReadyNAS tries to access the outside world. e.g. BIOS Update Check. Weird.
- StephenBApr 04, 2022Guru - Experienced User
ncameron wrote:
They look OK:
But STILL I get the comms error when the ReadyNAS tries to access the outside world. e.g. BIOS Update Check. Weird.
This may be limited to services that use TLS/SSL.
Try
openssl s_client -connect www.google.com:443and see what happens.
- ncameronApr 07, 2022Aspirant
Tried that. I get a long result which I have posted here three times, but never sticks - so I think it's too long.
The highlights are:
CONNECTED(00000003)
depth=2 C = US, O = Google Trust Services LLC, CN = GTS Root R1
verify error:num=20:unable to get local issuer certificate
verify return:0
---
Certificate chain
0 s:/CN=www.google.com
i:/C=US/O=Google Trust Services LLC/CN=GTS CA 1C3
1 s:/C=US/O=Google Trust Services LLC/CN=GTS CA 1C3
i:/C=US/O=Google Trust Services LLC/CN=GTS Root R1
2 s:/C=US/O=Google Trust Services LLC/CN=GTS Root R1
i:/C=BE/O=GlobalSign nv-sa/OU=Root CA/CN=GlobalSign Root CAThen certificate details; then:
subject=/CN=www.google.com
issuer=/C=US/O=Google Trust Services LLC/CN=GTS CA 1C3
---
No client certificate CA names sent
---
SSL handshake has read 4901 bytes and written 415 bytes
---
New, TLSv1/SSLv3, Cipher is ECDHE-RSA-AES128-GCM-SHA256
Server public key is 2048 bit
Secure Renegotiation IS supported
Compression: NONE
Expansion: NONE
SSL-Session:
Protocol : TLSv1.2
Cipher : ECDHE-RSA-AES128-GCM-SHA256
Session-ID: B7DFFDB1747B843CC6A897757CAA578305FA3BAF5313E281BD6DA43651763C2C
Session-ID-ctx:
Master-Key: 0F9BB680075A2F425EB86FE290C233D7345188FBD22B3EC2B18612E25F2E2E58757F41005E5D86D7FE2CC50B56EA87B8
Key-Arg : None
PSK identity: None
PSK identity hint: None
SRP username: None
TLS session ticket lifetime hint: 100800 (seconds)
TLS session ticket:And finally:
Verify return code: 20 (unable to get local issuer certificate)
So it looks like in trying to update SSL I have screwed it up. But how do I get a working certificate if I can't connect to anything?!
Thanks for all your help by the way...
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!