In the last days I migrated all my internal services to IPv6.
All my jails have an IPv4 and an IPv6 address now. All Apaches (I have one for my picture gallery, one for webmail, and one for internal management) now listen on the internal IPv6 address too. Squid is updated from 2.x to 3.1 (the most recent version in the Ports Collection) and I added some IPv6 ACLs. The internal Postfix is configured to handle IPv6 too (it is delivering everything via an authenticated and encrypted channel to a machine with a static IPv4 address for final delivery). My MySQL does not need an IPv6 address, as it is only listening to requests via IPC (the socket is hardlinked between jails). All ssh daemons are configured to listen to IPv6 too. The IMAP and CUPS server was picking the new IPv6 addresses automatically. I also updated Samba to handle IPv6, but due to lack of a Windows machine which prefers IPv6 over IPv4 for CIFS access (at least I think my Windows XP netbook only tries IPv4 connections) I can not really test this.
Only my Wii is a little bit behind, and I have not checked if my Sony-TV will DTRT (but for this I first have to get some time to have a look if I have to update my DD-WRT firmware on the little WLAN-router which is “extending the cable” from the TV to the internal network, and I have to look how to configure IPv6 with DD-WRT).
GD Star Rating
loading…
GD Star Rating
loading…
Tags: dd wrt firmware,
internal management,
ipv4 address,
ipv6 address,
ipv6 addresses,
ipv6 ipv4,
netbook,
sony tv,
wii,
wlan router —
After enabling IPv6 in my WLAN router, I also enabled IPv6 in my FreeBSD systems. I have to tell that the IPv6 chapter in the FreeBSD handbook does not contain as much information as I would like to have about this.
Configuring the interfaces of my two 9–current systems to also carry a specific IPv6 address (an easy one from the ULA I use) was easy after reading the man-page for rc.conf. After a little bit of experimenting it came down to:
ifconfig_rl0_ipv6=“inet6 ::2:1 prefixlen 64 accept_rtadv“
ipv6_defaultrouter=”<router address>”
Apart from this address (I chose it because the IPv4 address ends in “.2″, this way I can add some easy to remember addresses for this machine if needed), I also have two automatically configured addresses. One is with the same ULA and some not so easy to remember end (constructed from the MAC address), and one is from the official prefix the router constructed out of the official IPv4 address from the ISP (+ the same end than the other end).
Additionally I also have all my jails on this machine with an IPv6 address now (yes, they are like “…:2:100″ with the :100 because the IPv4 address ends in “.100″). Still TODO is the conversion of all the services in the jails to also listen on the IPv6 address.
I already changed the config of my internal DNS to have the IPv6 addresses for all systems, listen on the IPv6 address (when I add an IPv6 network to allow-query/allow-query-cache/allow-recursion bind does not want to start). And as I was there, I also enabled the DNSSEC verification (but I get a lot of error messages in the logs: “unable to convert errno to isc_result: 42: Protocol not available”, one search result which talks exactly about this error tells it is a “cosmetic error”…).
I noticed that an IPv6 ping between two physical machines takes a little bit more time than an IPv4 ping (no IPsec enabled). It surprised me that this is such a noticeable difference (not within the std-dev at all):
— m87.Leidinger.net ping statistics —
10 packets transmitted, 10 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 0.168÷0.193÷0.220÷0.017 ms
— m87.Leidinger.net ping6 statistics —
10 packets transmitted, 10 packets received, 0.0% packet loss
round-trip min/avg/max/std-dev = 0.207÷0.325÷0.370÷0.047 ms
The information I miss in the FreeBSD handbook in the IPv6 chapter is what those other IPv6 related services are and when/how to configure them. I have an idea now what this radvd is, but I am not sure what the interaction is with the accept_rtadv setting for ifconfig (and I do not think I need it, as my WLAN router seems to do it already). I know that I get the IPv6-friendly network neighborhood displayed with ndp(8). I did not have a look at enabling IPv6 multicast support in FreeBSD, and I do not know what those other IPv6 options for rc.conf do.
GD Star Rating
loading…
GD Star Rating
loading…
Tags: address ends,
cosmetic error,
current systems,
freebsd handbook,
freebsd systems,
ipv4 address,
ipv6 address,
ipv6 addresses,
ipv6 network,
wlan router —
The manufacturer of my WLAN router released a new firmware. It contains IPv6 and DNSSEC support. I got a little bit of time and power to install it. Unfortunately my ISP does not provide IPv6 connectivity.
I have now installed the IPv6 support in Windows XP for the Netbook, created (and registered) an ULA prefix at SixXS, and verified that the network stack of XP gets it from the WLAN router.
When I do an IPv6 ping from the laptop to the router, it works, but the IPv6 address does not show up in the Homenetwork overview of the router. Seems they still have some work to do.
Regarding DNSSEC I do not see any options in the management interface, but I assume it just means that the DNS server does the right thing when he is confronted with recursive DNSSEC requests. No idea if he will validate himself and if yes, if he will add some log messages regarding it or not.
GD Star Rating
loading…
GD Star Rating
loading…
Tags: dns server,
firmware,
ipv6 address,
ipv6 support,
log messages,
management interface,
netbook,
network stack,
prefix,
wlan —