View previous topic :: View next topic |
Author |
Message |
pmam Veteran
Joined: 30 Dec 2013 Posts: 1145
|
Posted: Thu Jan 29, 2015 11:38 am Post subject: |
|
|
charles17,
I think am not using fluxbox - I have lxde and xfce (also kde) -
I dont have screenshot in lxde so replace to xfce and installed xfce4-screenshooter...
http://imgur.com/rshH2YG
but it is not adding much info I guess...
At least I have screenshooter
Please see if you can help connect this dongle with dhcpcd.
Thanks _________________ “You can take our property, our sweet homes, even our cloths...
But don't touch the streets, Ah, That's NO, NO, NO!
The streets are our @world's compilable kernel ...” |
|
Back to top |
|
|
khayyam Watchman
Joined: 07 Jun 2012 Posts: 6227 Location: Room 101
|
Posted: Thu Jan 29, 2015 12:22 pm Post subject: |
|
|
pmam wrote: | Code: | wpa_supplicant_ra0="nl80211" |
|
pmam ... you have a typo, that should read: wpa_supplicant_ra0="-Dnl80211" ... however, it's WEXT, so you should probably use '-Dwext' ... as suggested by the following error:
pmam wrote: | Code: | Could not open file /sys/class/net/ra0/phy80211/name: No such file or directory |
|
pmam wrote: | Meanwhile I fixed it by installing this pacakge: sys-apps/ifplugd. I am still preferring DHCPCD, so if there is any idea, I am here... |
ifplugd will simply activate the device based on it being detected, it will not configure wpa_supplicant, netifrc, or what-have-you, it might start dhcpcd on the interface however. I'd leave this out of the equation right now, already you have netifrc, dhcpcd and wpa_gui, all of which "manage the network". Your over-complicating things, and right now I'm not sure which is actually doing the managing (ie, whether you'd disabled the dhcpcd configuration for ra0 in dhcpcd.conf).
As for using dhcpcd, I'm not sure how it starts wpa_supplicant, if it runs /etc/init.d/wpa_supplicant, or what configuration is needed for the right parameters to be supplied to wpa_supplicant when dhcpcd calls it. If its using /etc/init.d/wpa_supplicant then /etc/conf.d/wpa_supplicant will need to be configured, ie:
Code: | wpa_supplicant_args="-Dwext" |
Not knowing how dhcpcd goes about these things makes it difficult for me to suggest the correct setup, but right now if you have dhcpcd and net.ra0 (ie, netifrc, which will be using ifplugd if not otherwise configured now that its installed) and wpa_gui you never going to know what is working and what is not. If you want to use dhcpcd then disable everything else, if you want to use wpa_gui or netifrc w/ ifplugd then do the same. If one or other doesn't work then methodically disable/enable another. BTW, wpa_gui just offers an interface for configuring, and switching, networks, so it can work along with other components "managing" (or starting) the network ... but keep it simple, its not really necessary here because you are connecting to one network, and wpa_supplicant will do that without the aid of wpa_gui.
charles17 wrote: | And what's the output of debugging wpa_supplicant? |
charles ... we can see from the above that wpa_supplicant is not able to do anything with the device because its being told its '-Dnl80211' and not '-Dwext', you're not going to get anymore debug from it because it doesn't understand how it should handle it.
best ... khay |
|
Back to top |
|
|
pmam Veteran
Joined: 30 Dec 2013 Posts: 1145
|
Posted: Thu Jan 29, 2015 12:28 pm Post subject: |
|
|
charles17,
It is working..
According to debugging wpa_supplicant's output I saw this problem:
Code: | nl80211: Failed to set interface 4 to mode 2: -19 (No such device)
nl80211: Could not configure driver to use managed mode |
So I added this line (as I added to /etc/conf.d/net) with "nl80211" :
Code: | interface ra0
static ip_address=10.0.0.11/24
static routers=10.0.0.138
static domain_name_servers=10.0.0.138
wpa_supplicant_ra0="nl80211" |
EDIT: The information in this post is wrong - it is not working - please ignore it!
Thanks you all _________________ “You can take our property, our sweet homes, even our cloths...
But don't touch the streets, Ah, That's NO, NO, NO!
The streets are our @world's compilable kernel ...”
Last edited by pmam on Fri Jan 30, 2015 7:36 am; edited 2 times in total |
|
Back to top |
|
|
charles17 Advocate
Joined: 02 Mar 2008 Posts: 3664
|
Posted: Thu Jan 29, 2015 12:36 pm Post subject: |
|
|
khayyam wrote: | pmam wrote: | Code: | wpa_supplicant_ra0="nl80211" |
|
pmam ... you have a typo, that should read: wpa_supplicant_ra0="-Dnl80211" ... however, it's WEXT, so you should probably use '-Dwext' ... as suggested by the following error:
pmam wrote: | Code: | Could not open file /sys/class/net/ra0/phy80211/name: No such file or directory |
|
| That's what's been confusing me, understanding it's nl80211.
Syntax for setting in dhcpcd.conf is according to loc cit 1.
Maybe like dhcpcd.conf wrote: | env wpa_supplicant_driver=wext |
|
|
Back to top |
|
|
charles17 Advocate
Joined: 02 Mar 2008 Posts: 3664
|
Posted: Thu Jan 29, 2015 12:38 pm Post subject: |
|
|
pmam wrote: | So I added this line (as I added to /etc/conf.d/net) with "nl80211" | For dhcpcd you shouldn't need that file at all.
And also debugging should work with wext Quote: | $ wpa_supplicant -Dwext -ira0 -C/var/run/wpa_supplicant/ -c/etc/wpa_supplicant/wpa_supplicant.conf -dd |
|
|
Back to top |
|
|
khayyam Watchman
Joined: 07 Jun 2012 Posts: 6227 Location: Room 101
|
Posted: Thu Jan 29, 2015 1:54 pm Post subject: |
|
|
pmam wrote: | It is working.. |
pmam ... perhaps, but it has nothing to do with the following ...
pmam wrote: | So I added this line (as I added to /etc/conf.d/net) with "nl80211" :
Code: | wpa_supplicant_ra0="nl80211" |
|
... again, thats incorrect, it should be '-Dnl80211' or '-Dwext'.
best ... khay |
|
Back to top |
|
|
pmam Veteran
Joined: 30 Dec 2013 Posts: 1145
|
Posted: Thu Jan 29, 2015 2:17 pm Post subject: |
|
|
Sorry for a big confusion - I was harry to go out of office and.. misleading..
First, I did not notice that netifrc is running but not dhcpcd. So do not refer to my last post.
Quote: | pmam wrote:
So I added this line (as I added to /etc/conf.d/net) with "nl80211"
For dhcpcd you shouldn't need that file at all. |
I know - It is only for netifrc.
So, know return to the previous stage - It is working with netifrc but not dhcpcd.
I tried your suggestions for wpa_supplicant_ra0= but not working -
can you please give me the link for all this dhcpcd's syntax? _________________ “You can take our property, our sweet homes, even our cloths...
But don't touch the streets, Ah, That's NO, NO, NO!
The streets are our @world's compilable kernel ...” |
|
Back to top |
|
|
charles17 Advocate
Joined: 02 Mar 2008 Posts: 3664
|
Posted: Thu Jan 29, 2015 2:27 pm Post subject: |
|
|
pmam wrote: | can you please give me the link for all this dhcpcd's syntax? | Still the same. |
|
Back to top |
|
|
pmam Veteran
Joined: 30 Dec 2013 Posts: 1145
|
Posted: Thu Jan 29, 2015 2:50 pm Post subject: |
|
|
Can you please let me know - The topic of the link you noted - For what device is?
I really dont know what line suppose to be for my device- I tried:
Code: | env wpa_supplicant_driver=nl80211 |
and this:
Code: | env wpa_supplicant_driver=wext |
what else can be? _________________ “You can take our property, our sweet homes, even our cloths...
But don't touch the streets, Ah, That's NO, NO, NO!
The streets are our @world's compilable kernel ...” |
|
Back to top |
|
|
charles17 Advocate
Joined: 02 Mar 2008 Posts: 3664
|
Posted: Thu Jan 29, 2015 3:14 pm Post subject: |
|
|
pmam wrote: | and this:
Code: | env wpa_supplicant_driver=wext |
| This one should be working. Did you check debugging with wext (some of my previous posts)?
pmam wrote: | what else can be? | See man 8 wpa_supplicant, section "AVAILABLE DRIVERS".
Edit:
pmam wrote: | Can you please let me know - The topic of the link you noted - For what device is? | The device is Code: | # lspci -vvv -s 08:00.0
08:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG [Golan] Network Connection (rev 02)
Subsystem: Hewlett-Packard Company PRO/Wireless 3945ABG [Golan] Network Connection
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 16
Region 0: Memory at e8000000 (32-bit, non-prefetchable) [size=4K]
Capabilities: [c8] Power Management version 2
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [d0] MSI: Enable- Count=1/1 Maskable- 64bit+
Address: 0000000000000000 Data: 0000
Capabilities: [e0] Express (v1) Legacy Endpoint, MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s <512ns, L1 unlimited
ExtTag- AttnBtn- AttnInd- PwrInd- RBE- FLReset-
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+
MaxPayload 128 bytes, MaxReadReq 128 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr+ TransPend-
LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Latency L0 <128ns, L1 <64us
ClockPM+ Surprise- LLActRep- BwNot-
LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- Retrain- CommClk+
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
Kernel driver in use: iwl3945
Kernel modules: iwl3945 |
|
|
Back to top |
|
|
pmam Veteran
Joined: 30 Dec 2013 Posts: 1145
|
Posted: Thu Jan 29, 2015 6:35 pm Post subject: |
|
|
I add this line to /etc/dhcpcd.conf:
Code: | env wpa_supplicant_driver=wext |
and here wpa_debug output:
http://pastebin.com/DGKEz1tB _________________ “You can take our property, our sweet homes, even our cloths...
But don't touch the streets, Ah, That's NO, NO, NO!
The streets are our @world's compilable kernel ...” |
|
Back to top |
|
|
khayyam Watchman
Joined: 07 Jun 2012 Posts: 6227 Location: Room 101
|
Posted: Thu Jan 29, 2015 6:47 pm Post subject: |
|
|
pmam wrote: | http://pastebin.com/DGKEz1tB |
Code: | ra0: CTRL-EVENT-CONNECTED - Connection to 00:26:5a:12:36:60 completed [id=0 id_str=] |
... so, connection completed, what does the following show:
best ... khay
btw: THE DRIVER IS WEXT, WEXT!!! WEXT!!!!!!!! ... just so you know :) |
|
Back to top |
|
|
pmam Veteran
Joined: 30 Dec 2013 Posts: 1145
|
Posted: Thu Jan 29, 2015 7:00 pm Post subject: |
|
|
khayyam,
WOW, you are right!
The problem is - I do not see the interface in wpa_gui -
so I thought it is disconnected...
But I can connect to web and it seems ok and here:
Code: | wpa_cli status
Selected interface 'ra0'
bssid=00:26:5a:12:36:60
ssid=AFMBZPD7
id=0
mode=station
pairwise_cipher=WEP-40
group_cipher=WEP-40
key_mgmt=NONE
wpa_state=COMPLETED
ip_address=10.0.0.11
address=00:22:c0:31:44:20 |
So it means that I am connected - It is nice to be connected.. to the right places
but why there is no wpa_gui????
Quote: | btw: THE DRIVER IS WEXT, WEXT!!! WEXT!!!!!!!! ... just so you know |
Please - explanation to your joke (my english..) - I suspect it is good one..
Thanks _________________ “You can take our property, our sweet homes, even our cloths...
But don't touch the streets, Ah, That's NO, NO, NO!
The streets are our @world's compilable kernel ...” |
|
Back to top |
|
|
khayyam Watchman
Joined: 07 Jun 2012 Posts: 6227 Location: Room 101
|
Posted: Thu Jan 29, 2015 7:55 pm Post subject: |
|
|
pmam wrote: | WOW, you are right! :D |
pmam ... I'm always right ... sometimes :)
pmam wrote: | The problem is - I do not see the interface in wpa_gui |
This suggests your user isn't in the wheel group, and so can't access the cntl_interface. What does the following show:
If you're not in wheel then you can modify the user like so:
Code: | # usermod -a -G wheel pmam |
pmam wrote: | khayyam wrote: | btw: THE DRIVER IS WEXT, WEXT!!! WEXT!!!!!!!! ... just so you know :) |
Please - explanation to your joke (my english..) - I suspect it is good one.. :wink: |
I told you numerious times the driver is wext ... "don't make me angry ... you wouldn't like me when I'm angry" :)
best ... khay |
|
Back to top |
|
|
pmam Veteran
Joined: 30 Dec 2013 Posts: 1145
|
Posted: Thu Jan 29, 2015 8:39 pm Post subject: |
|
|
It is not stable.. now I can't connect to web...though the same output of wpa_cli status
EDIT: It is ok only when first I connect with wired and then disconnect the cable and wireless is working.
Quote: | This suggests your user isn't in the wheel group, and so can't access the cntl_interface. What does the following show: |
so why it is ok with netifrc...
Code: | groups
root bin daemon sys adm disk wheel floppy tape video |
Quote: | I told you numerious times the driver is wext |
yes, but in netifrc we put: wpa_supplicant_ra0="nl80211" so I thought this is the driver... _________________ “You can take our property, our sweet homes, even our cloths...
But don't touch the streets, Ah, That's NO, NO, NO!
The streets are our @world's compilable kernel ...” |
|
Back to top |
|
|
khayyam Watchman
Joined: 07 Jun 2012 Posts: 6227 Location: Room 101
|
Posted: Thu Jan 29, 2015 10:33 pm Post subject: |
|
|
pmam wrote: | It is not stable.. now I can't connect to web...though the same output of wpa_cli status
EDIT: It is ok only when first I connect with wired and then disconnect the cable and wireless is working. |
pmam ... if that's the case then this doesn't seem to be an issue with the connection per-se but with the "management". If 'wpa_cli status' shows "connected" and an you have an ip address then you might test the network, ie, ping the ip address of the gateway, this is how you go about debugging such things, ruling out possible issues (ie, DNS).
pmam wrote: | khayyam wrote: | This suggests your user isn't in the wheel group, and so can't access the cntl_interface. What does the following show: |
so why it is ok with netifrc... |
I said "suggests", I don't know enough about using dhcpcd to manage the network so any problem there I can't really help with. The fact that the interface shows up when netifrc is in use can mean only one thing, dhcpcd isn't configured correctly.
pmam wrote: | khayyam wrote: | I told you numerious times the driver is wext |
yes, but in netifrc we put: wpa_supplicant_ra0="nl80211" so I thought this is the driver... :wink: |
No, we didn't, you did, and besides that being wrong (again) I said "no, you need to use -Dwext" and then you said "so I added this line [...] nl80211", and I said again "its -Dwext", then you said "I really dont know what line suppose to be for my device", so I had to say "btw: THE DRIVER IS WEXT, WEXT!!! WEXT!!!!!!!!". Clear?
best ... khay |
|
Back to top |
|
|
pmam Veteran
Joined: 30 Dec 2013 Posts: 1145
|
Posted: Fri Jan 30, 2015 7:33 am Post subject: |
|
|
OK - since I have a working solution with netirfc, at the moment, am giving up with dhcpcd manager for this laptop -
until someone will inform me, he have done it with this type of usb dongle.
I takes me too much time...
Thanks you all _________________ “You can take our property, our sweet homes, even our cloths...
But don't touch the streets, Ah, That's NO, NO, NO!
The streets are our @world's compilable kernel ...” |
|
Back to top |
|
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|