I see in the Untangle IPv6 roadmap (http://wiki.untangle.com/index.php/IPv6) that version 9.0 supports IPv6 by pass through in bridge mode. I also see that IPv6 application processing is planned for 2013. I believe that in bridge mode Untangle will currently pass through IPv6 traffic but none of the applications, such as web filter [lite], spyware blocker, virus blocker [lite], intrusion prevention, application control [lite], etc., will process (inspect) any of the IPv6 traffic and management applications such as DNCP and DNS will not manage IPv6 addresses. Is that correct?
Will phase 2 support IPv6 NAT such that internal addresses using IPv4 can route to the Internet when the ISP provides only an IPv6 address in a way that the application stack will process traffic destined for the Internet from the internal network?
Are you aware of AT&T's aggressive IPv6 migration schedule that is forcing customers onto IPv6 only (see http://fecinc.com/blog/att-lays-out-...ration-plan/)? Apparently AT&T is forcing customers (maybe currently only ADSL2/ADSL2+ customers) to use IPv6 only on their WAN connection in a way that requires upgrading the DSL modem and router. I am guessing that customers who are paying for a fixed IP (v4) address will be able to keep that IPv4 address. (BTW, apparently AT&T is doing this with very little notice to the customer, and whatever notice they give might be buried on a bill.) AFIK, AT&T is doing this migration region-by-region and Southern California (where I am located) is in the process of this migration (meaning customer no longer gets an IPv4 address) now.
Is it possible to use a DSL modem/router (which supports IPv6) such that the modem/router does IPv4 to IPv6 NAT and an Untangle server can get an IPv4 address for its external address so that the internal network uses IPv4 and the Untangle UTM stack can inspect traffic?
Will phase 2 support IPv6 NAT such that internal addresses using IPv4 can route to the Internet when the ISP provides only an IPv6 address in a way that the application stack will process traffic destined for the Internet from the internal network?
Are you aware of AT&T's aggressive IPv6 migration schedule that is forcing customers onto IPv6 only (see http://fecinc.com/blog/att-lays-out-...ration-plan/)? Apparently AT&T is forcing customers (maybe currently only ADSL2/ADSL2+ customers) to use IPv6 only on their WAN connection in a way that requires upgrading the DSL modem and router. I am guessing that customers who are paying for a fixed IP (v4) address will be able to keep that IPv4 address. (BTW, apparently AT&T is doing this with very little notice to the customer, and whatever notice they give might be buried on a bill.) AFIK, AT&T is doing this migration region-by-region and Southern California (where I am located) is in the process of this migration (meaning customer no longer gets an IPv4 address) now.
Is it possible to use a DSL modem/router (which supports IPv6) such that the modem/router does IPv4 to IPv6 NAT and an Untangle server can get an IPv4 address for its external address so that the internal network uses IPv4 and the Untangle UTM stack can inspect traffic?