6rd tunneling will be available to Hong Kong Science and Technology Park

Hong Kong Science and Technology Park (HKSTP) is the second hi-tech center in Hong Kong with lots of technology companies doing R&D on new products and applications.  Sadly, no native IPv6 connections and facilities are available there yet.  How could the technology companies develop IPv6 products, solutions and applications.

Cyberport Hong Kong is aware of the situation.  I have been told quite firm that Cyberport is now developing a 6RD solution for extending a network node to tenants in HKSTP which basically works like native IPv6 connections.  6RD is a well-proven quick tunneling solution built on existing IPv4 infrastructure and only a few hardware facilities are required. What a tenant needs  is a simple router supporting 6RD connection in WAN side (D-LINK, Linksys, Netgear etc) whereas the LAN side can have DHCPv6, SLAAC or other methods of address allocation.  I hope the project could be implemented as soon as possible such that important IPv6 network resource and connectivity could be available to the high-tech community in Hong Kong.


Missing the trailing dot in zone file

Missing the trailing dot in config authoritative name servers is a common mistake committed by network administrators. I admit that I always forget this important aspect.  As a reminder, I now jot down some easy reference to alert myself aware of this carelessness.

Forward lookup of mx for zome example.com

; zone example.com.
@  IN  MX 10  mailhost.example.com
[ the final part should be mailhost.example.com.]
@  IN  MX 10  mailhost.example.com.example.com.

Reverse lookup of to produce host.example.com

; zone 2.0.192.in-addr.arpa.
1  IN  PTR    host.example.com
[ the final part should be host.example.com.]
1  IN  PTR    host.example.com.2.0.192.in-addr.arpa.

Keep the above in mind as much and as long as possible.


My new IPv6 address is 2401:0300:0:1:8080

Netfront has assigned the block 2401:300:0:1::/64 to me. I see my NIC doing auto-config after learning the prefix from the router. The IPv6 address was 2401:300:0:1:215:f2ff:febc:38c which was  derived from EUI-64.

Oh God, too difficult to remember the long string. I manually assigned 2401:300:0:1::8080 to the NIC. Afterwards, I just added the default gateway and everything was working so smoothly without reboot. Thanks to the power and flexibility of IPv6 in Linux