THE ROAD GOES EVER ON AND ON
DOWN FROM THE DOOR WHERE IT BEGAN
NOW FAR AHEAD THE ROAD HAS GONE
Tuesday, August 3, 2010
Rant no. 080310_01
Wesley has grinding gears today. It drives him crazy to see someone double-click a hyperlink. He frowns on excessive bookmarking. Oh, and saving everything created or downloaded to the Desktop? As if the My Documents folder is on the far side of Pluto. And while he is kicking things, he detests Microsoft. Linux, take me away. Eh, I'm a slave to the man.
Tuesday, June 29, 2010
Hacking the WGR614v10 - Part 2
"Upgrading" from 54Mpbs to 150Mpbs
Note: This tutorial is now obsolete. The official Netgear firmware for the WGR614v10 now allows Wireless-N speeds up to 150Mbps. But you're still welcome to follow along if you're interested in the "educational" factor. :)
I remember way back when caller ID first came out for landlines. I thought it was the neatest thing since socks. I just had to get myself one of those spiffy caller ID boxes. And so I did. It was a CIDCO, model something, I don't recall now. It had a 30-call memory so at the 30th call, you had to start deleting. As it turns out, it had a 90-call memory. "Eh? You just said it had a 30-call memory." Yes, I did. You see, the 30-call and 90-call boxes were essentially the same. The difference was the 30-call was intentionally "crippled" by CIDCO. But this cripple could be made, bigger, stronger, faster. Well, bigger at least. All you had to do was pop the box open and desolder one specific jumper and BAM!, you had a 90-call box for the price of 30-call. So what's this all have to do with the price of tea in China? Well, it's the same ballgame with the WGR614v10. The WGR614v10 has a top wireless speed of 54Mbps but has the same underlying hardware as a 150Mpbs capable router; it's just crippled. But we can make it faster. :) If you plan on trying out what I'm about to explain and aren't too handy with a soldering iron, don't worry, you won't need one for this; however, you should be aware this is a potentially unsafe procedure and it's possible to brick your router. With that said, I had no issues performing this procedure and my router works just fine. Now, to the "upgrading" part.
To perform the upgrade you will need 3 things:
Ok, here we go.
That's it! If everything went accordingly, you should now have a 150Mpbs router. Cheers! :)
Note: This tutorial is now obsolete. The official Netgear firmware for the WGR614v10 now allows Wireless-N speeds up to 150Mbps. But you're still welcome to follow along if you're interested in the "educational" factor. :)
I remember way back when caller ID first came out for landlines. I thought it was the neatest thing since socks. I just had to get myself one of those spiffy caller ID boxes. And so I did. It was a CIDCO, model something, I don't recall now. It had a 30-call memory so at the 30th call, you had to start deleting. As it turns out, it had a 90-call memory. "Eh? You just said it had a 30-call memory." Yes, I did. You see, the 30-call and 90-call boxes were essentially the same. The difference was the 30-call was intentionally "crippled" by CIDCO. But this cripple could be made, bigger, stronger, faster. Well, bigger at least. All you had to do was pop the box open and desolder one specific jumper and BAM!, you had a 90-call box for the price of 30-call. So what's this all have to do with the price of tea in China? Well, it's the same ballgame with the WGR614v10. The WGR614v10 has a top wireless speed of 54Mbps but has the same underlying hardware as a 150Mpbs capable router; it's just crippled. But we can make it faster. :) If you plan on trying out what I'm about to explain and aren't too handy with a soldering iron, don't worry, you won't need one for this; however, you should be aware this is a potentially unsafe procedure and it's possible to brick your router. With that said, I had no issues performing this procedure and my router works just fine. Now, to the "upgrading" part.
To perform the upgrade you will need 3 things:
- A telnet enabled router (see Part 1 of Hacking the WGR614v10).
- A telnet utility. You can use the MS Win ver. or another of your choosing.
- The WNR1000v3 firmware from Netgear. Dowloand here.
Ok, here we go.
- Step 1: Enable telnet on your router and telnet in by opening a command console and typing telnetenable 192.168.1.1 C03F0E34675C Gearguy Geardog and press enter. You will need to replace C03F0E34675C with the mac address of your router, which can be found on the back of your router or on the box that the router came in. Next type telnet 192.168.1.1 and press enter. If everything worked correctly, you should now see something like:
- Step 2: Now we're going to change the nvram board_id value to U12H139T00_NETGEAR by typing burnboardid U12H139T00_NETGEAR and pressing enter. This is necessary because when we attempt to update the firmware the router will check the new firmware version against the value stored in nvram. If the values don't match, then we have a no go.
- Step 3: Reboot the router by typing reboot and pressing enter. Wait for the router to come back online and login to the router via the web interface (http://192.168.1.1).
- Step 4: Now we're going to upload the new firmware via the web interface. To do so, click on the "Router Upgrade" left menu link. Click on the "Browse" button, locate and select the firmware file that you downloaded (WNR1000v3-V1.0.2.4_39.0.39.chk) then click the "Upload" button.
- Note: The upload process will take a minute or two. DO NOT power off or reset your router until it is complete!
- Step 5: Reset your router to the factory default settings (per the new firmware) by pressing and holding the reset button, located on the back of your router, for approximately 5 seconds until the power light begins to blink, then release. Refer to your router's help manual if you need additional information on how to perfom a reset.
- Step: 6 Login into your router via the web interface to configure the router's settings.
Chances are you will be unable to connect to your router wirelessly at this point. Simply remedy this by connecting your computer to the router directly via ethernet cable. Once connected via cable, login to the web interface and change the "Region" setting, located by clicking "Wireless Settings" under the "Setup" section, to whatever region you're located in. This occurs because the firmware we're using is actually an "international" firmware and different countries/regions have different laws/regulations regarding radio frequency. The Region selection ultimately determines the operating frequency corresponding to the channel you select.
That's it! If everything went accordingly, you should now have a 150Mpbs router. Cheers! :)
Friday, June 25, 2010
Hacking My Cat
Notice the modified ears. I thought by inverting his ears I could improve upon him aerodynamically, thereby making him less clumsy. Oddly, he doesn't seem too happy about this.
Thursday, June 24, 2010
Hacking the WGR614v10 - Part 1
Enabling telnet Access
I recently got a new WRG614(v10) wireless router. Naturally, I wasn't content leaving it be, so I decided to see what sort of hacks were available. My first want was to replace the factory default firmware with an open source one, such as DD-WRT or OpenWRT. Sadly, I could not find a release for the WGR614v10. After a little more hack searching, I came across this: "hacking the WGR614v7" (enabling telnet access on the router). "This looks interesting", I thought, "let's give it a try." I downloaded the source code and compiled it under BackTrack 4. It compiled successfully on the first go, albeit with a few innocuous warnings.
Bingo! Works like a charm.
Holy haberdashery, Batman! It's running BusyBox 0.60.0 (rel. August 2, 2001). At present, the stable is 1.16.2 (rel. June 12, 2010)! I believe v10 of the WGR614 was released in the mid to latter part of '09. Hmmm?
I recently got a new WRG614(v10) wireless router. Naturally, I wasn't content leaving it be, so I decided to see what sort of hacks were available. My first want was to replace the factory default firmware with an open source one, such as DD-WRT or OpenWRT. Sadly, I could not find a release for the WGR614v10. After a little more hack searching, I came across this: "hacking the WGR614v7" (enabling telnet access on the router). "This looks interesting", I thought, "let's give it a try." I downloaded the source code and compiled it under BackTrack 4. It compiled successfully on the first go, albeit with a few innocuous warnings.
Bingo! Works like a charm.
Holy haberdashery, Batman! It's running BusyBox 0.60.0 (rel. August 2, 2001). At present, the stable is 1.16.2 (rel. June 12, 2010)! I believe v10 of the WGR614 was released in the mid to latter part of '09. Hmmm?
If you want to try this but don't have Linux on your system and/or don't want to hassle with installing a second OS, you can use a virtual machine such as VMware Player (free). Using VMware Player will (should) allow you to load and run the Linux distro of your choice, not to mention a number of other operating systems (i.e. Windows XP/2000/7, Mac Os X, Chrome OS, etc). You also might try Cygwin, although, I have not tested this under Cygwin so I cannot guarantee a smooth compile.
*Wesley hopes a v10 open source firmware comes available soon :)*
*Wesley hopes a v10 open source firmware comes available soon :)*
Wednesday, June 23, 2010
A First Post: More Than Markup
So, I've decided I would jump on the Blog bandwagon. Now, what to put here as my first post? Hmm, well, I have a bit of interest in building websites, so how about something I wrote a long time ago: a response to some ignoramus programmer calling web developers "HTML monkeys" and throwing off the profession as "easy". I don't have the link to the original article anymore but, as I recall, it was something to the effect of web development consisting exclusively of writing markup (HTML) and perhaps a little JavaScript. Fairly irritated and annoyed, I was moved to respond.
Response as follows:
To those who would dismiss our profession as "easy", I would say you have a fundamental misunderstanding of what it is we really do. Sure, I'm an "HTML monkey", just as much as a physicist is an administrative assistant. There's a lot more to web development than markup languages, client-side scripting and graphic design software. This might come as a surprise to some but web developers are also programmers, DBAs, server admins, project managers, diplomats, crisis managers, counselors and the list goes on. Well, maybe the last three are a slight exaggeration but you get my point.
The act of authoring an HTML document and throwing in a bit of JavaScript spice may not be rocket science but that does not imply that web development is necessarily "easy". Even if HTML and JavaScript were the only tricks in our bag that does not make our job inherently easy. Besides, what legitimate purpose does it serve to trivialize another's profession anyway? If writing HTML is just a bunch of monkey business, then I say be thankful for the monkeys! We certainly wouldn't want to leave our precious Web in the hands of those brainy types, would we? ;)
Remember, fellow creators, pay no attention to those who tell you what you do is easy or unimportant. Such observations merit no validity by virtue of knowledge or experience, and thus, are nothing more than a product of ignorance.
Cheers!
Response as follows:
To those who would dismiss our profession as "easy", I would say you have a fundamental misunderstanding of what it is we really do. Sure, I'm an "HTML monkey", just as much as a physicist is an administrative assistant. There's a lot more to web development than markup languages, client-side scripting and graphic design software. This might come as a surprise to some but web developers are also programmers, DBAs, server admins, project managers, diplomats, crisis managers, counselors and the list goes on. Well, maybe the last three are a slight exaggeration but you get my point.
The act of authoring an HTML document and throwing in a bit of JavaScript spice may not be rocket science but that does not imply that web development is necessarily "easy". Even if HTML and JavaScript were the only tricks in our bag that does not make our job inherently easy. Besides, what legitimate purpose does it serve to trivialize another's profession anyway? If writing HTML is just a bunch of monkey business, then I say be thankful for the monkeys! We certainly wouldn't want to leave our precious Web in the hands of those brainy types, would we? ;)
Remember, fellow creators, pay no attention to those who tell you what you do is easy or unimportant. Such observations merit no validity by virtue of knowledge or experience, and thus, are nothing more than a product of ignorance.
Cheers!
Subscribe to:
Posts (Atom)