Okay, I downloaded the main trunk rev 38812 since that's where latest commits seemed to be made, compiled from scratch and sure enough got a working image! Loaded it onto the router and boots like a champ. I have yet to play around and do full testing but it's looking pretty good.

Only question is... what happened to the extra NAND space? Currently I'm seeing:
[    0.540000] 12 cmdlinepart partitions found on MTD device ar934x-nfc
[    0.550000] Creating 12 MTD partitions on "ar934x-nfc":
[    0.560000] 0x000000000000-0x000000040000 : "u-boot"
[    0.560000] 0x000000040000-0x000000080000 : "u-boot-env"
[    0.570000] 0x000000080000-0x0000000c0000 : "caldata"
[    0.580000] 0x0000000c0000-0x000000140000 : "pot"
[    0.580000] 0x000000140000-0x000000340000 : "language"
[    0.590000] 0x000000340000-0x0000003c0000 : "config"
[    0.600000] 0x0000003c0000-0x0000006c0000 : "traffic_meter"
[    0.600000] 0x0000006c0000-0x0000008c0000 : "kernel"
[    0.610000] 0x0000008c0000-0x000001fc0000 : "ubiroot"
[    0.620000] 0x0000006c0000-0x000001fc0000 : "firmware"
[    0.940000] 0x000001fc0000-0x000002000000 : "caldata_backup"
[    0.950000] 0x000002000000-0x000008000000 : "reserved"

And when I check mount, I get:
rootfs on / type rootfs (rw)
/dev/root on /rom type squashfs (ro,relatime)
proc on /proc type proc (rw,noatime)
sysfs on /sys type sysfs (rw,noatime)
tmpfs on /tmp type tmpfs (rw,nosuid,nodev,noatime)
tmpfs on /tmp/root type tmpfs (rw,noatime,mode=755)
tmpfs on /dev type tmpfs (rw,relatime,size=512k,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
debugfs on /sys/kernel/debug type debugfs (rw,noatime)
/dev/mtdblock13 on /overlay type jffs2 (rw,noatime)
overlayfs:/overlay on / type overlayfs (rw,noatime,lowerdir=/,upperdir=/overlay)

but df shows me only 17.3 + 16.7 for ~32MB.... did I miss something, or is there a reason we don't get the full 128?...
Filesystem                Size      Used Available Use% Mounted on
rootfs                   17.3M    640.0K     16.7M   4% /
/dev/root                 2.3M      2.3M         0 100% /rom
tmpfs                    61.8M     56.0K     61.7M   0% /tmp
tmpfs                    61.8M     16.0K     61.7M   0% /tmp/root
tmpfs                   512.0K         0    512.0K   0% /dev
/dev/mtdblock13          17.3M    640.0K     16.7M   4% /overlay
overlayfs:/overlay       17.3M    640.0K     16.7M   4% /

It is lightning fast boot time by the way though, caught me off guard as I was still waiting for it to finish!

What more needs to be done to get builds to start showing up in http://downloads.openwrt.org/snapshots/trunk/ar71xx/   ??

I've investigated WNDR4300 wiki and this thread (thanks God, its only 4 pages).
However, it seems that I'd "semi-bricked" my wndr4300.
It lost 5GHz wifi chip totally.
From dmesg log (comparing with the one posted in wiki) I see that it just doesn't 'touch' PCI  bus: http://pastebin.com/3skQavwf
So, it can't find the 5GHz wifi chip, and doesn't initialize it.

When trying to make 'factory restore' (with oem flash downloaded from netgear and flashed using tftp client) I get 'eternal loop' of rebooting: all leds for 1 sec, then amber power for 3 secs, then amber power +LAN1 (where I am connected) for about 10 secs, then repeat).

However, if the factory restore is not possible, that is ok. I mainly looking into surviving with 5GHz wifi.
I've tried to put trace calls into the sources (like: printk ("pci_init invoked\n"); ) into the kernel sources.
I've found that the problem arises in these lines:

        bootstrap = ath79_reset_rr(AR934X_RESET_REG_BOOTSTRAP);
        if ((bootstrap & AR934X_BOOTSTRAP_PCIE_RC) == 0)
            return -ENODEV;

That lines organizes shortpath with ENODEV which is literally in use.
(that is in build_dir/target-mips_34kc_uClibc-0.9.33.2/linux-ar71xx_nand/linux-3.10.24/arch/mips/ath79/pci.c)
Does any similar problem exists? Or I am alone with it?

Did you turn it off and on again after it starts looping?  I think I get the same thing when I flash the stock firmware, but it will boot normally after I turn it off.

TheAsp, no.
However today's morning I've rebuilt again openwrt with freshest trunk (BARRIER BREAKER (Bleeding Edge, r39183)).
The first boot was the same (i.e. no PCI).
But after on/off all became ok (http://pastebin.com/JdS4iPFM). I believe, now I quite understand what is the meaning of the boolean named 'bootstrap' in the kernel source.
I would add 'switch it off, wait a bit, then switch on' to the flash instruction, since such initial bootstrapping cause a confusion (I really played about two days placing trace marks into kernel sources).

I am a bit confused whether the generated image for the WNDR4300 will work on my WNDR3700v4 or not. I have the same problems trying to upload it to the WNDR3700v4 as checksum and johndoe (tftp does nothing and stock web interface says "invalid image").

Can someone confirm that trunk built for the WNDR4300 works on the WNDR3700v4 as well?

Thanks!

Hello everyone,

i am very new to openwrt and its build envronment. But i can confirm that trunk build for wndr4300 works on wndr3700v4 as well (with small modification).

@mauritzius: there is a code block in ./target/linux/ar71xx/image/Makefile looking like this:

    $(STAGING_DIR_HOST)/bin/mkdniimg \
        -B $(6) -v OpenWrt.$(REVISION) -r "$$$$r" $(8) \
        -i $(imageraw) \
        -o $(call imgname,ubi,$(2))-factory.img

i changed it to:

    $(STAGING_DIR_HOST)/bin/mkdniimg \
        -B WNDR3700v4 -v OpenWrt.$(REVISION) -r "$$$$r" -H "29763948+128+128" \
        -i $(imageraw) \
        -o $(call imgname,ubi,$(2))-factory.img

and this workes for me being able to upload the file to the stock gui and successfully flash it.
After that i was able to reach openwrts gui at 192.168.1.1. I tested nothing else and i do not say that it will work as expected.

@falstaff and Zsub: Many thanks to your work.

@ nerbstoff:
what is the meaning of

-H "29763948+128+128" 

?
Is it connected to the amount of available flash space?

it is netgears hardware id for wndr3700v4. And yes it could be connected to the amount of flash and ram as well since the wndr3700v4 has 128MiB of Flash and 128MiB of Ram. I think that the first number is somethink like the id of the pcb because it is the same to wndr4300.

The extra nand space is in mtdblock11, check also the OpenWRT flash layout on http://wiki.openwrt.org/toh/netgear/wndr4300  (the second one, the first layout is the Netgear one)

You might try to use mtdblock11 als overlay. I think it is by default reserved for Netgear stuff (/apps), so you probably will lose that.

Following is from memory, so no guarantee whatsoever ;-)
Also, I just tested this once on a test router; no idea whether it will work (nor for how long) on a production router.

first temporalily mount mtdblock11 somewhere, /mnt/mtdblock11 for instance

mount -t jffs2 /dev/mtdblock11 /mnt/mtdblock11

then copy everything from /overlay to /mnt/mtdblock11

tar -C /overlay -cvf - . | tar -C /mnt/mtdblock11 -xf -

then add the folowing before exit 0 in your /etc/rc.local

umount /overlay
sleep 5
mount -t jffs2 /dev/mtdblock11 /overlay

then reboot

It would be nice to mount the new overlay earlier in the boot proces. Don't know how, so far.

/edit:
added those lines to the very last section of /etc/init.d/boot, just before the }

        # create /dev/root if it doesn't exist
        [ -e /dev/root -o -h /dev/root ] || {
                rootdev=$(awk 'BEGIN { RS=" "; FS="="; } $1 == "root" { print $2 }' < /proc/cmdline)
                [ -n "$rootdev" ] && ln -s "$rootdev" /dev/root
        }

umount /overlay
sleep 5
mount -t jffs2 /dev/mtdblock11 /overlay

}

Seems to work, so far...

/edit2:
Unfortunately, it doesn't...

(Last edited by IcyK on 23 Feb 2014, 17:33)

If anyone is interested in an running image for the WNDR3700v4 you can find it here:
ar71xx-nand-wndr3700v4-ubi-factory.img
This image can be applied directly through the original Netgear GUI.

Cheers.

(Last edited by rpsoft on 18 Jan 2014, 23:24)

Can someone please build device image including
CONFIG_PACKAGE_wireless-tools=y

I'd like to see "iw list" and "iwconfig" info for this device (and for the WNDR4300).
I don't have the device myself and if it has good signal strength, I might move to it.

Thank you,
chhatc

(Last edited by chhatc on 21 Jan 2014, 08:21)

Thank you very much! Update went smooth, the system booted into OpenWrt and is now reachable via telnet.

Is this helpfull (WNDR3700v4) ?

root@OpenWrt:/# iw list
Wiphy phy1
    max # scan SSIDs: 4
    max scan IEs length: 2261 bytes
    Coverage class: 0 (up to 0m)
    Available Antennas: TX 0x3 RX 0x3
    Configured Antennas: TX 0x3 RX 0x3
    Supported interface modes:
         * IBSS
         * managed
         * AP
         * AP/VLAN
         * WDS
         * monitor
         * mesh point
         * P2P-client
         * P2P-GO
    Band 2:
        Capabilities: 0x11ef
            RX LDPC
            HT20/HT40
            SM Power Save disabled
            RX HT20 SGI
            RX HT40 SGI
            TX STBC
            RX STBC 1-stream
            Max AMSDU length: 3839 bytes
            DSSS/CCK HT40
        Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
        Minimum RX AMPDU time spacing: 8 usec (0x06)
        HT TX/RX MCS rate indexes supported: 0-15
        Frequencies:
            * 5180 MHz [36] (17.0 dBm)
            * 5200 MHz [40] (17.0 dBm)
            * 5220 MHz [44] (17.0 dBm)
            * 5240 MHz [48] (17.0 dBm)
            * 5260 MHz [52] (24.0 dBm) (passive scanning, no IBSS, radar detection)
              DFS state: usable (for 4294735 sec)
            * 5280 MHz [56] (24.0 dBm) (passive scanning, no IBSS, radar detection)
              DFS state: usable (for 4294735 sec)
            * 5300 MHz [60] (24.0 dBm) (passive scanning, no IBSS, radar detection)
              DFS state: usable (for 4294735 sec)
            * 5320 MHz [64] (24.0 dBm) (passive scanning, no IBSS, radar detection)
              DFS state: usable (for 4294735 sec)
            * 5500 MHz [100] (24.0 dBm) (passive scanning, no IBSS, radar detection)
              DFS state: usable (for 4294735 sec)
            * 5520 MHz [104] (24.0 dBm) (passive scanning, no IBSS, radar detection)
              DFS state: usable (for 4294735 sec)
            * 5540 MHz [108] (24.0 dBm) (passive scanning, no IBSS, radar detection)
              DFS state: usable (for 4294735 sec)
            * 5560 MHz [112] (24.0 dBm) (passive scanning, no IBSS, radar detection)
              DFS state: usable (for 4294735 sec)
            * 5580 MHz [116] (24.0 dBm) (passive scanning, no IBSS, radar detection)
              DFS state: usable (for 4294735 sec)
            * 5600 MHz [120] (disabled)
            * 5620 MHz [124] (disabled)
            * 5640 MHz [128] (disabled)
            * 5660 MHz [132] (24.0 dBm) (passive scanning, no IBSS, radar detection)
              DFS state: usable (for 4294735 sec)
            * 5680 MHz [136] (24.0 dBm) (passive scanning, no IBSS, radar detection)
              DFS state: usable (for 4294735 sec)
            * 5700 MHz [140] (24.0 dBm) (passive scanning, no IBSS, radar detection)
              DFS state: usable (for 4294735 sec)
            * 5745 MHz [149] (30.0 dBm)
            * 5765 MHz [153] (30.0 dBm)
            * 5785 MHz [157] (30.0 dBm)
            * 5805 MHz [161] (30.0 dBm)
            * 5825 MHz [165] (30.0 dBm)
    valid interface combinations:
         * #{ managed, WDS, P2P-client } <= 2048, #{ AP, mesh point, P2P-GO } <= 8, #{ IBSS } <= 1,
           total <= 2048, #channels <= 1, STA/AP BI must match
         * #{ IBSS, AP } <= 1,
           total <= 1, #channels <= 1, STA/AP BI must match, radar detect widths: { 20 MHz (no HT), 20 MHz }

    HT Capability overrides:
         * MCS: ff ff ff ff ff ff ff ff ff ff
         * maximum A-MSDU length
         * supported channel width
         * short GI for 40 MHz
         * max A-MPDU length exponent
         * min MPDU start spacing
Wiphy phy0
    max # scan SSIDs: 4
    max scan IEs length: 2257 bytes
    Coverage class: 0 (up to 0m)
    Available Antennas: TX 0x3 RX 0x3
    Configured Antennas: TX 0x3 RX 0x3
    Supported interface modes:
         * IBSS
         * managed
         * AP
         * AP/VLAN
         * WDS
         * monitor
         * mesh point
         * P2P-client
         * P2P-GO
    Band 1:
        Capabilities: 0x11ef
            RX LDPC
            HT20/HT40
            SM Power Save disabled
            RX HT20 SGI
            RX HT40 SGI
            TX STBC
            RX STBC 1-stream
            Max AMSDU length: 3839 bytes
            DSSS/CCK HT40
        Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
        Minimum RX AMPDU time spacing: 8 usec (0x06)
        HT TX/RX MCS rate indexes supported: 0-15
        Frequencies:
            * 2412 MHz [1] (27.0 dBm)
            * 2417 MHz [2] (27.0 dBm)
            * 2422 MHz [3] (27.0 dBm)
            * 2427 MHz [4] (27.0 dBm)
            * 2432 MHz [5] (27.0 dBm)
            * 2437 MHz [6] (27.0 dBm)
            * 2442 MHz [7] (27.0 dBm)
            * 2447 MHz [8] (27.0 dBm)
            * 2452 MHz [9] (27.0 dBm)
            * 2457 MHz [10] (27.0 dBm)
            * 2462 MHz [11] (27.0 dBm)
            * 2467 MHz [12] (disabled)
            * 2472 MHz [13] (disabled)
            * 2484 MHz [14] (disabled)
    valid interface combinations:
         * #{ managed, WDS, P2P-client } <= 2048, #{ AP, mesh point, P2P-GO } <= 8, #{ IBSS } <= 1,
           total <= 2048, #channels <= 1, STA/AP BI must match
         * #{ IBSS, AP } <= 1,
           total <= 1, #channels <= 1, STA/AP BI must match, radar detect widths: { 20 MHz (no HT), 20 MHz }

    HT Capability overrides:
         * MCS: ff ff ff ff ff ff ff ff ff ff
         * maximum A-MSDU length
         * supported channel width
         * short GI for 40 MHz
         * max A-MPDU length exponent
         * min MPDU start spacing

YES!
Thank you, seems quite powerful 27dBm on the 2.4GHz and 30dBm on the upper 5GHz (atleast on the channels which matter to me).
How is the range? Do you have any other router device to compare with?

If you've got a windows box, you can get an idea of running two different routers at the same channel at max output power and see how they fare on inSSIDer (you can google inssider 3 home edition and I'm sure you should be able to find links... that's if you didn't already know about it).

Regards,
chhatc

(Last edited by chhatc on 24 Jan 2014, 05:42)

So what about this (and the WNDR4300) is missing to finalize OpenWrt support?
I read in the openwrt developers list the sysupgrade is the only thing that is not functioning due to the NAND flash.

Is this correct?

Thanks,
chhatc

thx very much.
but anyways to add vpn server to this kernel?

The provided image is nearly naked so you can configure it as you want,
Have a look at the packages here to see what is available to install.

--
Ralph

(Last edited by rpsoft on 24 Jan 2014, 21:01)

Not much. But compared with the NetGear WNR2000v4 or WNR2200v3 the signal range seems higher and stronger.
I think it's a good router to work with, except the NAND flash.

--
Ralph

You can configure your own build and build it into the flashable image yourself.

sorry, i am new to oepnwrt
when i try to install pptpd, it return an error, anyways to fix it?
thanks

Installing pptpd (1.3.4-2) to root...
Downloading http://downloads.openwrt.org/snapshots/ … r71xx.ipk.
Multiple packages (kmod-ppp and kmod-ppp) providing same name marked HOLD or PREFER. Using latest.
Multiple packages (kmod-ipv6 and kmod-ipv6) providing same name marked HOLD or PREFER. Using latest.
Multiple packages (kmod-ppp and kmod-ppp) providing same name marked HOLD or PREFER. Using latest.
Multiple packages (kmod-crypto-core and kmod-crypto-core) providing same name marked HOLD or PREFER. Using latest.
Multiple packages (kmod-crypto-arc4 and kmod-crypto-arc4) providing same name marked HOLD or PREFER. Using latest.
Multiple packages (kmod-crypto-hash and kmod-crypto-hash) providing same name marked HOLD or PREFER. Using latest.
Multiple packages (kmod-crypto-core and kmod-crypto-core) providing same name marked HOLD or PREFER. Using latest.
Multiple packages (kmod-crypto-hash and kmod-crypto-hash) providing same name marked HOLD or PREFER. Using latest.
Multiple packages (kmod-crypto-core and kmod-crypto-core) providing same name marked HOLD or PREFER. Using latest.
Multiple packages (kmod-crypto-core and kmod-crypto-core) providing same name marked HOLD or PREFER. Using latest.
Multiple packages (kmod-crypto-core and kmod-crypto-core) providing same name marked HOLD or PREFER. Using latest.
Collected errors:
* satisfy_dependencies_for: Cannot satisfy the following dependencies for pptpd:
*     kernel (= 3.10.26-1-548d78d28805708a9747d14c925af282) *     kernel (= 3.10.26-1-548d78d28805708a9747d14c925af282) *     kernel (= 3.10.26-1-548d78d28805708a9747d14c925af282) *     kernel (= 3.10.26-1-548d78d28805708a9747d14c925af282) *     kernel (= 3.10.26-1-548d78d28805708a9747d14c925af282) *     kernel (= 3.10.26-1-548d78d28805708a9747d14c925af282) *     kernel (= 3.10.26-1-548d78d28805708a9747d14c925af282) *
* opkg_install_cmd: Cannot install package pptpd.

I have the same problem, when I try to install some packages I get some errors:
Collected errors:
* opkg_install_cmd: Cannot install package kmod-openswan.
* opkg_install_cmd: Cannot install package openswan.
* satisfy_dependencies_for: Cannot satisfy the following dependencies for ipsec-tools:
*      kernel (= 3.10.28-1-973615e2eb7786ede8048a627eb75438) *         kernel (= 3.10.28-1-973615e2eb7786ede8048a627eb75438) *         kernel (= 3.10.28-1-973615e2eb7786ede8048a627eb75438) * kernel (= 3.10.28-1-973615e2eb7786ede8048a627eb75438) *  kernel (= 3.10.28-1-973615e2eb7786ede8048a627eb75438) *         kernel (= 3.10.28-1-973615e2eb7786ede8048a627eb75438) *         kernel (= 3.10.28-1-973615e2eb7786ede8048a627eb75438) *  kernel (= 3.10.28-1-973615e2eb7786ede8048a627eb75438) *         kernel (= 3.10.28-1-973615e2eb7786ede8048a627eb75438) *         kernel (= 3.10.28-1-973615e2eb7786ede8048a627eb75438) *  kernel (= 3.10.28-1-973615e2eb7786ede8048a627eb75438) *         kernel (= 3.10.28-1-973615e2eb7786ede8048a627eb75438) *         kernel (= 3.10.28-1-973615e2eb7786ede8048a627eb75438) *  kernel (= 3.10.28-1-973615e2eb7786ede8048a627eb75438) *
* opkg_install_cmd: Cannot install package ipsec-tools.

Can I update my openwrt kernel?
I'm using the image given on #87, which includes kernel 3.10.24. All kernel module packages require current kernel, 3.10.28 today. When will be generated a stable build with wndr3700v4 support?

What should I do to use current snapshot?
Compile from git source (this one? https://github.com/mirrors/openwrt.git) save a copy of all packages and configure openwrt to access the copy?

(Last edited by scc on 3 Feb 2014, 14:12)

I'm not sure how to compile the kernel (router wndr3700v4).
I have downloaded latest openwrt source from https://github.com/mirrors/openwrt.git
Then I removed 'broken' word from file target/linux/ar71xx/nand/target.mk
Is the NAND subtarget you said this one?: Mikrotik devices with NAND flash

Here are 3 screen captures:
https://www.dropbox.com/s/qx4njyhqlm2ob … nfig-1.png
https://www.dropbox.com/s/3ugy1pqb8awhn … nfig-2.png
https://www.dropbox.com/s/boa9wvb1hy664 … nfig-3.png

Do I have to configure anything else or with the default configuration it should work?

If I make a mistake configuring kernel and upload it using UTFT, can the router be bricked forever or is always possible to upload a new image using utft because the boot program is never overwritten?

In spite of editing the target.mk and removing broken I needed to selected Advanced configuration options (for developers) and Show broken platforms/packages in order to get the Generic NAND and WNDR4300 options available.

To build your own version of WNDR3700v4 image you can apply my patch to get a separate configuration for this device.
After this you can choose the device directly by name in the "make menuconfig".
--
Ralph

(Last edited by rpsoft on 4 Feb 2014, 21:57)