Whitellisting and iOS
Posted: Tue Apr 28, 2020 6:23 am
Hello hello, thanks for such a great firmware, it's been very useful for us.
We have very expensive Iridium internet on board the ship and therefor we want that all devices that connect to the internet can ONLY do a few certain things;
We have pop3 email, some http and https sites and we want whatsapp messenger to work solely.
Solved it so far by making two groups via DHCP assignments based on their MAC address put in a range that the rules and quota's apply so they don't gobble up our 1 GB/month data. The PC's work well (windows 10) Daily 5 mb/ device reset every day, perfect! emails via pop3 are a few kb's and the weatherforecast is 100 kb per download.
I have an issue with iOS devices that go straight through all the rules that I make for them.
Setup that makes the most sense for me so far:
1st group (IP range) for PC that can access pop3 email (on port allowed) 993 and sending 568, plus a few http (80) and https (443) sites, that works well, the websites are allowed and the pop3 email connects easily.
2nd group (IP Range) are the mobile devices, that should only access whatsapp, now android behaves well, although I suspect it still tries and successful connects though the rules, but iOS just goes straight though the rules . If you leave it connected to the wifi, after about 3 minutes the 5mb is gone, and the phone hasn't done anything besided connecting to a lot of stuff that it shouldn't do based on the rules., and the the quota successfully disconnect the device (thank god!)
I tried this:
domain filter, gets fully ignored by iOS and gargoyle happily routes it. Safari does not work, so web domain works, but a lot more stuff eats data!
Port based on 5222, 5223 (default whatsapp ports) + and and without domain filters and combinations of that, also I see a lot of TCP connections on port 443 on domains I have to whitelisted.
I'm running the latest gargoyle on a TP-link wr1043 v1
Am I doing something wrong? Or can someone point where I could configure that the mobile devices can connect only to whatsapp dot net on port 5222 and 5223
We have very expensive Iridium internet on board the ship and therefor we want that all devices that connect to the internet can ONLY do a few certain things;
We have pop3 email, some http and https sites and we want whatsapp messenger to work solely.
Solved it so far by making two groups via DHCP assignments based on their MAC address put in a range that the rules and quota's apply so they don't gobble up our 1 GB/month data. The PC's work well (windows 10) Daily 5 mb/ device reset every day, perfect! emails via pop3 are a few kb's and the weatherforecast is 100 kb per download.
I have an issue with iOS devices that go straight through all the rules that I make for them.
Setup that makes the most sense for me so far:
1st group (IP range) for PC that can access pop3 email (on port allowed) 993 and sending 568, plus a few http (80) and https (443) sites, that works well, the websites are allowed and the pop3 email connects easily.
2nd group (IP Range) are the mobile devices, that should only access whatsapp, now android behaves well, although I suspect it still tries and successful connects though the rules, but iOS just goes straight though the rules . If you leave it connected to the wifi, after about 3 minutes the 5mb is gone, and the phone hasn't done anything besided connecting to a lot of stuff that it shouldn't do based on the rules., and the the quota successfully disconnect the device (thank god!)
I tried this:
domain filter, gets fully ignored by iOS and gargoyle happily routes it. Safari does not work, so web domain works, but a lot more stuff eats data!
Port based on 5222, 5223 (default whatsapp ports) + and and without domain filters and combinations of that, also I see a lot of TCP connections on port 443 on domains I have to whitelisted.
I'm running the latest gargoyle on a TP-link wr1043 v1
Am I doing something wrong? Or can someone point where I could configure that the mobile devices can connect only to whatsapp dot net on port 5222 and 5223