Posted: Sun May 04, 2014 12:39 Post subject: Telnet
Oh..... Okay..... I was not fully aware that was how it worked in this situation ..... I was just saying that because I know when you go to secure a Windows PC you pretty much always disable telnet because it is a highly universal port in it's utility. Thanks for explaining.
Oh no problem brother.
I'm glad I could help you understand the basics of it. After all isn't that thee entire premise of a forum(a group of users helping each other understand). With that said, I'll concede that although only vaguely, I too recall reading of "Telnet" being a security flaw(years ago at Spinrite.com).
I only wish the Major Player I posted my question to in this thread, could somehow bring himself to actually answer the bloody question that I asked of him way back on 12/17/13. After all it's a simple yes or no answer, but some 6 months later & I've yet to see any type of response. Who knows, I probably failed to read, say, do, or understand something correctly.
Posted: Wed Aug 20, 2014 14:01 Post subject: netgear router long wait...........
I would love to see these routers (wnr1000v2) given support they are becoming common as dirt in the usa, and have a single antenna connector that can be adapted to high quality antennas. both comcast and now dish network are handing them out like candy, I have one of the boards on my roof in a weather box adapted to rp-sma coax attached attached to a high gain onmi i now have wifi everywhere within 1000 feet.
i would love to have better control over the hardware though i feel that the tx pwr is set very low and could be tweeked up a lot more with a better frimware, i have been trying to research if this possible but have found little information
i have tons of these routers from my workings with dish, mostly units that have been damaged by customers but are in still working condition overall things like broken buttons , antennas, cosmetic and broken connectors, nothing that really affects the boards much
so the question is is a router donation still required? I have plenty to go around hell I will even send a brand new one if one is still needed........
Posted: Fri Sep 19, 2014 7:50 Post subject: Still no progress?
I am one of the lucky many that has just become a proud owner of a WNR1000v2.
I must say tho, I am quite disappointed that there is no DD-WRT working for it, especially since it's the 3rd netgear device I have now that doesn't have any DD-WRT development done on it.
Would love to see some progress with this device. if a router donation is still necessary for any sort of DD-WRT to get released, I'll happily part with mine so some of these other people can run decent firmware.
This router seems to be very common right now, even 2 of my friends have the exact same model/version.
Does anybody know what needs to happen for things to get rolling? Reading through this entire thread is rather confusing,
Someone please post what the next step is (1st step from the looks of it) for some development to happen.
Posted: Sat Sep 20, 2014 20:17 Post subject: Well, I've tried this.
Even though I'm running DD-WRT on three different routers, I'm pretty much a n00b for everything other than following the instructions here and on the wiki.
So I tried to install the firmware from the D-Link DIR-600 A1 (which is the DIR601A1 firmware, and it's two separate files, for whatever reason) on my Netgear WNR1000v2-VC, and there is a problem. Seems that the Netgear insists that the router firmware be in .IMG format rather than .BIN format, and, of course, the D-Link uses the .BIN format.
Now, I don't know if there is some trick to converting from .BIN to .IMG, but I can tell you that simply changing the extension doesn't work, because I receive a response stating that the firmware update has failed.
I've only tried this via the GUI on the Netgear router, because I can't seem to get TFTP to connect, no matter what I do. Maybe it's something with my system (running Windows 7), but the only option I've been able to try is the GUI.
For the record, I've had an easier time flashing Android tablets over USB.
I hope my complete lack of anything resembling success with this can serve as encouragement to someone here to move forward.
EDIT: I've done some more research, and I've found this thread at the OpenWRT forums which may give some additional information that may make this work. And it appears that the VC model has some sort of check built into the GUI that only allows specifically-signed firmwares to work on this router, so that may something to do with my failure.
I wanted to resurrect that work, and per your suggestion, I tried the wnr2000v3 build (09-22-2016-r30681/netgear-build/netgear-wnr2000v3) (instead of the DIR601A1 as I did a long time ago).
After some hex mods (2 magic numbers and 2 crc and 1 load/entry point (not sure if necessary on that last part)), it appears to be running fine. I haven't tested much functionality, but it at least generates the wifi AP, dhcp is working, can log in to the web console, configure it, etc...
So you may want to add this hardware to your build. Magic number 1001 for the wnr1000v2 (not sure for the comcast version as I don't have one...)
Let me know if I can help you test an actual build (provided it doesn't modify the bootloader...).
The original bootloader will only load the squashfs at offset 0x50040.
So I have no choice but to flash kernel+rootfs at 9f050000.
So the partition looks like this currently:
9f000000 - 9f03ffff "u-boot" (256k)
9f040000 - 9f04ffff "u-boot-env" (64k)
9f050000 - 9f3e7fff "rootfs" (3680k)
9f3e8000 - 9f3effff "nvram" (32k)
9f3f0000 - 9f3fffff "ART" (64k)
So I tried modifying the bootargs:
bootargs=console=ttyS0,115200=root=31:08 rootfstype=squashfs init=/etc/preinit mtdparts=ar7240-nor0:256k(u-boot),64k(u-boot-env),3680k(rootfs),32k(nvram),64k(ART),3768280@327744(mount_fs)
However, the kernel doesn't pick that up (hardcoded in your build ?)
[0.000000] Kernel command line: console=ttyS0,115200 root=1f02 rootfstype=squashfs noinitrd init=/sbin/init
Otherwise, it boots successfully and everything seems to be working...
So at this point, I personally have 2 choices:
-Get to the same partition structure as DD-WRT (implies replacing U-BOOT by Redboot (which I have no experience with, and I also risk bricking my board).
-Modify your build to keep the u-boot structure as is (which I don't really know where to even begin...)
Now that I think about it, the nvram partition most likely needs to be on an erase boundary (1k).
So I'm not sure what my options are:
-Hardcoded boot parameters in the bootloader (removing the need for the u-boot-env). And flashing the kernel/rootfs at 9f040000.
This last one would be the most straightforward for me.
I need help and any suggestion would be greatly appreciated!