I found the solution. With strace I figured out that wpa_supplicant created a second socket: /var/run/wpa_supplicant/eth0. When I use this one with wpa_cli it works without problems. <br><br>Thanks for the help.<br><br>Kind regards,<br>
<br>Peter<br><br><br><div class="gmail_quote">2010/3/26 Peter Fortuin <span dir="ltr"><<a href="mailto:peter.fortuin@gmail.com">peter.fortuin@gmail.com</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
The right on the socket is 777. So everybody could access it. Don't think it's a right problem. <br><br><br><div class="gmail_quote">2010/3/26 Holger Schurig <span dir="ltr"><<a href="mailto:holgerschurig@gmail.com" target="_blank">holgerschurig@gmail.com</a>></span><div>
<div></div><div class="h5"><br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div>> And I thougth that this message meant that the path was not correct.<br>
<br>
</div>Could also be the rights.<br>
<br>
You can always use "strace -efile" to check out which program access which<br>
file. Or "lsof" to find out which program has which files open.<br>
<font color="#888888"><br>
--<br>
<a href="http://www.holgerschurig.de" target="_blank">http://www.holgerschurig.de</a><br>
</font></blockquote></div></div></div><br>
</blockquote></div><br>