Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Wireless DHCP problem
35 views
Skip to first unread message
Robert Rappaport
Oct 31, 2011, 8:56:35 AM10/31/11
to
I am running Slackware 12.2 on my Dell Vostro 1500 laptop with a
Broadcom BCM 4311 802.11b/g WLAN and a Belkin N150 wireless router set
for automatic dns. I am unable to connect wireless to the network using
Slackware rc.inet1 or wicd-1.5.6- noarch-SBO with
python-2.5.2-i486-4/pygtk-2.12.1-i486-2.
I have a desktop also on this network that is wired to the router. Both
my desktop and laptop can be booted into WINXP or Slackware 12.2. WINXP
connects DHCP on both machines as well as Slackware 12.2 on the desktop.
I can get the laptop Slackware connected wireless if I set the router
and laptop with an assigned ip address,gateway, and dns. I am moving my
office and must get my laptop working wireless DHCP.
When I try to connect with rc.inet1 it times out waiting for valid DHCP
server response. When I change my setup and make rc.wicd executable and
modify rc.inet1.conf with no entries I get no response from clicking xfce
Wicd Network Manager and I get an error message when I run wicd-client on
an xfce terminal.
Here are copies of all my associated files. Can anyone help? Thanks for
any response.
Bob
Setup and results for Slackware DHCP Wireless Network Setup
***********************************************************
***********************************************************
** Results of running iwlist scan **
lo Interface doesn't support scanning.
eth1 Scan completed :
Cell 01 - Address: 08:86:3B:14:38:38
ESSID:"belkin.838"
Mode:Managed
Frequency:2.442 GHz (Channel 7)
Quality:5/5 Signal level:-29 dBm Noise level:-92 dBm
IE: Unknown:
DDA50050F204104A0001101044000102103B00010310470010775B6680BFDE11D38D2F088
\63B1438381021001442656C6B696E20496E7465726E6174696F6E616C102300144E31353
\020576972656C65737320526F757465721024000746394B313030311042000E323031313
\13547313130343832381054000800060050F20400011011001B42656C6B696E204E31353
\020576972656C65737320526F75746572100800020086
IE: WPA Version 1
Group Cipher : CCMP
Pairwise Ciphers (1) : CCMP
Authentication Suites (1) : PSK
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
** Results of running rc.inet1 - boot and restart **
Polling for DHCP Server
Broadcast DHCP_DISCOVER
timed out waiting for valid DHCP server response
**** Results of running dhclient command ***
Internet Systems Consortium DHCP Client V3.0.6 Copyright 2004-2007
Internet Systems Consortium. All rights reserved. For info, please visit
http://www.isc.org/sw/dhcp/
Listening on LPF/eth1/00:1e:4c:8d:b2:83 Sending on
LPF/eth1/00:1e:4c:8d:b2:83 Sending on Socket/fallback DHCPREQUEST on
eth1 to 255.255.255.255 port 67 DHCPREQUEST on eth1 to 255.255.255.255
port 67 DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 8 DHCPDISCOVER on
eth1 to 255.255.255.255 port 67 interval 12 DHCPDISCOVER on eth1 to
255.255.255.255 port 67 interval 13 DHCPDISCOVER on eth1 to
255.255.255.255 port 67 interval 7 DHCPDISCOVER on eth1 to 255.255.255.255
port 67 interval 12 DHCPDISCOVER on eth1 to 255.255.255.255 port 67
interval 2 No DHCPOFFERS received.
Trying recorded lease 192.168.2.3
PING 192.168.2.1 (192.168.2.1) 56(84) bytes of data.
--- 192.168.2.1 ping statistics ---
1 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms
No working leases in persistent database - sleeping.
** Result for running ifconfig command **
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:0 errors:0
dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0
overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0
B) TX bytes:0 (0.0 B)
** Results of running iwconfig command **
lo no wireless extensions.
eth1 IEEE 802.11bg ESSID:"" Nickname:""
Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated
Bit Rate:54 Mb/s Tx-Power:24 dBm
Retry min limit:7 RTS thr:off Fragment thr:off Encryption
key:off
Power Managementmode:All packets received Link Quality=5/5
Signal level=0 dBm Noise level=0 dBm Rx invalid nwid:0 Rx
invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0
Invalid misc:0 Missed beacon:0
** dhclient.conf file **
# dhclient.conf
#
# Configuration file for ISC dhclient (see 'man dhclient.conf') #
** dhcpd.conf file **
# dhcpd.conf
#
# Configuration file for ISC dhcpd (see 'man dhcpd.conf') #
** /etc/rc.d/rc.inet1.conf **
#
# This file contains the configuration settings for network interfaces. #
If USE_DHCP[interface] is set to "yes", this overrides any other settings.
# If you don't have an interface, leave the settings null ("").
# You can configure network interfaces other than eth0,eth1... by setting
# IFNAME[interface] to the interface's name. If IFNAME[interface] is unset
# or empty, it is assumed you're configuring eth<interface>.
# Several other parameters are available, the end of this file contains a
# comprehensive set of examples.
#
=============================================================================
# Config information for eth0:
IPADDR[0]=""
NETMASK[0]=""
USE_DHCP[0]=""
DHCP_HOSTNAME[0]=""
# Config information for eth1:
IFNAME[1]="eth1"
IPADDR[1]=""
NETMASK[1]=""
USE_DHCP[1]="yes"
DHCP_HOSTNAME[1]=""
# Config information for eth2:
IPADDR[2]=""
NETMASK[2]=""
USE_DHCP[2]=""
DHCP_HOSTNAME[2]=""
# Config information for eth3:
IPADDR[3]=""
NETMASK[3]=""
USE_DHCP[3]=""
DHCP_HOSTNAME[3]=""
# Default gateway IP address:
#GATEWAY="192.168.2.1"
# Change this to "yes" for debugging output to stdout. Unfortunately, #
/sbin/hotplug seems to disable stdout so you'll only see debugging output
# when rc.inet1 is called directly.
DEBUG_ETH_UP="yes"
## Example config information for wlan0. Uncomment the lines you need and
fill ## in your info. (You may not need all of these for your wireless
network) #IFNAME[1]=""
#IPADDR[1]=""
#NETMASK[1]=""
#USE_DHCP[1]=""
DHCP_HOSTNAME[1]="vostro"
#DHCP_KEEPRESOLV[4]="yes"
#DHCP_KEEPNTP[4]="yes"
#DHCP_KEEPGW[4]="yes"
#DHCP_IPADDR[4]=""
WLAN_ESSID[1]=my_essid
WLAN_MODE[1]=Managed
WLAN_RATE[1]="54M auto"
WLAN_CHANNEL[1]="auto"
WLAN_KEY[1]="s:my_key"
##WLAN_IWPRIV[4]="set AuthMode=WPAPSK | set EncrypType=TKIP | set
WPAPSK=96389dc66eaf7e6efd5b5523ae43c7925ff4df2f8b7099495192d44a774fda16"
WLAN_WPA[1]="wpa_supplicant"
WLAN_WPADRIVER[1]="wext"
## Some examples of additional network parameters that you can use. ##
Config information for wlan0:
#IFNAME[4]="wlan0" # Use a different interface name nstead of
# the default 'eth4'
#HWADDR[4]="00:01:23:45:67:89" # Overrule the card's hardware MAC address
#MTU[4]="" # The default MTU is 1500, but you might
need
# 1360 when you use NAT'ed IPSec traffic.
#DHCP_KEEPRESOLV[4]="yes" # If you dont want /etc/resolv.conf
overwritten #DHCP_KEEPNTP[4]="yes" # If you don't want ntp.conf
overwritten #DHCP_KEEPGW[4]="yes" # If you don't want the DHCP
server to change
# your default gateway
#DHCP_IPADDR[1]="192.168.2.3" # Request a specific IP address
from the DHCP
# server
#WLAN_ESSID[4]=DARKSTAR # Here, you can override _any_ parameter
# defined in rc.wireless.conf, by
prepending # 'WLAN_' to the parameter's
name. Useful for # those with multiple
wireless interfaces.
#WLAN_IWPRIV[4]="set AuthMode=WPAPSK | set EncrypType=TKIP | set
WPAPSK=thekey"
# Some drivers require a private ioctl to
be # set through the iwpriv command. If
more than # one is required, you can place
them in the # IWPRIV parameter (separated
with the pipe (|) # character, see the
example).
** wpa_supplicant.conf file **
# See /usr/doc/wpa_supplicant-0.5.10/wpa_supplicant.conf.sample # for many
more options that you can use in this file.
# This line enables the use of wpa_cli which is used by rc.wireless # if
possible (to check for successful association)
ctrl_interface=/var/run/wpa_supplicant # By default, only root (group 0)
may use wpa_cli ctrl_interface_group=0 eapol_version=1
ap_scan=1
fast_reauth=1
network={
scan_ssid=0
proto=WPA WPA2
key_mgmt=WPA-PSK
pairwise=CCMP TKIP
group=CCMP TKIP
ssid="my_network"
#psk="my_psk"
psk=<actual wpa_passphrase result>
}
# WPA protected network, supply your own ESSID and WPAPSK here: #network={
# scan_ssid=0
# ssid="your_essid_here"
# proto=WPA
# key_mgmt=WPA-PSK
# pairwise=CCMP TKIP
# group=CCMP TKIP WEP104 WEP40
# psk=your_psk_here
#}
# Plaintext connection (no WPA, no IEEE 802.1X), # nice for hotel/airport
types of WiFi network. #network={
# key_mgmt=NONE
# priority=0
#}
Results for WICD Setup with rc.wicd executable
**********************************************
**********************************************
** Results from running wicd-client **
** error message **
Traceback (most recent call last):
File "/usr/lib/wicd/wicd-client.py", line 50, in <module>
import wicd.gui as gui
File "/usr/lib/python2.5/site-packages/wicd/gui.py", line 2006, in
<module>
setup_dbus()
File "/usr/lib/python2.5/site-packages/wicd/gui.py", line 174, in
setup_dbus
proxy_obj = bus.get_object("org.wicd.daemon", '/org/wicd/daemon')
File "/usr/lib/python2.5/site-packages/dbus/bus.py", line 244, in
get_object
follow_name_owner_changes=follow_name_owner_changes)
File "/usr/lib/python2.5/site-packages/dbus/proxies.py", line 241, in
__init__
self._named_service = conn.activate_name_owner(bus_name)
File "/usr/lib/python2.5/site-packages/dbus/bus.py", line 183, in
activate_name_owner
self.start_service_by_name(bus_name)
File "/usr/lib/python2.5/site-packages/dbus/bus.py", line 281, in
start_service_by_name
'su', (bus_name, flags)))
File "/usr/lib/python2.5/site-packages/dbus/connection.py", line 622, in
call_blocking
message, timeout)
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.ServiceUnknown:
The name org.wicd.daemon was not provided by any .service files
** Results from running iwlist-scan after rc.wicd executed **
lo Interface doesn't support scanning.
eth1 Scan completed :
Cell 01 - Address: 08:86:3B:14:38:38
ESSID:"belkin.838"
Mode:Managed
Frequency:2.442 GHz (Channel 7)
Quality:5/5 Signal level:-23 dBm Noise level:-92 dBm
IE: Unknown:
DDA50050F204104A0001101044000102103B00010310470010775B6680BFDE11D38D2F088
\63B1438381021001442656C6B696E20496E7465726E6174696F6E616C102300144E31353
\020576972656C65737320526F757465721024000746394B313030311042000E323031313
\13547313130343832381054000800060050F20400011011001B42656C6B696E204E3135
\020576972656C65737320526F75746572100800020086
IE: WPA Version 1
Group Cipher : CCMP
Pairwise Ciphers (1) : CCMP
Authentication Suites (1) : PSK
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
** Results from running iwconfig with rc.wicd executed **
lo no wireless extensions.
eth1 IEEE 802.11bg ESSID:"" Nickname:""
Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated
Bit Rate:54 Mb/s Tx-Power:24 dBm
Retry min limit:7 RTS thr:off Fragment thr:off Encryption
key:off
Power Managementmode:All packets received Link Quality=5/5
Signal level=0 dBm Noise level=0 dBm Rx invalid nwid:0 Rx
invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0
Invalid misc:0 Missed beacon:0
** Results from running ifconfig with rc.wicd executed **
eth1 Link encap:Ethernet HWaddr 00:1e:4c:8d:b2:83
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0
errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0
dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX
bytes:0 (0.0 B) TX bytes:0 (0.0 B) Interrupt:17 Base
address:0xc000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:0 errors:0
dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0
overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0
B) TX bytes:0 (0.0 B)
** /etc/rc.inet1.conf before executing rc.wicd **
# /etc/rc.d/rc.inet1.conf
#
# This file contains the configuration settings for network interfaces. #
If USE_DHCP[interface] is set to "yes", this overrides any other settings.
# If you don't have an interface, leave the settings null ("").
# You can configure network interfaces other than eth0,eth1... by setting
# IFNAME[interface] to the interface's name. If IFNAME[interface] is unset
# or empty, it is assumed you're configuring eth<interface>.
# Several other parameters are available, the end of this file contains a
# comprehensive set of examples.
#
=============================================================================
# Config information for eth0:
IPADDR[0]=""
NETMASK[0]=""
USE_DHCP[0]=""
DHCP_HOSTNAME[0]=""
# Config information for eth1:
IFNAME[1]=""
IPADDR[1]=""
NETMASK[1]=""
USE_DHCP[1]=""
DHCP_HOSTNAME[1]=""
# Config information for eth2:
IPADDR[2]=""
NETMASK[2]=""
USE_DHCP[2]=""
DHCP_HOSTNAME[2]=""
# Config information for eth3:
IPADDR[3]=""
NETMASK[3]=""
USE_DHCP[3]=""
DHCP_HOSTNAME[3]=""
# Default gateway IP address:
#GATEWAY="192.168.2.1"
# Change this to "yes" for debugging output to stdout. Unfortunately, #
/sbin/hotplug seems to disable stdout so you'll only see debugging output
# when rc.inet1 is called directly.
DEBUG_ETH_UP="yes"
## Example config information for wlan0. Uncomment the lines you need and
fill ## in your info. (You may not need all of these for your wireless
network) #IFNAME[1]=""
#IPADDR[1]=""
#NETMASK[1]=""
#USE_DHCP[1]=""
#DHCP_HOSTNAME[1]="vostro"
#DHCP_KEEPRESOLV[4]="yes"
#DHCP_KEEPNTP[4]="yes"
#DHCP_KEEPGW[4]="yes"
#DHCP_IPADDR[4]=""
#WLAN_ESSID[1]=belkin.838
#WLAN_MODE[1]=Managed
#WLAN_RATE[1]="54M auto"
#WLAN_CHANNEL[1]="auto"
#WLAN_KEY[1]="s:8e4a6862"
##WLAN_IWPRIV[4]="set AuthMode=WPAPSK | set EncrypType=TKIP | set
WPAPSK=96389dc66eaf7e6efd5b5523ae43c7925ff4df2f8b7099495192d44a774fda16"
#WLAN_WPA[1]="wpa_supplicant"
#WLAN_WPADRIVER[1]="wext"
## Some examples of additional network parameters that you can use. ##
Config information for wlan0:
#IFNAME[4]="wlan0" # Use a different interface name nstead of
# the default 'eth4'
#HWADDR[4]="00:01:23:45:67:89" # Overrule the card's hardware MAC address
#MTU[4]="" # The default MTU is 1500, but you might
need
# 1360 when you use NAT'ed IPSec traffic.
#DHCP_KEEPRESOLV[4]="yes" # If you dont want /etc/resolv.conf
overwritten #DHCP_KEEPNTP[4]="yes" # If you don't want ntp.conf
overwritten #DHCP_KEEPGW[4]="yes" # If you don't want the DHCP
server to change
# your default gateway
#DHCP_IPADDR[1]="192.168.2.3" # Request a specific IP address
from the DHCP
# server
#WLAN_ESSID[4]=DARKSTAR # Here, you can override _any_ parameter
# defined in rc.wireless.conf, by
prepending # 'WLAN_' to the parameter's
name. Useful for # those with multiple
wireless interfaces.
#WLAN_IWPRIV[4]="set AuthMode=WPAPSK | set EncrypType=TKIP | set
WPAPSK=thekey"
# Some drivers require a private ioctl to
be # set through the iwpriv command. If
more than # one is required, you can place
them in the # IWPRIV parameter (separated
with the pipe (|) # character, see the
example).
** /etc/wicd/manager-sttings.conf file **
[Settings]
wireless_interface = eth1
link_detect_tool = 0
flush_tool = 0
signal_display_type = 0
dhcp_client = 1
window_height = 400
wired_connect_mode = 1
pref_width = 490
wired_interface = eth0
wpa_driver = wext
debug_mode = 1
pref_height = 590
global_dns_1 = None
global_dns_2 = None
global_dns_3 = None
use_global_dns = False
window_width = 605
always_show_wired_interface = False
auto_reconnect = True
** /etc/wicd/wireless-settings.conf file **
bssid = 08:86:3b:14:38:38
essid = belkin.838
mode = Managed
enctype = wpa-psk
encryption_method = WPA
key = 8e4a6862
automatic = True
use_static_dns = False
use_settings_globally = 0
Broadcom BCM 4311 802.11b/g WLAN and a Belkin N150 wireless router set
for automatic dns. I am unable to connect wireless to the network using
Slackware rc.inet1 or wicd-1.5.6- noarch-SBO with
python-2.5.2-i486-4/pygtk-2.12.1-i486-2.
I have a desktop also on this network that is wired to the router. Both
my desktop and laptop can be booted into WINXP or Slackware 12.2. WINXP
connects DHCP on both machines as well as Slackware 12.2 on the desktop.
I can get the laptop Slackware connected wireless if I set the router
and laptop with an assigned ip address,gateway, and dns. I am moving my
office and must get my laptop working wireless DHCP.
When I try to connect with rc.inet1 it times out waiting for valid DHCP
server response. When I change my setup and make rc.wicd executable and
modify rc.inet1.conf with no entries I get no response from clicking xfce
Wicd Network Manager and I get an error message when I run wicd-client on
an xfce terminal.
Here are copies of all my associated files. Can anyone help? Thanks for
any response.
Bob
Setup and results for Slackware DHCP Wireless Network Setup
***********************************************************
***********************************************************
** Results of running iwlist scan **
lo Interface doesn't support scanning.
eth1 Scan completed :
Cell 01 - Address: 08:86:3B:14:38:38
ESSID:"belkin.838"
Mode:Managed
Frequency:2.442 GHz (Channel 7)
Quality:5/5 Signal level:-29 dBm Noise level:-92 dBm
IE: Unknown:
DDA50050F204104A0001101044000102103B00010310470010775B6680BFDE11D38D2F088
\63B1438381021001442656C6B696E20496E7465726E6174696F6E616C102300144E31353
\020576972656C65737320526F757465721024000746394B313030311042000E323031313
\13547313130343832381054000800060050F20400011011001B42656C6B696E204E31353
\020576972656C65737320526F75746572100800020086
IE: WPA Version 1
Group Cipher : CCMP
Pairwise Ciphers (1) : CCMP
Authentication Suites (1) : PSK
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
** Results of running rc.inet1 - boot and restart **
Polling for DHCP Server
Broadcast DHCP_DISCOVER
timed out waiting for valid DHCP server response
**** Results of running dhclient command ***
Internet Systems Consortium DHCP Client V3.0.6 Copyright 2004-2007
Internet Systems Consortium. All rights reserved. For info, please visit
http://www.isc.org/sw/dhcp/
Listening on LPF/eth1/00:1e:4c:8d:b2:83 Sending on
LPF/eth1/00:1e:4c:8d:b2:83 Sending on Socket/fallback DHCPREQUEST on
eth1 to 255.255.255.255 port 67 DHCPREQUEST on eth1 to 255.255.255.255
port 67 DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 8 DHCPDISCOVER on
eth1 to 255.255.255.255 port 67 interval 12 DHCPDISCOVER on eth1 to
255.255.255.255 port 67 interval 13 DHCPDISCOVER on eth1 to
255.255.255.255 port 67 interval 7 DHCPDISCOVER on eth1 to 255.255.255.255
port 67 interval 12 DHCPDISCOVER on eth1 to 255.255.255.255 port 67
interval 2 No DHCPOFFERS received.
Trying recorded lease 192.168.2.3
PING 192.168.2.1 (192.168.2.1) 56(84) bytes of data.
--- 192.168.2.1 ping statistics ---
1 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms
No working leases in persistent database - sleeping.
** Result for running ifconfig command **
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:0 errors:0
dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0
overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0
B) TX bytes:0 (0.0 B)
** Results of running iwconfig command **
lo no wireless extensions.
eth1 IEEE 802.11bg ESSID:"" Nickname:""
Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated
Bit Rate:54 Mb/s Tx-Power:24 dBm
Retry min limit:7 RTS thr:off Fragment thr:off Encryption
key:off
Power Managementmode:All packets received Link Quality=5/5
Signal level=0 dBm Noise level=0 dBm Rx invalid nwid:0 Rx
invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0
Invalid misc:0 Missed beacon:0
** dhclient.conf file **
# dhclient.conf
#
# Configuration file for ISC dhclient (see 'man dhclient.conf') #
** dhcpd.conf file **
# dhcpd.conf
#
# Configuration file for ISC dhcpd (see 'man dhcpd.conf') #
** /etc/rc.d/rc.inet1.conf **
#
# This file contains the configuration settings for network interfaces. #
If USE_DHCP[interface] is set to "yes", this overrides any other settings.
# If you don't have an interface, leave the settings null ("").
# You can configure network interfaces other than eth0,eth1... by setting
# IFNAME[interface] to the interface's name. If IFNAME[interface] is unset
# or empty, it is assumed you're configuring eth<interface>.
# Several other parameters are available, the end of this file contains a
# comprehensive set of examples.
#
=============================================================================
# Config information for eth0:
IPADDR[0]=""
NETMASK[0]=""
USE_DHCP[0]=""
DHCP_HOSTNAME[0]=""
# Config information for eth1:
IFNAME[1]="eth1"
IPADDR[1]=""
NETMASK[1]=""
USE_DHCP[1]="yes"
DHCP_HOSTNAME[1]=""
# Config information for eth2:
IPADDR[2]=""
NETMASK[2]=""
USE_DHCP[2]=""
DHCP_HOSTNAME[2]=""
# Config information for eth3:
IPADDR[3]=""
NETMASK[3]=""
USE_DHCP[3]=""
DHCP_HOSTNAME[3]=""
# Default gateway IP address:
#GATEWAY="192.168.2.1"
# Change this to "yes" for debugging output to stdout. Unfortunately, #
/sbin/hotplug seems to disable stdout so you'll only see debugging output
# when rc.inet1 is called directly.
DEBUG_ETH_UP="yes"
## Example config information for wlan0. Uncomment the lines you need and
fill ## in your info. (You may not need all of these for your wireless
network) #IFNAME[1]=""
#IPADDR[1]=""
#NETMASK[1]=""
#USE_DHCP[1]=""
DHCP_HOSTNAME[1]="vostro"
#DHCP_KEEPRESOLV[4]="yes"
#DHCP_KEEPNTP[4]="yes"
#DHCP_KEEPGW[4]="yes"
#DHCP_IPADDR[4]=""
WLAN_ESSID[1]=my_essid
WLAN_MODE[1]=Managed
WLAN_RATE[1]="54M auto"
WLAN_CHANNEL[1]="auto"
WLAN_KEY[1]="s:my_key"
##WLAN_IWPRIV[4]="set AuthMode=WPAPSK | set EncrypType=TKIP | set
WPAPSK=96389dc66eaf7e6efd5b5523ae43c7925ff4df2f8b7099495192d44a774fda16"
WLAN_WPA[1]="wpa_supplicant"
WLAN_WPADRIVER[1]="wext"
## Some examples of additional network parameters that you can use. ##
Config information for wlan0:
#IFNAME[4]="wlan0" # Use a different interface name nstead of
# the default 'eth4'
#HWADDR[4]="00:01:23:45:67:89" # Overrule the card's hardware MAC address
#MTU[4]="" # The default MTU is 1500, but you might
need
# 1360 when you use NAT'ed IPSec traffic.
#DHCP_KEEPRESOLV[4]="yes" # If you dont want /etc/resolv.conf
overwritten #DHCP_KEEPNTP[4]="yes" # If you don't want ntp.conf
overwritten #DHCP_KEEPGW[4]="yes" # If you don't want the DHCP
server to change
# your default gateway
#DHCP_IPADDR[1]="192.168.2.3" # Request a specific IP address
from the DHCP
# server
#WLAN_ESSID[4]=DARKSTAR # Here, you can override _any_ parameter
# defined in rc.wireless.conf, by
prepending # 'WLAN_' to the parameter's
name. Useful for # those with multiple
wireless interfaces.
#WLAN_IWPRIV[4]="set AuthMode=WPAPSK | set EncrypType=TKIP | set
WPAPSK=thekey"
# Some drivers require a private ioctl to
be # set through the iwpriv command. If
more than # one is required, you can place
them in the # IWPRIV parameter (separated
with the pipe (|) # character, see the
example).
** wpa_supplicant.conf file **
# See /usr/doc/wpa_supplicant-0.5.10/wpa_supplicant.conf.sample # for many
more options that you can use in this file.
# This line enables the use of wpa_cli which is used by rc.wireless # if
possible (to check for successful association)
ctrl_interface=/var/run/wpa_supplicant # By default, only root (group 0)
may use wpa_cli ctrl_interface_group=0 eapol_version=1
ap_scan=1
fast_reauth=1
network={
scan_ssid=0
proto=WPA WPA2
key_mgmt=WPA-PSK
pairwise=CCMP TKIP
group=CCMP TKIP
ssid="my_network"
#psk="my_psk"
psk=<actual wpa_passphrase result>
}
# WPA protected network, supply your own ESSID and WPAPSK here: #network={
# scan_ssid=0
# ssid="your_essid_here"
# proto=WPA
# key_mgmt=WPA-PSK
# pairwise=CCMP TKIP
# group=CCMP TKIP WEP104 WEP40
# psk=your_psk_here
#}
# Plaintext connection (no WPA, no IEEE 802.1X), # nice for hotel/airport
types of WiFi network. #network={
# key_mgmt=NONE
# priority=0
#}
Results for WICD Setup with rc.wicd executable
**********************************************
**********************************************
** Results from running wicd-client **
** error message **
Traceback (most recent call last):
File "/usr/lib/wicd/wicd-client.py", line 50, in <module>
import wicd.gui as gui
File "/usr/lib/python2.5/site-packages/wicd/gui.py", line 2006, in
<module>
setup_dbus()
File "/usr/lib/python2.5/site-packages/wicd/gui.py", line 174, in
setup_dbus
proxy_obj = bus.get_object("org.wicd.daemon", '/org/wicd/daemon')
File "/usr/lib/python2.5/site-packages/dbus/bus.py", line 244, in
get_object
follow_name_owner_changes=follow_name_owner_changes)
File "/usr/lib/python2.5/site-packages/dbus/proxies.py", line 241, in
__init__
self._named_service = conn.activate_name_owner(bus_name)
File "/usr/lib/python2.5/site-packages/dbus/bus.py", line 183, in
activate_name_owner
self.start_service_by_name(bus_name)
File "/usr/lib/python2.5/site-packages/dbus/bus.py", line 281, in
start_service_by_name
'su', (bus_name, flags)))
File "/usr/lib/python2.5/site-packages/dbus/connection.py", line 622, in
call_blocking
message, timeout)
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.ServiceUnknown:
The name org.wicd.daemon was not provided by any .service files
** Results from running iwlist-scan after rc.wicd executed **
lo Interface doesn't support scanning.
eth1 Scan completed :
Cell 01 - Address: 08:86:3B:14:38:38
ESSID:"belkin.838"
Mode:Managed
Frequency:2.442 GHz (Channel 7)
Quality:5/5 Signal level:-23 dBm Noise level:-92 dBm
IE: Unknown:
DDA50050F204104A0001101044000102103B00010310470010775B6680BFDE11D38D2F088
\63B1438381021001442656C6B696E20496E7465726E6174696F6E616C102300144E31353
\020576972656C65737320526F757465721024000746394B313030311042000E323031313
\13547313130343832381054000800060050F20400011011001B42656C6B696E204E3135
\020576972656C65737320526F75746572100800020086
IE: WPA Version 1
Group Cipher : CCMP
Pairwise Ciphers (1) : CCMP
Authentication Suites (1) : PSK
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
** Results from running iwconfig with rc.wicd executed **
lo no wireless extensions.
eth1 IEEE 802.11bg ESSID:"" Nickname:""
Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated
Bit Rate:54 Mb/s Tx-Power:24 dBm
Retry min limit:7 RTS thr:off Fragment thr:off Encryption
key:off
Power Managementmode:All packets received Link Quality=5/5
Signal level=0 dBm Noise level=0 dBm Rx invalid nwid:0 Rx
invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0
Invalid misc:0 Missed beacon:0
** Results from running ifconfig with rc.wicd executed **
eth1 Link encap:Ethernet HWaddr 00:1e:4c:8d:b2:83
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0
errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0
dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX
bytes:0 (0.0 B) TX bytes:0 (0.0 B) Interrupt:17 Base
address:0xc000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:0 errors:0
dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0
overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0
B) TX bytes:0 (0.0 B)
** /etc/rc.inet1.conf before executing rc.wicd **
# /etc/rc.d/rc.inet1.conf
#
# This file contains the configuration settings for network interfaces. #
If USE_DHCP[interface] is set to "yes", this overrides any other settings.
# If you don't have an interface, leave the settings null ("").
# You can configure network interfaces other than eth0,eth1... by setting
# IFNAME[interface] to the interface's name. If IFNAME[interface] is unset
# or empty, it is assumed you're configuring eth<interface>.
# Several other parameters are available, the end of this file contains a
# comprehensive set of examples.
#
=============================================================================
# Config information for eth0:
IPADDR[0]=""
NETMASK[0]=""
USE_DHCP[0]=""
DHCP_HOSTNAME[0]=""
# Config information for eth1:
IFNAME[1]=""
IPADDR[1]=""
NETMASK[1]=""
USE_DHCP[1]=""
DHCP_HOSTNAME[1]=""
# Config information for eth2:
IPADDR[2]=""
NETMASK[2]=""
USE_DHCP[2]=""
DHCP_HOSTNAME[2]=""
# Config information for eth3:
IPADDR[3]=""
NETMASK[3]=""
USE_DHCP[3]=""
DHCP_HOSTNAME[3]=""
# Default gateway IP address:
#GATEWAY="192.168.2.1"
# Change this to "yes" for debugging output to stdout. Unfortunately, #
/sbin/hotplug seems to disable stdout so you'll only see debugging output
# when rc.inet1 is called directly.
DEBUG_ETH_UP="yes"
## Example config information for wlan0. Uncomment the lines you need and
fill ## in your info. (You may not need all of these for your wireless
network) #IFNAME[1]=""
#IPADDR[1]=""
#NETMASK[1]=""
#USE_DHCP[1]=""
#DHCP_HOSTNAME[1]="vostro"
#DHCP_KEEPRESOLV[4]="yes"
#DHCP_KEEPNTP[4]="yes"
#DHCP_KEEPGW[4]="yes"
#DHCP_IPADDR[4]=""
#WLAN_ESSID[1]=belkin.838
#WLAN_MODE[1]=Managed
#WLAN_RATE[1]="54M auto"
#WLAN_CHANNEL[1]="auto"
#WLAN_KEY[1]="s:8e4a6862"
##WLAN_IWPRIV[4]="set AuthMode=WPAPSK | set EncrypType=TKIP | set
WPAPSK=96389dc66eaf7e6efd5b5523ae43c7925ff4df2f8b7099495192d44a774fda16"
#WLAN_WPA[1]="wpa_supplicant"
#WLAN_WPADRIVER[1]="wext"
## Some examples of additional network parameters that you can use. ##
Config information for wlan0:
#IFNAME[4]="wlan0" # Use a different interface name nstead of
# the default 'eth4'
#HWADDR[4]="00:01:23:45:67:89" # Overrule the card's hardware MAC address
#MTU[4]="" # The default MTU is 1500, but you might
need
# 1360 when you use NAT'ed IPSec traffic.
#DHCP_KEEPRESOLV[4]="yes" # If you dont want /etc/resolv.conf
overwritten #DHCP_KEEPNTP[4]="yes" # If you don't want ntp.conf
overwritten #DHCP_KEEPGW[4]="yes" # If you don't want the DHCP
server to change
# your default gateway
#DHCP_IPADDR[1]="192.168.2.3" # Request a specific IP address
from the DHCP
# server
#WLAN_ESSID[4]=DARKSTAR # Here, you can override _any_ parameter
# defined in rc.wireless.conf, by
prepending # 'WLAN_' to the parameter's
name. Useful for # those with multiple
wireless interfaces.
#WLAN_IWPRIV[4]="set AuthMode=WPAPSK | set EncrypType=TKIP | set
WPAPSK=thekey"
# Some drivers require a private ioctl to
be # set through the iwpriv command. If
more than # one is required, you can place
them in the # IWPRIV parameter (separated
with the pipe (|) # character, see the
example).
** /etc/wicd/manager-sttings.conf file **
[Settings]
wireless_interface = eth1
link_detect_tool = 0
flush_tool = 0
signal_display_type = 0
dhcp_client = 1
window_height = 400
wired_connect_mode = 1
pref_width = 490
wired_interface = eth0
wpa_driver = wext
debug_mode = 1
pref_height = 590
global_dns_1 = None
global_dns_2 = None
global_dns_3 = None
use_global_dns = False
window_width = 605
always_show_wired_interface = False
auto_reconnect = True
** /etc/wicd/wireless-settings.conf file **
bssid = 08:86:3b:14:38:38
essid = belkin.838
mode = Managed
enctype = wpa-psk
encryption_method = WPA
key = 8e4a6862
automatic = True
use_static_dns = False
use_settings_globally = 0
+Alan Hicks+
Oct 31, 2011, 10:54:34 AM10/31/11
to
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 2011-10-31, Robert Rappaport <pape...@cox.net> wrote:
> When I try to connect with rc.inet1 it times out waiting for valid DHCP
> server response. When I change my setup and make rc.wicd executable and
> modify rc.inet1.conf with no entries I get no response from clicking xfce
> Wicd Network Manager and I get an error message when I run wicd-client on
> an xfce terminal.
Let me make sure I've got this right. If anything I say here is wrong,
please tell me.
1- Setting USE_DHCP[x]="no", along with static information in the other
fields for your wireless NIC in rc.inet1.conf results in a positive
wireless connection.
2- Reversing that so USE_DHCP[x]="yes" for your wireless NIC results in
no connection.
Assuming the above is true, that's a _very_ odd situation. One thing
you may wish to test is removing the encryption from your network
temporarily. Then you could connect your NIC to the WAP with iwconfig
and run either dhcpcd or dhclient manually to obtain an IP address. If
that works then you may want to look at possible issues with
wpasupplicant.
You're using a broadcom wireless NIC and that's never a particularly
good thing with Linux. Support for those cards has traditionally been
either absent or dodgy. Things have improved quite a bit lately with
the b43 driver. There's another driver for a lot of those cards that
isn't currently in the mainline tree but may offer better support. LWN
had a couple of articles on it and its challenges in being adopted into
the kernel a couple months back. If you're interested in pursuing that
you may wish to checkout those articles for more information.
Assuming all the above is true, then the best advice I can give you is
to upgrade to Slackware 13.37. If what I've understood from your post
is true than you likely have some sort of driver issue or a conflict
between your driver and wpa_supplicant, or dhcpcd, or dhclient, or....
you get the idea.
Another possibility is to switch from dhcpcd to dhclient. I've seen
some routers and DHCP servers that favor one dhcp client over the other
and flatout refuse to operate with the "wrong" one. I don't think
there's an easy way to change from dhcpcd to dhclient in rc.inet1, but
if you're using wicd then you should be able to make that change in
wicd's preferences tab.
HTH
- --
It is better to hear the rebuke of the wise,
Than for a man to hear the song of fools.
Ecclesiastes 7:5
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
iEYEARECAAYFAk6utqoACgkQDyaEVbMHxsYxQwCgjsyij4+8x/hjqKo9N5BinvCY
yOYAn3IWo4+5a20UG3X7P5EX6K32oLav
=E6TE
-----END PGP SIGNATURE-----
Hash: SHA1
On 2011-10-31, Robert Rappaport <pape...@cox.net> wrote:
> When I try to connect with rc.inet1 it times out waiting for valid DHCP
> server response. When I change my setup and make rc.wicd executable and
> modify rc.inet1.conf with no entries I get no response from clicking xfce
> Wicd Network Manager and I get an error message when I run wicd-client on
> an xfce terminal.
please tell me.
1- Setting USE_DHCP[x]="no", along with static information in the other
fields for your wireless NIC in rc.inet1.conf results in a positive
wireless connection.
2- Reversing that so USE_DHCP[x]="yes" for your wireless NIC results in
no connection.
Assuming the above is true, that's a _very_ odd situation. One thing
you may wish to test is removing the encryption from your network
temporarily. Then you could connect your NIC to the WAP with iwconfig
and run either dhcpcd or dhclient manually to obtain an IP address. If
that works then you may want to look at possible issues with
wpasupplicant.
You're using a broadcom wireless NIC and that's never a particularly
good thing with Linux. Support for those cards has traditionally been
either absent or dodgy. Things have improved quite a bit lately with
the b43 driver. There's another driver for a lot of those cards that
isn't currently in the mainline tree but may offer better support. LWN
had a couple of articles on it and its challenges in being adopted into
the kernel a couple months back. If you're interested in pursuing that
you may wish to checkout those articles for more information.
Assuming all the above is true, then the best advice I can give you is
to upgrade to Slackware 13.37. If what I've understood from your post
is true than you likely have some sort of driver issue or a conflict
between your driver and wpa_supplicant, or dhcpcd, or dhclient, or....
you get the idea.
Another possibility is to switch from dhcpcd to dhclient. I've seen
some routers and DHCP servers that favor one dhcp client over the other
and flatout refuse to operate with the "wrong" one. I don't think
there's an easy way to change from dhcpcd to dhclient in rc.inet1, but
if you're using wicd then you should be able to make that change in
wicd's preferences tab.
HTH
- --
It is better to hear the rebuke of the wise,
Than for a man to hear the song of fools.
Ecclesiastes 7:5
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
iEYEARECAAYFAk6utqoACgkQDyaEVbMHxsYxQwCgjsyij4+8x/hjqKo9N5BinvCY
yOYAn3IWo4+5a20UG3X7P5EX6K32oLav
=E6TE
-----END PGP SIGNATURE-----
Douglas Mayne
Oct 31, 2011, 11:46:42 AM10/31/11
to
On Mon, 31 Oct 2011 07:56:35 -0500, Robert Rappaport wrote:
> I am running Slackware 12.2 on my Dell Vostro 1500 laptop with a
> Broadcom BCM 4311 802.11b/g WLAN and a Belkin N150 wireless router set
> for automatic dns. I am unable to connect wireless to the network using
> Slackware rc.inet1 or wicd-1.5.6- noarch-SBO with
> python-2.5.2-i486-4/pygtk-2.12.1-i486-2.
>
> I have a desktop also on this network that is wired to the router. Both
> my desktop and laptop can be booted into WINXP or Slackware 12.2. WINXP
> connects DHCP on both machines as well as Slackware 12.2 on the desktop.
> I can get the laptop Slackware connected wireless if I set the router
> and laptop with an assigned ip address,gateway, and dns. I am moving my
> office and must get my laptop working wireless DHCP.
>
Have you used this page to get cut the firmware:
> I am running Slackware 12.2 on my Dell Vostro 1500 laptop with a
> Broadcom BCM 4311 802.11b/g WLAN and a Belkin N150 wireless router set
> for automatic dns. I am unable to connect wireless to the network using
> Slackware rc.inet1 or wicd-1.5.6- noarch-SBO with
> python-2.5.2-i486-4/pygtk-2.12.1-i486-2.
>
> I have a desktop also on this network that is wired to the router. Both
> my desktop and laptop can be booted into WINXP or Slackware 12.2. WINXP
> connects DHCP on both machines as well as Slackware 12.2 on the desktop.
> I can get the laptop Slackware connected wireless if I set the router
> and laptop with an assigned ip address,gateway, and dns. I am moving my
> office and must get my laptop working wireless DHCP.
>
http://linuxwireless.org/en/users/Drivers/b43
If not, it is unusual that you can scan the network without the firmware
in place. I agree that you should consider upgrading to the latest and
greatest slackware version, including the latest kernel (2.6.38.x). YMMV
--
Douglas Mayne
Martin
Oct 31, 2011, 4:54:49 PM10/31/11
to
Robert Rappaport wrote:
> Thanks for
> any response.
>
> Bob
Just in case it is a configuration issue I can point you towards my wireless
> Thanks for
> any response.
>
> Bob
configuration that does what you want. However, it is built on 13.37 so it
might not help you.
http://www.frogge.de/pepper/p50ij/p50ij.html#wlan
Martin
Robert Rappaport
Nov 1, 2011, 6:34:47 PM11/1/11
to
On Mon, 31 Oct 2011 14:54:34 +0000, +Alan Hicks+ wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 2011-10-31, Robert Rappaport <pape...@cox.net> wrote:
>> When I try to connect with rc.inet1 it times out waiting for valid DHCP
>> server response. When I change my setup and make rc.wicd executable
>> and modify rc.inet1.conf with no entries I get no response from
>> clicking xfce Wicd Network Manager and I get an error message when I
>> run wicd-client on an xfce terminal.
>
> Let me make sure I've got this right. If anything I say here is wrong,
> please tell me.
>
> 1- Setting USE_DHCP[x]="no", along with static information in the other
> fields for your wireless NIC in rc.inet1.conf results in a positive
> wireless connection.
> 2- Reversing that so USE_DHCP[x]="yes" for your wireless NIC results in
> no connection.
>
I have no problem when I change my router to locally assigned ip
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 2011-10-31, Robert Rappaport <pape...@cox.net> wrote:
>> When I try to connect with rc.inet1 it times out waiting for valid DHCP
>> server response. When I change my setup and make rc.wicd executable
>> and modify rc.inet1.conf with no entries I get no response from
>> clicking xfce Wicd Network Manager and I get an error message when I
>> run wicd-client on an xfce terminal.
>
> Let me make sure I've got this right. If anything I say here is wrong,
> please tell me.
>
> 1- Setting USE_DHCP[x]="no", along with static information in the other
> fields for your wireless NIC in rc.inet1.conf results in a positive
> wireless connection.
> 2- Reversing that so USE_DHCP[x]="yes" for your wireless NIC results in
> no connection.
>
addresses, gateway, and my isp dns address. I setup rc.inet1.conf with
ip, gateway and /etc/resolv.conf with a dns ip. Works like a charm.
Where I am moving their router setup is dhcp and I am trying to get
ready. Somehow I feel the problem is a dns issue as my resolv.conf isp
dns is overwritten with with my gateway address.
> Assuming the above is true, that's a _very_ odd situation. One thing you
> may wish to test is removing the encryption from your network
> temporarily. Then you could connect your NIC to the WAP with iwconfig
> and run either dhcpcd or dhclient manually to obtain an IP address. If
> that works then you may want to look at possible issues with
> wpasupplicant.
>
> You're using a broadcom wireless NIC and that's never a particularly
> good thing with Linux. Support for those cards has traditionally been
> either absent or dodgy. Things have improved quite a bit lately with the
> b43 driver. There's another driver for a lot of those cards that isn't
> currently in the mainline tree but may offer better support. LWN had a
> couple of articles on it and its challenges in being adopted into the
> kernel a couple months back. If you're interested in pursuing that you
> may wish to checkout those articles for more information.
>
accurate router info.
> Assuming all the above is true, then the best advice I can give you is
> to upgrade to Slackware 13.37. If what I've understood from your post is
> true than you likely have some sort of driver issue or a conflict
> between your driver and wpa_supplicant, or dhcpcd, or dhclient, or....
> you get the idea.
>
> Another possibility is to switch from dhcpcd to dhclient. I've seen some
> routers and DHCP servers that favor one dhcp client over the other and
> flatout refuse to operate with the "wrong" one. I don't think there's an
> easy way to change from dhcpcd to dhclient in rc.inet1, but if you're
> using wicd then you should be able to make that change in wicd's
> preferences tab.
>
some type of "busy" error message. It did connect once this way but I
cant get it to repeat. Can you advise me how to set this up at boot time?
I dont think that I know enough to modify /etc/rc.d/rc.inet1 on my own.
Thanks for your interest.
Bob
Robert Rappaport
Nov 1, 2011, 6:41:39 PM11/1/11
to
On Mon, 31 Oct 2011 21:54:49 +0100, Martin wrote:
>
> Just in case it is a configuration issue I can point you towards my
> wireless configuration that does what you want. However, it is built on
> 13.37 so it might not help you.
>
> http://www.frogge.de/pepper/p50ij/p50ij.html#wlan
>
I will check this out tomorrow. Thanks!
>
> Just in case it is a configuration issue I can point you towards my
> wireless configuration that does what you want. However, it is built on
> 13.37 so it might not help you.
>
> http://www.frogge.de/pepper/p50ij/p50ij.html#wlan
>
Bob
> Martin
Henrik Carlqvist
Nov 2, 2011, 3:39:46 AM11/2/11
to
Robert Rappaport <pape...@cox.net> wrote:
> I have no problem when I change my router to locally assigned ip
> addresses, gateway, and my isp dns address.
If so, maybe static IP configuration is the way to go for you? Static
> I have no problem when I change my router to locally assigned ip
> addresses, gateway, and my isp dns address.
adresses does have some advantages, usually that is the preferred choice
for a server in the network.
DHCP has other advantages, it is comfortable to use DHCP on a laptop which
moves between different networks.
> I setup rc.inet1.conf with ip, gateway and /etc/resolv.conf with a dns
> ip. Works like a charm. Where I am moving their router setup is dhcp
> and I am trying to get ready.
static IP worked?
> Somehow I feel the problem is a dns issue as my resolv.conf isp dns is
> overwritten with with my gateway address.
settings include IP address, netmask, gateway and DNS servers. Also other
settings can be provided.
As the gateway has to tell the client what DNS servers to use your gateway
must be correctly configured to know about DNS servers. It is rather
common for gateways to have a builtin caching DNS server, but still it has
to know about some real servers.
If you for some reason are unable to configre the DNS settings in your
gateway you can instruct dhcpcd to not overwrite resolv.conf using the -C
switch, see "man dhcpcd" for more information and example on how to use
the -C switch.
regards Henrik
--
The address in the header is only to prevent spam. My real address is:
hc123(at)poolhem.se Examples of addresses which go to spammers:
root@localhost postmaster@localhost
+Alan Hicks+
Nov 2, 2011, 10:00:58 AM11/2/11
to
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hash: SHA1
On 2011-11-01, Robert Rappaport <pape...@cox.net> wrote:
> When my dhcpd fails I try to run dhclient from the command line and I get
> some type of "busy" error message. It did connect once this way but I
> cant get it to repeat. Can you advise me how to set this up at boot time?
> I dont think that I know enough to modify /etc/rc.d/rc.inet1 on my own.
This "busy" error message probably means that dhcpcd is still running
> When my dhcpd fails I try to run dhclient from the command line and I get
> some type of "busy" error message. It did connect once this way but I
> cant get it to repeat. Can you advise me how to set this up at boot time?
> I dont think that I know enough to modify /etc/rc.d/rc.inet1 on my own.
in the background. Kill it and then you should be able to run dhclient.
# kill -9 $(pgrep dhcpcd)
# dhclient wlan0
If the above two lines get you on the network than I think it's a safe
bet that your router just doesn't like the dhcpcd included in Slackware
12.2. The "best" solution might be to upgrade to 13.37 and enjoy all
the benefits of increased hardware support and newer applications, but
that's not a garaunteed fix either.
Another thing you could do is edit /etc/rc.d/rc.M. I don't recommend
that people do this as a general rule, but it is a dirty kludge that
could work in this situation. Simply find the spot where it calls
rc.inet1 to setup the network and add in the two lines above just below
that call. Doing this will let rc.inet1 setup the link layer portion of
the wireless NIC, then attempt to get a dhcp generated IP address. When
that fails it will then kill that dhcpcd client and immediately run
dhclient to obtain an address before continuing the boot process as
normal.
- --
It is better to hear the rebuke of the wise,
Than for a man to hear the song of fools.
Ecclesiastes 7:5
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
YCwAmwVMlUMRj2o1KbK1pNnzImjgdigo
=RUDc
-----END PGP SIGNATURE-----
Helmut Hullen
Nov 2, 2011, 12:28:00 PM11/2/11
to
Hallo, +Alan,
Du meintest am 02.11.11:
> This "busy" error message probably means that dhcpcd is still running
> in the background. Kill it and then you should be able to run
> dhclient.
> # kill -9 $(pgrep dhcpcd)
or
pkill -9 dhcpcd
or
killall -9 dhcpcd
I prefer the last version.
Viele Gruesse
Helmut
"Ubuntu" - an African word, meaning "Slackware is too hard for me".
Du meintest am 02.11.11:
> This "busy" error message probably means that dhcpcd is still running
> in the background. Kill it and then you should be able to run
> dhclient.
> # kill -9 $(pgrep dhcpcd)
pkill -9 dhcpcd
or
killall -9 dhcpcd
I prefer the last version.
Viele Gruesse
Helmut
"Ubuntu" - an African word, meaning "Slackware is too hard for me".
0 new messages