SliTaz Forum
You are not logged in.
Pages: 1
I am using Slitaz 4. Each time I boot the machine I have to to go to my wifi configuration and start my network conection manually. I cannot see an option to get it to start the network automatically on reboot. Is there a way to do this please.
Offline
http://doc.slitaz.org/en:guides:wifi-easy
Offline
Do you use a live-system or have you installed slitaz permanently on HD?
If you use a live-system, then every chanches are lost when you restart.
Offline
No it's installed on the HDD.
I realise that a live system will need resetting every time. It even asks for the wifi key every reboot.
Offline
I have read through the link that Kultex posted. My linux skill is basic so I'm struggling. I think that I have to add the line
/etc/init.d/network.sh start to my /etc/network.conf file.
Is that it? Does it have to be at the begining or in a particular place. Or am I totally wrong.
Thanks.
Offline
network.conf is a configuration file. It won't run network.sh.
How did you configure your Wi-Fi for the first time and what do you have to do now at boot to start it?
Offline
That's the wifi-part of my network.config:
#
# Wi-Fi settings for iwconfig.
#
# Wi-Fi interface. It can auto-search interface if value below is fail.
WIFI_INTERFACE="wlan0"
# WPA driver; default is "wext" (Wireless Extension).
WIFI_WPA_DRIVER="wext"
# Set the operating mode of the device. The mode can be "Ad-Hoc", "Managed",
# "Master", "Repeater", "Secondary", "Monitor" or "Auto".
WIFI_MODE="managed"
# Set the operating channel in the device. Empty by default.
WIFI_CHANNEL=""
# Force the card to register to the Access Point given by the address, if it's
# possible. Empty by default to automatic mode.
WIFI_AP=""
#
# Wi-Fi settings for wpa_supplicant (for given network).
#
# SSID (network name)
WIFI_ESSID="my SSID"
# BSSID (optional), use this block to associate with the AP
WIFI_BSSID=""
# Wi-Fi security. Empty ("") for open network; "ANY" for trying many methods;
# "WEP" for WEP; "WPA" for WPA/WPA2-PSK; "EAP" for 802.1x EAP.
WIFI_KEY_TYPE="WPA"
# Password for WEP, WPA, EAP, WAPI, and ANY; both in ASCII or HEX form.
WIFI_KEY="my key"
# Method for EAP: "PEAP", "TLS", "TTLS", "PWD".
WIFI_EAP_METHOD=""
# File path to CA certificate file (PEM/DER).
WIFI_CA_CERT=""
# File path to client certificate file (PEM/DER).
WIFI_CLIENT_CERT=""
# Identity string for EAP.
WIFI_IDENTITY=""
# Anonymous identity string for EAP.
WIFI_ANONYMOUS_IDENTITY=""
# Inner authentication parameters: "", "PAP", "MSCHAP", "MSCHAPV2", "GTC".
WIFI_PHASE2=""
Offline
Slitaz network.sh can only configure/enable one interface.
Using wired INTERFACE then WIFI="no"
Using wireless WIFI_INTERFACE then WIFI="yes"
Since WIFI="yes" in /etc/network.conf is required to enable wifi adapter( WIFI_INTERFACE).
Preconfigured wifi enabled on boot requires WIFI="yes"
Applies to slitaz 2,3,4,5
Offline
mojo > Slitaz network.sh can only configure/enable one interface.
is that a bug or a feature?
Offline
The one adapter configuration is a feature. Different network configurations can be loaded on network.sh restart to quickly switch between installed adapters or connect to access points with different login credentials.
http://doc.slitaz.org/en:guides:network-script
The internet sharing tutorial shows how to add a second ethernet adapter.
http://forum.slitaz.org/topic/internet-connection-sharing/page/2#post-1335
Offline
This issue is with my Panasonic Toughbook CF-28 (P3 800mhz 248 Mb ram). It was installed via network boot floppy as there is no cd drive on this. The ethernet connection I did nothing. It just connected from the boot floppy. The wifi is via a MSI PCMCIA WiFi adaptor which uses an rtl chipset. I dont recall exactly what I did to connect via wifi but it was nothing special other than configuring the wifi key and encryption type. I alway connect via wifi. To start it I have to go to applications/system tools/wifi configeration. Root password then highlight my wifi connection and click start. It then connects although sometimes it asks again for the wifi key which I know by heart so its not a big problem just a bit annoying. Today it connected on boot without any input from me but this is a first.
Here is my network conf
# /etc/network.conf: SliTaz system wide networking configuration.
# Config file used by: /etc/init.d/network.sh
#
# Set default interface.
INTERFACE="eth0"
# Dynamic IP address.
# Enable/disable DHCP client at boot time.
DHCP="yes"
# Static IP address.
# Enable/disable static IP at boot time.
STATIC="no"
# Set IP address and netmask for a static IP.
IP="192.168.0.6"
NETMASK="255.255.255.0"
# Set route gateway for a static IP.
GATEWAY="192.168.0.1"
# Set DNS server for a static IP.
DNS_SERVER="192.168.0.1"
# Wifi connection.
# Enable/disable wireless connection at boot time.
WIFI="yes"
# Wifi interface (iwconfig) and ESSID.
WIFI_INTERFACE="wlan0"
WIFI_ESSID="NETGEAR"
WIFI_MODE="managed"
WIFI_KEY="xxxxxxxxx"
WIFI_KEY_TYPE="WPA"
WPA_DRIVER=""
WIFI_CHANNEL=""
WIFI_IWCONFIG_ARGS=""
I have edited my network key with xxxx in this post but it is shown in full and correctly in the conf file.
Do I have to change the default connection to wifi rather than eth0.
Thanks
Offline
@terrybull
Your network.conf is correct.
INTERFACE="eth0" is correct.
Check if you have no internet connection on boot:
Error messages in dmesg or /var/log/messages concerning wlan0 interface or wpa_supplicant not associating with NETGEAR access point.
Offline
I have just booted it now and again had to start the wifi and put in my nework key.
This is a copy of the boot log. Seems to be relivent although I dont understand it?
Processing /etc/init.d/rcS...
Mounting proc filesystem...[70G[ [1;32mOK[0;39m ]
Checking filesystem on : /dev/hda1
/dev/hda1: clean, 22489/1802240 files, 657265/7198720 blocks
Remounting rootfs read/write...
Starting udev daemon...
Udevadm requesting events from the Kernel...
Udevadm waiting for the event queue to finish...
Using Udev for hotplugging...
Mounting filesystems in fstab...
Searching for early boot options...[70G[ [1;32mOK[0;39m ]
Cleaning up the system...[70G[ [1;32mOK[0;39m ]
Setting up tmp X11 and ICE unix dir...[70G[ [1;32mOK[0;39m ]
Mounting /proc/bus/usb filesystem...[70G[ [1;32mOK[0;39m ]
Starting system log deamon: syslogd...[70G[ [1;32mOK[0;39m ]
Starting kernel log daemon: klogd...[70G[ [1;32mOK[0;39m ]
Requesting events from the Kernel...[70G[ [1;32mOK[0;39m ]
Executing all initialization scripts...
Parsing kernel cmdline for SliTaz live options...
Swap memory detected on: /dev/hda5
Activating swap memory...
Setting hostname...[70G[ [1;32mOK[0;39m ]
Configuring loopback...[70G[ [1;32mOK[0;39m ]
wlan0 is not a wifi interface, changing it.
Configuring ...lo no wireless extensions.
eth0 no wireless extensions.
dummy0 no wireless extensions.
iwconfig: unknown command "on"
[70G[ [1;32mOK[0;39m ]
Starting wpa_supplicant for WPA-PSK...
wpa_supplicant: option requires an argument -- 'i'
wpa_supplicant v0.7.3
Copyright (c) 2003-2010, Jouni Malinen <j@w1.fi> and contributors
This program is free software. You can distribute it and/or modify it
under the terms of the GNU General Public License version 2.
Alternatively, this software may be distributed under the terms of the
BSD license. See README and COPYING for more details.
This product includes software developed by the OpenSSL Project
for use in the OpenSSL Toolkit (http://www.openssl.org/)
usage:
wpa_supplicant [-BddhKLqqstuvW] [-P<pid file>] [-g<global ctrl>] \
-i<ifname> -c<config file> [-C<ctrl>] [-D<driver>] [-p<driver_param>] \
[-b<br_ifname>] [-f<debug file>] \
[-o<override driver>] [-O<override ctrl>] \
[-N -i<ifname> -c<conf> [-C<ctrl>] [-D<driver>] \
[-p<driver_param>] [-b<br_ifname>] ...]
drivers:
wext = Linux wireless extensions (generic)
hostap = Host AP driver (Intersil Prism2/2.5/3)
atmel = ATMEL AT76C5XXx (USB, PCMCIA)
wired = Wired Ethernet driver
options:
-b = optional bridge interface name
-B = run daemon in the background
-c = Configuration file
-C = ctrl_interface parameter (only used if -c is not)
-i = interface name
-d = increase debugging verbosity (-dd even more)
-D = driver name (can be multiple drivers: nl80211,wext)
-g = global ctrl_interface
-K = include keys (passwords, etc.) in debug output
-t = include timestamp in debug messages
-h = show this help text
-L = show license (GPL and BSD)
-o = override driver parameter for new interfaces
-O = override ctrl_interface parameter for new interfaces
-p = driver parameters
-P = PID file
-q = decrease debugging verbosity (-qq even less)
-v = show version
-W = wait for a control interface monitor before starting
-N = start describing new interface
example:
wpa_supplicant -Dwext -iwlan0 -c/etc/wpa_supplicant.conf
Starting udhcpc client on: ...
udhcpc: SIOCGIFINDEX: No such device
Restoring last alsa configuration...[70G[ [1;32mOK[0;39m ]
Starting TazPanel web server on port 82...[70G[ [1;32mOK[0;39m ]
Checking if /etc/locale.conf exists...
Locale configuration: en_GB[70G[ [1;32mOK[0;39m ]
Keymap configuration: uk
Loading /usr/share/kbd/keymaps/i386/qwerty/uk.map.gz
Starting local startup commands...
Starting all daemons specified in /etc/rcS.conf...
Starting message bus daemon: DBUS... [70G[ [1;32mOK[0;39m ]
Starting Hardware Abstraction Layer: HAL... [70G[ [1;32mOK[0;39m ]
Starting slim login manager: Slim... [70G[ [1;32mOK[0;39m ]
Setting up kernel security rules... [70G[ [1;32mOK[0;39m ]
Iptables rules are disabled in: /etc/firewall.conf...
Starting httpd deamon: httpd... [70G[ [1;32mOK[0;39m ]
[3g H H H H H H H H H
c]R
[1mWelcome to your box.[0m
SliTaz boot time: 16s
Offline
@terrybull
The boot.log indicates there is no wifi interface available when network.sh attempts to start wpa_supplicant. The cardbus could be a bottleneck that slows down the initialization of the network interface. Check for cardbus or network interface errors in /var/log/messages and dmesg.
Offline
Appologese for the long post but this doesn't mean a thing to me. Boot this morning and again I had to start the wifi manually and got asked nor the wifi key.
Copy of /var/log/messages
and this is dmesg
Thanks
Offline
as long as you dont change your network.conf it will stay like this
can you post the output of
dmesg | grep eth
and
iwconfig
Offline
Thanks Kultex. Here they are............
david@slitaz:~$ dmesg | grep eth
e100 0000:01:04.0: eth0: addr 0xe8112000, irq 9, MAC addr 00:d0:59:3d:f3:b3
david@slitaz:~$ iwconfig
lo no wireless extensions.
eth0 no wireless extensions.
dummy0 no wireless extensions.
wlan0 IEEE 802.11bg ESSID:"NETGEAR"
Mode:Managed Frequency:2.437 GHz Access Point: 00:1F:33:03:57:34
Bit Rate=54 Mb/s Tx-Power=20 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Power Management:on
Link Quality=64/70 Signal level=-46 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:30 Invalid misc:4 Missed beacon:0
Offline
if you set
# Set default interface.
INTERFACE="eth0"
then your SliTaz tries to start your lan interface at boot - wlan0 is only on standby
so you have to change
# Set default interface.
INTERFACE="wlan0"
to connect your wifi at boot
Offline
That has done the trick. Easy when you know how. Thank you Kultex. Now connects to wifi on boot.
Offline
Pages: 1
[ Generated in 0.020 seconds, 7 queries executed - Memory usage: 1.58 MiB (Peak: 1.77 MiB) ]