|
Bugzilla – Full Text Bug Listing |
| Summary: | DHCP4 does not start on wlan0 | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 12.1 | Reporter: | Freek de Kruijf <freek> |
| Component: | Network | Assignee: | E-mail List <bnc-team-screening> |
| Status: | RESOLVED DUPLICATE | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | cfeck |
| Version: | Milestone 5 | ||
| Target Milestone: | --- | ||
| Hardware: | x86-64 | ||
| OS: | SUSE Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Bug Depends on: | 716013 | ||
| Bug Blocks: | |||
This bug is related to bug#716013 and the solution of that bug solves this one. bug 716013 causes no zone assigned to interfaces that are not explicitly configured. Therefore all traffic get blocked on such interfaces. So I guess some dhcp stuff gets blocked too. I've added a workaround in Factory but the question how an invalid value manages to get into the firewall config remains. *** This bug has been marked as a duplicate of bug 716013 *** As you can see in bug#716013 there is a patch which apparently solves that bug, so this bug is solved also. Removing '' from that line in /etc/sysconfig/SuSEfirewall2 also solves this problem. I installed M5 today (previous version was 11.4), and was hit by the same problem that I had to manually start dhcpd. Additionally, I have SuSEfirewall2-3.6.277-1.1.noarch installed, so that version does not fix the issue. |
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:6.0) Gecko/20100101 Firefox/6.0 I installed openSUSE 12.1 M5 on my laptop an Acer ASPIRE 5520G. I changed the configuration of the network devices, eth0 and wlan0, to the traditional ifup. My network has a native IPv6 router and no DHCP6 server. eth0 is set to become active when a cable is plugged in. The wifi interface is configured to start at boot time. Furthermore both interfaces are set to start only DHCP4, because the network does not have a DHCP6 server. Starting the system with a cable plugged in, this interface gets an IPv4 address and 2 global IPv6 addresses via stateless autoconfiguration. However the wifi interface only gets 2 global IPv6 addresses and no IPv4 address. After unplugging the cable, the eth0 still seems to remains in the same status. However after ifdown and ifup eth0 the interface has no IP addresses anymore. In this situation ifdown wlan0 is given, which means that the device wlan0 completely disappears. After that the following command is given: # ifup wlan0 wlan0 device: Atheros Communications Inc. AR242x / AR542x Wireless Network Adapter (PCI-Express) (rev 01) wlan0 starting wpa_supplicant command 'iwconfig wlan0 power off' returned Error for wireless request "Set Power Management" (8B2C) : SET failed on device wlan0 ; Operation not supported. # Now again the interface only gets IPv6 addresses and no IPv4 address. I don't see a DHCP client being started. Reproducible: Always Steps to Reproduce: 1. 2. 3.