dslreports logo
site
 
    All Forums Hot Topics Gallery
spc

spacer




how-to block ads


Search Topic:
uniqs
1284
share rss forum feed

DrStrangLov

join:2012-03-28
kudos:1

[Exede] Back in the Slow Lane

I turned off Exede's modem for two days, and received a different IP address.

WB-1: 163

I was using one of the 75.106.62.xxx addresses,

now I'm using 184.20.92.xxx

The "75.106.62.xxx" addresses were originally with WB-1 users...and the other with Exede-5/12 users.

When using the "75" address, it worked fine, now coming back to "184" its a "stop, wait, wait, go" process to access pages.

Here's what Google's gmail shows

DrStrangLov

join:2012-03-28
kudos:1
Back on "75" address format...have to wait-n-see about speed issue, which may have been related to students back in school, doing their "Internet Homework"

I flashed DD-WRT into the ASUS RT_N10+ router I use to rule out an issue with ASUS's QOS, if any.

Upload Speed tests look OK for Exede-5, from 4:23 PM to 8:28 PM

1.67 Mbps
765 Kbps
1.26 Mbps


Exede Zac

join:2013-03-06
Davenport, IA
kudos:1
reply to DrStrangLov
Please let us know if this issue becomes a continuing occurance. We want to know about this so we can help out! Thank you.
--
Exede Zac
Exede Internet Social Media Escalations

DrStrangLov

join:2012-03-28
kudos:1
Back on 12-17-2012, I reported that this Exede router-pathway using 10.74.255.249 created issues, for myself, and another person.

I'm hooked direct to desktop computer, and here's a 10 PM CDT tracert to DNS server:

C:\>tracert 184.63.64.xxx

Tracing route to 184.63.64.xxx over a maximum of 30 hops

1 * * * Request timed out.
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * 2332 ms 620 ms 184.63.64.xxx

Trace complete.

I have no idea how long I've been using 10.74.255.249 pathway...but my gut feeling its a DNS issue...I had to use Opera to post this.

Sometimes, loading a web page takes a long, long time...and sometimes, it don't load.
Gmail stalled out, for instance.

Here's a trace to Wildblueworld

C:\>tracert 204.10.141.160

Tracing route to server.wildblueworld.com [204.10.141.160]
over a maximum of 30 hops:
  1     *        *        *     Request timed out.
  2   758 ms   725 ms   718 ms  10.74.101.1
  3   750 ms   720 ms   757 ms  10.74.10.2
  4   721 ms   737 ms   719 ms  10.74.255.249
  5   741 ms   804 ms   761 ms  xe-5-2-1.bar1.Phoenix1.Level3.net [4.28.80.129]
 
  6   798 ms   789 ms   810 ms  OMNIS-NETWO.bar1.Phoenix1.Level3.net [4.28.81.17
8]
  7     *        *        *     Request timed out.
  
 
etc/etc/etc...
 
30     *        *        *     Request timed out.
 
Trace complete.

I have FireFox (Waterfox) configured to not store DNS address info...so, if DNS server/etc is not working...stuff happens, as in wait/wait/stall/nothing.

DrStrangLov

join:2012-03-28
kudos:1
reply to Exede Zac
I re-connected to router and got IP address flipped from "75.106.61.xxx" to "184.63.212.xxx"

Interesting, tracert to same DNS server is different in number of hops:

Via "184.63.212.xxx"

C:\>tracert 184.63.64.xxx

Tracing route to 184.63.64.xxx over a maximum of 30 hops
  1    <1 ms    <1 ms     1 ms  DD-WRT [192.168.1.1]
  2     *        *        *     Request timed out.  (SB-2 Modem)
  3   654 ms   635 ms   640 ms  10.74.101.1
  4   630 ms   657 ms   673 ms  10.74.10.2
  5   643 ms   640 ms   633 ms  184.63.64.xxxx
 
Trace complete.

On tracert using 75.106.61.xxx, there were six hops (previous post), instead of three.

Still using "10.74.255.249" pathway on further out traces:

C:\>tracert 24.25.224.142

Tracing route to 24.25.224.142 over a maximum of 30 hops

  1    <1 ms    <1 ms     1 ms  DD-WRT [192.168.1.1]
  2     *        *        *     Request timed out. (SB-2 Modem)
  3   671 ms   635 ms   638 ms  10.74.101.1
  4   658 ms   639 ms   639 ms  10.74.10.2
  5   650 ms   639 ms   640 ms  10.74.255.249
  6   676 ms   670 ms   678 ms  xe-5-2-1.bar1.Phoenix1.Level3.net [4.28.80.129]
 
  7   687 ms   680 ms   689 ms  ae-0-11.bar2.Phoenix1.Level3.net [4.69.148.114]
 
  8   672 ms   678 ms   681 ms  ae-4-4.ebr2.LosAngeles1.Level3.net [4.69.133.38]
 
  9   671 ms   680 ms   688 ms  ae-82-82.csw3.LosAngeles1.Level3.net [4.69.137.2
6]
 10   679 ms   679 ms   679 ms  ae-3-80.edge1.LosAngeles6.Level3.net [4.69.144.1
44]
 11   657 ms   680 ms   678 ms  66.109.9.121
 12   684 ms   679 ms   672 ms  107.14.19.66
 
etc/etc...
 
 

DrStrangLov

join:2012-03-28
kudos:1
reply to DrStrangLov
Hence, why did it take three additional hops to reach DNS server on "75" IP address.


Exede Zac

join:2013-03-06
Davenport, IA
kudos:1
said by DrStrangLov:

Hence, why did it take three additional hops to reach DNS server on "75" IP address.

That's a good question. I don't have any information regarding this. I do know with Exede using a "Dynamic IP" setup, the IP address changes frequently.

I would contact our Technical Team about this to see if they can provide any other insight or communication about how this works. They should be able to work. You can reach them at 866-945-3258 option 2. Thanks.
--
Exede Zac
Exede Internet Social Media Escalations

DrStrangLov

join:2012-03-28
kudos:1
said by Exede Zac:

That's a good question....I would contact our Technical Team

I'm using the "184.63.212.xxx" IP address currently...without an issue. It's a three hop path to the DNS server, and it works fine.

When I was using the 75.106.61.220 IP address, there were six hops instead of three to DNS server; and I had stall outs/etc. Download/Upload speed was not the issue, once I was connected to a site.

My Guess:

1. Some router on the six hop route to DNS server was dropping these DNS lookup packets.

The FireFox (Waterfox) browser I use is configured to not save previously seen sites' IP addresses...so, when Waterfox is reopened, it must get these sites' IP addresses.

If it happens again, I'll just try to acquire another IP address, which has three hops to DNS server.

Just pass this information along to them...thanks