Hi all.
In light of a new discussion blossoming in Norway, we are curious about the
IPv6 security policy different ISP’s has adopted. So it would be very helpful
if you could do a quick response, either here or directly to me, on the
following question:
Which security policy are you using for
On Mon, 19 Sep 2016 12:32:27 +, Anfinsen, Ragnar wrote:
Hi all.
In light of a new discussion blossoming in Norway, we are curious
about the IPv6 security policy different ISP’s has adopted. So it
would be very helpful if you could do a quick response, either here
or
directly to me, on the
hey,
I guess none of the users know they are using IPv6 around 75-80% of
the time internal, or 20-30% on their external traffic either:-)
Indeed. I've been spreading knowledge about our deployment to our
customers and most of them have been amazed that they had no idea :) But
they have never
When we were still doing DSL I brought IPv6 online, but the only way our
customers could access it was to have the DSL modem/CPE in bridged mode,
and run their own router which was IPv6 compliant. Thus the "CPE"
security policy was whatever the router vendor defaulted. Our
observation was tha
Ted Mittelstaedt writes:
> This kind of mirrors the "default" security policy on IPv4 CPEs (since
> those CPE's have NAT automatically turned on which creates a "block in,
> permit out" kind of approach.) so I'm not sure why you would want to
> default it to being different for IPv6.
I was expla
I can tell you that -today- in my location both CenturyLink and Comcast
(giant ISPs) supply IPv6 by default on their residential CPEs - and both
of those CPEs have "inbound block outbound allow" on by default on IPv6.
As far as I know neither support UPnP on IPv6
I think you are overthinkin
