Page 21 of 22
Re: Gargoyle 1.11.0 Release Candidate 5
Posted: Thu May 09, 2019 1:31 pm
by RomanHK
tester wrote: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.
Got it, thanks. But what output of 'cat /proc/net/ip_tables_names' will be in cases 'a)' and 'b)'?
For a):
Code: Select all
root@Gargoyle:~# cat /proc/net/ip_tables_names
mangle
filter
root@Gargoyle:~#
For b):
Code: Select all
root@Gargoyle:~# cat /proc/net/ip_tables_names
nat
mangle
filter
root@Gargoyle:~#
For c):
Code: Select all
root@Gargoyle:~# cat /proc/net/ip_tables_names
nat
mangle
filter
root@Gargoyle:~#
EDIT:
Just to notice:
If there is an error in NAT, you can run the module install command as many times as you want and nothing will be done anyway (only a new router restart will help):
Code: Select all
root@Gargoyle:~# modprobe iptable_nat
root@Gargoyle:~#
Correct output (when NAT works):
Code: Select all
root@Gargoyle:~# modprobe iptable_nat
iptable_nat is already loaded
root@Gargoyle:~#
Re: Gargoyle 1.11.0 Release Candidate 5
Posted: Thu May 09, 2019 4:14 pm
by tester
RomanHK wrote:For b):
How then we can detect this bug with a script?
Yours `cat /proc/net/ip_tables_names | grep nat` is not enough now, it's only for case 'a'.
RomanHK wrote:(only a new router restart will help)
Do you try smth like this:
/etc/init.d/firewall stop
/etc/init.d/qos_gargoyle restart
/etc/init.d/firewall start
Will not help as well?
Re: Gargoyle 1.11.0 Release Candidate 5
Posted: Thu May 09, 2019 4:54 pm
by RomanHK
tester wrote:How then we can detect this bug with a script? Yours `cat /proc/net/ip_tables_names | grep nat` is not enough now, it's only for case 'a'.
This IMQ@NAT error is only when these two modules collide. The OpenWrt module no longer uses the IMQ, so I am making it out - that's the only difference between OpenWrt and Gargoyle. When the Internet does not run, I run the script and the error is reflected every time that iptable_nat is not loaded.
tester wrote:Do you try smth like this:
/etc/init.d/firewall stop
/etc/init.d/qos_gargoyle restart
/etc/init.d/firewall start
Yes, I tried to restart all of these services but no result. The error is in the kernel module and nothing else will help, nor release the module and reload it - it behaves as if it has loaded correctly, but it is not.
Re: Gargoyle 1.11.0 Release Candidate 5
Posted: Sat May 11, 2019 12:39 pm
by tester
RomanHK wrote:
When we rename 46-ipt-imq to ipt-imq it starts to load earlier or later? I thought that numbers are loading earlier, no?
Re: Gargoyle 1.11.0 Release Candidate 5
Posted: Sat May 11, 2019 12:53 pm
by RomanHK
I also thought, but still it didn't help:
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.
I have nothing better. My latest edits will ensure that the IMQ module is loaded first independently of the other modules that are responsible for it.
Re: Gargoyle 1.11.0 Release Candidate 5
Posted: Sat May 11, 2019 1:43 pm
by tester
I mean, maybe we had to rename 46-ipt-imq to 01-ipt-imq?
But moving to modules-boot.d looking better, of course.
Re: Gargoyle 1.11.0 Release Candidate 5
Posted: Sat May 11, 2019 2:02 pm
by RomanHK
tester wrote:I mean, maybe we had to rename 46-ipt-imq to 01-ipt-imq?
But moving to modules-boot.d looking better, of course.
It doesn't matter in the
/etc/modules-boot.d directory because NAT modules do not run in this directory.
Re: Gargoyle 1.11.0 Release Candidate 5
Posted: Sat May 11, 2019 2:09 pm
by tester
RomanHK
So if I don't want to use links I have to copy (not move) file
46-ipt-imq to /etc/modules-boot.d/ ?
Re: Gargoyle 1.11.0 Release Candidate 5
Posted: Sat May 11, 2019 2:12 pm
by RomanHK
tester wrote:RomanHK
So if I don't want to use links I have to copy (not move) file
46-ipt-imq to /etc/modules-boot.d/ ?
Practically yes.
EDIT: The link there is just to ensure consistency when something changes in the module so that it doesn't have to change in more places. In this case, size doesn't matter. But it is correct to create a link.
Re: Gargoyle 1.11.0 Release Candidate 5
Posted: Wed May 15, 2019 10:51 am
by RomanHK
So I have too much bad news.
Although I delayed loading the IMQ module a few seconds, it did not help and sometimes the
iptable_nat kernel module was not loaded.
Now I'm going to test if the IMQ is responsible for the mistakes by deleting it.