Read the statement by Michael Teeuw here.
Issue with White list IP(s) not working :(
-
I do thank you for your time, but that thread is someone with the exact same problem as me and the answer is the same one you posed here and it doesnt work.
Why does it seem only a few people are having this issue?
-
@pingywon said in Issue with White list IP(s) not working :(:
Why does it seem only a few people are having this issue?
I really can’t say why it happens to some and not others. It’s hard to troubleshoot for someone when there are so many unknowns. There are so many different setups (various Pi’s, PC’s, Mac’s, etc) all running different OS’s (various Raspbian flavors, various Windows versions, Mac OS, various uBuntu versions). This make’s it impossible for “one fix fits all” solutions. Personally, I do the best I can to help people that ask for help. There are many Whitelist topics that have been posted. I can only suggest that you use the search function here on the forum. In the meantime, someone else may have a suggestion that might work for you.
Best of luck to you
https://forum.magicmirror.builders/search?term=Whitelist&in=titlesposts
-
Anyone else have any input. Im kinda stuck here. I have looked at other threads and have not drawn any conclusions
-
Not my area, but I was reading this: https://forum.magicmirror.builders/topic/1326/ipwhitelist-howto/8
and it mentions that the whitelisting on a range is for IPv6 , so maybe not working with IPv4.
Hope that help -
-
FOUND A WAY TO RESOLVE THIS!
Add
cat /etc/modprobe.d/ipv6.conf # Don't load ipv6 by default alias net-pf-10 off # uncommented alias ipv6 off # added options ipv6 disable_ipv6=1 # this is needed for not loading ipv6 driver blacklist ipv6
to turn off all IPv6 on the Raspi.
Than edit all the IPv6 out of your config file.}, ipWhitelist: [ "192.168.0.92", "192.168.0.1/24", "127.0.0.1"
I still have the .92 in there from testing. It is not needed.
did a sudo reboot just for safe measure and now it all seems to be working as intended. No real idea what the actual issue was…but it is resolved. FINALLY! :)
-
I just realized something. The machine I’m working on had MM 2.1.1 on it. I upgraded to MM 2.1.2 and lo and behold, the IPWhitelist is as whacked as can be. So, if I gave bad information, which I did, please excuse my oversight.
Peace! -
So, After a research about all this mess it up, the problem was a bug inside of ipfilter and MagicMirror too. When I added inside the sample config I’ve using express-ipfilter@0.2.4 In this version has a bug was fixed in 0.3.1 https://github.com/baminteractive/express-ipfilter/commit/4adc5dc33e6ef5086e36a7a56184da7cdcd056bf
The bug for MagicMirror was fixed some weeks ago,
https://github.com/MichMich/MagicMirror/commit/a7297d2685f5ed9b6b34df496065f05ee0d36568You can using now the develop branch or install express-ipfilter previous of the 0.3.1
-
@roramirez said in Issue with White list IP(s) not working :(:
You can using now the develop branch or install express-ipfilter previous of the 0.3.1
Ahh, thank you! :^)
-
@roramirez does that mean that I only have to do an
npm install express-ipfilter
from the rooter with my console, if I have the actual magic mirror installed?
tnx
Peter