[Bug 535750] New: Wireless NIC with Atheros chipset can't connect with any websites despite having ip address
http://bugzilla.novell.com/show_bug.cgi?id=535750 Summary: Wireless NIC with Atheros chipset can't connect with any websites despite having ip address Classification: openSUSE Product: openSUSE 11.2 Version: Factory Platform: x86-64 OS/Version: SuSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: pilotgi@gmail.com QAContact: qa@suse.de Found By: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.2) Gecko/20090730 SUSE/3.5.2-3.1 Firefox/3.5.2 I have a D-Link wireless pci NIC that uses the Atheros ar2413 chipset. It's recognized and configured with YaST2 using the ath5k module. Everything I look at shows that wlan0 is up and running except for an error that 'dhcp4 client is not running'. ifconfig looks like this: eth0 Link encap:Ethernet HWaddr 00:17:31:6F:3C:02 inet addr:192.168.1.69 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::217:31ff:fe6f:3c02/64 Scope:Link UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:14843 errors:0 dropped:0 overruns:0 frame:0 TX packets:11946 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:12916277 (12.3 Mb) TX bytes:2106314 (2.0 Mb) Interrupt:23 Base address:0xc000 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:141 errors:0 dropped:0 overruns:0 frame:0 TX packets:141 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:10780 (10.5 Kb) TX bytes:10780 (10.5 Kb) wlan0 Link encap:Ethernet HWaddr 00:24:01:12:A5:27 inet addr:192.168.1.68 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::224:1ff:fe12:a527/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1706 errors:0 dropped:0 overruns:0 frame:0 TX packets:41 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:76506 (74.7 Kb) TX bytes:7878 (7.6 Kb) wmaster0 Link encap:UNSPEC HWaddr 00-24-01-12-A5-27-00-00-00-00-00-00-00-00-00-00 UP RUNNING MTU:0 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) And this is what I get when I do rcnetwork restart (eth0 disconnected): rcnetwork restart Shutting down network interfaces: eth0 device: nVidia Corporation MCP51 Ethernet Controller (rev a3) eth0 done wlan0 device: Atheros Communications Inc. AR2413 802.11bg NIC (rev 01) wlan0 done Shutting down service network . . . . . . . . . done Hint: you may set mandatory devices in /etc/sysconfig/network/config Setting up network interfaces: eth0 device: nVidia Corporation MCP51 Ethernet Controller (rev a3) eth0 Starting DHCP4 client. . . . . . . . eth0 DHCP4 continues in background eth0 waiting wlan0 device: Atheros Communications Inc. AR2413 802.11bg NIC (rev 01) wlan0 starting wpa_supplicant wlan0 Starting DHCP4 client. . wlan0 DHCP4 client NOT running wlan0 failed Setting up service network . . . . . . . . . . done SuSEfirewall2: Setting up rules from /etc/sysconfig/SuSEfirewall2 ... SuSEfirewall2: using default zone 'ext' for interface wmaster0 SuSEfirewall2: batch committing... SuSEfirewall2: Firewall rules successfully set I can ping 192.168.1.68 with no errors but I can't ping any other web addresses. This is the results of dhcpcd-test: info, wlan0: hardware address = 00:24:01:12:a5:27 info, wlan0: broadcasting for a lease debug, wlan0: sending DHCP_DISCOVER with xid 0x5224f7fc debug, wlan0: waiting for 10 seconds debug, wlan0: got a packet with xid 0x5224f7fc info, wlan0: offered 192.168.1.68 from 192.168.1.254 IPADDR='192.168.1.68' NETMASK='255.255.255.0' NETWORK='192.168.1.0' BROADCAST='192.168.1.255' ROUTES='' GATEWAYS='192.168.1.254' DNSSERVERS='192.168.1.254' DHCPSID='192.168.1.254' LEASETIME='86400' RENEWALTIME='43200' REBINDTIME='75600' INTERFACE='wlan0' CLASSID='dhcpcd 3.2.3' CLIENTID='01:00:24:01:12:a5:27' DHCPCHADDR='00:24:01:12:a5:27' info, wlan0: exiting This NIC is working with 11.1. Reproducible: Always Steps to Reproduce: 1. 2. 3. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=535750
User pilotgi@gmail.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=535750#c1
kevin vandeventer
http://bugzilla.novell.com/show_bug.cgi?id=535750
Marcus Meissner
http://bugzilla.novell.com/show_bug.cgi?id=535750
User vbotka@novell.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=535750#c2
Vladimir Botka
http://bugzilla.novell.com/show_bug.cgi?id=535750
User pilotgi@gmail.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=535750#c3
--- Comment #3 from kevin vandeventer
http://bugzilla.novell.com/show_bug.cgi?id=535750
User mt@novell.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=535750#c4
Marius Tomaschewski
Marius, you are the maintainer of the rcnetwork script. Can you take over please ? Sure.
Kevin, Vladimir, can you take a look into 'dmesg' output and into /var/log/messages, /var/log/boot.msg if you find kernel Oopses as in bug 537350 comment 6? [Must not be related - just because you've disabled IPv6.] (In reply to comment #0)
Everything I look at shows that wlan0 is up and running except for an error that 'dhcp4 client is not running'.
I'm going now to try to reproduce the dhcp start-report problems. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=535750
User mt@novell.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=535750#c5
--- Comment #5 from Marius Tomaschewski
http://bugzilla.novell.com/show_bug.cgi?id=535750
User mt@novell.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=535750#c6
--- Comment #6 from Marius Tomaschewski
http://bugzilla.novell.com/show_bug.cgi?id=535750
User vbotka@novell.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=535750#c7
--- Comment #7 from Vladimir Botka
can you take a look into 'dmesg' output and into /var/log/messages, /var/log/boot.msg if you find kernel Oopses as in bug 537350 comment 6?
No Oops here. But, I have found the problem. It is the new nl80211 extension. If the wpa_supplicant is running with the -Dnl80211 then it does not authenticate. -Dwext works fine. # ifup wlan0 wlan0 device: Intel Corporation Wireless WiFi Link 5100 wlan0 starting wpa_supplicant It seems now as a wpa-supplicant problem with the new nl80211 extension here. I am not sure if this is the same problem for Kevin. Kevin could you post the output of the "# iwconfig wlan0" and "# ps ax | grep wpa" ? -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=535750
User pilotgi@gmail.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=535750#c8
--- Comment #8 from kevin vandeventer
http://bugzilla.novell.com/show_bug.cgi?id=535750
User pilotgi@gmail.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=535750#c9
kevin vandeventer
http://bugzilla.novell.com/show_bug.cgi?id=535750
User vbotka@novell.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=535750#c10
Vladimir Botka
http://bugzilla.novell.com/show_bug.cgi?id=535750
User pilotgi@gmail.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=535750#c11
--- Comment #11 from kevin vandeventer
http://bugzilla.novell.com/show_bug.cgi?id=535750
User pilotgi@gmail.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=535750#c12
--- Comment #12 from kevin vandeventer
http://bugzilla.novell.com/show_bug.cgi?id=535750
User pilotgi@gmail.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=535750#c13
kevin vandeventer
http://bugzilla.novell.com/show_bug.cgi?id=535750
User pilotgi@gmail.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=535750#c14
--- Comment #14 from kevin vandeventer
http://bugzilla.novell.com/show_bug.cgi?id=535750
User pilotgi@gmail.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=535750#c15
--- Comment #15 from kevin vandeventer
http://bugzilla.novell.com/show_bug.cgi?id=535750
kevin vandeventer
http://bugzilla.novell.com/show_bug.cgi?id=535750
User pilotgi@gmail.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=535750#c16
--- Comment #16 from kevin vandeventer
http://bugzilla.novell.com/show_bug.cgi?id=535750
User pilotgi@gmail.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=535750#c17
--- Comment #17 from kevin vandeventer
http://bugzilla.novell.com/show_bug.cgi?id=535750
User pilotgi@gmail.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=535750#c18
--- Comment #18 from kevin vandeventer
http://bugzilla.novell.com/show_bug.cgi?id=535750
User vbotka@novell.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=535750#c19
Vladimir Botka
cannot find 'iw', please install wlan0 dead I haven't seen 'cannot find 'iw', please install' before. I also haven't seen 'dead' in red letters before. Could this be a problem with the ath5k module?
The /usr/sbin/iw comes from the iw package. This package is needed. The iw shall be the "next generation" iwconfig replacement. Try to update to the Milestone 7 first. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=535750
User pilotgi@gmail.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=535750#c20
kevin vandeventer
http://bugzilla.novell.com/show_bug.cgi?id=535750
User pilotgi@gmail.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=535750#c21
--- Comment #21 from kevin vandeventer
http://bugzilla.novell.com/show_bug.cgi?id=535750
User vbotka@novell.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=535750#c22
--- Comment #22 from Vladimir Botka
wpa_state=COMPLETED ip_address=192.168.1.68
Maybe the output of the following commands tells more. # iwconfig wlan0 # netstat -r # ps ax | grep wpa # ps ax | grep dhcp -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=535750
User pilotgi@gmail.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=535750#c23
--- Comment #23 from kevin vandeventer
http://bugzilla.novell.com/show_bug.cgi?id=535750
User vbotka@novell.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=535750#c24
Vladimir Botka
netstat -r
Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 192.168.1.0 * 255.255.255.0 U 0 0 0 eth0 192.168.1.0 * 255.255.255.0 U 0 0 0 wlan0 link-local * 255.255.0.0 U 0 0 0 eth0 loopback * 255.0.0.0 U 0 0 0 lo default home 0.0.0.0 UG 0 0 0 eth0
It seems like a rooting problem. Can you ping the home from both interfaces ? # ping -I wlan0 home # ping -I eth0 home What route does the next command show ? # ip route get to <ip address of home> What route does the next command show ? # ip route get to 209.191.93.52 Can you ping to the outside from home ? -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=535750
User pilotgi@gmail.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=535750#c25
kevin vandeventer
It seems like a rooting problem. Can you ping the home from both interfaces ? # ping -I wlan0 home
PING home.gateway.2wire.net (192.168.1.254) from 192.168.1.68 wlan0: 56(84) bytes of data. ^C --- home.gateway.2wire.net ping statistics --- 178 packets transmitted, 0 received, 100% packet loss, time 176998ms
# ping -I eth0 home
PING home.gateway.2wire.net (192.168.1.254) from 192.168.1.64 eth0: 56(84) bytes of data. 64 bytes from home (192.168.1.254): icmp_seq=1 ttl=255 time=1.09 ms 64 bytes from home (192.168.1.254): icmp_seq=2 ttl=255 time=0.813 ms 64 bytes from home (192.168.1.254): icmp_seq=3 ttl=255 time=0.991 ms 64 bytes from home (192.168.1.254): icmp_seq=4 ttl=255 time=0.991 ms 64 bytes from home (192.168.1.254): icmp_seq=5 ttl=255 time=1.20 ms 64 bytes from home (192.168.1.254): icmp_seq=6 ttl=255 time=0.971 ms 64 bytes from home (192.168.1.254): icmp_seq=7 ttl=255 time=0.964 ms 64 bytes from home (192.168.1.254): icmp_seq=8 ttl=255 time=0.455 ms ^C --- home.gateway.2wire.net ping statistics --- 8 packets transmitted, 8 received, 0% packet loss, time 7007ms rtt min/avg/max/mdev = 0.455/0.936/1.206/0.210 ms
What route does the next command show ? # ip route get to <ip address of home>
192.168.1.254 dev eth0 src 192.168.1.64 cache mtu 1500 advmss 1460 hoplimit 64
What route does the next command show ? # ip route get to 209.191.93.52
209.191.93.52 via 192.168.1.254 dev eth0 src 192.168.1.64 cache mtu 1500 advmss 1460 hoplimit 64
Can you ping to the outside from home ? I don't understand what you want here.
-- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=535750
User vbotka@novell.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=535750#c26
Vladimir Botka
# ping -I wlan0 home
PING home.gateway.2wire.net (192.168.1.254) from 192.168.1.68 wlan0: 56(84) bytes of data.
^C --- home.gateway.2wire.net ping statistics --- 178 packets transmitted, 0 received, 100% packet loss, time 176998ms
Connect the AP to the home. Did this solve the problem ? -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=535750
User pilotgi@gmail.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=535750#c27
--- Comment #27 from kevin vandeventer
Connect the AP to the home. Did this solve the problem ?
Sorry, but I don't know what you want here. How do I do this? -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=535750
User vbotka@novell.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=535750#c28
--- Comment #28 from Vladimir Botka
(In reply to comment #26)
Connect the AP to the home. Did this solve the problem ?
Sorry, but I don't know what you want here. How do I do this?
You can not ping the home from the interface wlan0. Your default gateway is home. You can ping from the interface eth0 via home to the Internet. So I deduce that your AP has no connection to the home. [wlan0] <---> [AP] <---> [home] <---> (Internet) Check the connection to the AP. # ping -I wlan0 <AP IP address> and check the connection from the AP to the home. Either # ping -I wlan0 <home IP address> or connect to the AP's UI and check the diagnostic if available. How is your AP connected to the home ? It can be an ethernet cable or wireless connection if home got wireless interface. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=535750
User pilotgi@gmail.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=535750#c29
kevin vandeventer
http://bugzilla.novell.com/show_bug.cgi?id=535750
User vbotka@novell.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=535750#c30
Vladimir Botka
I can ping the AP ip address but the home ip address returns 0 received and 100% packet loss like the output of 'ping -I wlan0 home' in comment #25. I don't see any point in diagnosing the AP since my wireless connection is working fine on both my MacBook and openSUSE 11.1. Milestone 7 and 11.1 are installed on the same computer.
Weird. You can ping the home via wlan0 from 11.1 but you can not from 11.2. Right ? What can be the difference if the AP is between and you can ping the AP from both 11.1 and 11.2 ? Anyway, tou can connect to the Internet from eth0. If I understand it right you cannot connect to the Internet from wlan0. It happens when you unplug the ethernet cable from the box. Right ? Post the routing table "netstat -r " then. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=535750
User pilotgi@gmail.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=535750#c31
kevin vandeventer
Weird. You can ping the home via wlan0 from 11.1 but you can not from 11.2. Right ? What can be the difference if the AP is between and you can ping the AP from both 11.1 and 11.2 ?
Good question. I don't know.
Anyway, you can connect to the Internet from eth0. If I understand it right you cannot connect to the Internet from wlan0. It happens when you unplug the ethernet cable from the box. Right ?
Yes. Post the routing table "netstat -r " then. netstat -r (eth0 unplugged) Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 192.168.1.0 * 255.255.255.0 U 0 0 0 eth0 192.168.1.0 * 255.255.255.0 U 0 0 0 wlan0 link-local * 255.255.0.0 U 0 0 0 eth0 loopback * 255.0.0.0 U 0 0 0 lo default 192.168.1.254 0.0.0.0 UG 0 0 0 eth0 netstat -r (eth0 plugged in) Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 192.168.1.0 * 255.255.255.0 U 0 0 0 eth0 192.168.1.0 * 255.255.255.0 U 0 0 0 wlan0 link-local * 255.255.0.0 U 0 0 0 eth0 loopback * 255.0.0.0 U 0 0 0 lo default home 0.0.0.0 UG 0 0 0 eth0 I'm still getting the 'wlan0 DHCP4 client NOT running wlan0 failed' when I do rcnetwork restart but when I do 'ifstatus wlan0' it says wlan0 is up and DHCP4 client (dhcpcd) is running. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=535750
User vbotka@novell.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=535750#c32
--- Comment #32 from Vladimir Botka
netstat -r (eth0 unplugged)
Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 192.168.1.0 * 255.255.255.0 U 0 0 0 eth0 192.168.1.0 * 255.255.255.0 U 0 0 0 wlan0 link-local * 255.255.0.0 U 0 0 0 eth0 loopback * 255.0.0.0 U 0 0 0 lo default 192.168.1.254 0.0.0.0 UG 0 0 0 eth0
If the eth0 is unplugged there should be no route via eth0 anymore. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=535750
User pilotgi@gmail.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=535750#c33
--- Comment #33 from kevin vandeventer
If the eth0 is unplugged there should be no route via eth0 anymore.
With the ethernet cable unplugged, I get the same output from netstat -r after rcnetwork restart and after a reboot as in comment #31 (eth0 unplugged). -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=535750
User pilotgi@gmail.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=535750#c34
--- Comment #34 from kevin vandeventer
http://bugzilla.novell.com/show_bug.cgi?id=535750
User mt@novell.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=535750#c35
--- Comment #35 from Marius Tomaschewski
http://bugzilla.novell.com/show_bug.cgi?id=535750
User mt@novell.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=535750#c36
--- Comment #36 from Marius Tomaschewski
http://bugzilla.novell.com/show_bug.cgi?id=535750
User pilotgi@gmail.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=535750#c37
--- Comment #37 from kevin vandeventer
Sorry, but it will never work properly to connect to the same network with two interfaces. Even when there are two default routes, the kernel will use only first one (one interface).
When you really want to use both at same time and same network config, you need several custom hooks (http://lartc.org/howto/lartc.rpdb.html).
I think maybe you misunderstood. I don't want to use both at the same time. I want to use either or. I usually use wlan0 so I don't have to run a 50 ft ethernet cable to the router from my computer. But sometimes I need to use the ethernet cable, such as when I'm changing settings to the wireless router or if I need the added security of a wired connection. I also discovered that I can have the same problem in reverse. I did a clean install of Milestone 8 and only wlan0 was configured. Then I added the eth0 configuration and eth0 can't ping any websites, only the assigned ip address. I have never had this problem before, going back to openSUSE 10.0. It only popped up in the Milesone releases for 11.2. So I edited /etc/sysconfig/network/ifcfg-wlan0 and eth0 like the examples above and both interfaces are working now. Shouldn't YaST do this automatically when more than one interface is configured? Why haven't I had this problem in the past? Is this a problem with ifup but not with NetworkManager? Surely you don't expect new users to edit /etc/sysconfig/network by hand if they configure both wired and wireless interfaces. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=535750
User pilotgi@gmail.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=535750#c38
--- Comment #38 from kevin vandeventer
http://bugzilla.novell.com/show_bug.cgi?id=535750
User mt@novell.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=535750#c39
Marius Tomaschewski
I think maybe you misunderstood. I don't want to use both at the same time.
OK.
So I edited /etc/sysconfig/network/ifcfg-wlan0 and eth0 like the examples above and both interfaces are working now.
OK.
Shouldn't YaST do this automatically when more than one interface is configured? Why haven't I had this problem in the past?
YaST did this until now.
Is this a problem with ifup but not with NetworkManager?
NetworkManager has a daemon that AFAIK automatically selects the fastest interface, that is, this setup is default for NetworkManager.
Surely you don't expect new users to edit /etc/sysconfig/network by hand if they configure both wired and wireless interfaces.
No, I reassign to the yast2 network maintainer to verify what happens. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=535750
http://bugzilla.novell.com/show_bug.cgi?id=535750#c40
Michal Zugec
participants (1)
-
bugzilla_noreply@novell.com