(old)Puppy Linux Discussion Forum

prit1 wrote:when I rebooted, the network did not get enabled. I had to load the profile again, and run auto dhcp to get the network running. Tried rebooting once again with the same result.

Can you try looking in /tmp/bootsysinit.log and see what kind of messages are there?

Here is an error message I noticed when running net-setup.sh from the prompt.

Code: Select all

Failure (Operation not supported)
/usr/sbin/net-setup.sh: line 622: 4171 Terminated  gxmessage -center -bg "orange" -buttons "" -title "Puppy Network Wizard" "Configuring interface..."
Error, ra0: dhcpd not running

That seems ok, it what you get after killing a dialog window.

Dougal wrote:

Keef wrote:When I run it from the command line I get:-
/usr/bin/net-setup.sh: line 1341: scanpci: command not found

That means that Barry hasn't included scanpci in Dingo (which is part of the Xorg package).

When I try to save a profile I get:-
/usr/sbin/wag-profiles.sh: line 706: : No such file or directory

Ok, I'll have another look at it.

Yes I have. I've got it in 4.1 anyway. I don't recall if it got left out of 4.00, Surprised if I did, as my PupScan program uses it.

Thanks for including the "Broadcast SSID" "Driver" "Hidden SSID" button label modification.

... when you do the next revision, can I just suggest a change in the order?
Between lines 531 and and 561 of wag-profiles.sh, I suggest shift the "Hidden SSID" stuff to the top, then "Broadcast SSID" next, then "Driver" at the bottom.
This would then result in a more logical graphical layout, as per attachment.

@Dougal:

Here are the messages from bootsysinit.log:

Duplicate post.

I ran Pfind for scanpci and found
/usr/X11R7/lib/xorg/modules/libsanpci.la and
/usr/X11R7/lib/modules/libsanpci.la

Is this what the network wizard is looking for?

tempestuous wrote: ... when you do the next revision, can I just suggest a change in the order?
Between lines 531 and and 561 of wag-profiles.sh, I suggest shift the "Hidden SSID" stuff to the top, then "Broadcast SSID" next, then "Driver" at the bottom.

Ok, I'll do that tomorrow.

prit1 wrote:

Code: Select all

...
...
  loading module rt2500
....
....
configuring network interface eth0
interface eth0 has not been configured... skipping
configuring network interface ra0
wireless scan with iwlist failed... skipping interface

It seems like it doesn't find anything with the wireless scan...
When you run "iwlist ra0 scan", does it detect anything?

Keef wrote:I ran Pfind for scanpci and found
/usr/X11R7/lib/xorg/modules/libsanpci.la and
/usr/X11R7/lib/modules/libsanpci.la

Is this what the network wizard is looking for?

No, there should be a binary, /usr/X11R7/bin/scanpci, that is run. If it existed, running "scanpci" in a terminal would work...

I've updated the attachment again, hopefully it will help solve the problem with saving profiles...

Sorry to report a bug, but trying to create a WPA Profile goes well until you click on 'Save'. The whole wizard then crashes out completely. Poof - gone!

Edit - sorry it looks like you've just addressed this. I'll try the latest version.

Another Edit Sadly the July 22nd version behaves exactly the same as the earlier one. In addition the 'Use this profile' button has the same effect.

It's worth pointing out at this stage that I've never got WPA to work with the latest kernel since the iwp3945 driver was replaced by iwl3945 (and despite Tempestuous' best efforts), so this behaviour may be a symptom of those issues.

New Bug Resorting to wired (on eth0) - the internet isn't activated on reboot. It looks to me that this is because /etc/eth0mode isn't written - see screenshot.

Dougal wrote: It seems like it doesn't find anything with the wireless scan...
When you run "iwlist ra0 scan", does it detect anything?

I get the message "interface doesnt support scanning".

Please note that the when the default network wizard in Dingo would detect and save a profile, it worked on every reboot. No rescanning was required.

using the 22nd july version I found a couple of problems in rc.network
using an IPW2200 card with WEP security

1.
for PROF in `ls ${PROFILES_DIR}/${CELL_AP_MAC}.w[ep][pa]*.conf 2>/dev/null` ; do
my profile is named 00:16:B6:28:90:C1.WEP.conf so the case is a problem

2.
if [ "$SUCCESS" = "yes" ] && testInterface; then
the testInterface function requires an argument $INTERFACE

I've tried the July 22nd version, but the wizard is still closing down when I try to save.
Same error message:
/usr/sbin/wag-profiles.sh: line 712: : No such file or directory

It did pick up the interface though (on second boot).
I've also copied scanpci and libscanpci.so from a 2.14R CD, so that error message has gone.

By the way, I am using WPA/TKIP. Just as an experiment I've found that selecting Open or WEP will allow a profile to save (won't connect of course) but not WPA.

Don't know if this is relevant, but when I select 'use this profile' the console throws up the message:

Invalid AP_SCAN command: needs one argument (ap_scan value)

It connects properly though.

OK, a few updates:
1) I fixed the bugs reported by HairyWill. The testInterface problem
existed in other places, including the wired connection code, so
with the last version I think no-one would have been able to
connect...

2) I noticed something small that I'm not sure what to do with, maybe
someone (tempestuous?) will know:
While testing, I tried using the "autoconnect" profile and got an error
from iwconfig, that the interface (wlan0, the Ralink in the Classmate
with rt73usb) does not support the "Auto" mode...

3) I've fixed something I implemented originally but was incomplete, but
I'm not even sure if it's the right thing to do:
When configuring a wireless interface (with iwconfig, wpa_sup or
wlanctl-ng), if any of the commands fails (setting mode, essid etc.), then
it will declare the configuration as failed, not even trying to see if
it's connected.
Is there a point in doing so, or just go on and test the interface (with
ifplugstatus) anyway?

4) I've found the problem that caused the crashing, the question is how
to solve it:
When creating a new profile not from a scan result (i.e, a
completely "made up" one, like the samples), the user is asked for a name
and ESSID.
But the profile is saved according to the MAC address... so you get the
file /etc/wireless/profiles/.Open.conf (blank MAC address before first
dot...)

The reason I use the MAC address is that, in my experience (cycling around
and scanning for networks...), people don't always make sure they have a
unique ESSID: I've seen things like "default", "connexant", "linksys"
and "k" (no kidding)...
I also assumed that people might change the ESSID, so sticking with the
MAC address would make the profile still usable.

So, what should I do?
I could:
- make the profiles saved as $ESSID.$MAC_ADDRESS.$ENCRYPTION.conf, which
would make sure it has a unique name. But this adds a dependency on the
ESSID.

- if the MAC address is blank, save it as $ESSID.$ENCRYPTION.conf
but this way it will not be used at bootup (though the network might still
be autoconnected when trying to connect to open networks)

- let the user specify the MAC address, rather than the ESSID (or as well
as the ESSID, but this will make the wizard window bigger than it already
is...).

What I don't really understand is why would a user create a profile
that is not based on scan results? Is there any other "general" profile
but "autoconnect" that anyone would want?

prit1 wrote:I get the message "interface doesnt support scanning".

Please note that the when the default network wizard in Dingo would detect and save a profile, it worked on every reboot. No rescanning was required.

Does it use one of the prism2 modules? If so, then wlanctl-ng is supposed to be used for scanning, which should be done at bootup. What that would mean is that the problem is just that the interface configuration option telling it to use wlanctl-ng is missing (it should be in the config file in /etc/wireless/interfaces).

Keef wrote:I've tried the July 22nd version, but the wizard is still closing down when I try to save.
Same error message:
/usr/sbin/wag-profiles.sh: line 712: : No such file or directory

See my long post above about this.

By the way, I am using WPA/TKIP. Just as an experiment I've found that selecting Open or WEP will allow a profile to save (won't connect of course) but not WPA.

I'll look and see if there's anything in the WPA code that might cause problems...

Don't know if this is relevant, but when I select 'use this profile' the console throws up the message:

Invalid AP_SCAN command: needs one argument (ap_scan value)

It connects properly though.

This could be something to do with the specific driver (see the problem I mention I have with "Auto", point 2 above). I actually think that you might have a problem connecting with the latest version, since I just fixed the code that aborts if there's an error... (see my point 3 above)

Used your suggestion and after I downloaded 23July opened a terminal in my downloads folder and ran tgz2pet against the file and then ran the newly created PET.

Then I rebooted with both wired LAN and a wireless GigaFast USB modem attached.

Both connections were recognized and I was able to Scan and find my home network and add the WEP but even though it "says" that it is OK and ran dhcpd OK it still would not connect.

I tried switching over to the wired connection and my CF-28 locked up.

I have another laptop running 3.01 right next to this one and it is connected via internal wireless and is working fine.

Dougal wrote:Does it use one of the prism2 modules? If so, then wlanctl-ng is supposed to be used for scanning, which should be done at bootup. What that would mean is that the problem is just that the interface configuration option telling it to use wlanctl-ng is missing (it should be in the config file in /etc/wireless/interfaces).

My wireless card uses RT2500 modules. The scan from your network wizard works in the 1st or 2nd attempts. Does this not use iwlist?

How do I use wlanctl-ng?

Dougal wrote:What I don't really understand is why would a user create a profile
that is not based on scan results?

I agree entirely. For a long time I didn't even realise that the network wizard had a scan button.

It would probably be better if you moved the scan button to the top of the form and make it clearer that the action is to "scan for available networks" or similar.

Maybe change the frame label Load Profile to Load Existing Profile, this makes it clear that you need to create one.