Joachim Ott skrev:
Hi Esben,
I'd like to bug you with 2 requests:
1. Can you split iliwi into 2 parts, a little daemon started at system
boot, that controls wpa_supplicant and udhcpc and a little gui, where
you can show available networks and manually switch to a different
than the current network?
I've already have had a similar thought. I'm not completely sure I know
what you mean though.. I would argue like Visti not to keep wifi on all
the time.
What I would like though is to make a dbus daemon so applications could
tell Iliwi-the-daemon to connect to configured networks. And then you
configure your networks in the current gui.
2. Instead of creating a configfile, can you use an existing
/etc/wpa_supplicant/wpa_supplicant.conf? It's not needed to have a
editor built into the gui to edit wap_supplicant.conf, it would be
sufficiant to send a HUP signal to wpa_supplicant to let it reread its
config. This would allow roaming once the ar6000 is fixed. Currently I
do this with "wpa_cli reassociate" to make it roam.
I'm not sure I should edit that file. If users use that file, Iliwi
should not. Or am I wrong?
_______________________________________________
Shr-devel mailing list
[email protected]
http://lists.shr-project.org/mailman/listinfo/shr-devel
