Improved Network Wizard (and rc.network)
- urban soul
- Posts: 273
- Joined: Wed 05 Mar 2008, 17:03
- Location: "Killing a nerd is not as much fun as ist sounds" B.Simpson
- Contact:
Dougal,
When I run it from the command line I get:-
/usr/bin/net-setup.sh: line 1341: scanpci: command not found
When I try to save a profile I get:-
/usr/sbin/wag-profiles.sh: line 706: : No such file or directory
This was with the original version - I have since tried the new one, but could not get a connection (did not detect wlan0) even after several reboots. Now reverted to the first, and have got back on-line. No save though!
When I run it from the command line I get:-
/usr/bin/net-setup.sh: line 1341: scanpci: command not found
When I try to save a profile I get:-
/usr/sbin/wag-profiles.sh: line 706: : No such file or directory
This was with the original version - I have since tried the new one, but could not get a connection (did not detect wlan0) even after several reboots. Now reverted to the first, and have got back on-line. No save though!
@Dougal:
I tried your latest version. This time, it created the network connection. This is better than the last time.
But 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.
Here is an error message I noticed when running net-setup.sh from the prompt.
I tried your latest version. This time, it created the network connection. This is better than the last time.
But 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.
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
[url=http://macpup.org][b]Macpup - The beauty of linux[/b][/url] [b] | [/b] [url=http://pritlog.com/][b]Pritlog - Simple blog app[/b][/url]
- Dougal
- Posts: 2502
- Joined: Wed 19 Oct 2005, 13:06
- Location: Hell more grotesque than any medieval woodcut
It would be easy to do, but I'm not sure worth it, since that will just have to be updated, just like the wizard, and it just makes things more scattered...urban soul wrote:Hi, sounds great. - can you put the WPA driver specs into a separate config-file ? Otherwise every time a new driver is compiled by tempestuous the wizard itself has to be modified.
What's the ugliest part of your body?
Some say your nose
Some say your toes
But I think it's your mind
Some say your nose
Some say your toes
But I think it's your mind
- Dougal
- Posts: 2502
- Joined: Wed 19 Oct 2005, 13:06
- Location: Hell more grotesque than any medieval woodcut
That means that Barry hasn't included scanpci in Dingo (which is part of the Xorg package).Keef wrote:When I run it from the command line I get:-
/usr/bin/net-setup.sh: line 1341: scanpci: command not found
Ok, I'll have another look at it.When I try to save a profile I get:-
/usr/sbin/wag-profiles.sh: line 706: : No such file or directory
What's the ugliest part of your body?
Some say your nose
Some say your toes
But I think it's your mind
Some say your nose
Some say your toes
But I think it's your mind
- Dougal
- Posts: 2502
- Joined: Wed 19 Oct 2005, 13:06
- Location: Hell more grotesque than any medieval woodcut
Can you try looking in /tmp/bootsysinit.log and see what kind of messages are there?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.
That seems ok, it what you get after killing a dialog window.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
What's the ugliest part of your body?
Some say your nose
Some say your toes
But I think it's your mind
Some say your nose
Some say your toes
But I think it's your mind
- BarryK
- Puppy Master
- Posts: 9392
- Joined: Mon 09 May 2005, 09:23
- Location: Perth, Western Australia
- Contact:
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.Dougal wrote:That means that Barry hasn't included scanpci in Dingo (which is part of the Xorg package).Keef wrote:When I run it from the command line I get:-
/usr/bin/net-setup.sh: line 1341: scanpci: command not found
Ok, I'll have another look at it.When I try to save a profile I get:-
/usr/sbin/wag-profiles.sh: line 706: : No such file or directory
[url]https://bkhome.org/news/[/url]
-
- Posts: 5464
- Joined: Fri 10 Jun 2005, 05:12
- Location: Australia
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.
... 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.
- Attachments
-
- wpa-ap-scan.jpg
- (4.5 KiB) Downloaded 2087 times
@Dougal:
Here are the messages from bootsysinit.log:
Here are the messages from bootsysinit.log:
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
[url=http://macpup.org][b]Macpup - The beauty of linux[/b][/url] [b] | [/b] [url=http://pritlog.com/][b]Pritlog - Simple blog app[/b][/url]
Fat Free 3.01
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?
/usr/X11R7/lib/xorg/modules/libsanpci.la and
/usr/X11R7/lib/modules/libsanpci.la
Is this what the network wizard is looking for?
- Dougal
- Posts: 2502
- Joined: Wed 19 Oct 2005, 13:06
- Location: Hell more grotesque than any medieval woodcut
Ok, I'll do that tomorrow.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.
What's the ugliest part of your body?
Some say your nose
Some say your toes
But I think it's your mind
Some say your nose
Some say your toes
But I think it's your mind
- Dougal
- Posts: 2502
- Joined: Wed 19 Oct 2005, 13:06
- Location: Hell more grotesque than any medieval woodcut
It seems like it doesn't find anything with the wireless scan...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
When you run "iwlist ra0 scan", does it detect anything?
What's the ugliest part of your body?
Some say your nose
Some say your toes
But I think it's your mind
Some say your nose
Some say your toes
But I think it's your mind
- Dougal
- Posts: 2502
- Joined: Wed 19 Oct 2005, 13:06
- Location: Hell more grotesque than any medieval woodcut
Re: Fat Free 3.01
No, there should be a binary, /usr/X11R7/bin/scanpci, that is run. If it existed, running "scanpci" in a terminal would work...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?
What's the ugliest part of your body?
Some say your nose
Some say your toes
But I think it's your mind
Some say your nose
Some say your toes
But I think it's your mind
-
- Posts: 405
- Joined: Mon 01 Jan 2007, 20:24
- Location: Hayslope, near Middlemarch, Midlands, England
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.
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.
Last edited by nic2109 on Wed 23 Jul 2008, 13:33, edited 1 time in total.
[color=darkblue][b][size=150]Nick[/size][/b][/color]
I get the message "interface doesnt support scanning".Dougal wrote: It seems like it doesn't find anything with the wireless scan...
When you run "iwlist ra0 scan", does it detect anything?
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.
[url=http://macpup.org][b]Macpup - The beauty of linux[/b][/url] [b] | [/b] [url=http://pritlog.com/][b]Pritlog - Simple blog app[/b][/url]
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
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
Will
contribute: [url=http://www.puppylinux.org]community website[/url], [url=http://tinyurl.com/6c3nm6]screenshots[/url], [url=http://tinyurl.com/6j2gbz]puplets[/url], [url=http://tinyurl.com/57gykn]wiki[/url], [url=http://tinyurl.com/5dgr83]rss[/url]
contribute: [url=http://www.puppylinux.org]community website[/url], [url=http://tinyurl.com/6c3nm6]screenshots[/url], [url=http://tinyurl.com/6j2gbz]puplets[/url], [url=http://tinyurl.com/57gykn]wiki[/url], [url=http://tinyurl.com/5dgr83]rss[/url]
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.
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.
- Dougal
- Posts: 2502
- Joined: Wed 19 Oct 2005, 13:06
- Location: Hell more grotesque than any medieval woodcut
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?
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?
What's the ugliest part of your body?
Some say your nose
Some say your toes
But I think it's your mind
Some say your nose
Some say your toes
But I think it's your mind