[EAS] IPAWS IP

[Dave Turnmire]

As long as the various IP addresses used are adjacent (as in your Google 
example) or few (in Google example), that is easy to manage.  Telling 
people they need an enterprise level Cisco router (something like $8K) 
just to accommodate FEMA, in an environment that could have had good 
security for a fraction of that, is something else.  Spending that kind 
of money (and having the associated in-house expertise to configure such 
a router) is not remotely practical for a lot of stations.

So as a practical matter, if FEMA isn't can't keep their IP address 
options to a fairly narrow range (say, a particular subnet), 
broadcasters will either have to open outbound internet connections 
entirely on their equipment LAN (something they may have significant 
security concerns about), or move it to another LAN... such as an office 
LAN that already has open outbound access (which is what we did).

Dave

On 6/29/2012 7:50 AM, Harold Price wrote:
> ...I'm not an expert on firewalls either, but remember to take into
> account DNS based load balancing.
>
> For example, I did a ping on google.com, a few seconds apart, from
> two different computers on the same lan segement, and got two
> different addresses:
> 74.125.226.230
> 74.125.226.200
>
> Indeed, checking directly with a DNS server, I got this for google.com:
> Name:    google.com
>             74.125.226.197
>             74.125.226.194
>             74.125.226.198
>             74.125.226.192
>             74.125.226.196
>             74.125.226.201
>             74.125.226.200
>             74.125.226.199
>             74.125.226.195
>             74.125.226.193
>             74.125.226.206
>