![]() |
Re: [ANNOUNCE] Wlan Driver Selector Applet - Switch easily between stock and bleeding edge drivers and shut down WLAN complitely [0.2.0]
Quote:
|
Re: [ANNOUNCE] Wlan Driver Selector Applet - Switch easily between stock and bleeding edge drivers [0.2.0]
Quote:
|
Re: [ANNOUNCE] Wlan Driver Selector Applet - Switch easily between stock and bleeding edge drivers and shut down WLAN complitely [0.2.1]
What actually is this mod ? What is doing ?
|
Re: [ANNOUNCE] Wlan Driver Selector Applet - Switch easily between stock and bleeding edge drivers and shut down WLAN complitely [0.2.1]
Quote:
|
Re: [ANNOUNCE] Wlan Driver Selector Applet - Switch easily between stock and bleeding edge drivers and shut down WLAN complitely [0.2.1]
Testing the new wifi on/off feature, using the stock or the bleeding edge drivers, I'm unable to connect to my wifi network: the wifi drivers are loaded, the connection dialog pop up, I select the SSID and then after 5 seconds, I'm notified of a connection error.
This was tested after having uninstalled wifi-switcher and rebooted the device. This is completely reproducible Enabling and disabling wifi connection works perfectly with wifi switcher. If that can help, the SSID is a hidden WPA2 protected network |
Re: [ANNOUNCE] Wlan Driver Selector Applet - Switch easily between stock and bleeding edge drivers and shut down WLAN complitely [0.2.1]
Quote:
|
Re: [ANNOUNCE] Wlan Driver Selector Applet - Switch easily between stock and bleeding edge drivers and shut down WLAN complitely [0.2.1]
I'm also using hidden WPA2 protected network, without any issuses with new (or any old) version of selector applet.
Anyway, when connection dialog pops up, selector applet consider job done, and rest is for maemo connectivity parts, i.e. its most likely that it's not selector fault. Personally, i think that Your drivers may not be loaded properly (something stop the from loading like they should) - can You provide more debug info on this? Maybe it could be used to upgrade selector applet "detection" mechanism (i.e. when it should output "drivers loaded", and when kick off errors). ---- Version 0.2.1-2 installed and tested, of course no errors (having in mind that only thing changed was package description, no surprise here, huh? ;) ) When it will make it's way into -testing, I'll happily vote. // Edit If by modified osso-wlan package You mean that one by lxp (bleeding edge drivers creator) I'm NOT using it ATM - may be worth to mention. As i said, for me everything is working fine. |
Re: [ANNOUNCE] Wlan Driver Selector Applet - Switch easily between stock and bleeding edge drivers and shut down WLAN complitely [0.2.1]
Quote:
dpkg -l osso-wlan gives me version 3.0.20+0m5, so I guess it is the non customized package. Do I have to install the customized one ? what does it change ? |
Re: [ANNOUNCE] Wlan Driver Selector Applet - Switch easily between stock and bleeding edge drivers and shut down WLAN complitely [0.2.1]
Quote:
Code:
user ~ md5sum /usr/sbin/wlancond Quote:
|
Re: [ANNOUNCE] Wlan Driver Selector Applet - Switch easily between stock and bleeding edge drivers and shut down WLAN complitely [0.2.1]
then I have the stock osso-wlan, but from what Estel wrote, it does not seem to be the problem
What kind of "debug info" would you need ? |
Re: [ANNOUNCE] Wlan Driver Selector Applet - Switch easily between stock and bleeding edge drivers and shut down WLAN complitely [0.2.1]
The funny part is I never installed the modified osso-wlan and also never encountered that bug. I often drive away from home without killing my connection first and wlan never got stuck.
Well I made today a simple script and put in bin which does nothing more than linking load.sh to a command wlanload and wlanunload. Maybe an idea to include for this applet too, so that we can load and unload the drivers with a simple command. Note: Not worth sharing, my n900 is my first linux device so my scripting skillz are way below yours. Just wanted to tell that it could be a nice addition since when we gonna use these drivers we probably need xterm anyway. The only GUI I know for aircrack-ng (faircrack) has already a button for loading the drivers... |
Re: [ANNOUNCE] Wlan Driver Selector Applet - Switch easily between stock and bleeding edge drivers and shut down WLAN complitely [0.2.1]
Quote:
Code:
stop wlancond Code:
cat /proc/modules | grep wl Quote:
Code:
user ~ load-bleeding-edge-drivers.sh |
Re: [ANNOUNCE] Wlan Driver Selector Applet - Switch easily between stock and bleeding edge drivers and shut down WLAN complitely [0.2.1]
Awesome, but when loading bleeding edge through applet and load the stock through xterm the button stays glowed.
I don't know but the code to unglow it should be included in load-stock-drivers.sh. Well, should sounds maybe a bit commanding, but I don't mean it that way. I mean this post as feedback and help to improve this easy applet ;) |
Re: [ANNOUNCE] Wlan Driver Selector Applet - Switch easily between stock and bleeding edge drivers and shut down WLAN complitely [0.2.1]
Quote:
|
Re: [ANNOUNCE] Wlan Driver Selector Applet - Switch easily between stock and bleeding edge drivers and shut down WLAN complitely [0.2.1]
Quote:
Quote:
Quote:
Quote:
|
Re: [ANNOUNCE] Wlan Driver Selector Applet - Switch easily between stock and bleeding edge drivers and shut down WLAN complitely [0.2.1]
Quote:
I'm sorry that i can't be much more help here :( // Edit Did quick research, and: dmesg run as root indeed provide some info about connection stages. Just be sure to execute it AFTER failed attempt - it's not updating in real time, so when run, it show you messages to the moment that it was executed. to update, need to run it again. My output look like this: unloading stock drivers: [86817.312927] wl1251: down [86817.844177] wl1251: 151 tx blocks at 0x3b788, 35 rx blocks at 0x3a780 [86817.859802] wl1251: firmware booted (Rev 4.0.4.3.7) [86818.000915] ADDRCONF(NETDEV_UP): wlan0: link is not ready [86818.117736] wl1251: down [86818.281677] wl1251: unloaded loading stock drivers: [87210.910308] cfg80211: Using static regulatory domain info [87210.910339] cfg80211: Regulatory domain: US [87210.910339] (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) [87210.910369] (2402000 KHz - 2472000 KHz @ 40000 KHz), (600 mBi, 2000 mBm) [87210.910369] (5170000 KHz - 5190000 KHz @ 40000 KHz), (600 mBi, 2300 mBm) [87210.910369] (5190000 KHz - 5210000 KHz @ 40000 KHz), (600 mBi, 2300 mBm) [87210.910400] (5210000 KHz - 5230000 KHz @ 40000 KHz), (600 mBi, 2300 mBm) [87210.910400] (5230000 KHz - 5330000 KHz @ 40000 KHz), (600 mBi, 2300 mBm) [87210.910400] (5735000 KHz - 5835000 KHz @ 40000 KHz), (600 mBi, 3000 mBm) [87210.910430] cfg80211: Regulatory domain changed to country: US [87210.910430] (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) [87210.910461] (2402000 KHz - 2472000 KHz @ 40000 KHz), (600 mBi, 2000 mBm) [87210.910461] (5170000 KHz - 5190000 KHz @ 40000 KHz), (600 mBi, 2300 mBm) [87210.910461] (5190000 KHz - 5210000 KHz @ 40000 KHz), (600 mBi, 2300 mBm) [87210.910491] (5210000 KHz - 5230000 KHz @ 40000 KHz), (600 mBi, 2300 mBm) [87210.910491] (5230000 KHz - 5330000 KHz @ 40000 KHz), (600 mBi, 2300 mBm) [87210.910491] (5735000 KHz - 5835000 KHz @ 40000 KHz), (600 mBi, 3000 mBm) [87210.991912] phy0: Selected rate control algorithm 'minstrel' [87210.996551] wl1251: loaded [87210.996948] wl1251: initialized [87212.227020] wl12xx spi4.0: firmware: requesting wl1251-fw.bin [87212.474731] wl12xx spi4.0: firmware: requesting wl1251-nvs.bin [87213.086425] wl1251: 151 tx blocks at 0x3b788, 35 rx blocks at 0x3a780 [87213.102020] wl1251: firmware booted (Rev 4.0.4.3.7) [87213.203887] ADDRCONF(NETDEV_UP): wlan0: link is not ready [87214.766113] wl1251: down [87216.930847] wl1251: 151 tx blocks at 0x3b788, 35 rx blocks at 0x3a780 [87216.931488] wl1251: firmware booted (Rev 4.0.4.3.7) [87217.032012] ADDRCONF(NETDEV_UP): wlan0: link is not ready [87218.016052] wlan0: authenticate with AP 00:18:39:ce:dc:5a [87218.018829] wlan0: authenticated [87218.018859] wlan0: associate with AP 00:18:39:ce:dc:5a [87218.022552] wlan0: RX AssocResp from 00:18:39:ce:dc:5a (capab=0x431 status=0 aid=2) [87218.022583] wlan0: associated [87218.113250] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready --- That's output from loading drivers and associating with my WPA2 hidden network, so same setup as Yours. Check please. if Your output isn't kicking out any errors, or missing any part. Or even better, paste it here? Sorry in advance if dmsg output is irrelevant for fixing this problem - as i said, I'm no way an expert here. |
Re: [ANNOUNCE] Wlan Driver Selector Applet - Switch easily between stock and bleeding edge drivers and shut down WLAN complitely [0.2.1]
I think i was able to reproduce (or semi-reproduce) the problem. After messing up for some time with loading and reloading drivers via selector applet, sudden of nothing I'm not able anymore to connect into my network. Steps are exactly like pierrem reported, with exception that after some time of wifi-status icon flashing, I got message:
"Error connection to Internet: could not receive IP address from server. Try again?" (I get communicate in my language, so translation may be not accurate to the letter - of course trying again don't help) From that point, nor bleeding edge or stock drivers are able to connect me. dmesg print output as usual, stating that i was authenticated with AP - so it's likely really part with negotiating IP from DHCP that fail. Strange thing is that other computers in my network doesn't have this issue, and if i reboot N900, initial connection to Wifi work. Ho ever, if i use applet to disable and enable wifi, I'm not able to connect anymore. What on earth? :confused: I'll check if wifi-switcher work (uinstaled it already), and update my findings soon. Anyway, could it be that way selector applet unload and load drivers screw something badly with configuration? I double checked settings and disabled/enabled again auto obtaining IP from dhcp. Will check if static IP work. The most FRUSTRATING part is that i have absolutely no idea what i did to "trigger" this error, and now I'm unable to get rid of it ;) Prior to that point, i was using selector applet to enable and disable my wifi quite often, sometimes even load bleeding edge - without ANY troubles. for worst-case scenario i got backup, but I'm really curious to find source of problems... // Edit 1 Reinstalling selector applet doesn't help. I checked from my router side, and its true that my N900 is "connected" - can see client and signal quality via tomato firmware, ho ever IP is not obtained. the strange thing is that MAC reported to router is different than my usual N900 MAC? :confused: I got static dhcp rule that always worked, now i see that connection attempt is made with totally different MAC. Still, I'm sure that it's me trying to connect. and keep in mind that we're talking about stock drivers attempts. I wonder if that can be a clue to our problem - anyway, keep in mind that i DON'T have MAC filter set on my router, so it can't be direct source of problems. Will investigate further. // Edit 2 Just small update - at every attempt to connect again via prompt asking me if i want to try again, MAC reported to router is the same. ho ever, if i shut down wifi via selector, and re-enable it again, mac changes to another fresh one. Also, first 3 portions of max adress (parts between ":" ) are the same, only last 3 parts are different. IDK if this is normal behaviour for wifi connection in stage of negotiating IP address (or any post-wpa2 authentication), so this may be totally irrelevant info. If so, correct me. With bleeding edge drivers situation is the same - constant N900 MAC reported to router when i re-apply attempts to connect, but switching drivers on and off result in MAC that have 3 last portions different. Still don't know if this info is valuable, i hope so... |
Re: [ANNOUNCE] Wlan Driver Selector Applet - Switch easily between stock and bleeding edge drivers [0.2.0]
Quote:
|
Re: [ANNOUNCE] Wlan Driver Selector Applet - Switch easily between stock and bleeding edge drivers and shut down WLAN complitely [0.2.1]
Quote:
Quote:
http://hosted.laasonen.net/attachment-0MHYWV.png |
Re: [ANNOUNCE] Wlan Driver Selector Applet - Switch easily between stock and bleeding edge drivers and shut down WLAN complitely [0.2.1]
It would be great, cause this way static DHCP service (i.e. port forwarding, etc) can work as it should. Other way, You must re-define open ports (for torrent client on N900, as example from top of my head) every time You disable/enable Your wifi on N900.
Anyway, if i set IP address manually, I'm connected without any problems using selector applet. With DHCP, it doesn't work - just the moment i check "obtain IP automatically" and maemo re-enable connection (after settings were saved) I'm not able to connect anymore. I'm most confused... Now, I'm almost sure that this bug isn't related directly to selector applet, but something with maemo connectivity or routers behaviour - still, somehow this bug is triggered by usage of selector applet. // Edit May it be (copyright enya ;) ) that so many changes of MAC and connection attempts make routers deny leasing IP addresses to DHCP anymore? Full DHCP pool or something? I doubt, cause if so, why i connect without problems after reboot... (I mean the first, initial connection done by maemo. Still, further connection attempt done by maemo after enabling DHCP IP fail - really, what the hell is going on?:confused:) |
Re: [ANNOUNCE] Wlan Driver Selector Applet - Switch easily between stock and bleeding edge drivers and shut down WLAN complitely [0.2.1]
Quote:
|
Re: [ANNOUNCE] Wlan Driver Selector Applet - Switch easily between stock and bleeding edge drivers and shut down WLAN complitely [0.2.1]
I just updated, and i think whats need to be added is to cancel the opening of the available networks, is there any need to open a wireless connection when the driver is loaded ?
|
Re: [ANNOUNCE] Wlan Driver Selector Applet - Switch easily between stock and bleeding edge drivers and shut down WLAN complitely [0.2.1]
First, initial connection after reboot i done automatically using my regular N900 mac, so static DHCP give correct IP to known MAC. I'm starting to wonder if even maemo, after disabling and enabling auto through DHCP, uses other mac? May it be that saving MAc and keeping it constant will fix this hilarious problems?
// Edit Checked - maemo keep MAC after switching IP obtaining method, but IF selector applet changed MAC before, only static IP will work, and router deny to give new IP through DHCP. Now I'm restarting router (to clear DHCP lease table) - if after that everything works again, we've solved problem. @ AgogData Because people asked for that feature - most of us want to connect to network when enable WiFi. for that rare cases, where you don't You can just cancel - much easier that opening connection window every other time. This is also way wifi-switcher worked. |
Re: [ANNOUNCE] Wlan Driver Selector Applet - Switch easily between stock and bleeding edge drivers and shut down WLAN complitely [0.2.1]
[Solved]!!!
After router reboot, DHCP leases we're cleared and everything work like charm again. I bet my left shoe, that this is exact same case as with pierrem - because MAC change every time we load/unload WiFi drivers via selector applet, router DHCP lease table get filled with useless leased IPs. When lease table reach set max, no other IP is leased until oldest entry lease time expire - that's why negotiating IP via DHCP fail. Normally You can set DHCP pool in router settings - for regular users it is 100-200 numbers and lease time no longer than 24 hours, so not everyone is affected by this problem (ho ever, spamming with reloading drivers 100-200 times isn't so hard, and if IP lease time is like said 24 hours, You can accidentaly perform DHCP DoS attack on your own AP ;) ) Some people, for security or other reasons (like me) set DHCP pool quite low - i use mostly static DHCP (for my N900, notebooks, etc - working port forwarding on my home, still having possibility to connect to open networks without changing settings) or static IP (for desktops), so i keep DHCP pool to be only 20 entries long, for guest and friends when they come to my place and connect. In such a case, switching MAC spam DHCP entry table quite fast. I wonder if wifi-switcher saved MAC - that would explain why connecting via wifi-switcher worked for pierrem. Anyway, keeping MAC constant will fix that issue, once for all... I think it's time to get some sleep, its 3:30 here :) |
Re: [ANNOUNCE] Wlan Driver Selector Applet - Switch easily between stock and bleeding edge drivers and shut down WLAN complitely [0.2.1]
Quote:
New scripts I made are in here. I'm probably going to upload them to extras tomorrow (today) after some extra testing, 05:29 here :D I'm going get some sleep also :) |
Re: [ANNOUNCE] Wlan Driver Selector Applet - Switch easily between stock and bleeding edge drivers and shut down WLAN complitely [0.2.1]
Laasonen, Thanks again for implementing my ideas. This is one reason why I love N900 and its community here!
Regarding the dhcp issue: frequent mac changes might also trigger intrusion detection on some routers. I use static IPs on my own networks anyway. |
Re: [ANNOUNCE] Wlan Driver Selector Applet - Switch easily between stock and bleeding edge drivers and shut down WLAN complitely [0.2.1]
Quote:
@laasonen: the test scripts work fine here. Thank you both for your fast reaction to solve this issue |
Re: [ANNOUNCE] Wlan Driver Selector Applet - Switch easily between stock and bleeding edge drivers and shut down WLAN complitely [0.2.1]
I was too busy yesterday to do anything for this, but I did today more testing and made couple more changes to the loading process. It now restarts the osso-wlan also. This causes that you can only switch drivers like 8 times in short time, because after that the start-stop-daemon tool starts whining about the daemon spawning too fast. I'm not absolute sure, if this is needed, I'll maybe remove this in next version, but it shouldn't cause trouble, if you are not testing.
New version is now on the autobuilder queue :) |
Re: [ANNOUNCE] Wlan Driver Selector Applet - Switch easily between stock and bleeding edge drivers and shut down WLAN complitely [0.2.1]
is a custom wifi driver can be selected? im using aircrack to illegaly hack my home wifi :D
apologies if this was alredy mentioned and for my slothness for reading and searching >_< |
Re: [ANNOUNCE] Wlan Driver Selector Applet - Switch easily between stock and bleeding edge drivers and shut down WLAN complitely [0.2.1]
Quote:
|
Re: [ANNOUNCE] Wlan Driver Selector Applet - Switch easily between stock and bleeding edge drivers and shut down WLAN complitely [0.2.2]
Offtopic : How do you added that status menu incon for FM transmitter ?
|
Re: [ANNOUNCE] Wlan Driver Selector Applet - Switch easily between stock and bleeding edge drivers and shut down WLAN complitely [0.2.2]
Its the FMTX applet. Its usually only open when the FM transmitter is on, but if you have CSSU you can set it to be always visible via gconf:
Code:
gconftool-2 -s /apps/osso/maemo-statusmenu-fmtx/always_visible -t bool true |
Re: [ANNOUNCE] Wlan Driver Selector Applet - Switch easily between stock and bleeding edge drivers and shut down WLAN complitely [0.2.2]
1 Attachment(s)
Thank you , one more problem , after I made ur mod I cant connect to a wireless network where I could've connected before .
Attachment 20940 |
Re: [ANNOUNCE] Wlan Driver Selector Applet - Switch easily between stock and bleeding edge drivers and shut down WLAN complitely [0.2.2]
@ laasonen : After the last update the code you gave me to disable the auto opening of available connection (i think it was removing about 4 lines) is lost, can you post it again ?
|
Re: [ANNOUNCE] Wlan Driver Selector Applet - Switch easily between stock and bleeding edge drivers and shut down WLAN complitely [0.2.2]
Quote:
Quote:
Code:
if driver > 0: |
Re: [ANNOUNCE] Wlan Driver Selector Applet - Switch easily between stock and bleeding edge drivers and shut down WLAN complitely [0.2.2]
I can not reboot that router because it's from a pub , and the version of this app it's 0.2.1-2 , is this the last one ?
|
Re: [ANNOUNCE] Wlan Driver Selector Applet - Switch easily between stock and bleeding edge drivers and shut down WLAN complitely [0.2.2]
Quote:
|
Re: [ANNOUNCE] Wlan Driver Selector Applet - Switch easily between stock and bleeding edge drivers and shut down WLAN complitely [0.2.2]
Quote:
Disclaimer: Don't worry, it wasn't Your fault, and it won't bring You any legal consequences (although my statement about denial of service is somehow true - in fact totally true except "pro" part ;) ). It was just that i can't stop myself to write it :D ) laasonen, Thank You for new update and it's really my pleasure to contribute even in such small way. Tested new package - works fine, in every possible combination my MAC remain the same (except event just after update via 3G and enabling wifi later - got message about "unable to restore mac" - for obvious reasons, wifi was disabled on old version, so new version wasn't able to locate non-existing MAC file :) ). I also hit into too-fast-respawn bug You mentioned and i agree that it shouldn't be problem in real-life situations. Ho ever, if it happens, it's quite irritating, cause You must wait long time before using wifi again (or reboot phone). May is ask about rationale for restarting osso-wlan? I'm sure there is one, again I'm asking out-of-curiosity. It's related to MAC problem? --- Anyway, for lazy ones here is link to vote for package - we want to finally made it into testing, don't we? Voting is also important form of contribution, so pierrem and other, if You like it, please vote for this package (after testing). |
Re: [ANNOUNCE] Wlan Driver Selector Applet - Switch easily between stock and bleeding edge drivers and shut down WLAN complitely [0.2.2]
@laasonen - Thanks , I just updated it with FAM . I hope it will fix that problem .
@Estel - ahahahahahah that was funny :D:D:D . That router didn't deny all devices because a friend with an iphone 3 could connect and use their internet . |
Re: [ANNOUNCE] Wlan Driver Selector Applet - Switch easily between stock and bleeding edge drivers and shut down WLAN complitely [0.2.2]
Quote:
I'll take it off, because even the test script without it was working for him. If someone is having trouble with the new 0.2.2-3 try to uncomment these lines: Code:
STOP="`stop wlancond`" 2> /dev/null /sbin/load-bleeding-edge-drivers.sh /sbin/load-stock-drivers.sh |
All times are GMT. The time now is 07:23. |
vBulletin® Version 3.8.8