As far as I know, it's also required for NAT to work.
> Date: Sat, 11 Feb 2012 21:26:00 +0100
> From: m...@cvigano.de
> To: aur-general@archlinux.org
> Subject: Re: [aur-general] netcf and the libnl rebuild
>
> On 02/11/2012 07:06
On 02/11/2012 07:06 PM, Jan Steffens wrote:
> Alternatively, what functionality will we lose if libvirt is build
> without netcf?
"--with-netcflibnetcf support to configure physical host network"
That's what ./configure tells me for libvirt. Quick google has it that
this is used by libvirt to
On Sat, Feb 11, 2012 at 6:49 PM, Jan Steffens wrote:
> Seems like we need to build netcf with libnl3, since libvirt links to
> both libnetcf and libpcap (already built against libnl3).
>
> Also see http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=651033 .
>
> Too bad Ubuntu's netcf is so far remov
On Sat, Feb 11, 2012 at 4:13 PM, Jan Steffens wrote:
> Does anyone know netcf[1]? It still needs a rebuild[2] for the libnl
> 3.2 bump and it seems to be outdated as well (0.1.7 in our repos,
> 0.1.9 upstream).
>
> Ubuntu has libnl 3.2 patches[3] for it, but they don't apply to the
> upstream 0.1.
l@archlinux.org; arch-dev-pub...@archlinux.org;
> pupyki...@gmail.com
> Subject: [aur-general] netcf and the libnl rebuild
>
> Does anyone know netcf[1]? It still needs a rebuild[2] for the libnl
> 3.2 bump and it seems to be outdated as well (0.1.7 in our repos,
> 0.1.9 upstream).
&
Does anyone know netcf[1]? It still needs a rebuild[2] for the libnl
3.2 bump and it seems to be outdated as well (0.1.7 in our repos,
0.1.9 upstream).
Ubuntu has libnl 3.2 patches[3] for it, but they don't apply to the
upstream 0.1.9 sources.
I'd rather have this handled properly instead of just
