tech-net archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: tap interface detached
Robert Swindells wrote:
Frédéric Fauberteau <frederic%fauberteau.org@localhost> wrote:
I am trying to install a Xen domU and I am reproducing a working
configuration for NetBSD 9.0 amd64 from a running host.
I create a tunnel interface:
# ifconfig tap0 create
# ifconfig tap0 inet 192.168.0.1 up
I add this interface to a bridge:
# ifconfig bridge0 create
# brconfig bridge0 add tap0 up
The tap interface appears to be detached:
You need to add something else to the bridge that has a carrier signal,
the simplest configuration would be to add the outgoing interface of the
dom0.
Yes, I created the domU and a virtual interface had been added to the
bridge:
# brconfig bridge0
bridge0: flags=41<UP,RUNNING>
Configuration:
priority 32768 hellotime 2 fwddelay 15 maxage 20
ipfilter disabled flags 0x0
Interfaces:
xvif1i0 flags=3<LEARNING,DISCOVER>
port 6 priority 128
tap0 flags=3<LEARNING,DISCOVER>
port 4 priority 128
Address cache (max cache: 100, timeout: 1200):
00:16:3e:26:13:02 xvif1i0 1182 flags=0<>
But the tap interface is still detached:
# ifconfig tap0
tap0: flags=0x8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST>
mtu 1500
ec_capabilities=0x5<VLAN_MTU,JUMBO_MTU>
ec_enabled=0x1<VLAN_MTU>
description: "Xen VM tunnel"
address: f2:0b:a4:fb:22:75
status: no carrier
inet6 fe80::f00b:a4ff:fefb:2275%tap0/64 flags 0x8<DETACHED>
scopeid 0x4
inet6 2001:bc8:3807:101::1/64 flags 0x8<DETACHED>
inet 192.168.0.1/24 broadcast 192.168.0.255 flags 0x4<DETACHED>
Home |
Main Index |
Thread Index |
Old Index