What is the story with FC6 and Xen?
I have a user who claims the xen kernel installed by default without him knowing about it, and then he gets this issue with wireless... about half the time the iwconfig shows (correctly) that his wireless stats are associated with "eth1" and he can connect, but the other half the time they get associated with "peth0"
(normal eth0 dosn't receive or transmit netowrk traffic - though it does get an ip via dhcp).
This isn't making sense to me, even in the context of xen.
I understand that wireless networking over the bridge is dicey in xen, and is better done through routing. This dosn't seem to be like that - especially considering you'd notice
if you'd just installed a VM ... wouldn't you?
He's done a workaround by editing /etc/xen/xend-config.sxp to comment out the line that goes "(network-script network-bridge)"
Now eth0 behaves - but iwconfig sometimes lists his wireless stats next to a device called: "__tmp1804289383" and peth0 dosn't even show up.
i.e.[code]__tmp1804289383 IEEE 802.11b ESSID:"crap"
Mode:Managed Frequency:2.437 GHz Access Point: 00:0F:3D:5B:F7
Bit Rate:11 Mb/s Tx-Power=20 dBm Sensitivity=8/0
Retry limit:7 RTS thrff Fragment thrff
Encryption key:AFAF-AFAF-AFAF-AFAF-AFAF-AFAF-A6 Security mode:restricted
Link Quality=92/100 Signal level=-36 dBm Noise level=-88 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0[/quote]