Hello everyone.
After i have installed M7 i have some wireless problems. So let me describe the problems:
If i am using NetworkManager i can connect to a wored network ( my router ). But i cannot connect to any wireless networks. The main problem is it cannot get the IP from the router. This error is listed in the NetworkManager log. If i am using the ifu way, my wireless network works but way to slow, even with IPV6 disabled.
can anyone help my way out of this problem , or mabye i should write a bug report on this ? ( maybe it’s not a bug… i don’t know … )
Any advice will be appreciated ,
Thank you people.
Network Manager will show available wireless connections by ESSID not by IP. The LAN IP is assigned by the router, either by DHCP or by address reservation.
So come again.
If you are testing development you should find this a walk in the park really IMO.
Maybe you can tell us about your wireless device. What it is, what kernel module is loaded for it.
[edit]
http://forums.opensuse.org/pre-release-beta/421750-network-not-working-m7.html
Do you know how to access your router
http://192.168.2.1/ for Belkin
http://192.168.0.1 for Dlink
any other it should be in your documentation
maybe you need to change a setting for your router
also what is your ifconfig and maybe iwconfig
I’ve been having wireless problems with the Milestone’s also but not exactly like yours. I’m using ifup and I can get an ip address from the router and ping it with no problem. What I can’t do is ping any other internet addresses.
Occasionally it will connect wirelessly but it is very slow like the op mentioned. I have filed this bug report:
I’ve also had problems with M7. Connections that had been working ceased to
do so. Re-configuring with YAST did not help. Eventually, I thought of
checking System Log messages and found that I had to install module “iw”.
Once this was done, and I’d gone through the configuration steps again,
connections were restored.
–
Graham P Davis, Bracknell, Berks., UK. E-mail: newsman not newsboy
“I wear the cheese. It does not wear me.”
Graham P Davis wrote:
> I’ve also had problems with M7. Connections that had been working ceased to
> do so. Re-configuring with YAST did not help. Eventually, I thought of
> checking System Log messages and found that I had to install module “iw”.
> Once this was done, and I’d gone through the configuration steps again,
> connections were restored.
The utilities that used the so-called “wireless extensions” or wext
are being replaced by iw, which uses cfg80211. As wext was a prime
example of the opposite of good programming practice, this change is
indeed a step forward.
The lesson for everyone is to use the system logs to help diagnose the
problem. I have tested wireless in M7 using as many combinations of
parameters as I can. Everything has worked.
As I mentioned in my post above, I have filed a bug report about my wireless problems and there has been a lot of back and forth with the developers. I discovered today that if I delete my eth0 config from YaST Network Settings, wireless works. If I reconfigure eth0 again, wireless stops working again.
My network still uses wext with iw installed so I’m not sure what makes cfg80211 kick in.
One can use this command:
ps ax | grep wpa
to find which utility is being used.
More interesting would be how you configured eth0. (ifcfg-eth0)
A lot of your outputs show eth0 and wlan0 being up at the same time in the same subnet, which is most likely a configuration error made by the user and not by the system.
I’m using ifup and both interfaces are configured with YaST Network settings. In YaST, eth0 doesn’t really require any input on my part. Just click ok to everything and it’s set up. wlan0 requires the essid and to choose the type of encryption and the password. The correct modules are pre-selected for both. Pretty straightforward.
And actually posting the configuration file at least for eth0 did not come to your mind? (Not that I told you the name of it…)
I might nearly bet both interfaces are setup to be started automatically boot and bound into the same subnet (either by static addresses or DHCP) and there’s your configuration error.
First of all thanks for this great milestone 7 version!
I can confirmed that wifi-problems (wlan0) was solved by delete eth0 in Yast. Both interface configured to dhcp, but eth0 still appears in netstat -ei list with ip: 192.168.1.100 even the cable is not connected 
wlan0 got correctly 192.168.1.101 from dchp-server.
So I deleted eth0-interface in Yast (as not configured), rebooted, and now wlan0 works - stilled configured from dchp with 192.168.1.101.
Hp Pavillion dv9000z, M7 x86_64bit, BCM4312/b43 installed first with cableconnect/eth0 and execute/download:
sudo /usr/sbin/install_bcm43xx_firmware
Jan
Larry Finger wrote:
> The utilities that used the so-called “wireless extensions” or wext
> are being replaced by iw, which uses cfg80211. As wext was a prime
> example of the opposite of good programming practice, this change is
> indeed a step forward.
Pity it’s not included automatically. Had to include it by hand when making
a clean install of M8.
–
Graham P Davis, Bracknell, Berks., UK. E-mail: newsman not newsboy
“I wear the cheese. It does not wear me.”
janoholm wrote:
> First of all thanks for this great milestone 7 version!
> I can confirmed that wifi-problems (wlan0) was solved by delete eth0 in
> Yast. Both interface configured to dhcp, but eth0 still appears in
> netstat -ei list with ip: 192.168.1.100 even the cable is not connected
>
> wlan0 got correctly 192.168.1.101 from dchp-server.
>
> So I deleted eth0-interface in Yast (as not configured), rebooted, and
> now wlan0 works - stilled configured from dchp with 192.168.1.101.
>
> Hp Pavillion dv9000z, M7 x86_64bit, BCM4312/b43 installed first with
> cableconnect/eth0 and execute/download:
> sudo /usr/sbin/install_bcm43xx_firmware
Glad to hear it is working. I think the problem was that eth0 was set
to connect at boot; whereas it should connect “On Cable Connection”.
That way eth0 will be inactive whenever the cable is disconnected.
Where is this “On cable connection” setting?
pilotgi wrote:
> Where is this “On cable connection” setting?
It is in the “General” tab when editing an interface in YaST=>Network
Devices=>Network Settings.
You can accomplish the same thing with a
STARTMODE=‘ifplugd’
line in /etc/sysconfig/network/ifcfg-eth0.
Ok, I found it. The ‘Activate device’ button under the General tab has 6 items in the drop down menu.
You can accomplish the same thing with a
STARTMODE=‘ifplugd’
line in /etc/sysconfig/network/ifcfg-eth0.
That’s how I fixed it yesterday. You can choose which one starts first too, like this:
/etc/sysconfig/network/ifcfg-wlan0:
STARTMODE=“ifplugd”
IFPLUGD_PRIORITY=“10”
/etc/sysconfig/network/ifcfg-eth0:
STARTMODE=“ifplugd”
IFPLUGD_PRIORITY=“20”
Thanks Larry
I can confirm that it helped configure eth0 to start at “Cable connected”.
I still manage network by ifup. I think M7 was very slow rebooting as long as network was managed by NetworkManager.
Jan
janoholm wrote:
> Thanks Larry
> I can confirm that it helped configure eth0 to start at “Cable
> connected”.
> I still manage network by ifup. I think M7 was very slow rebooting as
> long as network was managed by NetworkManager.
I have not noticed much, if any, difference. NM doesn’t start until
you are logged in, thus it might take a bit longer in the final stages
if auto-login is enabled.
From Yast/network I hit the first tab and change it from Ifup to NM, and hit OK. Yast restart of the network is not working, I think a windows tells “No network” or something.
When I reboot and it makes autologin, it takes 4-5 minuttes before the new icon for NM is seen in right part of the processline. When I move the mouse over the NM-icon, it tells “Network information not available”.
I return to Yast/network and it tells, that network is conntrolled by NM, but I choice first tab again and return to Ifup. Reboot/autologin takes about 30-40 seconds.
If this installation can be reconstructed, I hope that it has been reported in Bugzilla.
Jan
janoholm wrote:
> From Yast/network I hit the first tab and change it from Ifup to NM, and
> hit OK. Yast restart of the network is not working, I think a windows
> tells “No network” or something.
> When I reboot and it makes autologin, it takes 4-5 minuttes before the
> new icon for NM is seen in right part of the processline. When I move
> the mouse over the NM-icon, it tells “Network information not
> available”.
> I return to Yast/network and it tells, that network is conntrolled by
> NM, but I choice first tab again and return to Ifup. Reboot/autologin
> takes about 30-40 seconds.
>
> If this installation can be reconstructed, I hope that it has been
> reported in Bugzilla.
There is something wrong in your system. On my M8 (M7 already
deleted), it took only 83.64 seconds from the kernel load until my
WLAN was up. The pertinent dmesg output is:
83.633517] wlan1: direct probe to AP 00:14:bf:85:49:fa (try 1)
83.636493] wlan1: direct probe responded
83.636506] wlan1: authenticate with AP 00:14:bf:85:49:fa (try 1)
83.638281] wlan1: authenticated
83.638332] wlan1: associate with AP 00:14:bf:85:49:fa (try 1)
83.640756] wlan1: RX AssocResp from 00:14:bf:85:49:fa (capab=0x411
status=0 aid=1)
83.640764] wlan1: associated
83.643800] ADDRCONF(NETDEV_CHANGE): wlan1: link becomes ready
What does yours show with NM?