egemen, please tell us why IPv6-filtering is disabled by default

Well, the title says it all. :slight_smile:

I already got warnings for IPv6 TCP or UDP connections, so it seems to be working.
Or is there something not finished, insecure etc.?

Thank you, I’d really appreciate an answer.
If it’s a good feature, why not enable it by default?

IPv6 filtering works but the support for the protocol is incomplete. Amongst other things, there’s no ICMPv6 filtering and there’s no support for IPv6 extension headers.

Because IPV6 is not ubiquitous yet, it can be asumed that only those who work with IPv6 need this feature on.

No need to show more alerts unnecessarily for now. Otherwise it working.

Are you sure?

http://www.ld-host.de/uploads/thumbnails/853f975f2abc23324971252dfe8dba51.png

Could you please demonstrate this?
What are the security risks coming with this?

Unfortunately, the options provided in CIS do not provide ICMPv6 filtering. In CIS currently, one may either allow all ICMPv6 traffic, or none. As ICMPv6 is critical to the correct functioning of IPv6, correct filtering is paramount. unfortunately, the current implementation is almost completely useless. You may read more here

Could you please demonstrate this? What are the security risks coming with this?

Here’s a fairly simple explanation. You may also wish to read RFC 2460

Thank you. :slight_smile:

Still something to do for Comodo…