issue with tinc and libvirt / Network is already in use by interface tun0

Guus Sliepen guus at tinc-vpn.org
Fri Mar 4 21:21:12 CET 2016


On Fri, Mar 04, 2016 at 07:46:24PM +0100, shad0wrunner at gmx.de wrote:

> >> I have tinc up and running on a kvm/libvirt host. libvirt creates a 
> >> bridge and assigns ip to this bridge, for instance 192.168.1.1. All 
> >> guests have an ip within 192.168.1.0/24. I want to access the guests 
> >> in this libvirt network with tinc from the internet via the host.
[...]
> > If libvirt wants to use "tun0" as an interface, then just have tinc 
> > use a different name for its interface. Change "Interface = tun0" to 
> > something else [...]
> 
> Nice hint, but it's not this simple. Libvirt complains about the network not
> the interface. The interfaces have different names already.
> It seems like tinc bind the subnet on startup and libvirt doesn't like it

Well, if it's about the subnet, then it's up to you to change the
Subnets in the host config files (and change the tinc-up script
accordingly if necessary), or somehow convince libvirt to use a
different range of IP addresses for its bridge interface.

-- 
Met vriendelijke groet / with kind regards,
     Guus Sliepen <guus at tinc-vpn.org>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://www.tinc-vpn.org/pipermail/tinc/attachments/20160304/bebae50b/attachment.sig>


More information about the tinc mailing list