I haven't been able to get https://kernel.org to load all year. The DNS lookup works, the TCP connection is made, but it stalls during the TLS handshake. I've waited up to 5 minutes for the connection to eventually time out, but it never does.
It's not really a big deal and I haven't brought it up until now because there are plenty of other places to grab the Linux source code. But it's really strange that kernel.org is the only site that does this for me. Perhaps their TLS server is somehow incompatible with AcceleNet?
It's not really a big deal and I haven't brought it up until now because there are plenty of other places to grab the Linux source code. But it's really strange that kernel.org is the only site that does this for me. Perhaps their TLS server is somehow incompatible with AcceleNet?
Posted 9 months ago
Bev, Champion
That one loads fine for me. Try clearing your browser, check firewall, etc...
I also can not go to that website without going directly to the IP address and bypassing the dns. so its nto just you.
xode0000, Champion
Do you have this problem with any other website? What happens if you do a traceroute to kernel.org? Another guess: possibly the cache in one of the hops is messed up?
I also can't get it to load. Firefox, sparrow.
xode0000, Champion
Do you by chance have the Exede wifi modem? If so, Joshua's workaround as described below might fix your problem.
Bev, Champion
As I mentioned in a reply above, I was also seeing this issue and was able to get a work-around going on my own.
However, I was going to mention, I think it is really worth it calling technical support and getting the issue escalated to the NOC. The NOC basically brushed me off as it not being an issue and it must be an issue with my firewall, etc.. They said that the site loaded on there test site but as I mentioned, I did discover the bug in the modem firmware that seems to result in the issue. I called support to let them know what I found but I have no idea if they actually forwarded that on to the right people internally...
At any rate, I think the more people call in who are experiencing the issue, and support tickets are raised. They'll actually have a look at the problem.
However, I was going to mention, I think it is really worth it calling technical support and getting the issue escalated to the NOC. The NOC basically brushed me off as it not being an issue and it must be an issue with my firewall, etc.. They said that the site loaded on there test site but as I mentioned, I did discover the bug in the modem firmware that seems to result in the issue. I called support to let them know what I found but I have no idea if they actually forwarded that on to the right people internally...
At any rate, I think the more people call in who are experiencing the issue, and support tickets are raised. They'll actually have a look at the problem.
(Edited)
I was optimistic about this solution, because my network was on 192.168.88.0/24. But switching to 192.168.1.0/24 didn't make a difference. :(
(Oops, I meant to reply to your other comment above.)
(Oops, I meant to reply to your other comment above.)
(Edited)
You may also want to check your DNS settings. I am using Exede's DNS servers, here are my nslookup results.
nslookup git.kernel.org
Server: 99.196.99.99
Address: 99.196.99.99#53
Non-authoritative answer:
git.kernel.org canonical name = pub.kernel.org.
pub.kernel.org canonical name = pub.sjc.kernel.org.
Name: pub.sjc.kernel.org
Address: 147.75.202.151
nslookup www.kernel.org
Server: 99.196.99.99
Address: 99.196.99.99#53
Non-authoritative answer:
www.kernel.org canonical name = pub.kernel.org.
pub.kernel.org canonical name = pub.sjc.kernel.org.
Name: pub.sjc.kernel.org
Address: 147.75.202.151
nslookup git.kernel.org
Server: 99.196.99.99
Address: 99.196.99.99#53
Non-authoritative answer:
git.kernel.org canonical name = pub.kernel.org.
pub.kernel.org canonical name = pub.sjc.kernel.org.
Name: pub.sjc.kernel.org
Address: 147.75.202.151
nslookup www.kernel.org
Server: 99.196.99.99
Address: 99.196.99.99#53
Non-authoritative answer:
www.kernel.org canonical name = pub.kernel.org.
pub.kernel.org canonical name = pub.sjc.kernel.org.
Name: pub.sjc.kernel.org
Address: 147.75.202.151
The only other thing I can think of would be to try a full modem reset (that was actually how I stumbled upon the issue).
so what was your work around because i'm having issues with my school and the only way i can get to the site is with a vpn so the issue is def with exede.
I should preface that I have the Exede WiFi Modem / Router combo.
I had configured the local subnet to something other than the default: 192.168.1.0/24. When I changed the setting back to the default, the site started loading fine.
I also, consequently enough, started getting a different response via DNS (using the same Exede DNS server). See https://community.viasat.com/viasat/topics/a-call-to-help-from-the-community for more details.
I had configured the local subnet to something other than the default: 192.168.1.0/24. When I changed the setting back to the default, the site started loading fine.
I also, consequently enough, started getting a different response via DNS (using the same Exede DNS server). See https://community.viasat.com/viasat/topics/a-call-to-help-from-the-community for more details.
Ok i have the same modem ill give it a shot and see if it helps me.
The interesting results for me were the differences in DNS..
When using 192.168.30.0/24 for my local network:
Server: 99-196-99-99.cust.exede.net
Address: 99.196.99.99
Non-authoritative answer:
Name: pub.ewr.kernel.org
Addresses: 2604:1380:1:3600::3
147.75.196.57
When using the default, 192.168.1.0/24 this is what I see
Server: 99-196-99-99.cust.exede.net
Address: 99.196.99.99
Non-authoritative answer:
Name: pub.sjc.kernel.org
Addresses: 2604:1380:1000:8100::5
147.75.202.151
When using 192.168.30.0/24 for my local network:
Server: 99-196-99-99.cust.exede.net
Address: 99.196.99.99
Non-authoritative answer:
Name: pub.ewr.kernel.org
Addresses: 2604:1380:1:3600::3
147.75.196.57
When using the default, 192.168.1.0/24 this is what I see
Server: 99-196-99-99.cust.exede.net
Address: 99.196.99.99
Non-authoritative answer:
Name: pub.sjc.kernel.org
Addresses: 2604:1380:1000:8100::5
147.75.202.151
xode0000, Champion
The NOC basically brushed me off as it not being an issue and it must be an issue with my firewall, etc..
@Joshua: I don't think that you ended up talking to the NOC, but to ViaSat's 3rd party technical support instead. The people there do not work for ViaSat. You might want to send an email to exedelistens@viasat.com and explain this problem to them as the people who manage that email address do work for ViaSat.
That's a good idea, I'll send along my results to them and hopefully it will end up in the right channel.
I should have clairified, I did end up all the way to there tier three support level and they would then relay the issue up to the NOC. So it's quite possible information got lost in transit.
I should have clairified, I did end up all the way to there tier three support level and they would then relay the issue up to the NOC. So it's quite possible information got lost in transit.
xode0000, Champion
You might also want to reference this forum thread as well in your email, as many of the same people who manage that email address are also on this forum. Exede (ViaSat?) Alex, requesting your assistance here.
Here's a traceroute, as requested:
C:\Users\David>tracert www.kernel.orgThe IP that TheName141 posted works for me, but the IP that I get from resolving www.kernel.org doesn't. A traceroute also succeeds:
Tracing route to pub.ewr.kernel.org [147.75.196.57]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.1.1
2 597 ms 584 ms 609 ms 10.75.13.224
3 613 ms 601 ms 600 ms 10.75.10.26
4 623 ms 640 ms 639 ms 10.95.240.161
5 632 ms 633 ms 643 ms six2.llnw.net [206.81.81.83]
6 712 ms 664 ms 680 ms lag15.fr4.ord.llnw.net [68.142.88.32]
7 732 ms 707 ms 719 ms lag26.fr4.lga.llnw.net [68.142.88.149]
8 652 ms 670 ms 691 ms ve5.fr3.lga.llnw.net [69.28.172.205]
9 * * * Request timed out.
10 696 ms 719 ms 732 ms 0.xe-1-0-0.bbr1.ewr1.packet.net [198.16.4.94]
11 1816 ms 687 ms 679 ms 0.ae12.dsr2.ewr1.packet.net [198.16.4.89]
12 666 ms 681 ms 713 ms 147.75.98.15
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
20 * * * Request timed out.
Trace complete.
C:\Users\David>tracert 147.75.202.151Last I knew, my gateway was in Idaho. But lately most websites seem to think I'm in Texas, so that may have changed; I'm not sure.
Tracing route to pub.sjc.kernel.org [147.75.202.151]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.1.1
2 643 ms 637 ms 639 ms 10.75.13.224
3 632 ms 637 ms 639 ms 10.75.10.26
4 671 ms 681 ms 688 ms 10.95.240.161
5 680 ms 684 ms 1680 ms six1.llnw.net [206.81.80.99]
6 637 ms 672 ms 670 ms lag20.fr3.sjc.llnw.net [68.142.88.44]
7 673 ms 649 ms 666 ms 68.142.89.99
8 646 ms 636 ms 639 ms 0.ae0.bbr2.sjc1.packet.net [147.75.200.65]
9 * * * Request timed out.
10 693 ms 680 ms 662 ms 147.75.200.61
11 642 ms 640 ms 637 ms pub.sjc.kernel.org [147.75.202.151]
Trace complete.
(Edited)
What DNS server is being reported when you do a lookup? (i.e. post the result of "Nslookup www.kernel.org")
If it's not Exede's servers, I would try manually plugging that in on the machine your using to test. One thing that can cause hiccups is if the router has some DNS caching built it, it can keep stale results and cause problems and also third party DNS results may also be causing an issue.
For reference, the Exede's DNS servers are 99.196.99.99 & 99.197.99.99.
If it's not Exede's servers, I would try manually plugging that in on the machine your using to test. One thing that can cause hiccups is if the router has some DNS caching built it, it can keep stale results and cause problems and also third party DNS results may also be causing an issue.
For reference, the Exede's DNS servers are 99.196.99.99 & 99.197.99.99.
I haven't customized my DNS settings at all. You can't use third-party DNS servers with Exede anyway without going through something like DNScrypt, but then you lose the benefits of AcceleNet.
Out of curiosity, if you put https://147.75.202.151/ in your browser? You'll get a cert issue because you're not using the domain, but I'm curious if you actually get the kernel archives since the trace route comes though.
David Brown
TheName141 .
xode0000, Champion
Bev, Champion
Joshua
I am using Exede's WiFi modem / router combo and what solved it for me was to ensure that my local network was on the 192.168.1.0/24 subnet. It apparently is a bug in there modem firmware.