ipv6 support

[ScottPause]

ipv6 support for devices, the platform and alerting/reporting.  Pretty much the whole shebang.  Alerting/reporting is the primary interest, then device support, the nthe platform.

[RSAAdmin]

I second this.

[RSAAdmin]

What is the driver? is IPV6 already getting implemented in your organizations?

[ScottPause]

ipv6 will be necessary to provide access to services on the internet.  As we are an ISP and MSSP, it stands to reason that when our customers need ipv6, we need it already in place. 

[RSAAdmin]

enVision today does have limited support for IPv6. If events have IPv6 addresses in them the events will be stored properly, you will be able to display and filter those IP addresses properly in Event Explorer, Event Viewer, Query Tool, and Alerter. See attached examples.

[ScottPause]

Thanks for the response Dan.  Its a start.  I hope that 2011 is the year of IPv6 for enVision!

[RSAAdmin]

Any update or official word on IPv6 Support?

[ScottPause]

I know that Windows 2008 servers store an IP in "source address" that is in an IPv4-to-IPv6 format (known as IPv4-Compatible IPv6 Addresses) and is too large for the 16 char field they allocated for Content 2.0!

That field used to be 32 char for the legacy tables!

Go figure!

[RSAAdmin]

We have been working on this issue and you should start to see updates to the tables so that they can accomodate IPv6 addresses in the ESUs.  I believe the changes started in the October ESU.

[ScottPause]

I finally got a new ESU installed and we recovered from the previous issue I reported with ipv6 formatted ipv4 addresses.  I've not taken a gander for IPv6 addresses, because seeing them will depress me in that they should not be there.