Until I know the purpose of these domains I am not allowing them to ‘secretly’ whitelist them in the 9100em config:
activatemyfios.verizon.net — what is the ongoing need to allow this?
activate.verizon.net — what is the ongoing need to allow this?
netservices.verizon.net — some portal features
sso.verizon.net — I do not want 1960s features in overpriced voip
techassist.verizon.com — no thanks, I do not need you poking about
cpe-ems.verizon.com — smtp?
cpe-ems80.verizon.com – wget 188.8.131.52:443
wbadownload.verizon.net — ‘free’ wifi hotspot bloatware that smells like netzero and?
download.verizon.net — what is the ongoing need to allow this?
Advanced Filter Initial outbound and initial inbound rules trump ‘secret’ whitelist:
This rule set does not break FIOS TV guide data. I could not care less about VOD and have not tested it.
Other modifications to the configuration file in a text editor are necessary to assure privacy (keep verizon out) and prevent verizon from further raping the firmware with “updates” or having the device destroy itself
solution: demand ethernet from ONT to house. verizon can provide as many 9100ems as are needed to bridge ethernet to moca for the STBs or DVRs. No GPON? They’ll whine that you’ll have to suffer 100 Mbps instead of ~240 Mbps (of version one point zero MoCa) as verizon “opted” not to bother with gigabit ports on the 9100em among other awesome features we mere mortals need not about fret. Yeah, right, I’ll definitely limit myself to the 9100em. It is reassuring to see how knowledgeable fios people are. :sigh: