Fireblade
join:2008-08-27
St Catharines, ON
 ·Cogeco Cable
 ·Vonage
| reply to urbanriot
Re: Pre-sign up questions
said by urbanriot  :Custom firmware? I was using DD-WRT mini on a Linksys WRT54G 2.1 until I got sick of a) various bugs and b) lousy performance during intense bandwidth periods. Since replacing it with a VM'd FreeBSD pf router / firewall I haven't looked back. Nope, not custom firmware just poorly designed garbage that cannot be downgraded.
DIR655 has over 4 revisions, each revision has something major done to it and I think Rev. A4 has a different CPU and D-Link designs firmware around the newest revision and really doesn't do that much testing on older versions. If 1.31 was downgradeable, we wouldn't be having this discussion because it would go back to perfectly stable 1.11B.
--
I love fish sticks. I love putting fish sticks in my mouth. |
|
urbanriot
join:2004-10-18
St Catharines, ON | reply to Fireblade
Custom firmware? I was using DD-WRT mini on a Linksys WRT54G 2.1 until I got sick of a) various bugs and b) lousy performance during intense bandwidth periods. Since replacing it with a VM'd FreeBSD pf router / firewall I haven't looked back. |
|
Fireblade
join:2008-08-27
St Catharines, ON
·Cogeco Cable
·Vonage
1 edit | reply to urbanriot
said by urbanriot :said by Fireblade :I've also noticed a slight degrade in quality over the month but it could be because my router is acting up, I haven't really gone after the issue. Could you be more specific? I'd be happy to entertain any diagnostics on my end that might isolate a Cogeco-wide issue. It's back, was completely fine yesterday. Going to do a direct modem connection to rule out the router.
EDIT: Just as I thought, router is the culprit.
--
I love fish sticks. I love putting fish sticks in my mouth. |
|
Asawulf
Ignorance is bliss
VIP
join:2005-08-17
Trois-Rivieres, QC
| reply to ariesmk
Re: Pre-sign up questions
said by ariesmk :I was wondering if Cogeco offers pre-purchased bandwidth blocks similar to TekSavvy or Bell(correct me if I'm wrong on this one), or if they have any plans to do so in the future. -Andrew No we don't and no plan that I know of to do it |
|
ariesmk
join:2009-07-03
| reply to ariesmk
Thanks for all the input guys. I was kinda sorry to see Gixxers posts removed, as I wasnt able to review his trace routes  . I also have another question if you dont mind. I was wondering if Cogeco offers pre-purchased bandwidth blocks similar to TekSavvy or Bell(correct me if I'm wrong on this one), or if they have any plans to do so in the future.
-Andrew |
|
Fireblade
join:2008-08-27
St Catharines, ON
·Cogeco Cable
·Vonage
| reply to urbanriot
Slow browsing on some websites, but once they load they seem to be decent for a few minutes. I'll see a blank screen for a few seconds and then the page will load, it's usually instant, loads in ms'. It was a terrible combination with Firefox 3.5, it seemed to really amplify the problem.
Usenet fluctuation between .600-1.1 MB/Sec, doesn't happen every time.
It's not happening right now at all, I get great browsing and usenet speed. The fact that it isn't constant, kind of points the blame slightly more towards Cogeco - but because it feels to me like a DNS issue, something my routers firmware screwed up last month or so point the blame right back at the router. Like I said, there is zero indication that it's occurring now.
--
I love fish sticks. I love putting fish sticks in my mouth. |
|
urbanriot
join:2004-10-18
St Catharines, ON
·Cogeco Cable
| reply to Fireblade
said by Fireblade :I've also noticed a slight degrade in quality over the month but it could be because my router is acting up, I haven't really gone after the issue. Could you be more specific? I'd be happy to entertain any diagnostics on my end that might isolate a Cogeco-wide issue. |
|
Fireblade
join:2008-08-27
St Catharines, ON | reply to chdude3
I've also noticed a slight degrade in quality over the month but it could be because my router is acting up, I haven't really gone after the issue.
--
I love fish sticks. I love putting fish sticks in my mouth. |
|
chdude3
join:2003-07-29
Oakville, ON
·Cogeco Cable
·Cogeco Voip
| reply to urbanriot
said by urbanriot :Sounds like you're blowing your own horn, because I'm able to pop my emails and access self care. Both were accessible yesterday, as I helped someone else set up both. No complaints from anyone today, and I'm sure we would have heard if it was more than just you. Maybe it was just me or a short local issue, but it doesn't change the fact that I'm noticing a decrease in the quality of Cogeco's service in the face of UBB and price increases. For what Cogeco charges for internet, it is terrible value. |
|
Fireblade
join:2008-08-27
St Catharines, ON
·Cogeco Cable
·Vonage
| reply to exseven
said by exseven :said by exseven :? i was just saying cogeco uses peer1 as well, among others And thats a good thing, looks like TekSavvy only uses peer1 (and maybe torix), but houses their equipment in one place for a single point of failure » TekSavvy Down (EDIT: Now back online) Small risk, it happens, Cogeco doesn't have a perfect track record itself. All of their equipment was fine, the fire was started by a UPS. At least when DSL goes down, you can use a different login from another company.
--
I love fish sticks. I love putting fish sticks in my mouth. |
|
urbanriot
join:2004-10-18
St Catharines, ON
·Cogeco Cable
| reply to chdude3
said by chdude3 :Well my internet service is up, but I can't seem to get to Cogeco's POP servers or their selfcare site (I need to pay the piper). As of late, Cogeco doesn't have a lot to trumpet about uptime or great service. Sounds like you're blowing your own horn, because I'm able to pop my emails and access self care. Both were accessible yesterday, as I helped someone else set up both. No complaints from anyone today, and I'm sure we would have heard if it was more than just you. |
|
exseven
Premium,VIP
join:2003-05-23
Beamsville, ON | reply to chdude3
maybe its just you
$ telnet pop.cogeco.net 110
Trying 216.221.81.110...
Connected to pop.cogeco.net.
Escape character is '^]'.
+OK rpopd fep9 POP3 server ready |
|
chdude3
join:2003-07-29
Oakville, ON
·Cogeco Cable
·Cogeco Voip
| reply to exseven
said by exseven :said by exseven :? i was just saying cogeco uses peer1 as well, among others And thats a good thing, looks like TekSavvy only uses peer1 (and maybe torix), but houses their equipment in one place for a single point of failure » TekSavvy Down (EDIT: Now back online) Well my internet service is up, but I can't seem to get to Cogeco's POP servers or their selfcare site (I need to pay the piper). As of late, Cogeco doesn't have a lot to trumpet about uptime or great service. |
|
exseven
Premium,VIP
join:2003-05-23
Beamsville, ON
2 edits | reply to exseven
said by exseven :? i was just saying cogeco uses peer1 as well, among others And thats a good thing, looks like TekSavvy only uses peer1 (and maybe torix), but houses their equipment in one place for a single point of failure
»TekSavvy Down (EDIT: Now back online) |
|
HoboJ
join:2008-03-27
Trenton, ON
 ·TekSavvy Solutions..
·voip.ms
·Cogeco Cable
| reply to ariesmk
said by ariesmk :69.65.3.27 (Chicago) 8.9.9.105 (Chicago) 8.2.121.204 (New york) 31ms
51ms
43ms |
|
Seve
join:2003-12-25
Waterdown, ON
| reply to ariesmk
$ ping -c5 69.65.3.27
PING 69.65.3.27 (69.65.3.27) 56(84) bytes of data.
64 bytes from 69.65.3.27: icmp_seq=1 ttl=117 time=23.3 ms
64 bytes from 69.65.3.27: icmp_seq=2 ttl=117 time=21.2 ms
64 bytes from 69.65.3.27: icmp_seq=3 ttl=117 time=22.1 ms
64 bytes from 69.65.3.27: icmp_seq=4 ttl=117 time=20.8 ms
64 bytes from 69.65.3.27: icmp_seq=5 ttl=117 time=22.2 ms
--- 69.65.3.27 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4028ms
rtt min/avg/max/mdev = 20.815/21.975/23.379/0.905 ms
$ ping -c5 8.9.9.105
PING 8.9.9.105 (8.9.9.105) 56(84) bytes of data.
64 bytes from 8.9.9.105: icmp_seq=1 ttl=54 time=43.2 ms
64 bytes from 8.9.9.105: icmp_seq=2 ttl=54 time=43.5 ms
64 bytes from 8.9.9.105: icmp_seq=3 ttl=54 time=43.8 ms
64 bytes from 8.9.9.105: icmp_seq=4 ttl=54 time=41.9 ms
64 bytes from 8.9.9.105: icmp_seq=5 ttl=54 time=41.9 ms
--- 8.9.9.105 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4048ms
rtt min/avg/max/mdev = 41.900/42.907/43.843/0.835 ms
$ ping -c5 8.2.121.204
PING 8.2.121.204 (8.2.121.204) 56(84) bytes of data.
64 bytes from 8.2.121.204: icmp_seq=1 ttl=52 time=35.0 ms
64 bytes from 8.2.121.204: icmp_seq=2 ttl=52 time=35.7 ms
64 bytes from 8.2.121.204: icmp_seq=3 ttl=52 time=35.3 ms
64 bytes from 8.2.121.204: icmp_seq=4 ttl=52 time=34.9 ms
64 bytes from 8.2.121.204: icmp_seq=5 ttl=52 time=34.5 ms
--- 8.2.121.204 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4040ms
rtt min/avg/max/mdev = 34.597/35.117/35.719/0.449 ms
$ traceroute 69.65.3.27
traceroute to 69.65.3.27 (69.65.3.27), 30 hops max, 60 byte packets
1 192.168.0.1 (192.168.0.1) 0.365 ms 0.326 ms 0.308 ms
2 10.85.64.1 (10.85.64.1) 7.284 ms 11.090 ms 11.333 ms
3 d226-9-133.home.cgocable.net (24.226.9.133) 11.895 ms 12.813 ms 13.076 ms
4 105-0-226-24.cgocable.net (24.226.0.105) 14.115 ms 14.365 ms 14.634 ms
5 qix-tor-gw.peer1.net (69.28.230.245) 13.479 ms 13.747 ms 16.337 ms
6 10ge.xe-0-0-0.tor-1yg-cor-1.peer1.net (216.187.114.133) 17.093 ms 9.509 ms 12.600 ms
7 oc48-po5-0.chi-eqx-dis-1.peer1.net (216.187.114.141) 21.968 ms 20.245 ms 24.322 ms
8 mpr1.ord7.us (206.223.119.86) 24.583 ms 25.330 ms 26.045 ms
9 ge-2-1-0.mpr1.ord2.above.net (64.125.26.249) 28.575 ms 29.406 ms 29.668 ms
10 ge-1-0-0.mpr1.ord2.us.above.net (64.125.26.185) 28.206 ms 28.750 ms 28.988 ms
11 ge0.0013.core2.ord.servernap.com (209.249.88.118) 27.571 ms 27.822 ms 19.922 ms
12 pos2-1.csr1.Chi3.Servernap.net (69.39.239.170) 26.224 ms 26.456 ms 21.728 ms
13 69.65.3.27 (69.65.3.27) 26.297 ms 26.707 ms 21.638 ms
$ traceroute 8.9.9.105
traceroute to 8.9.9.105 (8.9.9.105), 30 hops max, 60 byte packets
1 192.168.0.1 (192.168.0.1) 0.351 ms 0.323 ms 0.317 ms
2 10.85.64.1 (10.85.64.1) 9.330 ms 15.717 ms 15.982 ms
3 d226-9-133.home.cgocable.net (24.226.9.133) 16.249 ms 16.507 ms 16.774 ms
4 105-0-226-24.cgocable.net (24.226.0.105) 17.889 ms 18.149 ms 18.408 ms
5 xe-3-1-0-107.tor11.ip4.tinet.net (77.67.69.241) 16.977 ms 17.233 ms 17.494 ms
6 xe-1-0-0.nyc20.ip4.tinet.net (89.149.185.45) 49.727 ms xe-2-0-0.nyc20.ip4.tinet.net (89.149.185.82) 23.074 ms 22.146 ms
7 213.200.73.118 (213.200.73.118) 26.370 ms 26.629 ms 26.892 ms
8 xe-4-2-0.cr1.ord1.us.nlayer.net (69.22.142.85) 48.425 ms 48.676 ms 48.949 ms
9 tge6-4.ar1.ord1.us.nlayer.net (69.31.111.134) 49.211 ms 49.479 ms 49.734 ms
10 as20473.tge8-2-1605.ar1.ord1.us.nlayer.net (69.31.111.54) 49.984 ms 52.801 ms 53.064 ms
11 8.9.9.105 (8.9.9.105) 51.936 ms 43.569 ms 46.510 ms
$ traceroute 8.2.121.204
traceroute to 8.2.121.204 (8.2.121.204), 30 hops max, 60 byte packets
1 192.168.0.1 (192.168.0.1) 0.346 ms 0.318 ms 0.412 ms
2 10.85.64.1 (10.85.64.1) 9.632 ms 15.116 ms 14.814 ms
3 d226-8-233.home.cgocable.net (24.226.8.233) 15.362 ms 15.619 ms 15.886 ms
4 113-0-226-24.cgocable.net (24.226.0.113) 18.135 ms 18.389 ms 18.645 ms
5 xe-3-1-0-107.tor11.ip4.tinet.net (77.67.69.241) 17.208 ms 17.480 ms 17.736 ms
6 xe-8-3-0.nyc30.ip4.tinet.net (89.149.185.122) 41.096 ms 33.386 ms 34.389 ms
7 choopa-gw.ip4.tinet.net (77.67.68.142) 47.784 ms 48.057 ms 48.404 ms
8 (66.55.128.66) 44.243 ms (66.55.128.34) 40.458 ms 41.704 ms
9 8.2.121.204 (8.2.121.204) 41.964 ms 42.265 ms 43.292 ms |
|
exseven
Premium,VIP
join:2003-05-23
Beamsville, ON | reply to chdude3
?
i was just saying cogeco uses peer1 as well, among others |
|
chdude3
join:2003-07-29
Oakville, ON
·Cogeco Cable
·Cogeco Voip
| reply to exseven
said by exseven :said by Fireblade :Oh wait, didn't you know Tek Savvy's 200GB plan uses peer1 peering for excellent latency? just wanted to point this out... 3 * 9 ms 9 ms 26-0-226-24.cgocable.net [24.226.0.26] 4 9 ms 8 ms 9 ms qix-tor-gw.peer1.net [69.28.230.245] 5 9 ms 9 ms 12 ms 10ge.xe-0-0-0.tor-1yg-cor-1.peer1.net [216.187.1 14.133] WOW... how much is that plan?? |
|
