A forum to discuss the Gargoyle web interface for Openwrt
https://www.gargoyle-router.com/phpbb/
ramips/mt7620 -> Xiaomi Mi Router 3GLantis wrote:Which platforms? I've only ever seen it "crash" on mvebu, but it still works.
https://openwrt.org/docs/guide-user/net ... ic_shapingAs of r25641 qos-scripts dropped the use of IMQ (package iptables-mod-imq – Intermediate Queueing Device). Its successor is IFB (Intermediate Functional Block device), (requires package: kmod-ifb and the scheduler action act_connmark included)...
https://openwrt.org/docs/guide-user/net ... .schedulerIn r25641 iptables-mod-imq (Intermediate Queueing Device) was removed and is not supported any longer. It's successor is kmod-ifb. See Intermediate Functional Block device...
I would also leave the IMQ driver but it has to look at it @pbix, why it sometimes doesn't work and fix it. (I assume that @pbix is a co-developer of QoS in Gargoyle)Lantis wrote:They are not direct replacements of each other, and IMQ does some things that IFB is not capable of.
It would be possible, but not a trivial replacement.
I'd also rather do it in consultation with @pbix
Please try one more setting with the command via ssh and then restart the router:Cezary wrote:The same problem has several of my users, on various platform. One of them says that changing the priority of imq does not solve the problem.Lantis wrote:I’ve got a list to look at. Restrictions and IMQ are on it.
Just a bit short on time at the moment.
Code: Select all
ln -s /etc/modules.d/46-ipt-imq /etc/modules-boot.d/46-ipt-imqCan you please clarify, do you always have that error message 'Error hooking IMQ' when you get non-working NAT after reboot or not? Just in the begining you said 'there is nothing in Syslog or Kernellog' but later you said that there is that error. Did you ever seen, that there is no errors about IMQ in the logs, but NAT still doesn't work after reboot?RomanHK wrote:Hmm, I confirm, it helped me to delay the start-up time of the IMQ driver - as you can see, other machines are too tight and the time is not enough.
Yes, it behaves differently and time plays a big role. It depends on when and how the IMQ driver is loaded.tester wrote:Can you please clarify, do you always have that error message 'Error hooking IMQ' when you get non-working NAT after reboot or not? Just in the begining you said 'there is nothing in Syslog or Kernellog' but later you said that there is that error. Did you ever seen, that there is no errors about IMQ in the logs, but NAT still doesn't work after reboot?RomanHK wrote:Hmm, I confirm, it helped me to delay the start-up time of the IMQ driver - as you can see, other machines are too tight and the time is not enough.
PS: Same (imo) problem mentioned here: viewtopic.php?f=14&t=11988#p53164
Got it, thanks. But what output of 'cat /proc/net/ip_tables_names' will be in cases 'a)' and 'b)'?RomanHK wrote:a) Sometimes the IMQ driver is loaded in parallel with the NAT driver and then the Internet is not running, the log does not show errors.
b) NAT is loaded first and then the error "Error hooking IMQ" appears in the log.
c) IMQ driver loads first, then NAT driver (not concurrently) and internet works.