250ms...I wish! I get 700-1000ms pings after 6pm on weekdays...try living with that! As a matter of fact...the DSL people are on their way here today...there goes another @home client. May they burn.:)
C'mon, the only real reason @home uses DHCP is that it's easier than assigning static IPs for them. It makes their lives easier so that their users have to suffer. Personally, I'd rather have a static IP. If it means I have to setup a firewall to keep the script kiddies away, so be it, but I'd rather have a static IP. I'm not sure how pppoe works, but dhcp will attempt to regain the same IP, so if the users' computer is powered on 99% of the time, then the chances are it'll have the same IP.
Oh and on an off-topic note, @home service varies so much by area, do some research before you invest $50/mo of your hard earned money. I currently have comcast @home in the sacramento area, and the latencies are horrible. Speeds are starting to suffer now as well. After 2 months of back and forths with the @home "technical support", there is still no resolution. Obviously they've TOTALLY maxed out a pipe and/or hub and are refusing to fix it, saying "we're investigating any malfunction in our hardware". Yeah right, it takes 2 months to diagnose poor performance on a traceroute *I* gave them? Like I said, TOTAL joke. Only a couple of more days until DSL is installed, and I can put the nightmare that is @home behind me.
We're not too far from laser wrist watches =)
on
Watch Camera
·
· Score: 1
Yeah, saw one of these in Nordstrom...pretty cool idea, but still too pricey for just a toy. I'll wait for cheap versions with a color display, thank you very much.
Slashdot Mirror
250ms...I wish! I get 700-1000ms pings after 6pm on weekdays...try living with that! As a matter of fact...the DSL people are on their way here today...there goes another @home client. May they burn. :)
C'mon, the only real reason @home uses DHCP is that it's easier than assigning static IPs for them. It makes their lives easier so that their users have to suffer. Personally, I'd rather have a static IP. If it means I have to setup a firewall to keep the script kiddies away, so be it, but I'd rather have a static IP. I'm not sure how pppoe works, but dhcp will attempt to regain the same IP, so if the users' computer is powered on 99% of the time, then the chances are it'll have the same IP.
Oh and on an off-topic note, @home service varies so much by area, do some research before you invest $50/mo of your hard earned money. I currently have comcast @home in the sacramento area, and the latencies are horrible. Speeds are starting to suffer now as well. After 2 months of back and forths with the @home "technical support", there is still no resolution. Obviously they've TOTALLY maxed out a pipe and/or hub and are refusing to fix it, saying "we're investigating any malfunction in our hardware". Yeah right, it takes 2 months to diagnose poor performance on a traceroute *I* gave them? Like I said, TOTAL joke. Only a couple of more days until DSL is installed, and I can put the nightmare that is @home behind me.
Yeah, saw one of these in Nordstrom...pretty cool idea, but still too pricey for just a toy. I'll wait for cheap versions with a color display, thank you very much.
I just hope this stuff isn't a relative of the green stuff from the meteor in "Creep Show". :)