Well, i'm pretty sure i did not change it manually, but it's still in the backup config/network:
option macaddr '0c:0e:76:cf:77:a3'
...on the "internet" and "ethernet" devices. I just read through the docs and removing it is also an option, so that would make the file portable.
the units create config files with the units mac address's
but if you save from one unit then upload into another
you will end up with the same MAC address's
a factory reset should recreate the config file with it' own mac address
Yes, but i think that was the exact issue, based on the assumption the mac address is read from the hardware device during reset:
Has anyone having issue with wireless connections dropping.
Most devices in my household keep loosing dropping connection every 5-10.
I have to restart the router for it to connect sometimes it does not connect at all.
"device reports saved / configuration failure"
here is what the log looks like.
Sun Jul 23 09:37:38 2023 daemon.notice hostapd: phy0-ap0: AP-STA-DISCONNECTED 3c:20:93:8b:78:82
Sun Jul 23 09:37:38 2023 daemon.info hostapd: phy0-ap0: STA 3c:20:93:8b:78:82 IEEE 802.11: disassociated
Sun Jul 23 09:37:43 2023 daemon.info hostapd: phy0-ap0: STA 3c:20:93:8b:78:82 IEEE 802.11: authenticated
Sun Jul 23 09:37:43 2023 daemon.info hostapd: phy0-ap0: STA 3c:20:93:8b:78:82 IEEE 802.11: associated (aid 1)
Sun Jul 23 09:37:44 2023 daemon.notice hostapd: phy0-ap0: AP-STA-CONNECTED 3c:20:93:8b:78:82 auth_alg=open
Sun Jul 23 09:37:44 2023 daemon.info hostapd: phy0-ap0: STA 3c:20:93:8b:78:82 WPA: pairwise key handshake completed (RSN)
Sun Jul 23 09:37:44 2023 daemon.notice hostapd: phy0-ap0: EAPOL-4WAY-HS-COMPLETED 3c:20:93:8b:78:82
Sun Jul 23 09:37:56 2023 daemon.info hostapd: phy1-ap0: STA ba:ed:1d:1b:c2:7f IEEE 802.11: authenticated
Sun Jul 23 09:37:56 2023 daemon.info hostapd: phy1-ap0: STA ba:ed:1d:1b:c2:7f IEEE 802.11: associated (aid 1)
Sun Jul 23 09:37:57 2023 daemon.notice hostapd: phy1-ap0: AP-STA-CONNECTED ba:ed:1d:1b:c2:7f auth_alg=sae
Sun Jul 23 09:37:57 2023 daemon.info hostapd: phy1-ap0: STA ba:ed:1d:1b:c2:7f WPA: pairwise key handshake completed (RSN)
Sun Jul 23 09:37:57 2023 daemon.notice hostapd: phy1-ap0: EAPOL-4WAY-HS-COMPLETED ba:ed:1d:1b:c2:7f
Sun Jul 23 09:38:06 2023 daemon.info hostapd: phy0-ap0: STA ba:ed:1d:1b:c2:7f IEEE 802.11: authenticated
Sun Jul 23 09:38:06 2023 daemon.info hostapd: phy0-ap0: STA ba:ed:1d:1b:c2:7f IEEE 802.11: associated (aid 2)
Sun Jul 23 09:38:06 2023 daemon.notice hostapd: phy1-ap0: Prune association for ba:ed:1d:1b:c2:7f
Sun Jul 23 09:38:06 2023 daemon.notice hostapd: phy1-ap0: AP-STA-DISCONNECTED ba:ed:1d:1b:c2:7f
Sun Jul 23 09:38:09 2023 daemon.notice hostapd: phy0-ap0: AP-STA-CONNECTED ba:ed:1d:1b:c2:7f auth_alg=open
Sun Jul 23 09:38:09 2023 daemon.info hostapd: phy0-ap0: STA ba:ed:1d:1b:c2:7f WPA: pairwise key handshake completed (RSN)
Sun Jul 23 09:38:09 2023 daemon.notice hostapd: phy0-ap0: EAPOL-4WAY-HS-COMPLETED ba:ed:1d:1b:c2:7f
Sun Jul 23 09:38:09 2023 daemon.notice hostapd: phy0-ap0: AP-STA-DISCONNECTED 3c:20:93:8b:78:82
Sun Jul 23 09:38:09 2023 daemon.info hostapd: phy0-ap0: STA 3c:20:93:8b:78:82 IEEE 802.11: disassociated
Sun Jul 23 09:38:14 2023 daemon.info hostapd: phy0-ap0: STA 3c:20:93:8b:78:82 IEEE 802.11: authenticated
Sun Jul 23 09:38:14 2023 daemon.info hostapd: phy0-ap0: STA 3c:20:93:8b:78:82 IEEE 802.11: associated (aid 1)
Sun Jul 23 09:38:14 2023 daemon.notice hostapd: phy0-ap0: AP-STA-CONNECTED 3c:20:93:8b:78:82 auth_alg=open
Sun Jul 23 09:38:14 2023 daemon.info hostapd: phy0-ap0: STA 3c:20:93:8b:78:82 WPA: pairwise key handshake completed (RSN)
Sun Jul 23 09:38:14 2023 daemon.notice hostapd: phy0-ap0: EAPOL-4WAY-HS-COMPLETED 3c:20:93:8b:78:82
Sun Jul 23 09:38:15 2023 daemon.notice hostapd: phy0-ap0: AP-STA-DISCONNECTED ba:ed:1d:1b:c2:7f
Sun Jul 23 09:38:15 2023 daemon.info hostapd: phy0-ap0: STA ba:ed:1d:1b:c2:7f IEEE 802.11: disassociated
Sun Jul 23 09:38:16 2023 daemon.info hostapd: phy0-ap0: STA ba:ed:1d:1b:c2:7f IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
could it be a driver issue? @RolandoMagico
Not at all, it's rock-stable and fast on both devices since about 16 hours now.
Not sure what causes the problem. Which image do you use? Do you have a special configuration or is it a "default" OpenWrt configuration: Router with AP?
i have no idea. maybe a defective unit?
here is my configuration. I'm currently running "Build_20230626_0748"
config interface 'loopback'
option device 'lo'
option proto 'static'
option ipaddr '127.0.0.1'
option netmask '255.0.0.0'
config globals 'globals'
option ula_prefix 'fdc5:b45e:d30e::/48'
option packet_steering '1'
config device
option name 'br-lan'
option type 'bridge'
list ports 'ethernet'
config device
option name 'ethernet'
option macaddr '0c:0e:76:cf:70:2e'
config interface 'lan'
option device 'br-lan'
option proto 'dhcp'
config device
option name 'internet'
option macaddr '0c:0e:76:cf:70:2e'
config interface 'wan'
option device 'internet'
option proto 'dhcp'
option type 'bridge'
config interface 'wan6'
option device 'internet'
option proto 'dhcpv6'
option type 'bridge'
root@OpenWrt:~# cat /etc/config/wireless
config wifi-device 'radio0'
option type 'mac80211'
option path '1e140000.pcie/pci0000:00/0000:00:01.0/0000:02:00.0'
option channel '9'
option band '2g'
option country 'DE'
option cell_density '0'
option htmode 'HE20'
option disabled '1'
config wifi-device 'radio1'
option type 'mac80211'
option path '1e140000.pcie/pci0000:00/0000:00:01.0/0000:02:00.0+1'
option channel '56'
option band '5g'
option htmode 'HE80'
option cell_density '0'
option country 'DE'
config wifi-iface 'wifinet0'
option device 'radio0'
option mode 'ap'
option ssid 'FBIUSEONLY'
option encryption 'sae-mixed'
option key 'xxxxxxxxxxxxxxx'
option network 'lan'
option disabled '1'
config wifi-iface 'wifinet1'
option device 'radio1'
option mode 'ap'
option ssid 'FBIUSEONLY'
option encryption 'sae-mixed'
option key 'xxxxxxxxxxx'
root@OpenWrt:~# cat /etc/config/dhcp
config dnsmasq
option domainneeded '1'
option boguspriv '1'
option filterwin2k '0'
option localise_queries '1'
option rebind_protection '1'
option rebind_localhost '1'
option local '/lan/'
option domain 'lan'
option expandhosts '1'
option nonegcache '0'
option cachesize '1000'
option authoritative '1'
option readethers '1'
option leasefile '/tmp/dhcp.leases'
option resolvfile '/tmp/resolv.conf.d/resolv.conf.auto'
option nonwildcard '1'
option localservice '1'
option ednspacket_max '1232'
option filter_aaaa '0'
option filter_a '0'
config dhcp 'lan'
option interface 'lan'
option start '100'
option limit '150'
option leasetime '12h'
option dhcpv4 'server'
option dhcpv6 'hybrid'
option ra 'hybrid'
list ra_flags 'managed-config'
list ra_flags 'other-config'
config dhcp 'wan'
option interface 'wan'
option ignore '1'
config odhcpd 'odhcpd'
option maindhcp '0'
option leasefile '/tmp/hosts/odhcpd'
option leasetrigger '/usr/sbin/odhcpd-update'
option loglevel '4'
root@OpenWrt:~# cat /etc/config/firewall
config defaults
option syn_flood 1
option input REJECT
option output ACCEPT
option forward REJECT
# Uncomment this line to disable ipv6 rules
# option disable_ipv6 1
config zone
option name lan
list network 'lan'
option input ACCEPT
option output ACCEPT
option forward ACCEPT
config zone
option name wan
list network 'wan'
list network 'wan6'
option input REJECT
option output ACCEPT
option forward REJECT
option masq 1
option mtu_fix 1
config forwarding
option src lan
option dest wan
# We need to accept udp packets on port 68,
# see https://dev.openwrt.org/ticket/4108
config rule
option name Allow-DHCP-Renew
option src wan
option proto udp
option dest_port 68
option target ACCEPT
option family ipv4
# Allow IPv4 ping
config rule
option name Allow-Ping
option src wan
option proto icmp
option icmp_type echo-request
option family ipv4
option target ACCEPT
config rule
option name Allow-IGMP
option src wan
option proto igmp
option family ipv4
option target ACCEPT
# Allow DHCPv6 replies
# see https://github.com/openwrt/openwrt/issues/5066
config rule
option name Allow-DHCPv6
option src wan
option proto udp
option dest_port 546
option family ipv6
option target ACCEPT
config rule
option name Allow-MLD
option src wan
option proto icmp
option src_ip fe80::/10
list icmp_type '130/0'
list icmp_type '131/0'
list icmp_type '132/0'
list icmp_type '143/0'
option family ipv6
option target ACCEPT
# Allow essential incoming IPv6 ICMP traffic
config rule
option name Allow-ICMPv6-Input
option src wan
option proto icmp
list icmp_type echo-request
list icmp_type echo-reply
list icmp_type destination-unreachable
list icmp_type packet-too-big
list icmp_type time-exceeded
list icmp_type bad-header
list icmp_type unknown-header-type
list icmp_type router-solicitation
list icmp_type neighbour-solicitation
list icmp_type router-advertisement
list icmp_type neighbour-advertisement
option limit 1000/sec
option family ipv6
option target ACCEPT
# Allow essential forwarded IPv6 ICMP traffic
config rule
option name Allow-ICMPv6-Forward
option src wan
option dest *
option proto icmp
list icmp_type echo-request
list icmp_type echo-reply
list icmp_type destination-unreachable
list icmp_type packet-too-big
list icmp_type time-exceeded
list icmp_type bad-header
list icmp_type unknown-header-type
option limit 1000/sec
option family ipv6
option target ACCEPT
config rule
option name Allow-IPSec-ESP
option src wan
option dest lan
option proto esp
option target ACCEPT
config rule
option name Allow-ISAKMP
option src wan
option dest lan
option dest_port 500
option proto udp
option target ACCEPT
### EXAMPLE CONFIG SECTIONS
# do not allow a specific ip to access wan
#config rule
# option src lan
# option src_ip 192.168.45.2
# option dest wan
# option proto tcp
# option target REJECT
# block a specific mac on wan
#config rule
# option dest wan
# option src_mac 00:11:22:33:44:66
# option target REJECT
# block incoming ICMP traffic on a zone
#config rule
# option src lan
# option proto ICMP
# option target DROP
# port redirect port coming in on wan to lan
#config redirect
# option src wan
# option src_dport 80
# option dest lan
# option dest_ip 192.168.16.235
# option dest_port 80
# option proto tcp
# port redirect of remapped ssh port (22001) on wan
#config redirect
# option src wan
# option src_dport 22001
# option dest lan
# option dest_port 22
# option proto tcp
### FULL CONFIG SECTIONS
#config rule
# option src lan
# option src_ip 192.168.45.2
# option src_mac 00:11:22:33:44:55
# option src_port 80
# option dest wan
# option dest_ip 194.25.2.129
# option dest_port 120
# option proto tcp
# option target REJECT
#config redirect
# option src lan
# option src_ip 192.168.45.2
# option src_mac 00:11:22:33:44:55
# option src_port 1024
# option src_dport 80
# option dest_ip 194.25.2.129
# option dest_port 120
# option proto tcp
You are using WPA3/2 mixed mode. Try switching to WPA2-PSK only. For me some issues with devices were resolved through that.
Which build are you running?
The prebuilt one from @RolandoMagico, flashed both through D-Link WebUI and also through recovery mode. Currently running three devices, all working perfect.
Flashed 3 devices yesterday and no issues this far. Roaming works as expected and everything is stable. The only problem is: I cannot install any software using opkg, it throws this error whenever I try to install something (here example with dawn):
Installing dawn (2022-07-24-9e8060ea-3) to root...
Downloading https://downloads.openwrt.org/snapshots/packages/mipsel_24kc/packages/dawn_2022-07-24-9e8060ea-3_mipsel_24kc.ipk
Installing libgpg-error (1.47-1) to root...
Downloading https://downloads.openwrt.org/snapshots/packages/mipsel_24kc/packages/libgpg-error_1.47-1_mipsel_24kc.ipk
Installing libgcrypt (1.10.2-1) to root...
Downloading https://downloads.openwrt.org/snapshots/packages/mipsel_24kc/packages/libgcrypt_1.10.2-1_mipsel_24kc.ipk
Installing libnl-tiny2023-07-01 (2023-07-01-d433990c-1) to root...
Downloading https://downloads.openwrt.org/snapshots/packages/mipsel_24kc/base/libnl-tiny2023-07-01_2023-07-01-d433990c-1_mipsel_24kc.ipk
Configuring libgpg-error.
Configuring libgcrypt.
Collected errors:
* check_data_file_clashes: Package libnl-tiny2023-07-01 wants to install file /usr/lib/libnl-tiny.so
But that file is already provided by package * libnl-tiny2023-04-02
* opkg_install_cmd: Cannot install package dawn.
You have to force overwrite existing files.
Not sure if this exact error is for the same reason here, but usually packages can only be installed to snapshot builds on the very same day the kernel was built, since the kernel and packages in the public repositories will be rebuilt every day, and packages need to match the exact version.
[OpenWrt Wiki] Cannot satisfy dependencies / kernel is not compatible
In this case, kernel was built by @RolandoMagico, so the packages are probably not compatible? (or did you use ImageBuilder on an existing kernel release instead?)
I also thought it will be the case with compatibility. I will rather wait for official image before I start to play around with software. Looks too risky now.
No, I didn’t use ImageBuilder, the builds are directly done from the main branch
Well, the errors:
* check_data_file_clashes: Package libnl-tiny2023-07-01 wants to install file /usr/lib/libnl-tiny.so
But that file is already provided by package * libnl-tiny2023-04-02
* opkg_install_cmd: Cannot install package dawn.
pretty clearly points to the usual opkg behaviour as it refuses to overwrite existing files from former versions or dependencies. In your case, just install it with:
opkg install --force-overwrite dawn
And it should work fine. The same switch is available from LuCI when installing software.
I created new images which should solve the problem as well:
Not sure for how long as it is still based on the main branch and not on a specific release.
I'll have a closer look to ImageBuilder in the next days, maybe this can fix the problem in general.
flashed this with firefox and it seems to have brick the device.
Cant get into recovery mode. is there any tricks to force it into recovery mode?
Is tehre any LED activity? Usually forcing recovery mode is done by pressing the reset button during power on of the device.
RED led. Try that doesn't seem to work. network activities seems like its boot looping.