what happened to WAG?

[violetdream]

Is WAG still at 0.3.2? I'm assuming so because that's what's in Puppy now but it hasn't been updated in a while. It works for me, but I tend to get weird readouts. For example:

not using PCMCIA

no module loaded
dhcpcd not running
wifi-beta not installed

wlan0 enabled
wireless ip: 192.168.2.5
access point acquired
no signal from access point

Weird thing about this is that I am using PCMCIA and I am connected to a network with a signal from the access point. I also have problems loading the profiles - if I select autoconnect, it doesn't seem to register the change after it reloads.

[keenerd]

WAG is still at 0.3.2. I'll be combining it into Rarsa's ethernet wizard, although I'll probably do one more bugfix release, for 2.6 kernel and ad-hoc networks.

The "not using PCMCIA" is a 2.6 kernel thing, my autodetection code breaks. Edit the "/etc/local/WAG/wag.conf" file and change the slot number to reflect which slot your card actually uses.

Could you give me more details about the autoconnect?

[rarsa]

I'm currently uploading wag to the Subversion repository so we can restart working on the network wizard and WAG. Both were reasonably stable so I started working on other stuff.

Now with the addition of Perl it's seems the right time to add the long awaited ndiswrapper functionality.

Keenerd,

I'll send you an email when it's ready.

[violetdream]

Thanks, could you post here too?

As for the autoconnect thing, when I try to load a profile, it looks like it's loading, but then when it goes back to the screen, it says "Autoconnect: no".

[keenerd]

It will always say that because it can not detect an AP called "Autoconnect". My fault on missing that exception.

[violetdream]

How do I manually set the card socket? I've tried going into /etc/WAG/wag-conf and putting in CARDSOC=1 (or 0) but it still says it hasn't been configured when it starts up.

[BarryK]

I'll just throw in a comment about /etc/networkmodules.
We need to get rid of this.

All of that info can be got from /lib/modules/<kernel-version>/modules.pcimap,
the modules inside /lib/modules/<kernver>/net/ and by using modinfo on them.
Maybe not so simple, but it can result in auto-generation of the equivalent to
/etc/networkmodules, so it doesn't have to be manually updated when I update
kernels.
I can probably have a go at doing this.

[rarsa]

I can probably have a go at doing this.

Great.

The net-setup wizard is on the subversion repository:

You can get it from here using the userId and password I emailed you some time ago.

Code: Select all

http://svn2.cvsdude.com/puppylinux/puppy-scripts/net-setup/trunk/