On 02/16/2013 06:26 AM, antttikutoja wrote:
> Using another box with a cable nic and a wireless nic and experimenting
> with various combos of “boot” and “hotplug”.
> Basically, if both networks are available both are brought up but the
> default route goes to the cable rather than the wireless. Since the
> wireless has the better bandwidth, it “should” be the choice but…
Are you sure that the wireless has better bandwidth? The only way that would
happen is if you have hardware from 1990 with 10 Mbps capability. Yes, wireless
might have 300 Mbps capability, but that is half-duplex so the throughput is cut
in half. In addition, the switch in your router gives you a private wired
connection, while wireless bandwidth is shared among all the users. Using iperf
to test throughput against a local server - no WAN is involved - I get 94 Mbps
on my 100 Mbps connection. The best I have ever seen with a wireless connection
with 300 Mbps capability is 70 Mbps, and the usual rate is 40-50.
> If I disconnect the cable after both nics have been set up, I lose the
> default route (dhcpd removes it) effectively killing the network. It
> would be good if the “underware” would re-assign the default route to
> the nic that is up still. After 1-15 minutes, still no default route. It
> only comes back if I plug the cable in again.
With the wired nic set to be enabled “on boot”, the system is doing exactly what
it should. You want to set the wired connection to be enabled on cable
connection. One other consideration is that the system might fail to boot if the
wired NIC is set to activate on boot, and the wire is disconnected. It happened
> If I use the ifplgd priority and both nets are available, it does seem
> to bring up the nic that has the highest priority. Certainly what I saw
> from the logs is that when it comes to doing the wlan, it saw that it
> had a lower priority than the cable and didn’t bring it up.
I think you should set the wired iface to connect on cable connection, and the
wireless on boot, and only adjust the priorities if you have multiple devices of
the same kind.
> With the box which was the subject of the original post, I have added
> the wlan nic after all the installation. The system attempts to bring it
> up but it is failing to authenticate. Its ifcfg-wlan0 is identical (a
> copy) of the one used on the box that is working fine but still it wont
Without logs, we will never be able to fix this. Some wireless devices in kernel
3.7 need different firmware than is provided by the kernel-firmware package. I
submitted the updated package to Factory, and I am assured that it will be in
12.3, but it is not there yet.