@GabeU I'm not. Is it recommended one way or the other? I've been tossing around the idea just to increase WiFi range and have some more options. But something I haven't looked much into is if there's a setting on the HT2000W to allow total passthrough and not apply any settings.
It's really entirely up to the user. Some people choose to use 3rd party routers for the additional options it can give them, depending on the model, of course, or the increased range, again being dependant on the model. Others are fine with the HT2000W's built in WiFi. It's really a "to each his/her own" type thing. I prefer the built in WiFi due to having a small house and not really needing the additional options a separate router might afford.
When people use a 3rd party router the WiFi in the HT2000W is manually disabled so as to not have the two sources interfering with each other, and pretty much all of the WiFi related aspects are then controlled by the router and however you set it up. There would still be a few things that could only be controlled by the HT2000W modem, similar to any other ISP's modem with which you would connect a router.
I was primarily asking about a router to make sure one way or the other, as if you were using a router it would be another unit whose DNS cache would have have to be cleared.
Lastly, for those experiencing range issues in a specific area of their home, HughesNet does offer a WiFi booster that works with the HT2000W modem and which extends the range in a particular direction, but for a general range increase, and the better options it offers, I would always recommend a 3rd party router.
Just an update. Changing the DNS server on both computer and router did not help. Disabling IPv6 did nothing as well.
I had a weird side effect from one of those methods or the combination in which my school's online homework system (Canvas) was being flagged as a privacy risk. Switching everything back to default fixed it. Kind of random.
Anyways. Still looking for possible solutions. Seems that github follows the trends of peak times. Works slowly during off-peak hours but not at all during peak hours.
I'm having the same exact problem and nothing I've tried has resolved it. The weird thing is, it does work sometimes, randomly.
This is severely impacting my ability to work on projects, being as I have no other options for Internet access without driving some distance.
The internet is severely overloaded nationwide due to the current crisis, and we're all seeing the effects, which are more noticeable in systems with less capacity. It may be a long time before it goes back to normal.
jackwilliambell wrote:I'm having the same exact problem and nothing I've tried has resolved it. The weird thing is, it does work sometimes, randomly.
This is severely impacting my ability to work on projects, being as I have no other options for Internet access without driving some distance.
In the case of my issue, it's been going on for the last year and a half or so. Nothing new with everything going on.
Yeah nothing here worked either. Some of the methods killed my connection to certain school services too.
There's a problem accessing Github, mostly git-remote-https (updating homebrew on a Mac) before 8am. I've noticed this myself for several months and it always seems to clear up around 7.30ish - 8am ET.
Someone's been pounding it daily for hours upon hours during the east coast bonus time. That's the best I can figure what is happening.
There's also been malicious probing for /.git all over the internet (mostly from AmazonAWS), so this could be something to do with that as well.
[Previous post was rejected without explanation, maybe automatic rejection due to links to specific github sites even though they are relevant to this problem? I've removed the links and spelled out site names]
The problem appears specific to github and hughesnet. Other sites are working fine for me via hughesnet (e.g., gmail). Github works fine for me via DSL.
Communciations with github via hughesnet is not working reliably for me, often the browser times-out just loading a repository page.
Ping and tracert show github dot com is reachable via hughesnet, however.
I have accessed github dot com through DSL, and github dot com works fine for me through the DSL, so github dot com servers are responding.
I have accessed github dot com from DSL in different locations, so I don't think anything about github dot com is specific to route or ip address.
Sometimes loading a github dot com page aborts with the error:
"The page you are trying to view cannot be shown because the authenticity of the received data could not be verified."
(Right now even help pages are not loading, though ping to help dot github dot com works)
When trying to clone a repository through hughesnet, I'm getting "fatal: TaskCanceledException encountered.". (The same command works through DSL.)
githubstatus dot com is currently reporting "All systems operational".
Github help (help dot github dot com, Getting started with Github, Troubleshooting slow downloads and connectivity problems) says they are not responsible for congestion outside of github, and links to github-debug dot com.
github-debug dot com is a web page with diagnostics for users to run, and reports diagnostics from their servers back to the client.
(Submitting the github contact form linked from github-debug failed when I tried through hughesnet. I did submit the contact form via DSL with the hughesnet data, but there has been no response, automated or otherwise, so I don't know if it was received.)
My results are something like the following (ip address and keys [elided], the [184....] is apparently my ip address).
I highlighted a couple errors that stood out to me in red.
Do these diagnostics help locate whether the problem is in equipment of github or hughesnet or someone in-between?
Command line diagnostic commands (from github-debug dot com)
git clone [https ://github dot com/github/debug-repo] debug-repo-http
Cloning into 'debug-repo-http'... remote: Enumerating objects: 1649, done. error: RPC failed; curl 56 OpenSSL SSL_read: Connection was reset, errno 10054 fatal: the remote end hung up unexpectedly fatal: protocol error: bad pack header
git clone [git at github dot com] :github/debug-repo debug-repo-ssh
Cloning into 'debug-repo-ssh'... The authenticity of host '[github dot com] (140.82 .114.4)' can't be established. RSA key fingerprint is SHA256:[nThb.......................................]. Are you sure you want to continue connecting (yes/no/[fingerprint])? no Host key verification failed. fatal: Could not read from remote repository.
ping -n 10 [github dot com]
Pinging github.com [140.82 .114.4] with 32 bytes of data: Reply from 140.82 .114.4: bytes=32 time=3241ms TTL=46 Reply from 140.82 .114.4: bytes=32 time=806ms TTL=46 Reply from 140.82 .114.4: bytes=32 time=638ms TTL=46 Reply from 140.82 .114.4: bytes=32 time=1187ms TTL=46 Reply from 140.82 .114.4: bytes=32 time=779ms TTL=46 Reply from 140.82 .114.4: bytes=32 time=669ms TTL=46 Reply from 140.82 .114.4: bytes=32 time=1163ms TTL=46 Reply from 140.82 .114.4: bytes=32 time=816ms TTL=46 Reply from 140.82 .114.4: bytes=32 time=676ms TTL=46 Reply from 140.82 .114.4: bytes=32 time=1247ms TTL=46 Ping statistics for 140.82 .114.4: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 638ms, Maximum = 3241ms, Average = 1122ms
tracert [github dot com]
Tracing route to [github dot com] [140.82 .114.4] over a maximum of 30 hops: 1 4 ms 1 ms 1 ms [192.........] 2 605 ms 635 ms 956 ms dpc6935198080_direcpc_com [69..........] 3 605 ms 794 ms 597 ms dpc6935196059_direcpc_com [69..........] 4 609 ms 828 ms 590 ms tyrmcbrc01-vln0115_ma_dl_suddenlink_net [66.76 .3.209] 5 602 ms 778 ms 623 ms 173-219-220-80_suddenlink_net [173.219 .220.80] 6 * * * Request timed out. 7 662 ms 1802 ms 777 ms ae2_cs1_dfw2_us_zip_zayo_com [64.125 .26.202] 8 656 ms 796 ms 659 ms ae5_cs1_iah1_us_eth_zayo_com [64.125 .28.98] 9 679 ms 775 ms 651 ms ae3_cs1_dca2_us_eth_zayo_com [64.125 .29.48] 10 * 1229 ms * ae8_cs3_iad93_us_eth_zayo_com [64.125 .25.99] 11 * * 687 ms ae1_ter1_iad10_us_zip_zayo_com [64.125 .25.137] 12 668 ms 786 ms 650 ms 209_66_120_181_IPYX-243981-004-ZYO_zip_zayo_com [209.66 .120.181] 13 * * * Request timed out. 14 * * * Request timed out. 15 * * * Request timed out. 16 679 ms 1006 ms 656 ms lb-140-82-114-4-iad_github_com [140.82 .114.4] Trace complete.
Web page diagnostics (on github-debug.com)
Error downloading Error downloading 2507998 bytes downloaded from [iad dot github-debug dot com] at 2.35 Mbps 2507998 bytes downloaded from [sea dot github-debug dot com] at 1.10 Mbps [184.........] [browser agent string] [733e............................] [7C16:....:....:....:........]
traceroute to [184.........] ([184.........]), 30 hops max, 60 byte packets 1 [fbe6............................] 0.261 ms 2 [ad4f............................] 0.190 ms 3 [8a71............................] 0.235 ms 4 [4539............................] 0.643 ms 5 [8ff2............................] 0.252 ms 6 [6721............................] 0.924 ms 7 [ae15_cr1-was1_ip4_gtt_net (69.174 .5.177) 26.450 ms 8 ash-bb2-link_telia_net (62.115 .143.120) 35.450 ms 9 ip4_gtt_net (69.174 .12.18) 33.258 ms 10 * 11 altice-ic-328598-dls-b21_c_telia_net (213.248 .88.95) 32.857 ms 12 utscswic01-vln111_ma_dl_suddenlink_net (66.76 .3.210) 48.511 ms 13 * 14 utscswic01-vln111_ma_dl_suddenlink_net (66.76 .3.210) 51.422 ms 15 dpc6935196057_direcpc_com (69.35 .196.57) 49.082 ms !N PING [184.........] ([184.........]) 56(84) bytes of data. From 69.35 .196.57 icmp_seq=1 Destination Net Unreachable From 69.35 .196.57 icmp_seq=2 Destination Net Unreachable --- [184.........] ping statistics --- 3 packets transmitted, 0 received, +2 errors, 100% packet loss, time 2002ms Start: Mon Mar 23 08:57:41 2020 HOST: [b741.....................] Loss% Snt Last Avg Best Wrst StDev 1.|-- [1eb1.....................] 0.0% 10 0.5 0.3 0.3 0.5 0.0 2.|-- [d8ab.....................] 0.0% 10 0.4 0.3 0.3 0.4 0.0 3.|-- [b20d.....................] 0.0% 10 0.4 0.4 0.3 0.6 0.0 4.|-- [2e48.....................] 0.0% 10 0.7 0.9 0.6 1.5 0.0 5.|-- [1ef1.....................] 0.0% 10 0.4 0.4 0.4 0.5 0.0 6.|-- [b1cb.....................] 0.0% 10 8.0 4.4 0.6 18.4 6.2 7.|-- et-6-0-1_er1_iad47_us_zip_zayo_com 0.0% 10 0.6 0.7 0.6 1.0 0.0 8.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0 9.|-- ae8_cs1_dca2_us_eth_zayo_com 0.0% 10 87.6 77.2 75.0 87.6 4.3 10.|-- ae3_cs1_iah1_us_eth_zayo_com 0.0% 10 75.2 76.2 75.0 86.0 3.4 11.|-- ae5_cs1_dfw2_us_eth_zayo_com 0.0% 10 75.6 76.1 75.5 77.1 0.3 12.|-- ae9_cs3_phx2_us_eth_zayo_com 0.0% 10 75.8 76.7 75.8 80.8 1.3 13.|-- ae17_mpr4_phx2_us_zip_zayo_com 0.0% 10 75.3 75.4 75.3 75.7 0.0 14.|-- 64_125_187_33_IPYX-249626-ZYO_zip_zayo_com 0.0% 10 75.5 75.6 75.4 75.8 0.0 15.|-- 173.219 .166.78 0.0% 10 75.6 75.4 75.1 75.6 0.0 16.|-- 173-219-233-251_suddenlink_net 0.0% 10 78.0 78.0 77.9 78.5 0.0 17.|-- 173-219-220-81_suddenlink_net 0.0% 10 74.2 74.1 73.9 74.2 0.0 18.|-- utscswic01-vln111_ma_dl_suddenlink_net 0.0% 10 73.8 73.8 73.6 73.9 0.0 19.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0 [.........184]_in-addr_arpa domain name pointer host[184......]_direcway_com.
Do these diagnostics help locate whether the problem is in equipment of hughesnet or github or someone inbetween?
I have also been having trouble communicating with github while other sites work fine.
Github has been responsive for me through other routes when it is unresponsive for me through hughesnet.
Usually the browser times out.
Occasionally it says "The page you are trying to view cannot be shown because the authenticity of the received data could not be verified."
Github has some bidirectional network diagnostics at github-debug dot com.
I can't tell if the problem is in equipment of github, hughesnet, or someone in between.
I tried to post a redacted message showing my results for you to compare, but it was flagged as spam.
Two errors that stood out to me were:
- The ssh git clone test also said "The authenticity of host '[github dot com]' (140...4) can't be established."
- A ping test from some github host to my ip address said "Destination Net Unreachable".