One way of temporarily getting round this would be to possibly set a quota for ips in certain ranges - not checked properly but it would be fairly quick to check if it would help
cArNaGe wrote:Well I got around it. I threaten to throw his laptop out the window if I caught him changing his IP again...
I'd still set a very low qos % for the catch all class, so he loses out when changing ip. Not sure what he would then gain by changing it. Show him it and he won't change it then
I think I have a fix for this in the repo now. I attach the revised file. If you will unzip it and replace the file of the same name on your router located at /usr/lib/gargoyle_firewall_util life should improve.
Please post your results here to confirm that the fix is good.
Thanks for your work on identifying and isolating this bug.
The target directory for this file is /usr/lib/gargoyle_firewall_util. You will know you are in the right place when you are replacing a file of the same name in that directory.
This directory is not the one you listed in your previous post so I suspect you just dropped the file in the wrong location.
If that does not fix it for you then show me the output of the command "iptables -vnL forward -t filter" after connecting with the blocked MAC.
Sorry yes that was a typo - I renamed the old one before copying the new one in place.
I also know I overwrote a valid file as I just had grief from the family, just got in this evening (I did the work this morning) without realising I just reset my wireless rules with the file
I am doing this on 1.5.4. My ip I set as 192.168.1.211 and it is connected by wired connection
Hopefully these are what you wanted
Many thanks for your assistance on this, happy todo whatever is required to assist in resolving it