Just a warning, latest trunk bricked my r8000.
I don't have a ttl so I can't provide more information.

Are you sure you used the latest trunk? Which revision/commit did you compile?

Zajec wrote:

Are you sure you used the latest trunk? Which revision/commit did you compile?

I don't compile myself, I download the daily build from downloads.openwrt.org. Its md5sum is 6a0db016a1d013668480ca7e491830a6.

I don't compile myself, I download the daily build from downloads.openwrt.org. Its md5sum is 6a0db016a1d013668480ca7e491830a6. So you didn't use the latest trunk revision at all.

You used image generated by following build:
http://buildbot.openwrt.org:8010/builde … builds/269
which was abb09a1a965dbd83fd9d1e96459d39f30bbbd669 AKA r49158.

Revision you tested contained a regression that was fixed by r49159. Make sure to use build of revision 49159 or newer.

@aru is 'Power LED' flashing?
if yes, then just use a tftp client to push a working firmware.
If no, try shorting the tx/rx pins on the UART. use google image search to look for R8000 board images. I saw a few highlighting the UART pins. I believe myopenrouter has them as well.

Can I unbricked R8000 without a ttl ?

You can try entering failsafe mode and see if you can ping router (192.168.1.1) then. If that works, you should be able to scp working image and install it using sysupgrade.

Zajec wrote:

You can try entering failsafe mode and see if you can ping router (192.168.1.1) then. If that works, you should be able to scp working image and install it using sysupgrade.

Thanks.
I get a new R8000 and flashed with 15.05.1.
Everything goes well.
But I can't do PPPOE dial, dhcp wan works。

I can do PPPOE via my old openwrt router running with 15.05 and R8000 with stock firmware.
I look into log, no useful  information.

Thu Apr 14 02:11:00 2016 daemon.info pppd[10791]: Plugin rp-pppoe.so loaded.
Thu Apr 14 02:11:00 2016 daemon.info pppd[10791]: RP-PPPoE plugin version 3.8p compiled against pppd 2.4.7
Thu Apr 14 02:11:00 2016 daemon.notice pppd[10791]: pppd 2.4.7 started by root, uid 0

network file

config interface 'loopback'
        option ifname 'lo'
        option proto 'static'
        option ipaddr '127.0.0.1'
        option netmask '255.0.0.0'

config globals 'globals'
        option ula_prefix 'fd98:3ba4:51d7::/48'

config interface 'lan'
        option ifname 'eth0.1'
        option force_link '1'
        option type 'bridge'
        option proto 'static'
        option netmask '255.255.255.0'
        option ip6assign '60'
        option ipaddr '192.168.10.1'

config interface 'wan'
        option ifname 'eth0.2'
        option _orig_ifname 'eth0.2'
        option _orig_bridge 'false'
        option proto 'pppoe'
        option username 'PPPusername'
        option password 'PPPpassword'


config interface 'wan6'
        option ifname 'eth0.2'
        option proto 'dhcpv6'

config switch
        option name 'switch0'
        option reset '1'
        option enable_vlan '1'

config switch_vlan
        option device 'switch0'
        option vlan '1'
        option ports '0 1 2 3 5t'

config switch_vlan
        option device 'switch0'
        option vlan '2'
        option ports '4 5t'

Cause i don't have the bridge and orig_ifname options.. And PPPOE has always been working for me.. even in the latest Nightly. And this is what i have been using..

Currently I use dd-wrt for the usual Wi-Fi base station, routing, NAT, and so on, behind my ISP's cable modem, including IPv6 from the ISP (DHCPv6 with prefix delegation). I assume, given that these parts all work in dd-wrt, that they will work at least as well in OpenWrt.

In an ideal world I would like to have my R8000 be an IKEv2 VPN endpoint (or failing that, L2TP/IPsec) so that I can remotely connect back to my home LAN and route traffic through my home connection when on the road. dd-wrt developers seem uninterested in supporting this (I want to use built-in operating system features at the client end, so OpenVPN is unappealing to me), but my understanding is that OpenWrt will work for this.

Does OpenWrt currently support the router including all Wi-Fi functionality (3 radios, 802.11ac, and so on), and are there any impediments to getting the VPN configuration I'd like up and running? The wiki suggestions that jffs isn't operational for some reason, meaning that the large (80 MB or so) flash space presumably isn't available for installing packages or storing certificates or anything like that. Is that still an issue, and will it be an issue for my use-case?

DrPizza wrote:

Currently I use dd-wrt for the usual Wi-Fi base station, routing, NAT, and so on, behind my ISP's cable modem, including IPv6 from the ISP (DHCPv6 with prefix delegation). I assume, given that these parts all work in dd-wrt, that they will work at least as well in OpenWrt.

In an ideal world I would like to have my R8000 be an IKEv2 VPN endpoint (or failing that, L2TP/IPsec) so that I can remotely connect back to my home LAN and route traffic through my home connection when on the road. dd-wrt developers seem uninterested in supporting this (I want to use built-in operating system features at the client end, so OpenVPN is unappealing to me), but my understanding is that OpenWrt will work for this.

Does OpenWrt currently support the router including all Wi-Fi functionality (3 radios, 802.11ac, and so on), and are there any impediments to getting the VPN configuration I'd like up and running? The wiki suggestions that jffs isn't operational for some reason, meaning that the large (80 MB or so) flash space presumably isn't available for installing packages or storing certificates or anything like that. Is that still an issue, and will it be an issue for my use-case?

OK so I said yolo and installed openwrt 15.05.1.

The firsts odd behaviour (which may be by design, I just don't know what that design is) is that the wan and lan MACs changed on every boot, which meant my cable modem didn't assign me an address properly. I told it to use the default addresses for those interfaces and things are much happier.

The next issue is that Wi-Fi seems to not really be working properly. Only radio1 (2.4 GHz) seems to actually do anything. radio0 and radio2 (5 GHz) show as "Wireless is disabled or not associated" even if enabled and configured. Is this something that a newer build with the PCIe fixes will address?

1. Regarding the WAN and LAN MACs.. i believe it is due to driver unable to get a valid MAC and assigning a random MAC. Curious how you set it to use the default address.

2. Regarding the Wi-Fi, please share your config (/etc/config/wireless). I have it working perfectly, though i don't use the 2.4GHz radio.

adityaxavier wrote:

1. Regarding the WAN and LAN MACs.. i believe it is due to driver unable to get a valid MAC and assigning a random MAC. Curious how you set it to use the default address.

I reflashed with the Netgear firmware and copied the MACs from that. Then use option.macaddr to force a specific MAC to be sent in DHCP requests.

adityaxavier wrote:

2. Regarding the Wi-Fi, please share your config (/etc/config/wireless). I have it working perfectly, though i don't use the 2.4GHz radio.

config wifi-device 'radio0'
        option type 'mac80211'
        option hwmode '11a'
        option path '18000000.axi/bcma0:7/pci0000:00/0000:00:00.0/0000:01:00.0'
        option txpower '20'
        option htmode 'VHT160'
        option channel '132'
        option country 'US'

config wifi-iface
        option device 'radio0'
        option network 'lan'
        option mode 'ap'
        option encryption 'psk2'
        option key 'password'
        option ssid 'grackle-nest-backhaul'

config wifi-device 'radio1'
        option type 'mac80211'
        option channel '11'
        option hwmode '11g'
        option path '18000000.axi/bcma0:8/pci0001:00/0001:00:00.0/0001:01:00.0/0001:02:01.0/0001:03:00.0'
        option htmode 'HT20'
        option txpower '20'
        option country 'US'

config wifi-iface
        option device 'radio1'
        option network 'lan'
        option mode 'ap'
        option ssid 'grackle-nest'
        option encryption 'psk2'
        option key 'password'

config wifi-device 'radio2'
        option type 'mac80211'
        option hwmode '11a'
        option path '18000000.axi/bcma0:8/pci0001:00/0001:00:00.0/0001:01:00.0/0001:02:02.0/0001:04:00.0'
        option htmode 'VHT160'
        option txpower '20'
        option channel '44'
        option country 'US'

config wifi-iface
        option device 'radio2'
        option network 'lan'
        option mode 'ap'
        option ssid 'grackle-nest-5g'
        option encryption 'psk2'
        option key 'password'

Got it.

Change the "option country 'US' " to " option country '00' " to all the radios and then do a reboot. That should do the trick

adityaxavier wrote:

Got it.

Change the "option country 'US' " to " option country '00' " to all the radios and then do a reboot. That should do the trick

Hm, unfortunately that does not appear to have changed anything. radio1 is working, but radio0 and radio2 do not seem to be.

The system log has lots of things that, superficially at least, look bad, e.g.:

Fri Apr 15 01:09:26 2016 kern.err kernel: [   17.066604] brcmfmac: brcmf_cfg80211_reg_notifier: not a ISO3166 code
Fri Apr 15 01:09:26 2016 kern.info kernel: [   17.075270] pci 0001:01:00.0: enabling device (0140 -> 0142)
Fri Apr 15 01:09:26 2016 kern.info kernel: [   17.081034] pci 0001:02:01.0: enabling device (0140 -> 0142)
Fri Apr 15 01:09:26 2016 kern.info kernel: [   17.086756] brcmfmac 0001:03:00.0: enabling device (0140 -> 0142)
Fri Apr 15 01:09:26 2016 kern.warn kernel: [   17.260561] brcmfmac 0001:03:00.0: Direct firmware load for brcm/brcmfmac43602-pcie.txt failed with error -2
Fri Apr 15 01:09:26 2016 kern.warn kernel: [   17.270474] brcmfmac 0001:03:00.0: Falling back to user helper
Fri Apr 15 01:09:26 2016 kern.err kernel: [   17.283818] firmware brcm!brcmfmac43602-pcie.txt: firmware_loading_store: map pages failed
Fri Apr 15 01:09:26 2016 kern.err kernel: [   17.292412] brcmfmac: brcmf_fw_request_nvram_done: Found platform NVRAM (36304 B)
Fri Apr 15 01:09:26 2016 kern.err kernel: [   17.583104] brcmfmac: brcmf_c_preinit_dcmds: Firmware version = wl0: Mar  3 2015 04:46:51 version 7.35.177.33 (r538052) FWID 01-c8317c80
Fri Apr 15 01:09:26 2016 kern.err kernel: [   17.603937] brcmfmac: brcmf_cfg80211_reg_notifier: not a ISO3166 code
Fri Apr 15 01:09:26 2016 kern.info kernel: [   17.613807] pci 0001:02:02.0: enabling device (0140 -> 0142)
Fri Apr 15 01:09:26 2016 kern.info kernel: [   17.619555] brcmfmac 0001:04:00.0: enabling device (0140 -> 0142)
Fri Apr 15 01:09:26 2016 kern.warn kernel: [   17.790468] brcmfmac 0001:04:00.0: Direct firmware load for brcm/brcmfmac43602-pcie.txt failed with error -2
Fri Apr 15 01:09:26 2016 kern.warn kernel: [   17.800373] brcmfmac 0001:04:00.0: Falling back to user helper
Fri Apr 15 01:09:26 2016 kern.err kernel: [   17.813660] firmware brcm!brcmfmac43602-pcie.txt: firmware_loading_store: map pages failed

...

Fri Apr 15 01:09:28 2016 daemon.notice netifd: radio2 (1210): command failed: Operation not supported (-95)
Fri Apr 15 01:09:28 2016 daemon.notice netifd: radio1 (1208): command failed: Operation not supported (-95)
Fri Apr 15 01:09:28 2016 daemon.notice netifd: radio0 (1207): command failed: Operation not supported (-95)
Fri Apr 15 01:09:28 2016 daemon.notice netifd: radio2 (1210): command failed: Operation not supported (-95)
Fri Apr 15 01:09:28 2016 daemon.notice netifd: radio1 (1208): command failed: Operation not supported (-95)
Fri Apr 15 01:09:28 2016 daemon.notice netifd: radio0 (1207): command failed: Operation not supported (-95)
Fri Apr 15 01:09:28 2016 daemon.notice netifd: radio2 (1210): command failed: File exists (-17)
Fri Apr 15 01:09:28 2016 daemon.notice netifd: radio1 (1208): command failed: File exists (-17)
Fri Apr 15 01:09:29 2016 daemon.notice netifd: radio1 (1208): Configuration file: /var/run/hostapd-phy1.conf
Fri Apr 15 01:09:29 2016 daemon.notice netifd: radio1 (1208): Failed to create interface mon.wlan1: -95 (Operation not supported)
Fri Apr 15 01:09:29 2016 daemon.notice netifd: radio2 (1210): Configuration file: /var/run/hostapd-phy2.conf
Fri Apr 15 01:09:29 2016 daemon.notice netifd: radio0 (1207): command failed: File exists (-17)
Fri Apr 15 01:09:29 2016 daemon.notice netifd: radio2 (1210): Failed to create interface mon.wlan2: -95 (Operation not supported)
Fri Apr 15 01:09:29 2016 daemon.notice netifd: radio1 (1208): wlan1: interface state UNINITIALIZED->COUNTRY_UPDATE
Fri Apr 15 01:09:29 2016 daemon.notice netifd: radio2 (1210): wlan2: interface state UNINITIALIZED->COUNTRY_UPDATE
Fri Apr 15 01:09:29 2016 daemon.notice netifd: radio1 (1208): wlan1: Could not connect to kernel driver
Fri Apr 15 01:09:29 2016 daemon.notice netifd: radio1 (1208): Using interface wlan1 with hwaddr e8:fc:af:fb:f7:0c and ssid "grackle-nest"
Fri Apr 15 01:09:29 2016 daemon.notice netifd: radio2 (1210): wlan2: interface state COUNTRY_UPDATE->HT_SCAN
Fri Apr 15 01:09:29 2016 daemon.notice netifd: radio0 (1207): Failed to create interface mon.wlan0: -95 (Operation not supported)
Fri Apr 15 01:09:29 2016 daemon.notice netifd: radio0 (1207): wlan0: interface state UNINITIALIZED->COUNTRY_UPDATE
Fri Apr 15 01:09:29 2016 daemon.notice netifd: radio0 (1207): wlan0: interface state COUNTRY_UPDATE->HT_SCAN
Fri Apr 15 01:09:29 2016 daemon.notice netifd: radio2 (1210): Switch own primary and secondary channel to get secondary channel with no Beacons from other BSSes
Fri Apr 15 01:09:29 2016 daemon.notice netifd: radio1 (1208): wlan1: interface state COUNTRY_UPDATE->ENABLED
Fri Apr 15 01:09:29 2016 daemon.notice netifd: radio1 (1208): wlan1: AP-ENABLED 
Fri Apr 15 01:09:29 2016 daemon.notice netifd: radio0 (1207): Interface initialization failed
Fri Apr 15 01:09:29 2016 daemon.notice netifd: radio0 (1207): wlan0: interface state HT_SCAN->DISABLED
Fri Apr 15 01:09:29 2016 daemon.notice netifd: radio0 (1207): wlan0: AP-DISABLED 
Fri Apr 15 01:09:29 2016 daemon.notice netifd: radio0 (1207): wlan0: interface state DISABLED->DISABLED
Fri Apr 15 01:09:29 2016 daemon.notice netifd: radio0 (1207): wlan0: AP-DISABLED 
Fri Apr 15 01:09:29 2016 daemon.notice netifd: radio0 (1207): hostapd_free_hapd_data: Interface wlan0 wasn't started
Fri Apr 15 01:09:29 2016 daemon.notice netifd: radio0 (1207): nl80211: deinit ifname=wlan0 disabled_11b_rates=0
Fri Apr 15 01:09:29 2016 kern.info kernel: [   22.609205] device wlan0 left promiscuous mode

config wifi-device 'radio0'
        option type 'mac80211'
        option hwmode '11a'
        option path '18000000.axi/bcma0:7/pci0000:00/0000:00:00.0/0000:01:00.0'
        option txpower '20'
        option htmode 'VHT160'
        option channel '132'
        option country 'US'

My bad, please change " option htmode 'VHT160' " to " option htmode 'VHT80' " again, a reboot would help.

adityaxavier wrote:

My bad, please change " option htmode 'VHT160' " to " option htmode 'VHT80' " again, a reboot would help.

OK. This has got radio2 working as well, though I assume using an 80 MHz channel instead of a 160 MHz channel will reduce performance somewhat.

radio0, however, still stubbornly refuses to activate.

DrPizza wrote:

config wifi-device 'radio0'
        option type 'mac80211'
        option hwmode '11a'
        option path '18000000.axi/bcma0:7/pci0000:00/0000:00:00.0/0000:01:00.0'
        option txpower '20'
        option htmode 'VHT160'
        option channel '132'
        option country 'US'

I don't think BCM43602 supports 160 MHz channel. Switch to 80 MHz.