[Cbe-oss-dev] Diagnosing NetworkManager/ps3_gelic connection issues in Ubuntu Jaunty

[Masakazu Mokuno]

Hi Dan,

Sorry for late reply.  I've not subscribed this list in these days. 

> The problem we're experiencing now is failure to connect to a wireless
> network if the wired interface has already been connected.
> 
> The most obvious possible cause would be because both interfaces have
> the same MAC address and both are connecting to the same network segment
> (e.g. basic home wifi/ethernet router). Because the system brings up
> eth0 first at boot and wlan0 on user login, eth0 beats wlan0 to the
> connection.
> 
> Although I have a working knowledge of networking, and this explanation
> makes sense to me, I want to be sure the symptoms are definitely due to
> this before moving on. In the log below it appears the gelic wireless
> driver is doing all the right things but it's just not getting the right
> results from the hardware/hypervisor.
> 
> Can anyone confirm this?

Yes, PS3 shares the MAC address for both wired ethernet and wireless. 
If both are connected to the same segment, the network will be unstable
at least.  As far as I experienced, the wireless connection itself kept
'associated' even with using the same segment though.

Could you please try the followings and see if the wireless connection
will succeed if you could:

 o Use separate ethernet segments for wired and wireless; unplug the
 ethernet cable or using standalone wireless APs etc...
 
 o See what will happen if disable NM and use wpa_supplicant only
 
 o Disable MAC address filtering feature on your AP if it has

The attached patch lets the driver emit more verbose messages to help
analyzing what happens in the driver.  Could you please try to reproduce
the symptom with the patch and send me the dmesg log?

Thanks

-- 
Masakazu Mokuno
-------------- next part --------------
A non-text attachment was scrubbed...
Name: for_dmunckton.patch
Type: application/octet-stream
Size: 4298 bytes
Desc: not available
URL: <http://lists.ozlabs.org/pipermail/cbe-oss-dev/attachments/20090305/0b877a41/attachment.obj>