New Hardware 2021

So I am finally running FreeBSD again on a Laptop.

The HW probe can be found here:

Notable obstacles:

DRM: I have to run the 5.7-wip branch and add my pciid. (

WLAN: There is no driver for the integrated wlan. After some help from dch@ I have now got an EDIMAX rtwm USB dongle which needs the following patch:

UPC IPv6 prefix delegation and FreeBSD

Don’t believe the Connect-Box that you only get a /64 from UPC. Normal prefix delegation is possible, you just have to guess/experiment how big your prefix is. Here is my dhcp6c.conf

interface vr0 {
    send ia-pd 1;
    send ia-na 1;
#     send rapid-commit;

id-assoc na 1 {

id-assoc pd 1 {
 prefix ::/56 1800;

 prefix-interface vr1 {
   sla-len 4;

My rtadvd.conf:


Some excerpts from my rc.conf:


KDE Plasma5 on FreeBSD

So I finally got it working.

Here is my list of things that don’t work:

  • sddm gives only a blank screen. Use gdm or lightdm instead
  • PATH is messed up. For konsole it is possible to specify the environment of a profile
  • baloo just doesn’t work. Opens 100k files.

Looks like I have to get my hands dirty again..

jboss5 + seam on FreeBSD

  1. Install jboss5 port
  2. ln -sf /var/jboss5 /usr/local/share/jboss5/server
  3. edit /etc/rc.conf:
    jboss5_jvm_opts="-server -Xms128m -Xmx512m -XX:MaxPermSize=256m \
    -Dorg.jboss.resolver.warning=true \
    -Dsun.rmi.dgc.client.gcInterval=3600000 \
    -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.bind.address= \

    Notice the jboss.bind.address and java.awt.headless=true (to prevent annoying warnings about missing X11).

  4. Edit /etc/sysctl.conf:

    Necessary for the shutdown script to work

  5. Add

    to seam’s

  6. …to be continued

ipv6, long way to go

I think the first time i saw IPv6 on the Internet was in the late nineties on IRC, when it was cool to have a hostname like 3ffe:1337::dead:babe. A few years later i tried out freenet6 but stopped using it, when most of the IRC servers k-lined freenet6 because of script kiddies abusing it. IRC was and maybe still is the only IPv6 killer application.
Since 2005 i have been using and started using IPv6 on my LAN. If i can trust the gif-interface counters my tunnel currently transfers about 70MB/day, while the IPv4 interface claims to transfer about 300MB/day.
I recently converted not only this webserver but also the kde-freebsd Teams’ development host to ipv6only. I did not expect this to be a big deal, as all people having accounts on it are unix geeks. I was quite surprised that more than half of the users did not have any ipv6 experience.
Another datapoint is, a system accessed by unix hackers only. According to netstat there are currently 43 tcp4 ssh sessions and only 10 tcp6 sessions,
Even worse, of these 10 sessions three are sessions and 2 are from my systems.
So if you have something interesting to offer on the internet, shut down your IPv4 interface.

Webserver moved

If you can read this, the move has been successfull.
I have decided to move to The new webserver has more RAM and a better CPU. Unfortunately charges 10EUR/month for 6 additional ip addresses. So i decided it is time for IPv6.
Although IPv6 has been around for quite some time, there are still some rough edges:
FreeBSD jails IPv6 support requires a patch from Björn Zeeb.
For access via legacy IPv4 i wanted to use lighttpd with mod_proxy, but mod_proxy does not support fetching IPv6-content yet, the following hack is required.
What i still have to think about is aggregated content, like the planet or the weather-plugin. There are way too many sites out there, that don’t support IPv6. (Hello twitter,, Possible solutions are NAT, a webproxy, or i have to put the aggregated content somewhere else.

Looking for a new hoster

My old hoster decided to move all his servers to XEN. Since FreeBSD XEN Support isn’t really there yet, this means i need to look for a new hoster.
So i am checking out the FreeBSD-rootserver offers in the 20 – 40EUR/month range. I am quite sure, i don’t want to play with depenguinator, so a real FreeBSD system is the preferred solution.
I currently know about and Anything else?
My current system runs 4 jails handling my email and a few lowtraffic sites. It currently has 256MB RAM which is a bit low, so preferably the new system should have 512MB.

New FreeBSD Desktop

After nearly 4 years i thought it was time to buy a new FreeBSD desktop.
Last week I bought a Shuttle XPC, with an Intel G31/ICH7 Chipset, a Core 2 Duo E8200, 2×2,66Ghz. It is faster than mchammer, my previous desktop and a lot quieter.
I named it dilek, a beautiful name which means something like desire.
Since last weekend was a party weekend it took me until this weekend to finally finish the installation.
Because it is not possible to disable the BIOS Boot sector protection, you may want to run boot0cfg -o noupdate
The ACPI implementation is buggy, so unless you like console message everyfew seconds, you have to run with debug.acpi.disabled="thermal"
The X installation was a bit problematic, as i had to add the device ids to the agp kernel driver and had to install the git version of the xorg intel driver. But now it is running smooth.
I am now installing KDE4 on it. With the new desktop i now have enough CPU power to help porting KDE4. Now i just need some more free time…