dhcpcd-discuss

On 08/04/16 09:51, Roy Marples wrote:
> Hi Tim
>
> On Thursday 04 August 2016 03:38:26 Tim Tassonis wrote:
> > The Gui also complained about not being able to write to /etc/dhcpcd.conf.
>
> You should only see that if you right click the icon and select preferences
> yes?

Yes, that was so.

> > I got these messages away by calling dhcpcd-gtk as root, but I wonder if
> > that is neccessary? Does dhcpcd-gtk have to make changes to dhcpcd.conf?
> > If so, no problem, I can also make the file group writable for wheel.
>
> It does, so make the file write-able for wheel.
> I may introduce config editing via the control socket, but that bloats dhcpcd
> more which I don't want.

Totally fine with the group write access. The only suggestion I would 
have is to maybe suppress the error dialog box and just disable the 
preferences option then, for users like me that only want to select 
access points.

I'll have a look at the source code and maybe write a patch to make the 
"advanced" features optional, maybe triggered by a startup option. The 
reason for this is that I'd love to use dhcpcd-gtk in my distribution, 
replacing networkmanager and any static network configuration is 
out-of-scope anyway and will be done in the corresponding network scripts.

> > But asides, I got no way to configure any access point, I assume that my
> > wpa_supplicant stuff is wrong, too.
>
> Well, it won't configure your access point for you.
> But it will configure wpa_supplicant to talk to your access point!
> Simply left click the icon and you'll see a list of SSIDs in range. Click your
> one and a box is presented to enter a PSK. You can either enter it, or click
> cancel and wpa_supplicant will use the last remembered PSK.
>
> If you don't see your SSID then you'll need to setup your AP to broadcast it I
> guess. All dhcpcd does here is show the contents of
>
> wpa_cli scan_results

It now works! The strange thing is that scan_results only got any 
output, after I called wpa_cli scan first. While my config is the same 
as yours, I reckon that's due to my starting parameters of 
wpa_supplicant. I'll have to have a look into that later. The bottom 
line is: it works, thanks a lot for your help.


Tim