Xen users - Apr 2011 - Starting xend = loss of wireless connection

So, upgrading to 4.1.0 had no effect on my wireless issue.

When I start xend and try to have it create a bridge using my wireless nic
it kills the interface. The only way to get the wireless back up is to
reload the driver and restart the interface.

 

I use Gentoo Linux. Before I start I have an interface for eth0 (wired),
eth1 (wireless), and lo. After, I have eth0, peth1, and lo.

 

The only change I made to xend-config.sxp was:

(network-script ''network-bridge netdev=eth1'')

If I don''t make this change it uses both wired and wireless and creates
peth0 and peth1, but eth1 still  vanishes.

If I  change it to eht0 it does nothing to the wireless and only creates the
peth0 as expected.

 

When I start I get a message:

Bridge eth1 does not exist!

 

The logs show:

[2011-04-03 08:47:14 25932] INFO (XendNetwork:114) Not recreating missing
unmanaged network eth1

[2011-04-03 08:47:14 25932] INFO (XendNetwork:114) Not recreating missing
unmanaged network wlan0

[2011-04-03 08:47:14 25932] INFO (XendNetwork:114) Not recreating missing
unmanaged network eth0

[2011-04-03 08:47:14 25932] INFO (XendNetwork:114) Not recreating missing
unmanaged network xenbr0

 

Is there a solution? I have found others who reported similar issues on
different Linux flavors who were directed to other virtual daemons.

I like xen, I don''t plan to go elsewhere.

 

Marc



_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

On Sun, Apr 3, 2011 at 8:25 PM, Marc Tousignant <myrdhn@gmail.com>
wrote:
> The only change I made to xend-config.sxp was:
>
> (network-script ‘network-bridge netdev=eth1’)
How did you come up with that change?

The general rule is don''t do random change unless you really now what
you''re doing. Usually the best way is to ask whoever suggested that
change. However, xen''s network-bridge change has changed several times
so something that works in another version might not work in this
version.
>
> If I don’t make this change it uses both wired and wireless and creates
> peth0 and peth1, but eth1 still  vanishes.
>
> If I  change it to eht0 it does nothing to the wireless and only creates
the
> peth0 as expected.
Looking inside xen''s network-bridge script might tell you more
what''s
going on, but in this case I''d actually suggest stop using
network-bridge script.

For one, the recommended bridging method now is to create your own
bridges using OS'' config files, and not network-bridge script. The
second reason is that when dealing with wireless interface, it''s not
enough just creating a bridge, you need to also use ebtables.
> I like xen, I don’t plan to go elsewhere.
The easiest way for you is to create a dummy bridge, then set up NAT
so domU can access outside network (but not the other way around).
Installing libvirt should get you virbr0 which behaves like that,
without having to set up bridging/NAT manually.

-- 
Fajar

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

On Sun, Apr 3, 2011 at 8:25 PM, Marc Tousignant <myrdhn@gmail.com>
wrote:
> The only change I made to xend-config.sxp was:
>
> (network-script ‘network-bridge netdev=eth1’)
How did you come up with that change?

The general rule is don''t do random change unless you really now what
you''re doing. Usually the best way is to ask whoever suggested that
change. However, xen''s network-bridge change has changed several times
so something that works in another version might not work in this
version.
>
> If I don’t make this change it uses both wired and wireless and creates
> peth0 and peth1, but eth1 still  vanishes.
>
> If I  change it to eht0 it does nothing to the wireless and only creates
the
> peth0 as expected.
Looking inside xen''s network-bridge script might tell you more
what''s
going on, but in this case I''d actually suggest stop using
network-bridge script.

For one, the recommended bridging method now is to create your own
bridges using OS'' config files, and not network-bridge script. The
second reason is that when dealing with wireless interface, it''s not
enough just creating a bridge, you need to also use ebtables.
> I like xen, I don’t plan to go elsewhere.
The easiest way for you is to create a dummy bridge, then set up NAT
so domU can access outside network (but not the other way around).
Installing libvirt should get you virbr0 which behaves like that,
without having to set up bridging/NAT manually.

-- 
Fajar

-------------

I came up with that change by reading the config file that installed itself
with xen.


##
# To bridge network traffic, like this:
#
# dom0: ----------------- bridge -> real eth0 -> the network
#                            |
# domU: fake eth0 -> vifN.0 -+
#
# use
#
# (network-script network-bridge)
#
# Your default ethernet device is used as the outgoing interface, by
default.
# To use a different one (e.g. eth1) use
#
# (network-script ''network-bridge netdev=eth1'')
#
# The bridge is named eth0, by default (yes, really!)
#

So I uncommented the line because my wireless was eht1.
However directly below that it does say:

# It is normally much better to create the bridge yourself in
# /etc/network/interfaces.  network-bridge start does nothing if you
# already have a bridge, and network-bridge stop does nothing if the
# default bridge name (normally eth0) is not a bridge.  See
# bridge-utils-interfaces(5) for full information on the syntax in
# /etc/network/interfaces, but you probably want something like this:
#    iface xenbr0 inet static
#        address [etc]
#        netmask [etc]
#        [etc]
#        bridge_ports eth0
#

I''ll try creating it myself and report back.
Thanks for your reply.

Marc


_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Am 03.04.2011 15:25, schrieb Marc Tousignant:
> (network-script ‘network-bridge netdev=eth1’)
I use
  (network-script /bin/true)

in my config and setup all the bridges by myself. And it works perfectly.

It''s very easy to setup bridges using baselayout/openrc. And IMHO, it
has always been the cleanest way of doing things.

However, bridging and wireless don''t go together very well.
AFAIK, any wireless LAN client is only allowed to use its own MAC
address. But sending packets with many different MAC address to the
network is a requirement for bridging to work.

You may have to switch to NAT or proper IP routing.

Regards,
  Sven


_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users