Displaying 8 results from an estimated 8 matches similar to: "Bhyve drv creates duplicate tap0 references"
2017 Jan 20
0
Re: Controlling the name of the 'tap0' device, in a bridged networking setup
2010 Feb 10
0
[PATCH] Use /dev/tap0 by default on BSD if mode != router
---
src/bsd/device.c | 9 +++++++--
1 files changed, 7 insertions(+), 2 deletions(-)
diff --git a/src/bsd/device.c b/src/bsd/device.c
index c2cd34c..b835b59 100644
--- a/src/bsd/device.c
+++ b/src/bsd/device.c
@@ -33,6 +33,7 @@
#endif
#define DEFAULT_DEVICE "/dev/tun0"
+#define DEFAULT_DEVICE_TAP "/dev/tap0"
typedef enum device_type {
DEVICE_TYPE_TUN,
@@ -60,8
2001 May 01
0
Tinc: tap0 probs
On Mon, Apr 30, 2001 at 03:57:25AM +0000, cuBe wrote:
> Having some probs with setting up tap0:
>
> aibo:~# ifconfig tap0 hw ether fe:fd:00:00:00:00
> SIOCSIFHWADDR: No such device
>
> Now, I;ve checked everthing, and it all seems in order. I have compiled in
> theUniversal TAP/TUN support, and Netlink (including CONFIG_NETLINK_DEV),
> but to no avil, that error always
2017 Jan 17
0
Re: Controlling the name of the 'tap0' device, in a bridged networking setup
On 01/14/2017 06:30 AM, Govert wrote:
> Hi,
>
> I'm trying to control the name of the 'tap0' device that gets created
> as I start a domain that uses bridged networking. The XML
> specification of the domain contains the following configuration
>
> <interface type='bridge'>
> <source bridge='br0'/>
>
2008 Jul 30
1
RHEL5 & Xen 3.2.1; Not creating tap0 in dom0 for domU''s
Hi All,
I have a weird issue I''m not sure how to solve. I''ve got Xen 3.2.1
working under RHEL 5.2 x86_64 just fine. I fired off a CentOS 5.2 PV
install and everything went smoothly... except that when I fire up the
PV, the tap0 for bridging isn''t being created. This results in the
CentOS 5.2 domU''s bridged eth0 only being able to ping the RHEL5
2007 Apr 18
4
Tap0?
Hello!
What is exactly "tap0" in the host ifconfig?
Thank you!
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
2017 Jan 14
2
Controlling the name of the 'tap0' device, in a bridged networking setup
Hi,
I'm trying to control the name of the 'tap0' device that gets created as I
start a domain that uses bridged networking. The XML specification of the
domain contains the following configuration
<interface type='bridge'>
<source bridge='br0'/>
</interface>
The libvirt documentation (
2017 Jan 20
2
Re: Controlling the name of the 'tap0' device, in a bridged networking setup
Thanks !! This clarifies completely what is happening. I'll look into
running virsh as root/attaching to qemu:///system. Or, perhaps I can
'statically' create tun devices, to which the domains attach when started
(although I have no idea weather this is possible).
Best,
Govert
2017-01-17 20:46 GMT+01:00 Laine Stump <laine@laine.org>:
> On 01/14/2017 06:30 AM, Govert wrote: