Now you get past that struggle, and a firmware update comes along for the firewall… Recent case in point.Ī client was going through a ISP requested IP Address Change to a new block. What ever the language, we need to keep our terminology as universal as possible, and some firewall admins still struggle. Or as different as Oxford English and Urban English (yup, look it up, Urban). Sometimes it’s as similar as Canadian English and American English, same but subtle differences. It’s hard keeping up with all the different firewalls so I try to keep the language universal, and yes it seems that just about every firewall product out there has their own language. Used to be we just needed a two-way NAT, then the terminology became Static NAT or SNAT, which now we can’t use thank you very much F5, so now the landed terminology that seems to have stuck which no one has usurped is “Bi-directional Static Network Address Translation”, BDSNAT or BSNAT… ok, we’ll stick with Bi-directional Static NAT. They are a necessary evil and the bane of pretty much every Lync/Skype Deployment Specialist since the beginning of UC.