-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sunday, 2013-08-18 at 19:03 -0500, Neil Rickert wrote:
So, again in Yast network settings, I told it to delete "eth0". And that completely solved the problem. That also deleted the default route that I had configured through device p5p1, which was fine since the DHCP configured route was working. It seems that the Yast "ifup" settings are confused by a non-existent device.
Similar problem in my laptop. Eth is configured "on cable connect", but in fact it is active after booting. This confuses things, because packages that should be routed via wlan0 are not. I have to run "rcnetwork stop eth0" after every boot, and then things work. I can not report bug because it is running 11.4 Evergreen. - -- Cheers, Carlos E. R. (from 12.3 x86_64 "Dartmouth" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iEYEARECAAYFAlIRYn8ACgkQtTMYHG2NR9VmugCeK58+96oBRs3pDK2kAUOkCR9f 9UcAoIvLERlM3wk+X9uLS335s71Zq9ho =9P6d -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org