OpenWrt Forum Archive

Topic: WZR-HP-G300NH Support

The content of this topic has been archived between 6 Feb 2018 and 3 May 2018. Unfortunately there are posts – most likely complete pages – missing.

Hi Lundman I also live in Japan (Yokohama) and have just subscribed to StrongVPN
and they suggested I buy a Buffalo WZR HP G450H but the girl at Yodobashi said that has been superceeded with
WZR-450HP so I bought one. Now I have gone back to StrongVpn and they are asking does it support DD-WRT without which I cannot set up a router using their service. Do you or anyone on the forum know if DD-WRT is
supported on this latest model ?
Ian

kowallis wrote:

I just bought a Buffalo WZR-HP-G300NH2. I wasn't able to do a tftp install, probably because of the locked U-boot mentioned in this forum and elsewhere, but I was able to do an mtd system upgrade from within an ssh session on the DD-WRT profesional firmware the router came with. (which I could tftp install just fine). As an important note, after the mtd flash and when the router came up, the red diag light never went off, but I was able to telnet in anyway. Once Luci was up I was able to turn off the red diag light, so it might be that the trunk version I installed just had the light on by default. (I installed OpenWrt Attitude Adjustment r32793)

I think this needs to be on the WZR-HP-G300NH page in big red letters. I ran mtd system upgrade; I tried to get on the web page (I didn't realize that the image doesn't have Luci); then I looked at the router and I saw diag light red; I rebooted - the light was still red - and I panicked. I tried to reset it, including 30/30/30 reset. Nothing helped - and I ended up returning the router.
The replacement router behaved the same (mtd upgrade successful, but the dial light was solid red). However, just like kowallis, I was able to telnet, change password, ssh, install Luci, and I am now in. There is a page of LED settings - so I turned diag off. I am still tinkering with the settings (I replaced old Linksys with openwrt on it) - but the main thing, it works fine!

is there any theme that supporting luci for this router? i just found one compatible theme. bootstrap. any other can share ?

Hi

I just got this router Buffalo WZR-HP-G300NH v1 Japanese model, and well I'm really disappointed to know that the only language is JP and I can't change it... I did a search (google) and ended up at the wiki of openwrt.
http://wiki.openwrt.org/toh/buffalo/wzr … ftp.window
More exactly at "Locked U-Boot, too short time TFTP window".
This is what I did...

1. I connected to the router using that link (http://your.router.ip.address/cgi-bin/c … debug.html), and then I enabled the telnet.
2. Since I'm using win7x64 and it already has the telnet client, I connected to the router using the "telnet 192.168.11.1".
3. I typed "# ubootenv -h" and then the help list pop out (good...i think...)
4. Well, here is thing...I don't know what to do next!

Since at the wiki says "Once there, one can use a command "ubootenv" to set above mentioned variables without trouble", and the steps to enable it to accept others firmwares are "ar7100> setenv accept_open_rt_fmt 1; ar7100> saveenv; ar7100> reset"; I tried:

1. # ubootenv setenv accept_open_rt_fmt 1 (it showed me that help list again...wrong I think)
2. # ubootenv set accept_open_rt_fmt 1 (I THINK it worked since it didn't showed that help list again, and the # came right after that)
3. I was unable to do the others 2 steps (saveenv and reset) since both showed me the help list.

I was reading the old messeges but I think all of them are talking about serial, tftp, etc... I didn't find anything about this "easy way" that wiki page was talking about.
Can someone please help me with this?
And sorry my bad english.
Thanks

EDIT: When I typed ''ubootenv list" the last line showed me this "accept_open_rt_fmt 1"
So, can I flash a new firmware (english) to overwrite the old firmware (japanese)?

(Last edited by jacksparrow on 20 Sep 2012, 16:32)

How is WZR-HP-G300NH rev A2A0 different from other revisions.
Does WZR-HP-G300NH rev A2A0 support OpenWrt 'Backfire' 10.03.1-RC5 and  OpenWrt trunk r28133

What is the difference between trunk and backfire?

As a result, this newer hardware is NOT supported in OpenWrt 'Backfire' 10.03.1-RC5 but it is supported in OpenWrt trunk since at least r28133. Not sure which new hardware it is referring to

(Last edited by moonbug on 14 Nov 2012, 04:34)

moonbug wrote:

How is WZR-HP-G300NH rev A2A0 different from other revisions.

The A2 A0 has the rtl8366rb switch, which is different from earlier/other versions of the G300NH, so Backfire doesn't work.  I was using trunk, and now the Attitude Adjustment betas, they work great on my WZR-HP-G300NH, which is revision A2 A0.

I tried upgrading the firmware on WZR-HP-G300NH rev A2A0 but I experienced problem with wired devices connected to the switch unable to ping or see each other.
Does the Attitude Adjustment (12.09) have similar issue?
Is the wifi also stable without having to reboot the router every couple of days.
Does it also support VPN clients?

Hello People,

I have got NH2 version (A1-A0), I have tried to update image through tftp.
It seems that OpenWrt tftp transfer was successful, DIAG LED started blink ~30 sec and went off, after restart DIAG is always on, ping is absent. Seems that updated fails.

Fortunately I could restore factory images via tftp (both: user_friendly and dd_wrt_based). During flashing DIAG blinked several minutes.
Could you please clarify average DIAG time blinking for OpenWrt during updating via tftp (~30 sec or ~3-5 min)?

Could you please clarify necessary images to update OpenWrt from factory image?

Is it correct to use http://downloads.openwrt.org/attitude_a … x/generic/ ?

Image 1:
openwrt-ar71xx-generic-wzr-hp-g300nh2-squashfs-factory.bin
(md5sum 4d2a50596fa7f4e58f083697dcbf581b)

Image 2:
openwrt-ar71xx-generic-wzr-hp-g300nh2-squashfs-tftp.bin
(md5sum 89fadd2bc217cac80285befd5f015928)

Which image is needed to update factory image to OpenWrt?

What packages are installed within image? I mean Luci and pppoe, are they available?

Also it is not 100% clear what MAC address use with arp command? Mentioned at the router back side or 02:aa:bb:cc:dd:1a? I have tried second (as OpenWrt Wiki recommend), but at some how-to scenarios native MAC is used (e.g. http://g300nh.blogspot.ru/2010/06/firmw … very.html)

Thanks.

(Last edited by Unmasked on 14 Dec 2012, 10:09)

I think I am successfully in OpenWrt!

This helped me to tftp at XP, recently only ubunty tftp was enough fast to catch tftp 4sec window.
https://forum.openwrt.org/viewtopic.php … 80#p143080

techweenie wrote:

From what I understand, you should still be able to use tftp to load a different firmware.  I use the Windows 7 procedure without a switch between the PC and router.  If you watch the link status lights on the back of the router when you plug it in, they will come on for a couple seconds, then turn off, then turn on again.  Immediately after they turn on the 2nd time you should be able to send the firmware with a tftp utility.

I think it must be added to the main description with highly appreciated to the techweenie, it could save a lot of time for a new users:
http://wiki.openwrt.org/toh/buffalo/wzr-hp-g300h

Do you have any idea/example how to config LEDs? Now I have power led green solid, diag red solid, wireless blinking.
For example to blink orange with wifi encryption and something like that.

Anyone tested latest trunk for WZR-HP-G300NH?

I customize, compile and flash, currently on r35062.
Running stable for 1d 2h 51m 14s.

I've WZR-HP-G300NH B0 B0.. having little stability issue with 10.03.1, don't know have I fucked something or what causes it. Random reboots now and then...It's been working earlier just fine.

Hi, I am new to Openwrt.   I have WZR-HP-G300NH B0 C0  and I want to setup openwrt with multi-wan.  Can someone suggest which version I should use?  Trunk, Attitude adjustment RC1 or Backfire 10.03.1
Also anyone know if this version has the old rtl8366s or the new rtl8366rb switch?

Thanks in advance!!!

(Last edited by snowx on 12 Jan 2013, 16:54)

>which version I should use?  Trunk, Attitude adjustment RC1 or Backfire 10.03.1

I believe Attitude adjustment RC1 (squashfs), it's better sine it is kind of safe, stable and up-to-date.

(Last edited by sstream on 15 Jan 2013, 21:58)

Anyone tried on a WZR-HP-G300NH2EU ? Seems to be what is selling in the UK at the moment. Not purchased yet so don't know the h/w rev.

I run OpenWRT on an Asus WL-330GE and want to run OpenWRT on a new router. Just had a disaster with an Asus RT-N16 and DD-WRT. Sent back after a week.

I need, VLANs, WIFI, Guest WIFI which should all be doable.

I noted somewhere that this device was not too happy having the LAN address changed. What I was hoping to do was use my block of "real" IP addresses. Maybe I would be better off using one to one NAT?

TIA

WRXIzumi wrote:
fabsle wrote:

Where are the images gone? I cant find a file to flash anymore sad

http://downloads.openwrt.org/snapshots/trunk/ar71xx/


Seems to be related to the size of the kernel and a limitation to 1 MB on our routers for the kernel.  Ticket 12569 is tracking this.

https://dev.openwrt.org/ticket/12569

I don't think this is the primary cause of the problem at least for now.
As the code pulled from trunk compiles fine and also boots fine, when I tried to make self-build openwrt for a slightly different device then yours that's gone missing due to recent changes and was available three weeks ago.
The only other issues of self-build firmware was minidlna disappears after 30mins as somebody has already reported the problem here https://forum.openwrt.org/viewtopic.php?id=41283

(Last edited by aadevice89 on 23 Jan 2013, 06:14)

aadevice89 wrote:
WRXIzumi wrote:
fabsle wrote:

Where are the images gone? I cant find a file to flash anymore sad

http://downloads.openwrt.org/snapshots/trunk/ar71xx/

Seems to be related to the size of the kernel and a limitation to 1 MB on our routers for the kernel.  Ticket 12569 is tracking this.

https://dev.openwrt.org/ticket/12569

I don't think this is the primary cause of the problem at least for now.
As the code pulled from trunk compiles fine and also boots fine, when I tried to make self-build openwrt for a slightly different device then yours that's gone missing due to recent changes and was available three weeks ago.
The only other issues of self-build firmware was minidlna disappears after 30mins as somebody has already reported the problem here https://forum.openwrt.org/viewtopic.php?id=41283

The code will compile just fine but the buildbot has runs in to the same issue of the resulting compiled kernel file being too big which prevents the image from being created.

We find the following line in the buildbot log

Warning: /home/openwrt/slave/ar71xx/build/build_dir/target-mips_r2_uClibc-0.9.33.2/linux-ar71xx_generic/tmp/vmlinux-wzr-hp-g300nh.uImage is too big

This is from the latest ar71xx build log located at:
http://buildbot.openwrt.org:8010/builde … logs/stdio

If you look at the line in the log just above the warning you can see that there is an if/else statement that checks the size of the kernel, the size of the jffs2 and only builds the image if they are both small enough.

Sorry to ask, but this os work whit WZR-HP-G300NH-R ?

pepepp3 wrote:
slybunda wrote:

still no client bridge mode support i see, strange how gargoyle and dd-wrt offer this client bridge mode but its not offered by openwrt.

To get client bridge mode on the WZR-HP-G300NH you only need to install the relayd package and follow this instructions.

I make my own compiled OpenWrt image with relayd built in to deploy it to two routers bridged wirelessly and the only weak point is the low throughput (about 9MB/s) between them.

Hey peppp3, were you able to resolve any issues with client bridge mode on the g300nh?  I am having all sorts of slow performance and duplicate pings.

sm0ke wrote:

Hey peppp3, were you able to resolve any issues with client bridge mode on the g300nh?  I am having all sorts of slow performance and duplicate pings.

I'm still running my own compiled Attitude Adjustment (today r36816) and having no issues at all. Throughput is OK (about 90 Mbits/sec tested with iperf) and I can transfer large files through both routers without disconnects.

Hi

I desperately need help from a  guru !

I just bricked my router.
I have an A0 A1 version, that was running Backfire 10.03.
I had wanted to upgrade to Attitude Adjustment (because of Luci broken interface), and uploaded http://downloads.openwrt.org/attitude_a … grade.bin. Then I launched the sysupgrade -v /tmp/openwrt-ar71xx-generic-wzr-hp-g300nh-jffs2-sysupgrade.bin command line. Everything seemed to work fine for the 1st part :
root@openwrt:/tmp$ sysupgrade -v openwrt-ar71xx-generic-wzr-hp-g300nh-jffs2-sysupgrade.bin
Saving config files...
root/statistics
[...]
Unlocking firmware ...

I get some "[w]" and "[e]" displayed in the console ...
I waited a long time, maybe 20 min, then, since the router was not rebooting by itself and the display not changing, I unplugged/plugged the power cord.
And the disaster appeared !
At reboot ... red solid led. No internet connection. Nothing working.
I have searched the wiki, and found this version (A0 A1) is now considered as a WZR-HP-G300NH2 (I think it wasn't until early last week).
Damn it !
I've tried to apply the failed upgrade procedure (http://wiki.openwrt.org/toh/buffalo/wzr … r.versions) by uploading  buffalo factory image that has the file extension 'enc', without success. TFTP transfers is working, but then, nothing.
I've tried with user-friendly image, with and without adding ".enc"  to the filename too. I've tried with various files, squashfs, jffs, tftp, even with the latest DD-WRT.bin firmware, but nothing happens ...
The red led stays solid.
I can't access in telnet/SSH/web.
It's just now as useful as a paperweight.
Is it the U-boot locked preventing me to write a new firmware ? If yes, what's the solution ?
Have I a last chance to save it ? How ?
Or do I have to change it ?
In this case, what would be the best choice ? Find another router (different brand/model) ? Buy a 2nd hand G300NH ? Buy a new G300NH2 ?




EDIT  (2014-08-01) :

Finally soldered a serial USB to TTL converter and played a little ...

I've tried to force to accept any firmware by entering the magic command:

ar7100> setenv accept_open_rt_fmt 1
ar7100> saveenv
Saving Environment to Flash...
Protect off BE040000 ... BE05FFFF
Un-Protecting sectors 2..2 in bank 1
Un-Protected 1 sectors
Erasing Flash...Erase Flash from 0xbe040000 to 0xbe05ffff in Bank # 1 First 0x2 las 100%
Erased 1 sectors
Writing to Flash...                                                                 100%
done
Protecting sectors 2..2 in bank 1
Protected 1 sectors
ar7100> reset

Resetting...




'cause at u-boot I first had something ending with:

[    2.040000] JFFS2 error: (1) jffs2_build_inode_pass1: child dir "firewall" (i        no #122) of dir ino #83 appears to be a hard link
[    2.050000] JFFS2 error: (1) jffs2_build_inode_pass1: child dir "ieee1394" (i        no #123) of dir ino #83 appears to be a hard link
[    2.060000] JFFS2 notice: (1) jffs2_build_xattr_subsystem: complete building         xattr subsystem, 0 of xdatum (0 unchecked, 0 orphan) and 0 of xref (0 dead, 0 or        phan) found.
[    2.080000] VFS: Mounted root (jffs2 filesystem) readonly on device 31:3.
[    2.080000] Freeing unused kernel memory: 212k freed
[    2.090000] Kernel panic - not syncing: No init found.  Try passing init= opt        ion to kernel. See Linux Documentation/init.txt for guidance.

Printenv command gave me this result:

ar7100> printenv
bootargs=console=ttyS0,115200 root=31:03 rootfstype=jffs2 init=/sbin/init mtdpar        ts=ar9100-nor0:256k(u-boot),128k(u-boot-env),1024k(uImage),31104k(rootfs),128k@3        2640k(ART),128k@32512k(properties)
bootcmd=bootm 0xbe060000
bootdelay=4
baudrate=115200
ethaddr=02:AA:BB:CC:DD:1A
tmp_ram=81F00000
tmp_bottom=83F00000
fw_eaddr=BE060000 BFFDFFFF
uboot_eaddr=BE000000 BE03FFFF
u_fw=erase $fw_eaddr; cp.b $fileaddr BE060000 $filesize; bootm BE060000;
ut_fw=tftp $tmp_ram firmware.bin; erase $fw_eaddr; cp.b $fileaddr BE060000 $file        size; bootm BE060000;
ut_uboot=tftp $tmp_ram u-boot.bin; protect off $uboot_eaddr; erase $uboot_eaddr;         cp.b $fileaddr BE000000 $filesize;
melco_id=RD_BB08009
hw_rev=0
tftp_wait=4
uboot_ethaddr=02:AA:BB:CC:DD:1A
DEF-p_wireless_ath0_11bg-authmode=psk
DEF-p_wireless_ath0_11bg-crypto=tkip+aes
DEF-p_wireless_ath0_11bg-authmode_ex=mixed-psk
custom_id=0
buf_ver=1.02
build_date=Feb 16 2009 - 10:47:08
pincode=07792083
DEF-p_wireless_ath0_11bg-wpapsk=xge7g3i1khc9m
buf_crc=DB71F11B
ipaddr=192.168.11.1
serverip=192.168.11.2
filesize=fffffe3e
fileaddr=81F00200
region=EU
stdin=serial
stdout=serial
stderr=serial
loadaddr=81F00000
ethact=eth1

Environment size: 1156/131068 bytes


The u-boot sequence via serial console, I now have the the following sequence:


BUFFALO U-BOOT Ver 1.02
AP83--539 (ar9100) U-boot 0.0.12
64 MB
Memory Test (address line)
Memory Test start(0x00000000) end(0x04000000) size(67108864)
Data line test start:0x00000000 pattern 0x00000001 0x00000003 0x00000007 0x0000000F 0x00000005 0x00000015 0x00000055 0xAAAAAAAA
Address line test start:0x00000000 len:0x4000000 pattern 0xAAAAAAAA 0x55555555
Fill test patnum:5
fill Pattern 5555AAAA  Writing...   Reading...
fill Pattern AAAA5555  Writing...   Reading...
fill Pattern 0000FFFF  Writing...   Reading...
fill Pattern FFFF0000  Writing...   Reading...
fill Pattern AAAAAAAA  Writing...   Reading...
Top of RAM usable for U-Boot at: 84000000
Reserving 250k for U-Boot at: 83fc0000
Reserving 256k for malloc() at: 83f80000
Reserving 44 Bytes for Board Info at: 83f7ffd4
Reserving 36 Bytes for Global Data at: 83f7ffb0
Reserving 128k for boot params() at: 83f5ffb0
Stack Pointer at: 83f5ff98
Now running in RAM - U-Boot at: 83fc0000
Dev ID2:2222
Name: AMD-SPANSION Flash id: 0x1227E, Size: 33554432 bytes.
Flash: 32 MB
In:    serial
Out:   serial
Err:   serial
Memory Test
uboot use  83F5FFB0 - 84000000
Memory Test start(80000000) end(83F00000) size(03F00000)
Pattern 00000000  Writing...  Reading...
Memory Test OK
### buf_ver=[1.02] U-Boot Ver.=[1.02]
### build_date(env)=[Feb 16 2009 - 10:47:08] build_date(bin)=[Feb 16 2009 - 10:47:08]
ag7100_enet_initialize...
: cfg1 0xf cfg2 0x7114
rtl8366sr_phy_setup  ethUnit=0
Realtek 8366SR switch ID 0x8366
Realtek Greeen Ethernet Setup
eth0: 02:aa:bb:cc:dd:1a
eth0 up
: cfg1 0xf cfg2 0x7114
eth1: 02:aa:bb:cc:dd:1a
eth1 up
eth0  02:AA:BB:CC:DD:1A
, eth1  02:AA:BB:CC:DD:1A

Trying eth0
eth0 is duplex
eth0 link down
FAIL
Trying eth1
eth1 link down
FAIL

tftp server(receive) go, waiting:4[sec]
Trying eth1
eth1 link down
FAIL
Trying eth0
eth0 is duplex
eth0 link down
FAIL
Load address: 0x81f00000

TftpServer Timeout;
Trying eth0
eth0 is duplex
eth0 link down
FAIL
Trying eth1
eth1 link down
FAIL
no file was loaded.
## Booting image at be060000 ...
Bad Magic Number
# LED(0x2) Blink[2] (Please press 'Ctrl+c' to stop)




I will try tomorrow to upload a new firmware ...

(Last edited by shadowman on 1 Aug 2014, 08:24)

Have uploaded the 12.09 squashfs tftp Attitude Adjustment .
Checking via serial during the installation phase, no problem occurred.
I don't know what have happened previously, it was the same firmware, the same upload procedure ...
But know it works.
I don't have changed anything, just put a secured SSH password (and forbidden access from wan for now, I will restore it later with encrypted keys access only), and activated WiFi through the GUI.

My new problem is on my ethernet workstation I can't access the Internet with Firefox nor IE, but no problem with Google Chrome. It's a static IP address (192.168.1.10X)
Nor do I have any problem with my android phone, DHCP bail brought me a 192.168.1.22X type address, I've been able to connect to playstore, to surf the internet with firefox for android etc.
I suppose it has something to do with my DNS settings, but I haven't changed anything yet since the installation ...
Do I have missed to do something basic ?


11/08
EDIT: never try to do something when under flu illness ... I had forgot to set the network mask ! Shame on me ...

(Last edited by shadowman on 11 Aug 2014, 10:20)

The discussion might have continued from here.