Joined: 26 Jan 2008 Posts: 13049 Location: Behind The Reset Button
Posted: Sat Jul 11, 2009 13:08 Post subject:
My neighbor, who I let peg my internet called and said he could not connect to my AP. I have him set up with a router configured as a client bridge.
I can see him, he can see me but he can not connect. He can not ping me, I can not ping his (my) router or his rig.
Nothing on his end has changed. I flashed my equipment last night testing and left this build on.
Normal trouble shooting steps didn't help. On his client he is running 12307. I flashed back my AP to 12387. He then connected right away after I restored the settings on the AP.
Funny thing is, I have other clients that could connect to the AP (non-dd-wrt) _________________ [Moderator Deleted]
NEWD2 micro and NEWD micro were successfully flashed into the WRT300N v1 but there was no radio detected by the computers, which is I think is expected since micro can't be used with N routers.
Ok, I got my WRT600N up and running with the dd-wrt.v24-12476_NEWD-2_mini.bin, but on the Status page, it says only build 12476M NEWD Eko, but I assume this is correct.
Otherwise, not much to report about the flashing, it all went as normal. Let the testing commence... _________________
Asus RT-AC66U DD-WRT v24-sp2 giga - build 25015 [Main]
Linksys E3000 DD-WRT v24-sp2 mega - build 15962 [Backup]
Linksys WRT600N v1.1 DD-WRT v24-sp2 (08/12/10) mega - build 14929 [Retired]
Linksys WRT54GS v4 DD-WRT v24-sp2 mini - build 15747 [Retired]
E3000 Info | WRT600N Info | Know-it-all thread
Joined: 01 May 2009 Posts: 274 Location: San Jose, Ca
Posted: Sat Jul 11, 2009 16:45 Post subject:
anyone try the NEWD2 on a WRT310N...i flashed my WRT54G v3 but the router stopped responding and then i did a 30/30/30 reset to put back the previous build i had on there _________________ E3000 K2.6 Eko 16758 Mega
E3000 CB K2.6 EKO 16758 STD USB NAS
WRT610N V2 CB K2.6 Eko15337 STD Nokaid
WRT310N V2 CB K2.6 BS 15362 STD Nokaid
Before i go updating and brick router does new2 fit on
WRT54GL v1.1 WRT54G-TM ? _________________ ___________________________________
WRT54GL v1.1 WRT54G-TM Firmware: DD-WRT v24-sp2 (02/03/10) big - build 13832
Joined: 31 Mar 2007 Posts: 181 Location: /Earth/USA/OH/Zville
Posted: Sat Jul 11, 2009 18:39 Post subject:
Sigh.... The excitment is over for me.
Is there anything I could help out with my WRT350N? I'm more than willing to brick it, real easy for me to jtag it. I also have a serial connection for debug. Anything? PLEASE!
EDIT: Wow, that sounds sad and pathetic.... _________________ WRT-350N v1.0; 128MB RAM, WPC600N, Dual USB, Mini+USB+FTP NEWD, CPU@330Mhz, Terk WF-R x3, Serial, external jtag, and working on SD Mod. Running Samba3, Lighttpd, and some Python apps.
WRT-300N v1.1; 128MB Ram, USB1.1, Bricked
Is there anything I could help out with my WRT350N? I'm more than willing to brick it, real easy for me to jtag it. I also have a serial connection for debug. Anything? PLEASE!
Does NEWD-2 work on both of your routers? _________________ R7000 Kong vpn 23550-R01 (Main Router)
WRT610Nv2 converted E3000 vpnKong 21661 (RB)
WRT600N v1.1 BS std-nokaid 13637(5Ghz CB)(2.4Ghz AP)
WRT54G v5 BS micro 14684(RB)
Before i go updating and brick router does new2 fit on
WRT54GL v1.1 WRT54G-TM ?
I'm not sure what you mean by "fit"....but there are mini, nokaid, mega builds of NEWD2.
Don't load any on the GL....it will brick it.
The TM will take any build including Mega....reports are that it will run on the TM.
redhawk
Ok thnx with fit i mean does it support sorry for the mis understanding. I have the TM so i will install it. If you ppl donnot see me back it has gone wrong. _________________ ___________________________________
WRT54GL v1.1 WRT54G-TM Firmware: DD-WRT v24-sp2 (02/03/10) big - build 13832
Joined: 31 Mar 2007 Posts: 181 Location: /Earth/USA/OH/Zville
Posted: Sat Jul 11, 2009 19:17 Post subject:
Second time I was called a dd-wrt Ho. But I already knew that it was true...
Just wanting to help out.
@Blazian, NEWD2 works great on my WRT300N V1.1, but it will brick my WRT350N. I would almost need NEWD2 on my WRT350N soon because I'm changing the wireless card with a WPC600N. (Be interesting if I install that and NEWD2 would work, highly unlikely since the thing stops responding when it attempts to load the kernel). _________________ WRT-350N v1.0; 128MB RAM, WPC600N, Dual USB, Mini+USB+FTP NEWD, CPU@330Mhz, Terk WF-R x3, Serial, external jtag, and working on SD Mod. Running Samba3, Lighttpd, and some Python apps.
WRT-300N v1.1; 128MB Ram, USB1.1, Bricked
NEWD2 drivers are working perfectly fine with Asus WL-500W
Using the following processor: Broadcom BCM4704
rev. 9 if that's a factor. The new driver seems to work much better with the device. _________________ I'll short all the pins on my router before I ever build a JTAG.
If I'm not wrong Eko's NEWD-2 builds are using Broadcom version 4.150.66.6 wireless drivers.
Victek's Tomato firmware Mod is using Broadcom version 4.158.4.0 wireless drivers which seem more recent than the ones eko is using and I can confirm that there have been no problems.
Installs and runs fine on GL's, Asus 520GU and others that usually run fine with a normal ND build.
Maybe this couls help Eko.
I wonder what that newer driver fixes and if it's the newest driver available from Broadcom. Any clue? Maybe it just makes everything more compatible. Eko or BS should be able to work in the newest driver correct? Why are we so behind those Tomato freaks anyway? _________________ R7000 Kong vpn 23550-R01 (Main Router)
WRT610Nv2 converted E3000 vpnKong 21661 (RB)
WRT600N v1.1 BS std-nokaid 13637(5Ghz CB)(2.4Ghz AP)
WRT54G v5 BS micro 14684(RB)
If I'm not wrong Eko's NEWD-2 builds are using Broadcom version 4.150.66.6 wireless drivers.
Victek's Tomato firmware Mod is using Broadcom version 4.158.4.0 wireless drivers which seem more recent than the ones eko is using and I can confirm that there have been no problems.
Installs and runs fine on GL's, Asus 520GU and others that usually run fine with a normal ND build.
Maybe this couls help Eko.
I wonder what that newer driver fixes and if it's the newest driver available from Broadcom. Any clue? Maybe it just makes everything more compatible. Eko or BS should be able to work in the newest driver correct? Why are we so behind those Tomato freaks anyway?
I have no idea what it fixes. What I do know is that it's not the newest broadcom driver. v.4.178.10.4 is the latest with support for the 2.4 linux kernel, the kernel used by Tomato and DD WRT, extracted from the original Linksys WRT610N source package.
The very latest drivers are v.5 and up but are for the 2.6 kernel and cannot be used by the 2.4 kernel, so I've been told.
DD WRT is not behind Tomato or the other way around. DD WRT supports way more routers and has alot more flexability and functions and Tomato is focused more on stability and speed.