- IPv6 news and information

MONTREAL (February 4, 2011) – gogo6 inc., the leading provider of IPv6 products, community and services, today announced the release of gogoCPE version 1.0 – a small v6 adaptor for the home that can be installed and providing IPv6 within a minute. Designed to work with, rather than replace home networking equipment, the gogoCPE can be used to deploy IPv6 using IPv4 or to deploy IPv4 using IPv6 – both resulting in a dual-stack home network. Early customers of the gogoCPE include SingTel, Comcast and Globe Telecom.

The gogoCPE is plug ‘n’ play simple and designed to be installed by the end user without any support. The gogoCPE uses the same code as the gogoCLIENT which has reliably provided IPv6 to over 150,000 users of the Freenet6 service.

The gogoCPE supports the most popular transition technologies including TSP, DS-Lite, 6RD, DSTM and L2TP. It is compatible with the gogoSERVER and other manufacturer systems. Its wide technology support allows it to work in any IPv4/v6 network scenario, including:
Providing IPv6 to existing and new customers with IPv4 home routers in an IPv4 network.
Providing IPv4 to new customers with IPv4 home routers in an IPv6 network.
Providing IPv6 to new customers without IPv4 home routers in an IPv4 network.

“Hands down the most difficult part of introducing IPv6 into a broadband network is the home. This is where a majority of the IPv6 costs lie and where service providers have the least control. In a vast majority of the cases the home networking equipment is either not upgradable or owned by the end user making IPv6 synonymous with installing new equipment,” said Bruce Sinclair, gogo6 CEO. “The recent depletion of IPv4 addresses from the IANA pool increases the pressure on service providers to find a simple yet effective solution to offer v6 and v4 by way of v6. Service providers can quickly introduce IPv6 into their networks with a single 1U gogoSERVER and one gogoCPE per home.”

Availability and pricing
The gogoCPE is available today after being tested by service providers around the world. In addition to being sold in volume individual gogoCPEs are available on the gogo6 website. These units are preconfigured to work with Freenet6 making them plug ‘n’ play ready out of the box. Individual units cost $99 plus shipping and handling. Volume pricing is lower.

For detailed information on the gogoCPE go to: http://bit.ly/gogoCPEinfo
To purchase individual units of the gogoCPE go to: http://bit.ly/gogoCPEbuy
To request a volume quote contact: [email protected]

With more then 400 votes on the last poll it is time for a fresh new question. The definite answer of the last poll will be posted next week.

Have you ever tried to get somebody to support IPv6 in their services/products or are you going to?

Yes

No

Why would i do that?

If you answered yes and you want to share your story please comment below!

Did you know that the IRC network GameSurge was reachable over IPv6?

You can now chat to your game mates over IRC using IPv6 on one of the following hostnames:

ipv6.gamesurge.net

irc.ipv6.gamesurge.net

 

An AAAA record for irc.gamesurge.net (i.e. IPv6 via irc.gamesurge.net if your client/os/connection support it) might be added in the future when services over IPv6 are stable.

Below are snippets for the settings you can use to enable IPv6 on Apache2. These settings can be changed/added from /etc/apache2/ports.conf

You can use multiple Listen directives to listen on multiple IP’s. This goes for both IPv4 and IPv6.

Listen *

(Both IPv4 and IPv6 on every IP)

Listen 192.168.0.100

(IPv4 Only)

Listen Listen [2001:db8::a00:20ff:fea7:ccea]:80

(IPv6 Only)

You can also specify the port apache uses with the Listen directive. To listen op port 443 on both IPv4 and IPv6 use the following:

Listen 443

(Both IPv4 and IPv6 on every IP on port 443)
  

These vhosts go in /etc/apache2/sites-enabled/nameofyourvhost.conf
Set a vhost on all IP’s (both IPv4 and IPv6).

<virtualhost *:80>
   ServerName fix6.net
   ServerAlias *.fix6.net
   DocumentRoot /www/fix6.net/public_html
   ErrorLog /www/fix6.net/logs/error_log
   Customlog /www/fix6.net/logs/combined_log combined
</virtualhost>

Set vhost to a specific IPv6 only

<virtualhost [2001:db8::a00:20ff:fea7:ccea]:80>
   ServerName fix6.net
   ServerAlias *.fix6.net
   DocumentRoot /www/fix6.net/public_html
   ErrorLog /www/fix6.net/logs/error_log
   Customlog /www/fix6.net/logs/combined_log combined
</virtualhost>

Set vhost to a specific IPv4 and IPv6 adres

<virtualhost 192.168.1.100:80, [2001:db8::a00:20ff:fea7:ccea]:80>
   ServerName fix6.net
   ServerAlias *.fix6.net
   DocumentRoot /www/fix6.net/public_html
   ErrorLog /www/fix6.net/logs/error_log
   Customlog /www/fix6.net/logs/combined_log combined
</virtualhost>

Source and more information: http://httpd.apache.org/docs/2.2/mod/mpm_common.html and http://httpd.apache.org/docs/2.2/vhosts/name-based.html

Below are snippets for the settings you can use to enable IPv6 on Postfix. These settings can be changed/added from /etc/postfix/main.cf

Select the protocols which postfix uses:

inet_protocols = ipv4

(DEFAULT: enable IPv4 only)

inet_protocols = all

(enable IPv4, and IPv6 if supported)

inet_protocols = ipv4, ipv6

(enable both IPv4 and IPv6)

inet_protocols = ipv6

(enable IPv6 only)

Set the listen interface:

inet_interfaces = all

(DEFAULT, all IPv4 and IPv6 interfaces available)

inet_interfaces = loopback-only

(Postfix version 2.2 and later)

inet_interfaces = 127.0.0.1

(Just Localhost)

inet_interfaces = 127.0.0.1, [::1]

(Postfix version 2.2 and later)

inet_interfaces = 192.168.1.2, 127.0.0.1

(Multiple IPv4)

inet_interfaces = [2001:db8::dddd:eeee:ffff], [2001:db8:42:1af::1]

(Postfix version 2.2 and later)

You can also set the preferred SMTP IP to be used.

smtp_bind_address6 = 2001:db8:42:1af::1

 
 

Source and more information: http://www.postfix.org/IPV6_README.html

On Thursday, 3 February 2011, at 14:30 UTC, the Number Resource Organization (NRO), along with the Internet Corporation for Assigned Names and Numbers (ICANN), the Internet Society (ISOC) and the Internet Architecture Board (IAB) will hold a ceremony and press conference to make a significant announcement and to discuss the global transition to the next generation of Internet addresses.

This event will be webstreamed live.
Find more information on www.nro.net.