A little feedback, please.....
#46
Well, I've been shut out for about 24 hours (somewhere in there), and my traceroute times out after my ISP gateway (they may have traceroute blocked, they block enough Other things ~ like port 25 *grubmbles*).
This is my first posting though, so I have no clue (yet) how fast everything reacts. I'll edit in just a second to note that.
----------EDIT--------
No real noticable change in speed... maybe a hair faster. BUT this could also be on my end.. my DSL companies idea of 'stable' is anything from 36 to 766kbps (yes, I get less than dial-up speeds on my $60/month DSL ~ the joys of living in BFE.)
This is my first posting though, so I have no clue (yet) how fast everything reacts. I'll edit in just a second to note that.
----------EDIT--------
No real noticable change in speed... maybe a hair faster. BUT this could also be on my end.. my DSL companies idea of 'stable' is anything from 36 to 766kbps (yes, I get less than dial-up speeds on my $60/month DSL ~ the joys of living in BFE.)
#47
Banned
Thread Starter
Hi Brian,
Unlike most folks - you are still coming in off the old circuit. After your ISPs' DNS servers refresh, you'll be in the new circuits...
Unlike most folks - you are still coming in off the old circuit. After your ISPs' DNS servers refresh, you'll be in the new circuits...
#49
Banned
Thread Starter
Hey Graham....
Well - welcome to the new circuits..! The reason they were off is that until this post, you were coming in from the old circuits - which my ISP can't hold the connectivity on... To see what I mean, look at your old tracert - and it have forums.rennlist.com [ 64.205.178.78 ] If you run it again - you'll see your DNS is now pulling the new IP from the third ISP I have and their circuits: "forums.rennlist.com [ 66.211.135.78 ], and the tracert will change substaintially, esp in the routing tables to that IP block...
Best to you!
John
Well - welcome to the new circuits..! The reason they were off is that until this post, you were coming in from the old circuits - which my ISP can't hold the connectivity on... To see what I mean, look at your old tracert - and it have forums.rennlist.com [ 64.205.178.78 ] If you run it again - you'll see your DNS is now pulling the new IP from the third ISP I have and their circuits: "forums.rennlist.com [ 66.211.135.78 ], and the tracert will change substaintially, esp in the routing tables to that IP block...
Best to you!
John
#51
Addict
Rennlist Member
Rennlist Member
tracert forums.rennlist.com
Tracing route to forums.rennlist.com [66.211.135.78]
over a maximum of 30 hops:
1 1 ms 1 ms 2 ms air.setup [192.168.0.1]
2 2 ms 5 ms 2 ms 157.252.160.1
3 2 ms 2 ms 2 ms bissell.rtr.trincoll.edu [157.252.0.1]
4 * * * Request timed out.
-----------------------------
When I'm not getting that 403 Forbidden error, it's pretty quick!
Sam
Tracing route to forums.rennlist.com [66.211.135.78]
over a maximum of 30 hops:
1 1 ms 1 ms 2 ms air.setup [192.168.0.1]
2 2 ms 5 ms 2 ms 157.252.160.1
3 2 ms 2 ms 2 ms bissell.rtr.trincoll.edu [157.252.0.1]
4 * * * Request timed out.
-----------------------------
When I'm not getting that 403 Forbidden error, it's pretty quick!
Sam
#53
Three Wheelin'
Join Date: Jul 2001
Location: Reading PA
Posts: 1,667
Likes: 0
Received 0 Likes
on
0 Posts
Rennlist seems a little faster for me today then it has been. I have DSL from Verizon. I ran a tracert although I have no clue what it means I figured it might help you out some.
#54
Hi John,
I'm on a T-1 just outside Newark, Delaware. Forums were intermittent at best Friday and Saturday morning. Much better last night, and all's fine today. Thanks for the quick response!
dale
still searching ...
I'm on a T-1 just outside Newark, Delaware. Forums were intermittent at best Friday and Saturday morning. Much better last night, and all's fine today. Thanks for the quick response!
dale
still searching ...
#55
Banned
Thread Starter
Thanks a million folks...!!!!
OK - I think I'm set back here.. Most of you are on in the new circuits which peak at 4.6Mbps and sustain over 3.9Mbps. (By comparision - the old ones were about 3-4x slower) for just this block of IPs. As well - I'm still pulling other sites off on of the old carrier circuits (which I'll keep for an automatic failover), but - for the Forums - I think we are now all set...!!! I'll try to keep any updates/changes to this server/proxy/firewall to a minimum over the next days....
I just want to say THANK YOU!!! to all of your for your patience, support and feedback. It's more appreciated than many may realize..
Also Tom - that is a GREAT SHOT of the tracert output! I'm amazed at the response time of the hops as it comes into the backbone, then upline into the CO I tap into.... If you look at yours, and Grahams's from earlier - you'll see some distinct speed differences.. My thanks for posting that, as it's quite informative....
My thanks - and best to all.....
John
OK - I think I'm set back here.. Most of you are on in the new circuits which peak at 4.6Mbps and sustain over 3.9Mbps. (By comparision - the old ones were about 3-4x slower) for just this block of IPs. As well - I'm still pulling other sites off on of the old carrier circuits (which I'll keep for an automatic failover), but - for the Forums - I think we are now all set...!!! I'll try to keep any updates/changes to this server/proxy/firewall to a minimum over the next days....
I just want to say THANK YOU!!! to all of your for your patience, support and feedback. It's more appreciated than many may realize..
Also Tom - that is a GREAT SHOT of the tracert output! I'm amazed at the response time of the hops as it comes into the backbone, then upline into the CO I tap into.... If you look at yours, and Grahams's from earlier - you'll see some distinct speed differences.. My thanks for posting that, as it's quite informative....
My thanks - and best to all.....
John