Weird one, have you messed with the IPV6 settings? wan6 is the alias for the IPV6 interface.
Its because of this bug and had no time to investigate this further: https://github.com/openwrt/packages/issues/10783
hnyman's 19.07 10784 just rebooted on me after 4 days of work. It was also behaving weird in 802.11r (roaming) mode. Overall rather vanilla configuration, just DHCP WAN, some ports blocked manually in firewall, and the 2.4ghz wifi enabled.
I went back to hnyman's 18.06. Pity... OpenWRT has become as much of a lottery as DD-WRT.
Roaming working right requires some fine tuning of the maximum transmit power so that radio physics matches with the roaming behavior you desire for your setup.
As an example - I actually had to turn down my max transmit power down to 23 to get a perfect roam for my two r7800 APs running hnyman’s build after some testing of RSSI values / house layout. One r7800 isn’t enough for the performance I want in my house... two required some fine tuning to get the behavior I desired, was very easy.
Your problem is a configuration issue rather than an issue with hnyman’s build or OpenWRT in general.
One reboot can happen with a power outage, accidentally pulling a plug, or a number of reasonable explanations. One reboot is hardly abort criteria without any proof from the logs that the software is to blame.
I’d open a separate thread on these two issues - there is probably a solution so that you aren’t stuck on a old software version (18.06).
1 Like
I meant that the old firmware was behaving better with 802.11r. I could actually go and turn off WiFi on one router, and my phone would switch without disconnecting. With 19.07, the WiFi icon disappears and then it takes it several seconds to reconnect. Moving between the access points doesn't do disconnect-reconnect, but it results in "stickier" behavior than with 18.06, the phone hanging on to weakening signal of router #1 even as I am standing right next to the alternate router #2. Power levels and all other settings identical to 18.06.
As for power outage... there was none. If it's enough to reboot the router, it would've been enough to blink the lights and reboot one of the PCs in the house.
Oftentimes old software is more reliable than new. After a major version comes to an end, they usually fixed many bugs without trying to create new features.
So I seem to be having an issue connecting with a certain device over wifi. Here's the edited log:
Fri Jan 3 09:54:44 2020 daemon.debug hostapd: wlan0: STA IEEE 802.11: authentication OK (open system)
Fri Jan 3 09:54:44 2020 daemon.debug hostapd: wlan0: STA MLME: MLME-AUTHENTICATE.indication(, OPEN_SYSTEM)
Fri Jan 3 09:54:44 2020 daemon.debug hostapd: wlan0: STA MLME: MLME-DELETEKEYS.request()
Fri Jan 3 09:54:44 2020 daemon.info hostapd: wlan0: STA IEEE 802.11: authenticated
Fri Jan 3 09:54:44 2020 daemon.debug hostapd: wlan0: STA IEEE 802.11: association OK (aid 3)
Fri Jan 3 09:54:44 2020 daemon.info hostapd: wlan0: STA IEEE 802.11: associated (aid 3)
Fri Jan 3 09:54:44 2020 daemon.debug hostapd: wlan0: STA MLME: MLME-ASSOCIATE.indication()
Fri Jan 3 09:54:44 2020 daemon.debug hostapd: wlan0: STA MLME: MLME-DELETEKEYS.request()
Fri Jan 3 09:54:44 2020 daemon.debug hostapd: wlan0: STA IEEE 802.11: binding station to interface 'wlan0'
Fri Jan 3 09:54:44 2020 daemon.debug hostapd: wlan0: STA WPA: event 1 notification
Fri Jan 3 09:54:44 2020 daemon.debug hostapd: wlan0: STA WPA: start authentication
Fri Jan 3 09:54:44 2020 daemon.debug hostapd: wlan0: STA IEEE 802.1X: unauthorizing port
Fri Jan 3 09:54:44 2020 daemon.debug hostapd: wlan0: STA WPA: sending 1/4 msg of 4-Way Handshake
Fri Jan 3 09:54:45 2020 daemon.debug hostapd: wlan0: STA WPA: EAPOL-Key timeout
Fri Jan 3 09:54:45 2020 daemon.debug hostapd: wlan0: STA WPA: sending 1/4 msg of 4-Way Handshake
Fri Jan 3 09:54:46 2020 daemon.debug hostapd: wlan0: STA WPA: EAPOL-Key timeout
Fri Jan 3 09:54:46 2020 daemon.debug hostapd: wlan0: STA WPA: sending 1/4 msg of 4-Way Handshake
Fri Jan 3 09:54:47 2020 daemon.debug hostapd: wlan0: STA WPA: EAPOL-Key timeout
Fri Jan 3 09:54:47 2020 daemon.debug hostapd: wlan0: STA WPA: sending 1/4 msg of 4-Way Handshake
Fri Jan 3 09:54:48 2020 daemon.debug hostapd: wlan0: STA WPA: EAPOL-Key timeout
Fri Jan 3 09:54:48 2020 daemon.debug hostapd: wlan0: STA WPA: PTKSTART: Retry limit 4 reached
Fri Jan 3 09:54:48 2020 daemon.debug hostapd: wlan0: STA WPA: event 3 notification
Fri Jan 3 09:54:48 2020 daemon.debug hostapd: wlan0: STA IEEE 802.1X: unauthorizing port
Fri Jan 3 09:54:48 2020 daemon.debug hostapd: wlan0: STA MLME: MLME-DEAUTHENTICATE.indication(, 2)
Fri Jan 3 09:54:48 2020 daemon.debug hostapd: wlan0: STA MLME: MLME-DELETEKEYS.request()
Fri Jan 3 09:54:53 2020 daemon.info hostapd: wlan0: STA IEEE 802.11: deauthenticated due to local deauth request
Any ideas how to fix this? Cheers!
EDIT: I should say, I'm on OpenWrt 19.07-SNAPSHOT r10833-91dde4291c from the Dropbox, the device connects fine over wired. Doesn't connect to any WLAN, 2ghz or 5ghz 
EDIT2: There are 2 topics that have the same issues as me ...
Also very strangely. If I connect over a wired connection, the connect to the network wirelessly, this happens:
Fri Jan 3 10:54:04 2020 daemon.debug hostapd: wlan0: STA IEEE 802.11: authentication OK (open system)
Fri Jan 3 10:54:04 2020 daemon.debug hostapd: wlan0: STA MLME: MLME-AUTHENTICATE.indication(, OPEN_SYSTEM)
Fri Jan 3 10:54:04 2020 daemon.debug hostapd: wlan0: STA MLME: MLME-DELETEKEYS.request()
Fri Jan 3 10:54:04 2020 daemon.info hostapd: wlan0: STA IEEE 802.11: authenticated
Fri Jan 3 10:54:04 2020 daemon.debug hostapd: wlan0: STA IEEE 802.11: association OK (aid 4)
Fri Jan 3 10:54:04 2020 daemon.info hostapd: wlan0: STA IEEE 802.11: associated (aid 4)
Fri Jan 3 10:54:04 2020 daemon.debug hostapd: wlan0: STA MLME: MLME-ASSOCIATE.indication()
Fri Jan 3 10:54:04 2020 daemon.debug hostapd: wlan0: STA MLME: MLME-DELETEKEYS.request()
Fri Jan 3 10:54:04 2020 daemon.debug hostapd: wlan0: STA IEEE 802.11: binding station to interface 'wlan0'
Fri Jan 3 10:54:04 2020 daemon.debug hostapd: wlan0: STA WPA: event 1 notification
Fri Jan 3 10:54:04 2020 daemon.debug hostapd: wlan0: STA WPA: start authentication
Fri Jan 3 10:54:04 2020 daemon.debug hostapd: wlan0: STA IEEE 802.1X: unauthorizing port
Fri Jan 3 10:54:04 2020 daemon.debug hostapd: wlan0: STA WPA: sending 1/4 msg of 4-Way Handshake
Fri Jan 3 10:54:04 2020 daemon.debug hostapd: wlan0: STA WPA: received EAPOL-Key frame (2/4 Pairwise)
Fri Jan 3 10:54:04 2020 daemon.debug hostapd: wlan0: STA WPA: sending 3/4 msg of 4-Way Handshake
Fri Jan 3 10:54:04 2020 daemon.debug hostapd: wlan0: STA WPA: received EAPOL-Key frame (4/4 Pairwise)
Fri Jan 3 10:54:04 2020 daemon.debug hostapd: wlan0: STA IEEE 802.1X: authorizing port
Fri Jan 3 10:54:04 2020 daemon.info hostapd: wlan0: STA RADIUS: starting accounting session F9E7944086B45C11
Fri Jan 3 10:54:04 2020 daemon.info hostapd: wlan0: STA WPA: pairwise key handshake completed (RSN)
Just a follow up, same thing happens on master-r11887.
Could you show your /etc/config/wireless ?
I recall having issues with IOS devices connectivity with either KRACK/802.11r Fast Transition enabled or 802.11w Management Frame Protection enforced.
No problem. Thanks for the reply.
config wifi-device 'radio0'
option type 'mac80211'
option hwmode '11a'
option path 'soc/1b500000.pci/pci0000:00/0000:00:00.0/0000:01:00.0'
option htmode 'VHT80'
option channel 'auto'
option log_level '1'
option country 'GB'
config wifi-iface 'default_radio0'
option device 'radio0'
option network 'lan'
option mode 'ap'
option wps_pushbutton '1'
option ssid 'NETGEAR62-5G-1'
option ieee80211w '1'
option key '123456'
option encryption 'psk2'
config wifi-device 'radio1'
option type 'mac80211'
option hwmode '11g'
option path 'soc/1b700000.pci/pci0001:00/0001:00:00.0/0001:01:00.0'
option htmode 'HT20'
option channel 'auto'
option country 'GB'
config wifi-iface 'default_radio1'
option device 'radio1'
option network 'lan'
option mode 'ap'
option wps_pushbutton '1'
option ssid 'NETGEAR62'
option ieee80211w '1'
option key '123456'
option encryption 'psk2'
Edit: Sorry @tmomas I didn't know but I do now 
1 Like
Have you tried different NIC firmware? Something like here:
Thanks for the suggestion, no change unfortunately 
I am pretty sure everything was working fine when I was on the link from this page.
@hnyman is there a updated guide to building images using your build data? Im a novice and tried to do this today, followed the wiki guide for beginners, got to the makemenu section, but I'm lost what I need to do with your patches etc? I don't know where they need to be or go?? Basically I want to recreate your build just without ipv6 as it's causing me headaches. On your dropbox site you have a folder of scripts, but there's also a few in each firmware directory, do I need them?? Or just the 3 patches in the firmware build I'm recreating?? Sorry for bothering you.
How about reading the message 2 of this thread, where I give exactly that advice about using my patched and build scripts...
2 Likes
I have done but am still struggling, I also found one from November on a different build with a bit more detail... But still struggling. I'll just keep playing about then. Cheers anyway.
So far I've downloaded the build environment sources from the quickstart guide, got the openwrt source code and arrived at the section "make menuconfig"
In this menu I've selected my target system and Target profile accordingly. I've now followed the instruction to select exit and save.
So now on my Linux machine I have a folder called openwrt with a whole load of stuff inside it. From what I gather from your instructions I need to now make a folder called openwrt19.07 and inside that put the patches from your latest build, and the newbuildroot.sh file from your scripts folder on Dropbox.
Then run the newbuildroot.sh file and magic should happen?
No, you are mixing things.
I have created my build script set to download the OpenWrt sources (which you already have done) and the feeds etc., and then patch them with my changes. No need to manually clone / download the OpenWrt repo.
If you want to use my patches and scripts, simply start with an empty directory, to which you download from my newest build the newbuildroot.sh script and the three patch files of that same build, and then you run newbuildroot.sh in that directory.
Just like described message 2: in Build for Netgear R7800 - #2 by hnyman
I just did the whole show as an example for you:
Create a suitable directory and change to it. I did "/family":
cd /
sudo mkdir family
chown perus family
sudo chown perus family
cd family/
Download the script and patches from the newest build:
wget https://www.dropbox.com/sh/ew0gap0crn30wyk/AADeo0r7GQdB1RHbH77GfGZya/owrt1907-r10846-3fc47dd443-20200105/R7800-owrt1907-r10846-3fc47dd443-20200105-1310-newBuildroot.sh?dl=0
wget https://www.dropbox.com/sh/ew0gap0crn30wyk/AABs4ZHQNYx5qTNqY1xKdZGLa/owrt1907-r10846-3fc47dd443-20200105/R7800-owrt1907-r10846-3fc47dd443-20200105-1310-main.patch?dl=0
wget https://www.dropbox.com/sh/ew0gap0crn30wyk/AADdc_0dgzHswY1VD8Qr0Yrga/owrt1907-r10846-3fc47dd443-20200105/R7800-owrt1907-r10846-3fc47dd443-20200105-1310-luci.patch?dl=0
wget https://www.dropbox.com/sh/ew0gap0crn30wyk/AAD--KwPA5MI4T0SNMyu9hIja/owrt1907-r10846-3fc47dd443-20200105/R7800-owrt1907-r10846-3fc47dd443-20200105-1310-packages.patch?dl=0
Rename the extra Dropbox ending "?dl=0" away
mv R7800-owrt1907-r10846-3fc47dd443-20200105-1310-luci.patch\?dl\=0 R7800-owrt1907-r10846-3fc47dd443-20200105-1310-luci.patch
mv R7800-owrt1907-r10846-3fc47dd443-20200105-1310-main.patch\?dl\=0 R7800-owrt1907-r10846-3fc47dd443-20200105-1310-main.patch
mv R7800-owrt1907-r10846-3fc47dd443-20200105-1310-packages.patch\?dl\=0 R7800-owrt1907-r10846-3fc47dd443-20200105-1310-packages.patch
mv R7800-owrt1907-r10846-3fc47dd443-20200105-1310-newBuildroot.sh\?dl\=0 R7800-owrt1907-r10846-3fc47dd443-20200105-1310-newBuildroot.sh
Modify script to be runnable:
ls -l
chmod 755 R7800-owrt1907-r10846-3fc47dd443-20200105-1310-newBuildroot.sh
(You should now have files like this:
perus@ub1910:/family$ ls -l
total 44
-rw-r--r-- 1 perus perus 2951 tammi 5 20:09 R7800-owrt1907-r10846-3fc47dd443-20200105-1310-luci.patch
-rw-r--r-- 1 perus perus 23465 tammi 5 20:09 R7800-owrt1907-r10846-3fc47dd443-20200105-1310-main.patch
-rwxr-xr-x 1 perus perus 2414 tammi 5 20:10 R7800-owrt1907-r10846-3fc47dd443-20200105-1310-newBuildroot.sh
-rw-r--r-- 1 perus perus 982 tammi 5 20:09 R7800-owrt1907-r10846-3fc47dd443-20200105-1310-packages.patch
Run the creation script:
./R7800-owrt1907-r10846-3fc47dd443-20200105-1310-newBuildroot.sh
Magic happens.
Go to see the created build env:
cd owrt1907/
EDIT: I did that as a bit dirty, as I copy-pasted the download link directly from the browser, so I got the stupid "?dl=0" endings that I needed to rename away. I could have also edited the pasted link a bit (remove ?dl=0 from the wget command line) to avoid that renaming.
EDIT2:
A clean example with proper links.
Just run these commands inside an empty directory, and it is enough:
wget https://www.dropbox.com/sh/ew0gap0crn30wyk/AADeo0r7GQdB1RHbH77GfGZya/owrt1907-r10846-3fc47dd443-20200105/R7800-owrt1907-r10846-3fc47dd443-20200105-1310-newBuildroot.sh
wget https://www.dropbox.com/sh/ew0gap0crn30wyk/AABs4ZHQNYx5qTNqY1xKdZGLa/owrt1907-r10846-3fc47dd443-20200105/R7800-owrt1907-r10846-3fc47dd443-20200105-1310-main.patch
wget https://www.dropbox.com/sh/ew0gap0crn30wyk/AADdc_0dgzHswY1VD8Qr0Yrga/owrt1907-r10846-3fc47dd443-20200105/R7800-owrt1907-r10846-3fc47dd443-20200105-1310-luci.patch
wget https://www.dropbox.com/sh/ew0gap0crn30wyk/AAD--KwPA5MI4T0SNMyu9hIja/owrt1907-r10846-3fc47dd443-20200105/R7800-owrt1907-r10846-3fc47dd443-20200105-1310-packages.patch
chmod 755 R7800-owrt1907-r10846-3fc47dd443-20200105-1310-newBuildroot.sh
./R7800-owrt1907-r10846-3fc47dd443-20200105-1310-newBuildroot.sh
Ah I see, I'm mixing different methods, explains the complications.... Using this method how can you remove ipv6 though??
Thanks for the help though, much appriciated.
There is no need too. If you don’t want to get ipv6 addresses on your dhcp clients you can’t simply remove the IPV6 ULA prefix and that should prevent your clients to get local ipv6 addresses
Today's 19.07 release gets a bad checksum error when I try to flash it via Tftpd64. 
Is it that simple?? So they won't get IPV6 leases or DNS??