Something seems not quite right with how you are using the image..
Did you start with our community 'fac'/factory image?... if not please try to explain the cronology of
what you flashed ( original version, what was upgraded over it etc. etc. )
Kmod tun is in the build... I use fdisk, bash and nano which are also in the build daily... across all builds
Which broadcom nic driver exactly ( both chipset and kmod package name if possible ) there are lots of kmods in the build and the ones which are not are installable via opkg.
All other packages you try to install should generally work... there are some build specific quirks... but I think we should first work out whats generally going wrong with how you are using the build ( you need to mention the build version also when reporting issues )
any build that says partuuid if flashed from factory will boot from usb (or mmc)... do not change cmdline to /dev... leave it as PARTUUID... if not flashed from factory ( upgraded ) you need to put in root=PARTUUID=nnnnnnnnn-0n and ensure you have no mmc in or the mmc has no OS on it of your RPI EEPROM has the default boot order...
Thankyou for Guinea willingness... i can always use more help testing and polishing the build...
Hi wulfy23, love your new build with the addition of the rpi4.qos.
How do i change the dscp classification of gaming from CS4 to CS7 using rpi4.qos. I tried looking for the setting in usr/lib/sqm/ctinfo_4layercake_rpi4.qos but i dont know what to change without messing it up.
I dont have user hooks for CS modifications yet, although they may be on the cards in over the next month or so...
the easiest / only current hook is the GAMING_MACS ini option ( search the thread for usage )...
basically... 'gaming' is defined mostly by ipset matches... ( there are no protocol static rules within the logic ) although there are some general static rules that try to expedite bursty stuff... so without defining your mac you are at the mercy of those rules... ( while I hope the ipsets give lots of positive matching I don't game... so I have no idea how well they are hitting stuff ) and then there are cloudflare and cdn ipsets which probably match both gaming and other stuff...
to be honest... I would probably need to see how it's working in realtime in order to better tweak the script for gaming... but I will definately keep an eye on where I'm making edits in the future and try to consolidate things to a point where there are some user hooks / ini values to set the actual CS values ( i've already done most of the variables... but they all interact so changes in one place often cascade into others and before you know it things are out of whack badly...
edit: if that's what you are looking at doing... you may try adding the game ports to the CONTROL PORTS ( tcp / udp ) variables... it would achieve a similar result... ( assuming they are not 443 lol )
Instead of placing my mac in GAMING_MACS I tried changing CS5 to CS7 in usr/lib/sqm/ctinfo_4layercake_rpi4.qos and used the RPI4QOS_GAMING_IPS_4 in wrt.ini, will this accomplish the same thing?
not sure if I finished coding the GAMING_IPS ... if you put the mac in MACS the ip's automatically get added to gamingdevice4 and gamingdevice6 which in the script would look like ${sLBL}4 ${sLBL}6 ...
ip(6)tables-save -c | grep gaming | grep set
will show you most of the relavent rules... ( and whether or not they are being hit... there is also qosdebug.sh which if your network is quiet you can use to check for hits and LEARNCONNECTIONS you can use to learn the ports )
also... it is not 'top priority'... giving any one PC 'top priority' implies you have total control of all traffic on that device ( and your highest tier free of all other traffic to assign )... not a wise move for most networks... surely you value your VOIP? DNS? traffic higher than gaming chat or windows updates on your gaming pc?
there is no capability within the script as things can go downhill very quickly... fwiw... if you really want to do that... the closest equivalent would probably be to remove it from gaming macs...
make your ipsets persistent;
RPI4QOS_IPSETPERSIST=1
add the PC ipv4 address to the latsens ipv4(6) ipset and restart sqm;
the collectd sqm collector script has been observed re-spawning itself many times... has been going on for probably around a month+... and I've been hoping for a general fix / more info to surface...
two weeks ago... once again via 'ps w', saw there were around 10 of them running... so I implemented a respawn limit to two... this had the effect of breaking sqm logging once that limit was reached...
i'm not sure which is the lesser of two evils... heaps of background processes or sqm logging stopping... perhaps a cron workaround restarting luci_statistics every 24 hours might be a better... ( which should help regardless whether my fix is implemented or not in the interim ) or something a teency bit fancier that finds all the zombies and ends those...
the message below I don't think is related... ( but it could be? ) pretty sure this message has been occuring for around 3 months... ( and i'm not sure what it relates to )
can you post the error for the dns plugin? + 'uci show luci_statistics | grep dns'
cheers
dns-plugin inclusion was marginal... kinda useful when the dnsmasq bugfixes were going on... but enabling for all builds was probably beyond what i'd personally / guess majority of users would enable...
i'll disable the 'beta' autosetup for that I think ( leave it up to the user to manually enable )... unless anyone else has input...
wireguard users are advised that for the 101(r16076) build, I needed to remove 'wireguard' as the package did not exist... ( kmod and related packages are all included... I think the above was just a previous wrapper package? )
remember reading something somewhere about it being 'in kernel' in the future but thought that may have been from 5.10 onwards... which we are not on yet...
could be a wrapper rejig and wireguard is perfectly fine... could be an interim state...
Just have to ask and here is probably the right place to do so. In the upcoming OpenWRT 21.02 release is there a official Rpi support? And if so does it make building and maintaining easier?
