LinuxQuestions.org
Visit the LQ Articles and Editorials section
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Networking > Linux - Wireless Networking
User Name
Password
Linux - Wireless Networking This forum is for the discussion of wireless networking in Linux.

Notices

Reply
 
Search this Thread
Old 11-12-2005, 10:31 PM   #1
bbcar
LQ Newbie
 
Registered: Sep 2003
Location: New Mexico
Distribution: SUSE 8.0
Posts: 6

Rep: Reputation: 0
wireless connection requires network restart


In order to establish a wireless connection I have to restart the wireless interfaces after booting (by ifdown eth1, ifup eth1 or /etc/rc.d/network restart). The problem appears to be related to dhcpcd and while this isn't too much of burden, it presents problems when someone without root privilege boots the machine. What changes can I make to allow the boot process to successfully establish the wireless connection? My system and diagnostic messages are as follows:

Computer: HP dv4000, dual boot, with fresh install of SUSE 10.0.
Network card: Intel Corporation PRO/Wireless 2200BG (rev 05)
Modem: Actiontec GT701-WG
(See end of message for changes necessary to get a wireless connection).

After booting, the network is visible:
===========================================
iwconfig eth1
eth1 IEEE 802.11g ESSID:"ACTIONTEC"
Mode:Managed Frequency:2.452 GHz Access Point: 00:15:05:0D:C0:95
Bit Rate=54 Mb/s Tx-Power=20 dBm
Retry limit:7 RTS thrff Fragment thrff
Encryption keyff
Power Managementff
Link Quality=57/100 Signal level=-37 dBm Noise level=-78 dBm
Rx invalid nwid:0 Rx invalid crypt:17 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:31
===========================================
but there is no connection:
===========================================
ifstatus eth1
eth1 device: Intel Corporation PRO/Wireless 2200BG (rev 05)
eth1 configuration: wlan-id-00:15:00:24:19:75
eth1 dhcpcd is still waiting for data
eth1 is up
3: eth1: <BROADCAST,MULTICAST,NOTRAILERS,UP> mtu 1500 qdisc pfifo_fast qlen 1000
link/ether 00:15:00:24:19:75 brd ff:ff:ff:ff:ff:ff
inet6 fe80::215:ff:fe24:1975/64 scope link
valid_lft forever preferred_lft forever
Configured routes for interface eth1:
default 192.168.0.1 - eth1
0 of 1 configured routes for interface eth1 up
bssid=00:15:05:0d:c0:95
ssid=ACTIONTEC
pairwise_cipher=WEP-40
group_cipher=WEP-40
key_mgmt=NONE
wpa_state=COMPLETED
Supplicant PAE state=UNKNOWN
suppPortStatus=Authorized
EAP state=FAILURE

ifstatus-dhcp eth1
eth1 dhcpcd is still waiting for data
===========================================

The problem appears to be due to the dhcpcd daemon:
===========================================
\var\log\boot.msg
Setting up network interfaces:
lo
lo IP address: 127.0.0.1/8
done eth0 device: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
eth0 configuration: eth-id-00:0a:e4:d9:c6:d8
eth0 (DHCP) . . .
. . no IP address yet... backgrounding.
waiting
eth1 device: Intel Corporation PRO/Wireless 2200BG (rev 05)
eth1 configuration: wlan-id-00:15:00:24:19:75
eth1 starting wpa_supplicant
<notice>checkproc: /sbin/dhcpcd 5014
eth1 (DHCP) . . <notice>checkproc: /opt/kde3/bin/kdm 5101
. . . no IP address yet... backgrounding.

eth1 Error while executing:
Command 'ip route replace to default via 192.168.0.1 dev eth1' returned:
RTNETLINK answers: Network is unreachable
Configuration line: default 192.168.0.1 - eth1
waiting
Waiting for mandatory devices: eth-id-00:0a:e4:d9:c6:d8 wlan-id-00:15:00:24:19:75
7 6 5 3 2 1 0
eth0 interface could not be set up
failed eth1 interface could not be set up

\var\log\messages
Nov 12 16:25:11 linbox dhcpcd[5075]: broadcasting DHCP_REQUEST for 192.168.0.4
Nov 12 16:25:20 linbox kernel: eth1: no IPv6 routers present
Nov 12 16:25:41 linbox ifup-route: Error while executing:
Nov 12 16:25:41 linbox ifup-route: Command 'ip route replace to default via 192.168.0.1 dev eth1' returned:
Nov 12 16:25:41 linbox ifup-route: RTNETLINK answers: Network is unreachable
Nov 12 16:25:41 linbox ifup-route: Configuration line: default 192.168.0.1 - eth1
Nov 12 16:25:41 linbox mDNSResponder (Engineering Build) (Sep 9 2005 15:59:08) [5522]: starting
Nov 12 16:26:11 linbox dhcpcd[5075]: timed out waiting for DHCP_ACK response
Nov 12 16:26:11 linbox dhcpcd[5075]: broadcasting DHCP_DISCOVER
===========================================

A network connection can be established after booting by either
/etc/rc.d/network restart
or
ifdown eth1
ifup eth1

Does anyone have a suggestion for making the boot process succeed?
Thanks.
Bill
===========================================
Actions I've tried without success:
I've tried the following with no success:
1. change eth0 start mode to 'manual' or 'cable connect'
2. modify the ifcfg-wlan0 file for DHCLIENT_MODIFY_RESOLV_CONF, DHCLIENT_SET_DEFAULT_ROUTE,DHCLIENT_PRIMARY_DEVICE
3. modify the dhcp file for DHCLIENT_REBOOT_TIMEOUT, DHCLIENT_SLEEP, DHCLIENT_WAIT_AT_BOOT

===========================================
Changes necessary to make a connection following installation of SUSE 10.0
1). Change /etc/sysconfig/network/ifcfg-eth-id-(actual MAC address) and /etc/sysconfig/network/ifcfg-wlan-id-(actual MAC address)
USERCONTROL='yes'
2). Provide the gateway either to /etc/sysconfig/network/routes or /etc/sysconfig/network/ifroute-wlan-id-(actual MAC address) by creating the file and adding the line
default 192.168.0.1 - eth1
3). Provide a domain name server (get this from your isp). Edit /etc/resolv.conf and add the IP address(es) as
nameserver 1111.1111.1111.1111 (substituting the values from your isp).
4). My isp uses a DHCP and this caused some problems. The default setup is to allow the DHCP to modify the /etc/resolv.conf with values obtained from the isp. The problem I experienced was that the DHCP placed the modem IP address first on the DNS list (192.168.0.1). This allowed some addresses to be resolved in the browser google but almost nothing else. To prevent this modify /etc/sysconfig/network/dhcp so that
DHCLIENT_MODIFY_RESOLV_CONF="no".

With these changes, I can use the wireless network but only by restarting the network after the system boots up. (After boot enter
ifdown eth1
ifup eth1
or /etc/rc.d/network restart
These reset the dhcpcd and establish a connection.
 
Old 11-21-2005, 02:02 AM   #2
bbcar
LQ Newbie
 
Registered: Sep 2003
Location: New Mexico
Distribution: SUSE 8.0
Posts: 6

Original Poster
Rep: Reputation: 0
I found a solution to this problem from Larry and Andreas. The problem is with supplicant.
Modify /etc/sysconfig/network/ifcfg-wlan-id... adding the line
PREFER_WPA_SUPPLICANT='no'

With this change, the network is up and running after a reboot.

--Bill
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Script to check connection (and restart network if down) mac_phil Linux - Networking 10 01-06-2010 05:19 AM
Restart network connection? GT_Onizuka Linux - Networking 6 09-09-2004 06:30 PM
Cron job to check/restart network connection? mac_phil Linux - Networking 6 09-01-2004 01:51 PM
How to restart network connection satimis Debian 2 01-12-2004 02:30 AM
acpid requires restart before hotkeys activated Smerk Linux - Software 0 11-09-2003 08:13 AM


All times are GMT -5. The time now is 03:36 AM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration