On Sat, Aug 29, 2009 at 15:16, André Ramaciotti<andre.ramaciotti@xxxxxxxxx> wrote: > That's what I thought too. Anyway, it didn't work, but I found out what the > real problem was. For some reason, sometimes I got: > Wireless -> eth0 > Ethernet -> eth1 > > and other times I got: > Ethernet -> eth0 > Wireless -> eth1 > > so netcfg would fail reporting that eth0 doesn't support scanning. I think I > solved the problem loading both modules manually so now I always have: > Ethernet -> eth0 > Wireless -> eth1 > A custom udev rule would probably work too... check the wiki.
