> when a TAC engineer wanted to bounce our Voice VLAN SVI in the middle of an
> *airport* production day.
> I about turned over my desk trying to wrest the remote control session back
> from him before he hit enter
> on the shut. Since then, I have had to go through a not insignificant
>
> But I also agree there are limits to what needs IoTing. I don't live in a
> house large enough that I can't go see if the box needs cleaning within
> about 20s. I also sure as hell don't need a notification on my phone that
> one of them just made a deposit.
*ding!* 1 New Notification: "clean
nt: Friday, July 17, 2020 5:00 PM
To: Lyden, John C
Cc: nanog@nanog.org
Subject: [EXTERNAL] Re: Wifi Calling Firewall Holes to Punch
In our university environment, wifi calling works just fine over NAT and we
have not made any inbound port exceptions in the firewall for it. The critical
piec
ro, NJ 08028
rowan.edu/irt<http://rowan.edu/irt>
From: Alex Buie
Sent: Friday, July 17, 2020 12:59 PM
To: Lyden, John C
Cc: nanog@nanog.org
Subject: [EXTERNAL] Re: Wifi Calling Firewall Holes to Punch
It's been a minute since I've set this up in a corp/campus wif
Hey gang.
We're setting up a unified wireless network for the students here, and to get
around the issues with Nintendo and NAT we devoted a large chunk of public IP
space to them.
We're aware that this is causing issues with wifi calling on Verizon, TMo etc
because it appears they initiate
5 matches
Mail list logo
