Feature Request: Adding IP subnets to whitelist
Posted: Mon Jul 11, 2016 10:24 am
It would be great to be able to add IP ranges to the whitelist. Like 172.23.208.0/24, 172.23.208.0-255, or 2001:67c
0::/64.
The scenario I'm having trouble with NoScript otherwise follows below:
---
Using https://map.luebeck.freifunk.net gets a little tricky with NoScript:
Once a user clicks on a node in this map, they can gather additional information about this device and its current status by clicking on the IP address. They end up on a page like this:
http://[2001:67c0
3cff:fe9a:5702]/
From there, a user can click on neighboring nodes to get their status page. So you can basically hop through the mesh network like this and get a picture of your mesh neighborhood.
One feature of this is, that these status pages are 100% decentralized, so each of these tiny plastic wifi routers provides their own little status page. Unfortunately, they do not have a common domain name though... Therefore IPv6 addresses are used instead.
0::/64.The scenario I'm having trouble with NoScript otherwise follows below:
---
Using https://map.luebeck.freifunk.net gets a little tricky with NoScript:
Once a user clicks on a node in this map, they can gather additional information about this device and its current status by clicking on the IP address. They end up on a page like this:
http://[2001:67c
0
3cff:fe9a:5702]/From there, a user can click on neighboring nodes to get their status page. So you can basically hop through the mesh network like this and get a picture of your mesh neighborhood.
One feature of this is, that these status pages are 100% decentralized, so each of these tiny plastic wifi routers provides their own little status page. Unfortunately, they do not have a common domain name though... Therefore IPv6 addresses are used instead.