Thread: Beat the bell & rogers throttle....all things mlppp!
-
Feb 26th, 2009 07:33 PM
#751

Originally Posted by
murdoc2k
I've been put on fastpath now and my ping went down to 35ms
I noticed I've been throttled after 6pm so I bought an Asus WL-520GU router and just flashed it with Tomato firmware.
BT speeds so far are have not exceeded 28 kb/sec. Did I do something wrong?
make sure your using tomato MLPPP firmware and not regular tomato.
-
Feb 26th, 2009 07:42 PM
#752

Originally Posted by
infamouskid
make sure your using tomato MLPPP firmware and not regular tomato.
hmm.. but I'm not on MLPPP though.. does it matter?
-
Feb 26th, 2009 07:45 PM
#753

Originally Posted by
murdoc2k
hmm.. but I'm not on MLPPP though.. does it matter?
uhh yes...mlppp is the only way to get around the throttle. did you read anything in the first thread at all??
-
Feb 26th, 2009 08:37 PM
#754

Originally Posted by
infamouskid
make sure your using tomato MLPPP firmware and not regular tomato.
Alright I made a big boo boo I need some help
I got all excited when first flashed to Tomato (non-MLPPP) firmware and so I thought it was going to be an easy process to go from Tomato -> Tomato MLPPP so I went to the upgrade page and immediately applied the MLPPP firmware.
The router restarted and now I can't even acess the router via 192.168.1.1 anymore. Is there anything I can do or am I screwed? I tried powering it off for 10 seconds and then repowering it and pressing the rest button but still no go.
-
Feb 26th, 2009 09:34 PM
#755
are you connected to the router? make sure you're connected by wire and not wirelessly
-
Feb 26th, 2009 09:44 PM
#756

Originally Posted by
nx6288
are you connected to the router? make sure you're connected by wire and not wirelessly
yes. The problem is that I suspect my router is bricked due to improper flashing. I forgot to clear out the settings and ram before doing it 
-
Feb 26th, 2009 09:46 PM
#757
how long did you hold the reset button for?
try 10+ seconds.
-
Feb 26th, 2009 10:26 PM
#758

Originally Posted by
nx6288
how long did you hold the reset button for?
try 10+ seconds.
Just tried it. Held reset button for 20 seconds and also left my router unplugged for about an hour or so before re-trying. Nothing has changed.
-
Feb 26th, 2009 10:52 PM
#759

Originally Posted by
murdoc2k
Alright I made a big boo boo I need some help
I got all excited when first flashed to Tomato (non-MLPPP) firmware and so I thought it was going to be an easy process to go from Tomato -> Tomato MLPPP so I went to the upgrade page and immediately applied the MLPPP firmware.
The router restarted and now I can't even acess the router via 192.168.1.1 anymore. Is there anything I can do or am I screwed? I tried powering it off for 10 seconds and then repowering it and pressing the rest button but still no go.
Check your IP settings on your computer and make sure its in the same IP range as the router. Often time Windows defaults to a 169.XXX.XXX.XXX IP when there's no DHCP server active. You might have to manually set the IP and subnet so its in the same range as the router. ie. 192.168.1.101 etc.
-LeeBear
-
Feb 27th, 2009 12:08 AM
#760
Its sickening that Bell makes Canadians jumps through all these hoops just to get decent speeds that we pay for...
-
Feb 27th, 2009 12:18 AM
#761
set everything dhcp. turn on router while connected to your computer.
go to command prompt and type inconfig /all
check default gateway. that will be your router ip.
if that does not work there is a tftp program on the net somewhere where you can force the firmware in. other then that i would reccomend posting in the teksavvy forum at dslreports.com under the canadian isp forums.
guspaz and bichapale are pretty good guys to ask.
-
Feb 27th, 2009 12:56 AM
#762

Originally Posted by
infamouskid
set everything dhcp. turn on router while connected to your computer.
go to command prompt and type inconfig /all
check default gateway. that will be your router ip.
if that does not work there is a tftp program on the net somewhere where you can force the firmware in. other then that i would reccomend posting in the teksavvy forum at dslreports.com under the canadian isp forums.
guspaz and bichapale are pretty good guys to ask.
I don't think tftp would work considering my default gateway is 0.0.0.0 (I've actually tried that ip to see if I could connect and no positive results have shown)

Originally Posted by
LeeBear
Check your IP settings on your computer and make sure its in the same IP range as the router. Often time Windows defaults to a 169.XXX.XXX.XXX IP when there's no DHCP server active. You might have to manually set the IP and subnet so its in the same range as the router. ie. 192.168.1.101 etc.
-LeeBear
Checked.
Default gateway shows 0.0.0.0
essentially there's no router detected and there's no ip assigned. My only conclusion so far is that I've bricked it 
-
Feb 27th, 2009 01:18 AM
#763

Originally Posted by
murdoc2k
I don't think tftp would work considering my default gateway is 0.0.0.0 (I've actually tried that ip to see if I could connect and no positive results have shown)
Checked.
Default gateway shows 0.0.0.0
essentially there's no router detected and there's no ip assigned. My only conclusion so far is that I've bricked it


That's why you have to manually input the IP address for your network card. In Windows set your IP address to 192.168.1.110 gateway to 192.168.1.1 subnet 255.255.255.0 and then see if you can connect to the router. From my experience with the Asus routers they are pretty hard to brick, but often times you lose DHCP during the flashing procedure.
-LeeBear
-
Feb 27th, 2009 02:16 AM
#764

Originally Posted by
LeeBear
That's why you have to manually input the IP address for your network card. In Windows set your IP address to 192.168.1.110 gateway to 192.168.1.1 subnet 255.255.255.0 and then see if you can connect to the router. From my experience with the Asus routers they are pretty hard to brick, but often times you lose DHCP during the flashing procedure.
-LeeBear
ok I do see your point. I've done "ipconfig /all" in cmd prompt and it did show that DHCP server has been shut off. I'm however unable to get back simply by entering the info that you've suggested. If only I can somehow re-enable the DHCP...
-
Feb 27th, 2009 02:50 AM
#765

Originally Posted by
murdoc2k
ok I do see your point. I've done "ipconfig /all" in cmd prompt and it did show that DHCP server has been shut off. I'm however unable to get back simply by entering the info that you've suggested. If only I can somehow re-enable the DHCP...
looks like your gonna have to jtag that sucker back to life. or rma it.
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
Forum Rules