Op woensdag 22 april 2015 10:10:51 schreef don fisher:
On 04/22/2015 01:09 AM, Freek de Kruijf wrote:
Op dinsdag 21 april 2015 20:58:34 schreef don fisher: There is a priority field associated with each interface, which goes with On cable connection. So you give the wireless a lower priority, in which case the wireless will not be active when the cable is connected. When the cable is not connected the wireless will be active. It is more or less explained in the help of YaST in the network module.
I looked at the help fields in each of the Yast2 windows. Do you know if 0 or 1 is the highest priority? Also it says that the "-" is an alias for any interface, but I tried that again and it still does not work. That assumption caused my original problem. The any interface would make sense because I would like the cable to have preference over wifi, if I have the cable available, and the "-" would allow the routing device to switch. I realize this is only a problem for laptops, which may be an endangered species due to touch pads and social media.
You need to specify "On Cable Connection", even for the wireless interface. In this case, if it has the highest priority, it needs to be able to connect to an AP, otherwise a lower priority interface will be used. Only one interface, typed "On Cable Connection" will become active, however it also needs to have a priority != 0. So look in /etc/sysconfig/network/ifcfg-<interface> for STARTMODE='ifplugd' and IFPLUGD_PRIORITY= The higher the numeric value, the higher the priority. So most likely you give wireless priority 1 and cable priority 2. -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org