But let’s not give them access to everything.
This is a common scenario I see, where someone needs to get updates to some magical software package on the internet. Â Great. Â And people just give them access to ANY site, which ends up being not only the internet (the intended destination) but the rest of their internal network. Â Granted a good defense in the SDN world is inbound rules as well for each VM, but everything is never 100%.
RFC1918Â defines our friends, the private address ranges:
10.0.0.0 - 10.255.255.255 (10/8 prefix) 172.16.0.0 - 172.31.255.255 (172.16/12 prefix) 192.168.0.0 - 192.168.255.255 (192.168/16 prefix)
However the solution to this fun filled problem is to grant them HTTP/HTTPS access to the inverse of this. Â Enter the netmask command. Â You can give it a range, and it’ll lay out what networks to you need to add like this:
netmask -c 0.0.0.0:188.8.131.52 0.0.0.0/5 184.108.40.206/7
Now I can exclude everything right up until 10.0.0.0/8 !
It’s quite the handy tool, but I didn’t see any Windows version. Â So a few minutes with MinGW, and dealing with it’s weird Makefile’s way of linking things, and here you go!
This way you can permit internet access, not give them inside, access and still have a global DENY actually work.
And if anyone is interested here are the networks:
0.0.0.0/5 220.127.116.11/7 18.104.22.168/8 22.214.171.124/6 126.96.36.199/4 188.8.131.52/3 184.108.40.206/2 220.127.116.11/3 18.104.22.168/5 22.214.171.124/6 126.96.36.199/12 188.8.131.52/11 184.108.40.206/10 220.127.116.11/9 18.104.22.168/8 22.214.171.124/7 126.96.36.199/4 192.0.0.0/9 188.8.131.52/11 184.108.40.206/13 220.127.116.11/16 18.104.22.168/15 22.214.171.124/14 126.96.36.199/12 188.8.131.52/10 184.108.40.206/8 220.127.116.11/7 18.104.22.168/6 22.214.171.124/5 126.96.36.199/4
Yes, I know it’s a LOT of typing.