Differences
This shows you the differences between two versions of the page.
|
toh:buffalo:wzr-600dhp [2013/02/07 06:06] jmeier |
toh:buffalo:wzr-600dhp [2013/04/29 00:22] (current) john_i |
||
|---|---|---|---|
| Line 5: | Line 5: | ||
| ^ Version/Model ^ Launch Date ^ S/N ^ OpenWrt Version Supported ^ Model Specific Notes ^ | ^ Version/Model ^ Launch Date ^ S/N ^ OpenWrt Version Supported ^ Model Specific Notes ^ | ||
| | C0B1 (600DHP) | ? | - | Attitude Adjustment | - | | | C0B1 (600DHP) | ? | - | Attitude Adjustment | - | | ||
| - | | C0_B2 (500DHP) | ? | - | Attitude Adjustment 12.09-rc1 | very difficult install (see below) | | + | | C0_B2 (500DHP) | ? | - | Attitude Adjustment 12.09-rc1 | - | |
| ===== Hardware Highlights ===== | ===== Hardware Highlights ===== | ||
| Line 26: | Line 26: | ||
| The instructions provided below for C0B1 could possibly be outdated now. I was unsuccessful with that method after many attempts. The installation instructions for C0B2 (posted below) worked for my C0B1. Be patient, as it will take some time for the install to take. Do not unplug while the red light is flashing. I came from Buffalo's Pro Build (20180) using WinSCP to transfer the firmware. | The instructions provided below for C0B1 could possibly be outdated now. I was unsuccessful with that method after many attempts. The installation instructions for C0B2 (posted below) worked for my C0B1. Be patient, as it will take some time for the install to take. Do not unplug while the red light is flashing. I came from Buffalo's Pro Build (20180) using WinSCP to transfer the firmware. | ||
| - | >> On the contrary to the following report regarding the router hardware version C0B1, my C0B1 was not successful. | + | >> Some have reported failure with C0B1 using tftp method. Be sure to follow tftp instructions to the letter, and it may take a few tries because of timing. Or try the C0B2 instructions as suggested above. |
| - | //Confirmed working with router version C0B1, using openwrt-ar71xx-generic-wzr-hp-ag300h-squashfs-tftp.bin (Attitude Adjustment RC1)// | + | |
| + | //Confirmed working with router version C0B1, using openwrt-ar71xx-generic-wzr-hp-ag300h-squashfs-tftp.bin (Attitude Adjustment RC1) (_john_i_ 2012-12-30)// | ||
| + | |||
| + | //Also confirmed working via sysupgrade on router version C0B1 using openwrt-ar71xx-generic-wzr-hp-ag300h-squashfs-sysupgrade.bin upgrading from 12.09-rc1 to 12.09 final (r36088) (_john_i_ 2013-04-28) // | ||
| If you read the following (previously posted) instructions, at least for version C0B1 there is no need to set the ubootenv accept_open_rt_fmt or (not mentioned, but like the WZR-HP-G300NH2 (version A1A0) (and not required for it either)) ubootenv tftp_wait. | If you read the following (previously posted) instructions, at least for version C0B1 there is no need to set the ubootenv accept_open_rt_fmt or (not mentioned, but like the WZR-HP-G300NH2 (version A1A0) (and not required for it either)) ubootenv tftp_wait. | ||
| - | This worked with Attitude Adjustment RC1 file openwrt-ar71xx-generic-wzr-hp-ag300h-squashfs-factory.bin (*Note*: This may be error by OP. I had to use the "-tftp.bin" firmware rather than the "-factory.bin" firmware), others are untested. Prob small consolation to you but the reading is way easier than the writing... total chaos!!! | + | This worked with Attitude Adjustment RC1 file openwrt-ar71xx-generic-wzr-hp-ag300h-squashfs-tftp.bin (...-factory.bin filename typo fixed by OP, I quite possibly repeated the "go get some coffee..." step a few to many times??) I can now also confirm that at least the ...wzr-hp-ag300h-jffs2-tftp.bin works as well. Likely of small consolation to you but the reading is way easier than the writing... total chaos!!! |
| - Pregame warmup ~ Give it a 30/30/30 | - Pregame warmup ~ Give it a 30/30/30 | ||
| Line 38: | Line 41: | ||
| - Issue arp command as follows: "arp -s 192.168.11.1 02:aa:bb:cc:dd:20" | - Issue arp command as follows: "arp -s 192.168.11.1 02:aa:bb:cc:dd:20" | ||
| - On linux box type following command at la prompt: "tftp -m binary 192.168.11.1 -c put name_of_firmware_file.bin" (windows users you'll have to make something up yourself) | - On linux box type following command at la prompt: "tftp -m binary 192.168.11.1 -c put name_of_firmware_file.bin" (windows users you'll have to make something up yourself) | ||
| - | - (Only tried this once and) I think this is rather early on the timing, (but regardless) press enter to issue step 4's command (tftp) and then plug in the 600DHP. | + | - (Only tried this once to many and while possibly early on the timing it works every time.) Press enter to issue step 4's command (tftp) and then plug in the 600DHP. |
| - Go get some coffee or tea while you wait for 5 minutes. | - Go get some coffee or tea while you wait for 5 minutes. | ||
| - | - After no more flashing "diag" light, reset the IP on your machine to 192.168.1.2, and enter 192.168.1.1 in your browser and proceed to configure. | + | - After no more flashing "diag" light (which (at least on CBO1 model) is somewhat sporadic in its appearance), reset the IP on your machine to 192.168.1.2, and enter 192.168.1.1 in your browser and proceed to configure. |
| - | - NOTE ~ As of this writing step 6 configuration phase is largely (ok totally) untested by me 8-o hmm, hope it really all went to plan. | + | - NOTE ~ As of this writing step 6 configuration phase is largely (ok totally) untested by me 8-o hmm, hope it really all went to plan. |
| + | - NOTE ~ Ignore previous note, no routers were harmed in the process, I repeat, no routers were harmed in the process. Configuration and operation work fine. I think I'm working towards creating some .bin files with proper 600DHP names, but it's hard to tell sometimes... to be certain, you'll know it when you see them. | ||
| + | |||
| + | Because someone might get a laugh out of this, I should add that I had contacted Buffalo's tech dept. hoping for some help with the flash process before figuring it out myself. No, that's not the funny part. I noted in the inital message that I was willing to accept responsiblity for any damage incurred by my attempt. The replied I got back stated that the tech dept. couldn't assist in any potential warranty voiding procedures or activities. I responded by noting that although the point was probably moot, there was technically no voidable warranty on my router as I hadn't filed the paperwork. I gathered they weren't swayed at all by this fact as they neglected to respond. | ||
| + | |||
| + | |||
| Existing info... which might apply to some models? | Existing info... which might apply to some models? | ||
| Line 84: | Line 92: | ||
| 2/06/13 - Just flashed a B2 with the regular TFTP method. | 2/06/13 - Just flashed a B2 with the regular TFTP method. | ||
| + | |||
| + | 2013-04-16: Confirmed flashing a B2 using the SCP & SSH, mtd method mentioned above. No issues. | ||
| + | |||
| + | 2013-04-24: Also confirmed flashing a B2 using SCP/SSH/mtd method mentioned above with no issues. Also used the RC2 image of the version referenced above without issues. | ||
toh/buffalo/wzr-600dhp.1360213568.txt.bz2 · Last modified: 2013/02/07 06:06 by jmeier