[raspberry-vi] Re: wpa_supplicant

  • From: "Darren Brewer" <darren.m.brewer@xxxxxxxxxxxxxxxx>
  • To: <raspberry-vi@xxxxxxxxxxxxx>
  • Date: Sat, 23 Mar 2013 20:45:12 -0000

Hi Glenn

As I said I'm new to this programme so not sure this will work.  I tried 
copying the same file to my PC and got the same error as you. Then I tried 
copying a file from my home directory and that worked ok. Maybe if you login 
into the pi and become root. Then copy the config file to your home 
directory and then see if you can copy it across to the PC? Maybe its an 
ownership issue? Not sure.

The field after the password is for a private key file. If you use the jaws 
cursor it will read this label just above the edit field. The button after 
is for browsing to that key file I think.

Darren.



----- Original Message ----- 
From: "Glenn" <glennervin@xxxxxxxxxxxx>
To: <raspberry-vi@xxxxxxxxxxxxx>
Sent: Saturday, March 23, 2013 6:03 PM
Subject: [raspberry-vi] Re: wpa_supplicant


> Darren,
> I used the SFTP program you directed me to, and I can log in, and I can 
> find
> the files on the RPI.
> I tried to copy /ect/wpa_supplicant/wpa_supplicant.conf and I get 
> permission
> denied, error code 3.
> I tried using F9 to change the properties to both read and write, and I 
> get
> the same error code.
> Do I have to SSH into the RPI with Putty and change the permissions first?
> Also, what is the window after the password window when I am starting 
> SFTP?
> I tried the password again, and I don't think that is it, because it says
> "file not found".
> So I tried the above-mentioned file including its path, and that did not
> work either.
> Thanks for any help.
> Glenn
> ----- Original Message ----- 
> From: "Darren Brewer" <darren.m.brewer@xxxxxxxxxxxxxxxx>
> To: <raspberry-vi@xxxxxxxxxxxxx>
> Sent: Saturday, March 23, 2013 8:04 AM
> Subject: [raspberry-vi] Re: wpa_supplicant
>
>
> Hi Glenn
>
> I can't remember if you are using a windows box, but if you are this might
> help you with editing files. I've just discovered a nifty program called 
> win
> scp. It allows you to SSH into a linux box and then display in a split
> screen all the files on both your linux box and windows machine so you can
> transfer files from one to the other very easily.
>
> If you select commander mode during installation then you will be able to 
> se
> all the permissions on the linux files which is handy. The only gotcha is
> that if you are editing linux config files in windows. You must make sure
> that the line endings are set correctly. Windows files use cr and lf at 
> the
> end of each line. Whereas linux files only use lf. There is a setting that
> allows win scp to automatically make sure the files have the correct line
> endings. Although I haven't looked through the settings yet. I try and 
> edit
> config files in linux with ED, but I'm still learning.
>
> Download link
> http://winscp.net/eng/download.php
>
> Hope that helps.
> Darren.
>
>
>
>
>
>
>
> ----- Original Message ----- 
> From: "Glenn" <glennervin@xxxxxxxxxxxx>
> To: <raspberry-vi@xxxxxxxxxxxxx>
> Sent: Saturday, March 23, 2013 4:06 AM
> Subject: [raspberry-vi] wpa_supplicant
>
>
>> Wow, I can't believe that I need to do all that editing of files to make
>> the
>> WIFI work.
>> I get to reading of all the editing and such, like copying a string of
>> text
>> that wpa supplicant generates, and putting that into a file in some /var
>> directory.
>> I don't even know how to copy information that is put out onto the screen
>> after running a command.
>> After reading all the steps and trying to figure it out, I almost fall
>> asleep at the keyboard.
>> I think that, tomorrow I will connect my RPI to my kitchen TV via the 
>> HDMI
>> cable, and slap on a keyboard, and have my teenage son log onto our 
>> router
>> for me.
>> Too bad we can't get Orca working!
>> Glenn
>>
>> ===========================================================
>> The raspberry-vi mailing list
>> Archives: //www.freelists.org/archives/raspberry-vi
>> Administrative contact: <mike.ray@xxxxxxxxxxxxxx>
>> -----------------------------------------------------------
>> Raspberry Pi and the Raspberry Pi logo are trademarks of the Raspberry Pi
>> Foundation.
>>
>> This list is not affiliated to the Raspberry Pi Foundation and the views
>> and attitudes expressed by the subscribers to this list do not reflect
>> those of the Foundation.
>>
>> Mike Ray, list creator, January 2013
>>
>
> ===========================================================
> The raspberry-vi mailing list
> Archives: //www.freelists.org/archives/raspberry-vi
> Administrative contact: <mike.ray@xxxxxxxxxxxxxx>
> -----------------------------------------------------------
> Raspberry Pi and the Raspberry Pi logo are trademarks of the Raspberry Pi
> Foundation.
>
> This list is not affiliated to the Raspberry Pi Foundation and the views 
> and
> attitudes expressed by the subscribers to this list do not reflect those 
> of
> the Foundation.
>
> Mike Ray, list creator, January 2013
>
> ===========================================================
> The raspberry-vi mailing list
> Archives: //www.freelists.org/archives/raspberry-vi
> Administrative contact: <mike.ray@xxxxxxxxxxxxxx>
> -----------------------------------------------------------
> Raspberry Pi and the Raspberry Pi logo are trademarks of the Raspberry Pi 
> Foundation.
>
> This list is not affiliated to the Raspberry Pi Foundation and the views 
> and attitudes expressed by the subscribers to this list do not reflect 
> those of the Foundation.
>
> Mike Ray, list creator, January 2013
> 

=========================================================== 
The raspberry-vi mailing list 
Archives: //www.freelists.org/archives/raspberry-vi
Administrative contact: <mike.ray@xxxxxxxxxxxxxx>
-----------------------------------------------------------
Raspberry Pi and the Raspberry Pi logo are trademarks of the Raspberry Pi 
Foundation.

This list is not affiliated to the Raspberry Pi Foundation and the views and 
attitudes expressed by the subscribers to this list do not reflect those of the 
Foundation.

Mike Ray, list creator, January 2013

Other related posts: