baselayout-1.12 forces all dhcp clients to store its resolv.conf in their own locations so they didn’t overwrite each others. It even merged them all together. This works very well. :D
So along comes openvpn with its ability to use an unspecified tun/tap interface (if tun0 is in use it will use tun1, etc) and that wanting to setup it’s own resolv.conf too (not that current portage one does this, but next one will ;) ).
I’ve been playing around with openvpn some more now, trying to get it to behave nicely as a server and a client with the minimum of fuss from a user perspective. Well, the server part it easy- it goes up or not ;)
The client part however is a little more complex …… So what I’ve been working on is a set of scripts that mimic baselayout-1.12’s inactive status so that the openvpn daemon can instruct the init script that authentication was successfull and mark it as started.
Well, it appears that every DHCP client allowed RFC violating space separated domain names being applied to the search parameter in /etc/resolv.conf :OSilly me for not allowing this violation in baselayout! Well, fear no more as you can will be able to do it in baselayout-1.12.0_pre17 which dhclient and udhcpc. dhcpcd-2.0.2 will be able to do it too when that comes out next week and I don’t have any plans to fix pump.
So I’ve not been blogging for a while, and if you’ve sent me email I’ve not replied right away. Well, the reason for all that is my server was dying- any write to the hard disk seems like it killed the server. Nasty :jawdrop:Now I have a new server :) It’s AMD64 Sempron 2800+ with 2x 120gig SATA disks in RAID 1, DVD writer and 512 meg memory. Installing Gentoo on it was a snap, however for hardened to work I have to use openssl-0.
Well, what I said earlier about being confident about the last release was wrong! Services stuck on each other and a few other things caused a downright mess! :O
This time, I think I’ve cracked it. What’s more is that other people have verified my patches, so all reported services sticking, not responding, not starting when they said they did, etc should now have been resolved :)
I also pushed out a udev/sysinit fix to all baselayouts in preparation for fixing bug #118419.
Roy's Blog