@Bray
You can define network segments for public IP addresses and then assign a building to them. I use one named Public. You also need to check the override building option as well.
Public Addresses
1.0.0.0 - 9.255.255.255
11.x.x.x - 126.255.255.255
129.0.0.0 - 169.253.255.255
169.255.0.0 - 172.15.255.255
172.32.0.0 - 191.0.1.255
192.0.3.0 - 192.88.98.255
192.88.100.0 - 192.167.255.255
192.169.0.0 - 198.17.255.255
198.20.0.0 - 223.255.255.255
The other way to do this is to specifically define and list all of your ip address ranges in your network segments then put a general one (1.0.0.1-255.255.255.254) and this will cover all other addresses. Anything that is defined will overrule the general one, but it covers all the bases. I then define the general one as Off-Campus. Keeps you from missing anything.
Gabe Shackney
Princeton Public Schools
Gabe,
I ran into an issue where doing this caused an issue. The ones defined DID NOT override the general one. I had to exclude our internal addresses (172.16.1.1 - 172.16.200.254), so I did this:
1.0.0.0 - 172.16.1.0 External 1
172.16.200.0 - 255.255.255.254 External 2
I defined the actual segments used and assigned them to buildings, etc…
Some policies require actually being on our network (6GB Adobe installs, etc…). This solves that issue easily.