If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.
The 100 Mb/s Ethernet connection between the NIC and cable modem doesn't seem to help with the 3 Mb/s cap Cox sets on the downstream. And it sure doesn't help with the measly little 256 kb/s upstream.
Originally posted by Jon P. Inghram The 100 Mb/s Ethernet connection between the NIC and cable modem doesn't seem to help with the 3 Mb/s cap Cox sets on the downstream. And it sure doesn't help with the measly little 256 kb/s upstream.
I've got 128 up, and with PPPoE that's more like 100 up, if I'm lucky.
Gigabyte P35-DS3L with a Q6600, 2GB Kingston HyperX (after *3* bad pairs of Crucial Ballistix 1066), Galaxy 8800GT 512MB, SB X-Fi, some drives, and a Dell 2005fpw. Running WinXP.
Maybe nothing now that so many home broadband routers support it in firmware.
But my Dad has it in software and it SUCKS.
Frequent disconections, unexplained slowdowns and just general badness.
chuck
Originally posted by LvR PPPOE bad?.................... why?
Am I just lucky here then?
Running a 512 down 256 up DSL link based on PPPOE and see those figure in practice via my Alcatel "FROG" Speedtouch USB ADSL modem.
Yes, you may see those numbers, but PPPoE is a crappy little wrapper. Whatever bandwidth it says you're getting, you can reduce that by about 20%, because that's the bloat that PPPoE is adding.
Go to DSLreports or somewhere. Their bandwidth test even shows the graph in two sections - total, and effective (after PPPoE is accounted for).
Gigabyte P35-DS3L with a Q6600, 2GB Kingston HyperX (after *3* bad pairs of Crucial Ballistix 1066), Galaxy 8800GT 512MB, SB X-Fi, some drives, and a Dell 2005fpw. Running WinXP.
Comment