hsmptg
2124
In fact hitting the Disabled button, SOLVED the problem!
Its 1 AM here in Portugal!
My brain needs to rest! 
Thanks you for your help!
3 Likes
johnd2
2125
yikes...well...this convo hit different (:
great support <3
2 Likes
swanson
2126
Isnt there any usb dual wifi dongle, that works stable on the rpi4, so I dont have to use the built in one PLUS the usb one? for me it even still acts out with the new build.
1 Like
I haven’t read about one anywhere. Why I use dumb access points with it like the TP-Link RE605x
hey @anon50098793
Openvpn performance is awesome. Mwan3 problem also seems to be solved for now.
The problem now is, we cant seem to access the GUI of the Optical network terminal (modem) which is on a different subnet (192.168.0.1)
I tried adding a static IP address and an alias of the interface but it did not work.
Same thing worked well in the Archer A7.
I am using 2 different VLANS for dual WAN configs.
Kindly help me out
1 Like
for this you will need a new thread, looking forward to seeing the previous working mwan3 / ip route~rule / iptables / /etc/config/network combination to get that running on the A7...
note: in the new thread it may be beneficial to state which VLAN is paired to the ONT or whether both are...
First of all thank you @anon50098793 for all your hard work! This build is the reason I bought an rpi4 to use as a router.
I've been lurking here for a while and never got to comment. I have 2 things to ask.
-
Is this normal? I've been seeing that since like 4-5 versions now.
- Unless I exclude wan and wan6 interfaces I get my system log spammed with messages like
Sun Feb 6 09:53:27 2022 daemon.warn dnsmasq[1948]: failed to create listening socket for SOMEIPV6ADDRESS%pppoe-wan: Address not available
Thing is, every update I have to remove wan and wan6 from my DHCP exclusions and readd them lest the log get spammed again.
Thank you again for all your hard work and for maintaining this amazing build.
edit: Also is bootstrap-dark supposed to work? All I get is light theme whichever bootstrap version I choose unless it's very early in the boot cycle. After a minute or two, theme switches to light mode again no matter what version I have picked.
1 Like
cheers...
first one is normal, a courtesy message i'm just testing out... I will remove it shortly or add an INI variable you can uncomment or something to disable
starting to annoy me also 
second one i'll need to see a diff of what you need to edit every upgrade or a printscreen of where you've entered the new settings before and after
so after upgrade they are blank?
um, general reports on the forum have been positive...
but there may be some build related issues with selecting darkVSlight overrides... I quickly tested it when it came down the pipe and didn't seem to work for me...
i use darkreader ... and the newer changes mess up the page tab menu's with that...
(21.02 looks very different)
so on master... at least for now it's light only or messed up tab sub-menus with darkreader
the luci mods are PITA as it is so i've resisted getting too deep into what's going on...
( 2 x themes x darkreader or not x 2 build versions x what color people select turns out to be about 70 different combinations and the last time I tried to touch it there were complaints about styling differences between them... so someone else with the right skills would have to take future mods on or i may have to fork the build or drop 21.02 builds to support both types... remind me if we ever drop 21.02 or the newer styles get backported to try to fix it...
No they're still there, they just get ignored unless I delete and add back again, aka I start getting the log flooded with that error every 4 mins or so.
1 Like
i've seen similar reports around and this seems to be related to pppoe connections only... so i'm calling official bug on that for now...
would be worth just trying a dnsmasq restart (after the system is settled yet the messages are contunuing to spam) and see of they go away...
i can probably add a local workaround/hack for you... seeings as there are 5-10 pppoe people using the build
1 Like
Will do next update, thanks!
1 Like
o' i see... in this case... also test a reboot... if the messages are just on 'upgrade-boot' and not on 'regular-boot' then that's a build related issue...
so they are two seperate question;
- on upgrade (after a while) does a dnsmasq restart fix it?
- on upgrade (after a while) does a odhcpd restart fix it?
- on upgrade... (after a while) does a reboot fix it?
also grab;
dmesg | grep kickit
#you can search for kickit in luci > system > logs > kernel or something also
(in other words don't re-add until you've tested both the above)
sorry I missed this bit... that's good news (kinda) and confirms what I think the problem is, so thanks very much for that... i'll take a look for an easy fix if I find time...
you can set;
NOLUCIMODS=1
(setting is an upgrade setting... aka not dynamic)
and see if the issue goes away... but you lose update notices and other build related warnings and whatnot...
1 Like
fixed @ 5.0.77-97+
darkreader is still crap suboptimal on bootstrap but native dark now is alright...
NOBANNERMSGS=1
should stop all splash notices if you don't want them (5.0.77-101+)... i've not tested it fully tho'
Sorry, I am using VLANS and a switch with the Pi and not the Archer A7. Since it physically had switches, I was able to make new alias interface with static IP in the ONT subnet
1 Like
fyi, previous upgrade log is now viewable from OS
1 Like
my Alfa MT76 and Ath9k work great.
1 Like
turns out this broke theme persistence logic, so upgrade would have left you with argon selected by default...
should be fixed (5.0.77-130+)including downgrading to 21.02 will change to just 'bootstrap' if light or dark is selected...
(in other words if you downgrade to 21... then upgrade again to master... you will have to re-select dark)
