Greetings! I started to use your firmware V3.0 on my old Linksys EA6350V3 recently. I am just testing and playing around to try to learn things about networking. When I tried to change the setting of unbound, I have no idea which unbound.conf I should be tackling with. I checked the contents of the files /etc/unbound/unbound.conf, /var/lib/unbound/unbound.conf, /etc/config/unbound. All those files do not seem to agree with each other. Please help! Thank you!
I'm guessing this is still based on swconfig with the hard coded vlan driver?
I have tested working DSA from the satura fork and added support for the wallystech DR4029 routerboard in my repo I'm wondering would you look at merging DSA and the DR4029 support in this to your repo ? or if i can create a pull request?
@hkfreeman
That highly depends on your config. With the default configuration, everything is configured from UCI and therefore from the LuCI UI. The file inside /var is the generated configuration. You should not modify it since it's generated automatically.
The file that you can edit in LuCI has "advanced" configuration for the server and the zones. Those files are imported on top of the LuCI config, since not every config is exposed to the LuCI web interface.
@professor_jonny
Thanks, professor. We can start by creating the pull request. Just make this clear for me:
Are we doing this to "early adopt" DSA?
Yes I have stitched ipq40x9 DSA driver to the wallystech dr4029 router board in my fork im wondering if you could add it into your fork as i would like to try the memory compression.
Just to report that the 3.0.0 stable release works very fine for me with the Fritz!box 4040 (currently only as a dump AP, didn't take time to play with vlans).
Just a example after a 15GB file transfert :
The Fritz antennaes are certainly not the best ones so the client placement on the room can make a big difference in speed, but this build works really fine on it.
That is the first time I can really have a decent Wifi speed with a OpenWrt FW (read: no huge speed loss versus the manufacturer firmware, it is perhaps even better now)
New problem. I have version 3.0.0 of the firmware running on my Linksys MR9000 router. I have been running in in a test environment for a couple of days and thought everything was working well, so I went live with it. Now I am noticing that a couple of devices are not connecting properly to the router. Some of them are Teckin S10 Smart Plugs. (IOT devices for turning things on and off.) They operate at 2.4Ghz and must connect that way for them to work. This is what I am seeing in the system logs:
Sat Nov 6 21:34:42 2021 daemon.notice hostapd: wlan1: AP-STA-POSSIBLE-PSK-MISMATCH c8:2e:47:5f:f1:b0
Sat Nov 6 21:34:42 2021 daemon.info hostapd: wlan1: STA 68:57:2d:8b:af:60 IEEE 802.11: authenticated
Sat Nov 6 21:34:42 2021 daemon.info hostapd: wlan1: STA 68:57:2d:8b:af:60 IEEE 802.11: associated (aid 1)
Sat Nov 6 21:34:42 2021 daemon.notice hostapd: wlan1: AP-STA-POSSIBLE-PSK-MISMATCH 68:57:2d:8b:af:60
Sat Nov 6 21:34:43 2021 daemon.notice hostapd: wlan1: AP-STA-POSSIBLE-PSK-MISMATCH c8:2e:47:5f:f1:b0
Sat Nov 6 21:34:43 2021 daemon.notice hostapd: wlan1: AP-STA-POSSIBLE-PSK-MISMATCH 68:57:2d:8b:af:60
Sat Nov 6 21:34:44 2021 daemon.notice hostapd: wlan1: AP-STA-POSSIBLE-PSK-MISMATCH c8:2e:47:5f:f1:b0
Sat Nov 6 21:34:44 2021 daemon.notice hostapd: wlan1: AP-STA-POSSIBLE-PSK-MISMATCH 68:57:2d:8b:af:60
Sat Nov 6 21:34:45 2021 daemon.notice hostapd: wlan1: AP-STA-POSSIBLE-PSK-MISMATCH 68:57:2d:8b:af:60
Sat Nov 6 21:34:46 2021 daemon.info hostapd: wlan1: STA c8:2e:47:5f:f1:b0 IEEE 802.11: authenticated
Sat Nov 6 21:34:46 2021 daemon.info hostapd: wlan1: STA c8:2e:47:5f:f1:b0 IEEE 802.11: associated (aid 10)
Sat Nov 6 21:34:46 2021 daemon.notice hostapd: wlan1: AP-STA-POSSIBLE-PSK-MISMATCH c8:2e:47:5f:f1:b0
Sat Nov 6 21:34:47 2021 daemon.notice hostapd: wlan1: AP-STA-POSSIBLE-PSK-MISMATCH c8:2e:47:5f:f1:b0
Sat Nov 6 21:34:48 2021 daemon.notice hostapd: wlan1: AP-STA-POSSIBLE-PSK-MISMATCH c8:2e:47:5f:f1:b0
Sat Nov 6 21:34:49 2021 daemon.notice hostapd: wlan1: AP-STA-POSSIBLE-PSK-MISMATCH c8:2e:47:5f:f1:b0
Sat Nov 6 21:34:51 2021 daemon.info hostapd: wlan1: STA c8:2e:47:5f:f1:b0 IEEE 802.11: authenticated
Sat Nov 6 21:34:51 2021 daemon.info hostapd: wlan1: STA c8:2e:47:5f:f1:b0 IEEE 802.11: associated (aid 10)
Sat Nov 6 21:34:51 2021 daemon.notice hostapd: wlan1: AP-STA-POSSIBLE-PSK-MISMATCH c8:2e:47:5f:f1:b0
Sat Nov 6 21:34:51 2021 daemon.info hostapd: wlan1: STA 68:57:2d:8b:af:60 IEEE 802.11: deauthenticated due to local deauth request
These statements just keep repeating as the device attempts to connect. This is how my wireless looks. I'm not sure what the deal is with Radio0 but maybe it has something to do with it.
I gave 3.0 a try last night on my linksys ea6350v3 and was quite impressed with the VLAN fixes and the UI, in general. However, I found that after a couple of reboots (from reconfiguring/applying changes) that the router resets completely and I lose my config. Any suggestions on a fix?
I cant create a pull request across your fork openwrt-custom only to your openwrt fork that is not read only, i believe you have todo it from your end.
I think it is cause you created a fork then clone it locally and pushed it back under a new name.
github does not allow you to create multiple forks under the same repo.
@hipyskipy
Did you note how many reboots are needed to cause the problem? Because if it's 3, then I probably know why. Also, do you have OpenWrt on both partitions?
@professor_jonny
I understand. Well, a fork is a GitHub thing. Technically you can have a tracking repo that effectively works the same but GitHub can't know that is a fork. Please send me your repo's URI and I'll check out. Or a diff from the fork point, that would work as well.
Yep, there was Openwrt on both. It may have been three times, now I can't remember. To clarify a bit, my first attempt was a sysupgrade from 21.02.1 and I had cleared my config on upgrade. Also, the reboots were not failed reboots (which would cause the fallback to the other partition) ... is that what you're thinking?
Just for grins (after it unexpectedly reset my config), I completely reset/reflashed with the "factory" 3.0 image, reconfigured my settings and rebooted a few times during the reconfig ... I believe after 3 reboots it reset my settings again.
hello, trying to repair my network problem, doing tests, delete unbound on a fritz 4040 with your firmware, this broke luci. I tried to repair it, it loads the image again from the console and now I can't access it either with its ip, or with 192.168.1.1. what would be the next step?
@NoTengoBattery
6in4 is not working on the latest build. I saw you enabled the modules back in 2020 but it seems like it has been disabled again. Are you able to enable it again in the next build?
Hi there - I'm using version 3.0 and love the capability/stability it brings to my EA6350v3.
Hopefully a quick question. How do I turn off IPv6? My ISP doesn't support this, so I'd like to turn it off for any LAN connected devices making DNS requests (I have an issue where a software build process gets IPv6 from Cloudflare DNS, but then a 'wget' fails)?
Would I be correct in assuming that I simply remove the IPv6 address (2nd in the list) from Network -> DHCP & DNS -> DNS Forwardings?
I'm testing a Mikrotik HAP AC2 that is based on this same SOC. Do you think it's possible to test your wifi calibration data on it? I am using the default nobuffers driver but wifi performance seems slow on the 5Ghz. Using iperf I can only get 270mbits on a iperf3 test for 600 seconds with a 80mhz channel. Using irbalance and packet steering and software offload I've been able to get the full 920-940mbits wired.