Ok, I packaged it up for tinycorelinux where it is a pending extension
at the moment, most people there don't have an easy to use alternative
to wicd yet.
There's a simple config file where you specify your two interface
names, then everything gets started like this:
ifconfig $WIRED up
wpa_suppli
Hi,
hiro wrote:
On Thu, Jan 20, 2011 at 9:33 AM, Kai Hendry wrote:
Please let me know if you figure this problem out.
I now use wpa_cli -a and netplugd with a few scripts to stick it all together.
I use wpa_cli -a for wifi events, because netplugd does too much with
the device, always tries
+--- hiro ---+
> I now use wpa_cli -a and netplugd with a few scripts to stick it all together.
> I use wpa_cli -a for wifi events, because netplugd does too much with
> the device, always tries to keep it up.
>
> If anybody wants these scripts I can tar them up.
>
i
On Thu, Jan 20, 2011 at 9:33 AM, Kai Hendry wrote:
> Please let me know if you figure this problem out.
I now use wpa_cli -a and netplugd with a few scripts to stick it all together.
I use wpa_cli -a for wifi events, because netplugd does too much with
the device, always tries to keep it up.
If
I think ifplugd also polls, it uses ethtool to detect changes.
I'll try netplug, which uses netlink(7).
Please let me know if you figure this problem out.
http://natalian.org/archives/2011/01/20/Trying_to_get_Windows_hotplug_usability/
I've yet to debug why /etc/ifplugd/netcfg.action doesn't work for me.
Code is hard to read at first glances.
Hi,
hiro wrote:
I also don't remember why I started using wicd instead of scripting,
there definitely was an other reason, too. Butl, nevermind.
Ok, my mind came back. It was automatically switching between wireless
networks which let me think I needed wicd.
The only thing missing now is a ni
On Wed, Jan 19, 2011 at 12:14:06PM +, hiro wrote:
> I still want wireless to be switched off completely when I attach the
> ethernet cable. Is there any program I could combine with wpa_actiond
> to acchieve this?
ifplugd is a daemon that runs a trigger script when ethernet cable is
attached/d
> I also don't remember why I started using wicd instead of scripting,
> there definitely was an other reason, too. Butl, nevermind.
Ok, my mind came back. It was automatically switching between wireless
networks which let me think I needed wicd.
The only thing missing now is a nice interface for
Cool. ifplugd seems to be exactly what I need.
I just tried running wpa_supplicant in the foreground and it doesn't
output anything when I connect my ethernet cable.
On 1/20/11, Kurt H Maier wrote:
> On Wed, Jan 19, 2011 at 8:15 PM, Jan wrote:
>> Maybe surveilling /var/log/messages (lines are similar to dmesg output)
>> for lines that includ
Jan dixit (2011-01-20, 02:33):
> On Thu, 20 Jan 2011 02:28:22 +0100, Antoni Grzymala
> wrote:
> > Jan dixit (2011-01-20, 02:26):
> >
> >> On Wed, 19 Jan 2011 20:22:51 -0500, Kurt H Maier
> >> wrote:
> >> > On Wed, Jan 19, 2011 at 8:15 PM, Jan wrote:
> >> >> Maybe surveilling /var/log/messages
On Thu, 20 Jan 2011 02:28:22 +0100, Antoni Grzymala
wrote:
> Jan dixit (2011-01-20, 02:26):
>
>> On Wed, 19 Jan 2011 20:22:51 -0500, Kurt H Maier
>> wrote:
>> > On Wed, Jan 19, 2011 at 8:15 PM, Jan wrote:
>> >> Maybe surveilling /var/log/messages (lines are similar to dmesg
>> >> output)
>> >>
I forgot about dmesg!
And I would rather not use polling. But I guess I should. wicd and
dbus is not the way to go.
I also don't remember why I started using wicd instead of scripting,
there definitely was an other reason, too. Butl, nevermind.
On Wed, Jan 19, 2011 at 8:26 PM, Jan wrote:
>
> Does wpa_supplicant work with wired devices?
Yes, using the 'wired' driver. However, afaik wpa_supplicant only
handles one device per instance, so any controlling script would need
to manage both instances, and at that point there's no point using
Jan dixit (2011-01-20, 02:26):
> On Wed, 19 Jan 2011 20:22:51 -0500, Kurt H Maier
> wrote:
> > On Wed, Jan 19, 2011 at 8:15 PM, Jan wrote:
> >> Maybe surveilling /var/log/messages (lines are similar to dmesg output)
> >> for lines that include "eth0" and "link" might work.
> >
> > wpa_supplican
On Wed, 19 Jan 2011 20:22:51 -0500, Kurt H Maier
wrote:
> On Wed, Jan 19, 2011 at 8:15 PM, Jan wrote:
>> Maybe surveilling /var/log/messages (lines are similar to dmesg output)
>> for lines that include "eth0" and "link" might work.
>
> wpa_supplicant puts all its info (i.e., CTRL_EVENT_DISCONN
On Wed, Jan 19, 2011 at 8:15 PM, Jan wrote:
> Maybe surveilling /var/log/messages (lines are similar to dmesg output)
> for lines that include "eth0" and "link" might work.
wpa_supplicant puts all its info (i.e., CTRL_EVENT_DISCONNECTED) out
on stderr. Could just pipe that to a shell script.
--
On Wed, 19 Jan 2011 11:10:18 -0500, Kurt H Maier
wrote:
>> I still want wireless to be switched off completely when I attach the
>> ethernet cable. Is there any program I could combine with wpa_actiond
>> to acchieve this?
>
> I don't see why this can't be scripted.
Maybe surveilling /var/log/m
On Wed, Jan 19, 2011 at 7:14 AM, hiro <23h...@googlemail.com> wrote:
> Thanks, I was still searching for alternatives to wicd.
> I get it that wpa_supplicant also knows how to do WEP?
>
wpa_supplicant supports wep, here's an example wep stanza:
network={
ssid="kfx"
key_mgmt=NONE
wep_key0=01
20 matches
Mail list logo