You are not logged in.
Pages: 1
Hi all,
After a long inactivity I upgraded basic packages. So now I have the latest network.sh which contains these changes: http://hg.slitaz.org/slitaz-boot-scripts/rev/f3e7c1cc6aef
I faced two problems:
1) Why call stop() from start()? Each time I boot this shuts down my Wifi card and starts it again right away, which adds a delay to the boot process; maybe does it wear off the card as well?
2) After commenting out "stop" in start(), I noticed there was still a delay before the "Configuring Wi-Fi..." message. I think this line:
[c][ "$WIFI" != 'yes' ] && ifconfig $INTERFACE up & sleep 5[/c]
should be changed into:
[c][ "$WIFI" != 'yes' ] && ( ifconfig $INTERFACE up & sleep 5 )[/c]
because I see no point in waiting when the conditional is false :-)
Cheers!
Offline
Hi llev,
If memory serves me well (3 months passed), "stop" in front of "start" here is for the next reason:
Imagine you are using TazPanel. Open Wireless configuration, and you see Wireless is stopped. Click "start" button.
Now imagine you need to switch to Wired connection. Open Wired configuration, and you see Wired is stopped. Click "start" button.
Anywhere I've read SliTaz supported only one (of Wireless / Wired) connection at a time. But if we not stopping connection before start we'll get both Wireless and Wired working at a time.
I haven't free time yet, but seems I can change logic a bit: in front of "start" — down all interfaces but interface listed in configuration file; then start it if it not started yet.
Offline
Hi llev,
Changes: http://hg.slitaz.org/slitaz-boot-scripts/rev/0c9119dea7b8
Released: http://cook.slitaz.org/cooker.cgi?pkg=slitaz-boot-scripts
Package: slitaz-boot-scripts-403
Please try it.
It works fine in my system allowing switch Eth<->Wi-Fi without stopping.
Offline
Hi Aleksej,
Sorry I've been off for some months. I'll try as soon as possible. Thanks for your work.
Offline
I upgraded the package, and it works as expected.
Thanks!
Offline
Hi llev,
Nice to hear it.
Offline
Pages: 1
[ Generated in 0.018 seconds, 7 queries executed - Memory usage: 1.54 MiB (Peak: 1.77 MiB) ]