At the moment I have the v1.0.1 installed on my wrt1900ac, the v1.0.1 have a minor bugs, but for me it's ok, finally I can make static routes and the nat rules work fine.
I have problems when I try to put the same SSID in de 2 wireless frequencies (2.4 and 5) But with separate SSIDs works fine (I don´t think the "ac" standard work with 2 different SSIDs, I Don't know how to test it) .
The pre-release v1.0.4, is funcional ? can I flash the .img into my router ? Someone has already try it?
I know about routers, switch, and firewall's but I'm not a linux expert and I dont have the the USB cable to connect the router.

(Last edited by carlos.quiron on 11 Sep 2014, 14:08)

I recommend that you wait for the next full release. The pre-release is more for development purposes.

Roger that. Thanks again.

I'm still seeing 5ghz hangs with the GPL source driver

Are you running the McWRT distro release V1.0.1 (not pre-release) or a custom build?

I've tried just pressing the reset button, but it didn't seem to have any effect. I've also tried a 30/30/30 reset, which also had no effect. Each time, it still boots up with the same settings it had before.

Am I just missing something simple?

Press the recessed reset button until the power led flashes faster then release.

That did the trick. Thanks so much, Chadster! Also, thank you so much for your hard work on this.

I would like to say a big Thank You to the Belkin developers for their hard work. Without their opensouce code base and expertise I know I would have been lost

Except the fact that requesting the 8.x driver source has been met with radio silence, since 7.x still has some bugs

I could not get it too work too.

Useing this http://wiki.openwrt.org/doc/recipes/guest-wlan

Thank you for your work Chadster766!

Build yesterday your McWRT, flash it on the Router and restart. I got some issues:

- The WebGUI did not work, all i got was a "Index of" Webpage. I used a telnet connection at workaround and configure the network the wlan and make a test.

All worked very very well.

- Later i thought i had a misconfiguration because i could not ping6 the internet or my ipv6 network as expected. So i do this and that.. and restart the Network.. yes and that break it. Did not expect that i break the whole configuration of my bridge interface.

- The mistake i made was probably to wrote the ip6 addresses as CIDR Notation with /64 or /128 in the /etc/config/network file.

- So restarting the Network itself break my ssh connection and now i had no access on my router. Any Suggestions how to reset all Configuration files so that i could fix this up?

- Actually i have no response from the Router, checked with wireshark.  I try to push the Reset button as suggested but it seems that this did not reset network Settings.

I was surprised to see no incoming Messages in wireshark at all. Even after holding the Reset Button and the Powerlight blinking faster.. i got no response to wireshark, and had no success with a ping on 192.168.1.1 or 192.168.200.1

Did i BRICK my Router? Or could i flash it again during Tftp Boot?

The Internet Device eth1 have no Running ssh or telnet Client so that i could use that interface?

(Last edited by Jolly on 12 Sep 2014, 00:29)

Try get it to revert to the alternate image by turning on and off 4 times fairly quickly.

Also the router is always recoverable using a $9.00 USB to TTL cable to access the boot loader through the serial console.

(Last edited by Chadster766 on 12 Sep 2014, 01:09)

Hi its me, i am back again! Play some more time around and found that the device used the Neighbor Discovery Protocol to communicate his fe80... neighbour Ipv6 Address. And BINGO since i configured dropbear and used my public ssh key as login i could log in with this:

$ ssh root@fe80:....%eth1

The fe80 Addresses are special so you have to add the device from where the connection starts. Here eth1 on my System. I anonymized the full Link-Local-Adress of the routers with the ... dots.

That's very cool.

If you load the pre-release you can install the dhcp6-client package. I think this is what you were looking for before.

Hi, I need help of my bricked  WRT1900 AC. Can anyone help me please?I have problem when I use TTL to flash the openwrt firmware from grub to it. I do everything according to the first page using ttl, but the putty always showing:
Loading: T T T T T T T T T T Retry count exceeded; starting again. 
The tftpd32 is hooked up to my with with IP 192.168.200.20. The firmware is in the same file with tftpd32.

Marvell>> setenv firmware_name abcd.img
Marvell>> setenv ipaddr 192.168.200.1
Marvell>> setenv serverip 192.168.200.20
Marvell>> run flash_pri_image
mvNetaSpeedDuplexSet
Using egiga0 device
TFTP from server 192.168.200.20; our IP address is 192.168.200.1
Filename 'abcd.img'.
Load address: 0x2000000
Loading: T T T T T T T T T T
Retry count exceeded; starting again

NAND erase: device 0 offset 0xa00000, size 0x4000000
Erasing at 0x49e0000 -- 100% complete.
OK

NAND write: device 0 offset 0xa00000, size 0x1e00000
31457280 bytes written: OK

Marvell>> printenv
CASset=min
MALLOC_len=5
MPmode=smp
alt_kern_addr=0x3200000
alt_kern_size=0x400000
altnandboot=run linksys_altnandboot
amp_enable=no
auto_recovery=no
autoload=no
badcount=0
baudrate=115200
boot_order=hd_scr hd_img pxe net_img net_scr
boot_part=2
boot_part_ready=3
bootargs=console=ttyS0,115200 mtdparts=armada-nand:1024K(uboot)ro,256K(u_env),256K(s_env),1m@9m(devinfo),40m@10m(kernel),37m@13m(rootfs),40m@50m(alt_kernel),37m@53m(alt_rootfs),80m@10m(ubifs),-@90m(syscfg) root=/dev/nfs rw nfsroot=192.168.200.20:/home/work/AXP/fs/rootfs ip=192.168.200.1:192.168.200.20:10.4.50.254:255.255.255.0:DSMP:eth0:none mv_net_config=4,(00:50:43:11:11:11,0:1:2:3),mtu=1500 video=dovefb:lcd0:640x480-16@60 clcd.lcd0_enable=0 clcd.lcd_panel=0
bootargs_dflt=$console $mtdparts $bootargs_root nfsroot=$serverip:$rootpath ip=$ipaddr:$serverip$bootargs_end $mvNetConfig video=dovefb:lcd0:$lcd0_params clcd.lcd0_enable=$lcd0_enable clcd.lcd_panel=$lcd_panel
bootargs_end=:10.4.50.254:255.255.255.0:DSMP:eth0:none
bootargs_root=root=/dev/nfs rw
bootbadcount=0
bootcmd=tftpboot
bootcmd_auto=stage_boot $boot_order
bootcmd_bak=stage_boot $boot_order
bootcmd_lgcy=tftpboot 0x2000000 $image_name; setenv bootargs $bootargs_dflt; bootm 0x2000000;
bootdelay=3
buffbadcount=0
cacheShare=no
console=console=ttyS0,115200
default_load_addr=0x2000000
default_mtdparts=mtdparts=armada-nand:1024K(uboot)ro,256K(u_env),256K(s_env),1m@9m(devinfo),40m@10m(kernel),37m@13m(rootfs),40m@50m(alt_kernel),37m@53m(alt_rootfs),80m@10m(ubifs),-@90m(syscfg)
device=1
device_partition=0:1
disL2Cache=yes
disL2Prefetch=yes
disaMvPnp=no
eeeEnable=no
enaAutoRecovery=yes
enaClockGating=no
enaCpuStream=no
enaDCPref=yes
enaFPU=yes
enaICPref=yes
enaLPAE=no
enaWrAllo=no
eth1addr=00:50:43:02:00:00
eth1mtu=1500
eth2addr=00:50:43:00:00:02
eth2mtu=1500
eth3addr=00:50:43:00:02:02
eth3mtu=1500
ethact=egiga0
ethaddr=B4:75:0E:5B:62:94
ethmtu=1500
ethprime=egiga0
fdt_addr=2040000
fileaddr=2000000
filesize=0x1e00000
firmaware_name=abcd.img
firmware_name=abcd.img
flash_alt_image=tftp $default_load_addr $firmware_name; nand erase $alt_kern_addr 0x4000000;nand write $default_load_addr $alt_kern_addr ${filesize};
flash_pri_image=tftp $default_load_addr $firmware_name; nand erase $pri_kern_addr 0x4000000;nand write $default_load_addr $pri_kern_addr ${filesize};
flash_ubi_image=mw.b 0x2000000 0x00 0x1e00000;tftp $default_load_addr blk-mamba.128mb.ubi.img; nand erase $pri_kern_addr 0x3600000; nand write $default_load_addr $pri_kern_addr 0x3600000
fs=ext2
fs_bootargs=console=ttyS0,115200 mtdparts=armada-nand:1024K(uboot)ro,256K(u_env),256K(s_env),256K(devinfo),4M(Linux),31M(rootfs),4M(Linux2),31M(rootfs2),-(syscfg)
fs_bootargs_root=ubi.mtd=6 root=ubi0:rootfs rootfstype=ubifs rootflags=sync
fs_type=jffs2
ide_path=/
image_name=uImage
initrd_name=uInitrd
interface=ide
ipaddr=192.168.200.1
jffs2_mtdparts=mtdparts=armada-nand:1024K(uboot)ro,256K(u_env),256K(s_env),1m@9m(devinfo),40m@10m(kernel),37m@13m(rootfs),40m@50m(alt_kernel),37m@53m(alt_rootfs),80m@10m(ubifs),-@90m(syscfg)
kernel_addr_r=2080000
lcd0_enable=0
lcd0_params=640x480-16@60
lcd_panel=0
linksys_altnandboot=nand read $default_load_addr $alt_kern_addr $alt_kern_size; setenv bootargs $console $default_mtdparts root=/dev/mtdblock7 ro rootfstype=$fs_type init=/sbin/init; bootm $default_load_addr;
linksys_nandboot=nand read $default_load_addr $pri_kern_addr $pri_kern_size; setenv bootargs $console $default_mtdparts root=/dev/mtdblock5 ro rootfstype=$fs_type init=/sbin/init; bootm $default_load_addr;
loadaddr=0x02000000
loads_echo=0
mfg_fs_bootargs=console=ttyS0,115200 mtdparts=armada-nand:640k(uboot)ro,128k@640k(u_env),128k@768k(s_env),3m@1m(kernel),16m@4m(rootfs),1m@20m(syscfg),4m@21m(data),3m@25m(alt_kernel),16m@28m(alt_rootfs),20m@44m(downloads)
mtddevname=uboot
mtddevnum=0
mtdids=nand0=armada-nand
mtdparts=mtdparts=armada-nand:1024K(uboot)ro,256K(u_env),256K(s_env),1m@9m(devinfo),40m@10m(kernel),37m@13m(rootfs),40m@50m(alt_kernel),37m@53m(alt_rootfs),80m@10m(ubifs),-@90m(syscfg)
mvNetConfig=mv_net_config=4,(00:50:43:11:11:11,0:1:2:3),mtu=1500
mv_pon_addr=00:50:43:00:00:02
nandEcc=1bit
nandboot=run linksys_nandboot
netbsd_en=no
netmask=255.255.255.0
netretry=no
nfsboot=tftpboot $default_load_addr $image_name; setenv bootargs $fs_bootargs $bootargs_root nfsroot=$serverip:$rootpath ip=$ipaddr:$serverip$bootargs_end $mvNetConfig; bootm $default_load_addr
openwrt_altnandboot=nand read $default_load_addr $alt_kern_addr $openwrt_fw_size; setenv bootargs $console $default_mtdparts root=/dev/mtdblock7 ro rootfstype=$fs_type init=/sbin/init; bootm $default_load_addr;
openwrt_fw_size=0x4000000
openwrt_mtdparts=mtdparts=armada-nand:1024K(uboot)ro,256K(u_env),256K(s_env),1m@9m(devinfo),40m@10m(kernel),37m@13m(rootfs),40m@50m(alt_kernel),37m@53m(alt_rootfs),80m@10m(ubifs),-@90m(syscfg)
openwrt_nandboot=nand read $default_load_addr $pri_kern_addr $openwrt_fw_size; setenv bootargs $console $default_mtdparts root=/dev/mtdblock5 ro rootfstype=$fs_type init=/sbin/init; bootm $default_load_addr;
partition=nand0,0
pcieTune=no
pexMode=rc
prefix=/boot/
pri_kern_addr=0xa00000
pri_kern_size=0x400000
pxe_files_load=:default.arm-armadaxp-db:default.arm-armadaxp:default.arm
pxefile_addr_r=3100000
ramdisk_addr_r=2880000
rcvrip=169.254.100.100
rootpath=/home/work/AXP/fs/rootfs
sata_delay_reset=0
sata_dma_mode=yes
script_addr_r=3000000
script_name=boot.scr
senvbadcount=0
server=192.168.200.20
serverip=192.168.200.20
standalone=fsload 0x2000000 $image_name;setenv bootargs $console $mtdparts root=/dev/mtdblock0 rw ip=$ipaddr:$serverip$bootargs_end; bootm 0x2000000;
stderr=serial
stdin=serial
stdout=serial
ubiboot=nand read $default_load_addr $pri_kern_addr $pri_kern_size; setenv bootargs $console $jffs2_mtdparts root=ubi0:rootfs rw ubi.mtd=8 rootfstype=ubifs init=/sbin/init; bootm $default_load_addr;
uenvbadcount=0
update_both_images=run flash_pri_image;run flash_alt_image
usb0Mode=host
usb1Mode=host
usb2Mode=device
usbActive=0
vxworks_en=no
yuk_ethaddr=00:00:00:EE:51:81

Environment size: 6266/262140 bytes

Does anybody have IPv6 functional on any of the Chadster builds using DHCP6-PD from their provider? 

I'm having a few issues.  First, the default route being sent by my provider (as shown by "ifstatus wan6") is not actually getting added as a default route, thus I have to manually add it before I can ping out or hit IPv6-only hosts from the router itself.

Second, my internal systems are getting the OpenWRT router as the gateway with their delegated address (in the correct 2601:...: range), but I can't ping any farther than the router even though as far as I can tell I have forwarding turned on and I have the firewall set up to allow all traffic from LAN to WAN.

Any suggestions here?  Things to try?  I have two WRT1900AC's so that I can use one for testing, so willing to risk a temporary brick if that's what it takes to figure it out.

Also, Chad, it appears the latest 1.04 Prerelease using the Luci trunk is missing the "IPv6 RA and DHCPv6 tab" from Luci, whereas the previous 1.01 build had it.  Don't think this is related to my issue but doesn't make it any easier to diagnose.

I have installed dhcp6-client and it doesn't seem to make a difference.

It would be helpful to have the tcpdump package available (and libpcap) so that packet dumps are available for debugging.

I did a comparison of your printenv and mine.

Variables that differ:

bootargs=console=ttyS0,115200 mtdparts=armada-nand:1024K(uboot)ro,256K(u_env),256K(s_env),1m@9m(devinfo),40m@10m(kernel),37m@13m(rootfs),40m@50m(alt_kernel),37m@53m(alt_rootfs),80m@10m(ubifs),-@90m(syscfg) root=/dev/mtdblock7 ro rootfstype=jffs2 init=/sbin/init

bootcmd=run nandboot

Variables that don't exist in my printenv:

mtddevname=uboot
mtddevnum=0
partition=nand0,0

The bootcmd variable could be "run altnandboot" defending on which image is set active.

The message you are getting "Loading: T T T T T T T T T T" means the router can't connect to the tftp server.

(Last edited by Chadster766 on 13 Sep 2014, 09:27)

I will add the tcpdump and libpcap packages if I can and check into the other IPv6 packages.

Done

Quick note I did some IPv6 testing on the pre-release and discovered that the IPv6 address on eth1 will disconnect and reconnect frequently. To see this do repeated "ifconfig eth1" and every so often the IPv6 address won't show.

Keep in mind that the Pre-release is just to testing and development.

Hi, I have managed to screw up bad with the firmware. I changed a setting in firewall where you had a choise of lan, wan and something else and changed it to wan and now I can't log into router. I have alredy ordered a usb to tll cable but is there anyway to reset the settings completely or what do I do when I log on with cable? Otherwise thanks alot for you amazing work on this.

Nb. I was trying to put a console in dmz.

@alkufai

Keep the recessed reset button on the back of the router until the power led blinks then release it.

nitroshift

Alredy tried that it did not work. Also the place i changed was in the first screen where it shows connections to router, hit the edit button on ethernet and in there was a sub meny regarding firewall, i picked the second one which was wan.

You might have delete the lan interface. Try the below to manually switch to the alternate firmware image:
https://github.com/Chadster766/McWRT/wi … s-firmware

For users that don't have the USB to TTL cable its best if you always flash OpenWRT from the Linksys firmware. This way you always have the Linksys stock firmware in the alternate image. It's and extra step but some assurance that you can recover from a lockup in the firmware.