i've been aware of 'complications' for a while (since over 6 months ago when neil1 was first having firstboot restoration issues)
for simplicity... i'd like to separate 'firstboot' from typical reboot (where I assume it would startup much more predictably)... so if it does not startup on a reboot and it is enabled... i'd like to know...
info-on-fixes
there are two or three workarounds for the firstboot situation...
disable it manually before and after upgrade
Test the ntp bypass method
Add something a bit fancier... a specific 'wait and watch for dns and or restart' during the firstboot process
i'm sure there is a fairly basic solution... but as this issue is intermittent and I don't run the service, i'm reluctant to spend the several hours needed to pinpoint where things are fouling up... especially when i'm unable to simulate the exact conditions for all users...
I run https-dns-proxy. Haven't had any issues on reboot, it just comes back up. It's disabled after upgrade, but I just re-enable it like I do SQM and irqbalance, etc. If I knew how to keep those enabled after an upgrade, I'd do it but I'm not that smart!
Can someone please advise me on how to configure Guest and IOT interfaces on the RPi4 and extend it to multiple WAP's? I would like the RPi4 to handle the Guest & IOT ip's.
The LAN WiFi works, but having issue with the other 2.
If it's a bit off topic, please comment in the other post:
I may be able to help, I run an IoT VLAN to a separate ssid and block those devices talking to the “trusted” LAN. PM me if you need a hand and I can explain what I have setup when I get some time today
masqbump for anyone testing 'current'... massive reduction in overheads/jiffies...
(not that is hugely effects us, but noteworthy)
dnsmasq-full - 2.85-7 -> 2.86-2
* Handle DHCPREBIND requests in the DHCPv6 server code.
* Fix bug which caused dnsmasq to lose track of processes forked.
* Major rewrite of the DNS server and domain handling code.
* Revise resource handling for number of concurrent DNS queries.
* Improve efficiency of DNSSEC.
[snip]
Tried this but nothing enable on upgrade. I must be ding something wrong....
First part of my wrt.ini:
##################################################################################
NORCCUSTOM=1 #rc.local negates most options here
###################################################################################
# EXPERIMENTAL=1 #enabletweaks non-standard+unexpected+risk you do not need this
###################################################################################
ENABLEDSERVICES="sqm irqbalance https-dns-proxy" [fboot/upgrade] enable+start
Hi guys,
A happy guys using rpi4 firmware here. Thank you @anon50098793 for making great firmware and maintaining this work. I have a question about how you operate the WAN port: Do you prefer using USB NIC for WAN, or using tagged VLAN on a separate managed switch?
wan vlans via smart-switch are much more scalable(fault-tolerant) once setup
the only reason i'd prefer wan-vlans is for dual/triple wan setups... ( providing the peak-wan-aggregate speed is under around 550Mb/s )... or they still run via a single usb wan interface...
Thank you for your answer, it helps me understand the setup. But I don't get why the wan vlans only good for <450 Mb/s, would you mind explaining to me?
can be quite challenging to find one both simple enough yet with the right features / security / or a little better and not too complicated...
the zyxels... some of the not lowest range netgears seem to be mentioned most often... ( at low-sh price points and half simple setup )... still probably upwards of 65$US
ubiquiti is also preferred by some... but I find it a bit too 'eco-system-ish' in general and there have been some hardware reliability/support concerns in the past... on the plus side... they are said to have the cleanest/simplest/well-featured user interface
a second hand microtik or similar would also be in the ballpark ( or er-x maybe )