Re: [leaf-user] Can openresolv.lrp be added to Bering-uClibc to provide resolvconf for wireguard

[Erich T. <eri...@th...>]

Hi

Am 30.03.2026 um 03:26 schrieb LEAF:
> Hello all,
> 
> It's been quite a while since I've used Bering-uClibc and been on the 
> list. Hope everyone is well.
> 
> As background, I'm setting Linux Mint booting off a CD image on a VMWare 
> 17 VM to allow to access the internet using wireguard running on another 
> VMWare 17 VM using Bering-uClibc_7.2.2_x86_64 
> _isolinux_vga.iso installed on a hard drive and booting via syslinux.
> 
> Currently I have Linux Mint VM -> Bering-uClibc VM -> CPE Router -> 
> Internet = works fine without wireguard.
> 
> I tried setting this up with Bering- 
> uClibc_7.5.2_x86_64_isolinux_vga.iso, but ran into a problems with 
> trying to install syslinux on the hard drive where it kept reporting the 
> hard drive was busy. So I went back to 7.2.2 as I already had this 
> image. I'll get some proper 7.5.2 error messages for this at a later 
> date when I try again.
> 
> Anyway, when running /etc/init.d/wireguard start I get a message from 
> wireguard saying resolvconf wasn't found and the VPN link isn't setup. I 
> looked at the Debian packages to see where resolvconf comes from and 
> found it is located in openresolv_3.13.2-3_all.deb. Looking at the files 
> in openresolv they all appear to be just scripts.
> 
> So I'm wondering if the good people at Bering-uClibc could make an 
> openresolv.lrp and add this to the LEAF system going forward.

I am running wireguard on various LEAF boxes without problems. Just to 
let me understand, why would openresolv be needed by wireguard? If I 
understand you correctly then wireguard is probably looking for 
resolv.conf which is built by one of the DNS packages available.

Then if your setup is not dynamic you could always build your own 
resolv.conf manually.

cheers
ET

-- 
„Wer von seinem Tag nicht zwei Drittel für sich hat, ist ein Sklave.“
―Friedrich Nietzsche