So I know that if you go to interfaces there is a packet steering option. What I don’t get is if you go to system startup > intiscripts. There is a service called packet steering. For me it looks like it is enabled but what I wanna know is if this service is related to the packet steering option inside interfaces. If not is there any benefit to disable this service as I know SQM/QOS does not work well with packet steering.
default fq_codel , a kind of QOS works perfectly well.
same with hfsc, all fifo-s.
Yes init script parses uci config, if disabled in uci script reads config and does nothing.
I’m sorry but could you elaborate the second half of what you said? Just so you know I use friendlywrt as the nano pi r6s doesn’t have official openwrt support yet besides rc2. Packet steering in interfaces is disabled. But when I check etc/config/network there is no ‘option packet_steering’. So I manually put it in there as 0 under option globals. But if I’m gonna try here and understand what you said. Basically packet steering in intiscripts is directly related to packet steering in interfaces.
You need to ask its authors.
Yeah unfortunately there’s little to no help from them. But one thing I can say is that it is pretty much the same as openwrt. It functions and behaves the same way. The only thing I’m asking is if I’m correct in understanding you. In which packet steering package in intiscript is directly related to the option in interfaces tab.
Wait yeah I got it lol. It is connected to it. I just had to read it again. I’m working so my mind is everywhere lol.
opkg search /etc/init.d/packet_steering
It appears you are using firmware that is not from the official OpenWrt project.
When using forks/offshoots/vendor-specific builds that are "based on OpenWrt", there may be many differences compared to the official versions (hosted by OpenWrt.org). Some of these customizations may fundamentally change the way that OpenWrt works. You might need help from people with specific/specialized knowledge about the firmware you are using, so it is possible that advice you get here may not be useful.
You may find that the best options are:
- Install an official version of OpenWrt, if your device is supported (see https://firmware-selector.openwrt.org).
- Ask for help from the maintainer(s) or user community of the specific firmware that you are using.
- Provide the source code for the firmware so that users on this forum can understand how your firmware works (OpenWrt forum users are volunteers, so somebody might look at the code if they have time and are interested in your issue).
If you believe that this specific issue is common to generic/official OpenWrt and/or the maintainers of your build have indicated as such, please feel free to clarify.
This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.