Arch Linux

virati

Member

Registered: 2008-04-14

Posts: 83

Wireless dhcpcd timeout

installed the rt2x00lib and associated libraries. I can see my wireless card and i can scan the available networks.

When i try to 'dhcpcd wlan0' it times out. I'm wondering: is the problem that I'm technically already running 'dhcpcd eth0' and i won't be able to do it for both.

Or, do i have to set up the router in a special way. My hostname is not the default right now so maybe that's a problem.
Another potential problem may be that every other computer on the network is a windows computer and maybe i need to get the router set up in a special way to make it work with linux (it works on my vista partition).

I'm not too knowledgeable about network happenings so pardon the ignorance.

synthead

Member

Registered: 2006-05-09

Posts: 1,337

Re: Wireless dhcpcd timeout

Have you associated your interface to your access point?  Run "iwconfig" and it should say either "Associated" or "Not Associated".

My favorite way to set up networking is with the Arch network scrips, called netcfg2 (although the package is called "netcfg").  Install it via "pacman -S netcfg".  It'll install a folder to your system, "/etc/networks.d".  Inside that folder is another folder called "examples".  You might want to look through the example scripts (less file) to get a general idea of what you're getting into. 

Decide on a script that resembles what you're trying to do, then copy it to your "/etc/network.d" folder with a name of your choice, i.e. "cp /etc/network.d/examples/ethernet.example /etc/network.d/mynetwork".  This command will create a script called "mynetwork" on your system, but it can be whatever you want.  And of course, edit it to your liking.  Change the interface to reflect yours, the ESSID, your WPA or WEP key, etc.

To use your configuration, run "netcfg2 mynetwork" from a terminal as root. 

If you want to have this network active when your computer boots up, edit your /etc/rc.conf file, commenting out all the network settings and uncommenting NETWORKS=(), inserting your network config name, like NETWORKS=(mynetwork).  Add net-profiles to your DAEMONS list too.  Like so ...

#
# /etc/rc.conf - Main Configuration for Arch Linux
#

# -----------------------------------------------------------------------
# LOCALIZATION
# -----------------------------------------------------------------------
#
# LOCALE: available languages can be listed with the 'locale -a' command
# HARDWARECLOCK: set to "UTC" or "localtime"
# USEDIRECTISA: use direct I/O requests instead of /dev/rtc for hwclock
# TIMEZONE: timezones are found in /usr/share/zoneinfo
# KEYMAP: keymaps are found in /usr/share/kbd/keymaps
# CONSOLEFONT: found in /usr/share/kbd/consolefonts (only needed for non-US)
# CONSOLEMAP: found in /usr/share/kbd/consoletrans
# USECOLOR: use ANSI color sequences in startup messages
#
LOCALE="en_US.utf8"
HARDWARECLOCK="localtime"
USEDIRECTISA="no"
TIMEZONE="Canada/Pacific"
KEYMAP="us"
CONSOLEFONT=
CONSOLEMAP=
USECOLOR="yes"

# -----------------------------------------------------------------------
# HARDWARE
# -----------------------------------------------------------------------
#
# MOD_AUTOLOAD: Allow autoloading of modules at boot and when needed
# MOD_BLACKLIST: Prevent udev from loading these modules
# MODULES: Modules to load at boot-up. Prefix with a ! to blacklist.
#
# NOTE: Use of 'MOD_BLACKLIST' is deprecated. Please use ! in the MODULES array.
#
MOD_AUTOLOAD="yes"
#MOD_BLACKLIST=() #deprecated
MODULES=(forcedeth vboxdrv)

# Scan for LVM volume groups at startup, required if you use LVM
USELVM="no"

# -----------------------------------------------------------------------
# NETWORKING
# -----------------------------------------------------------------------
#
# HOSTNAME: Hostname of machine. Should also be put in /etc/hosts
#
HOSTNAME="killterm2"

# Use 'ifconfig -a' or 'ls /sys/class/net/' to see all available interfaces.
#
# Interfaces to start at boot-up (in this order)
# Declare each interface then list in INTERFACES
#   - prefix an entry in INTERFACES with a ! to disable it
#   - no hyphens in your interface names - Bash doesn't like it
# 
# DHCP:     Set your interface to "dhcp" (eth0="dhcp")
# Wireless: See network profiles below
#
#eth0="eth0 192.168.0.2 netmask 255.255.255.0 broadcast 192.168.0.255"
#INTERFACES=(eth0)

# Routes to start at boot-up (in this order)
# Declare each route then list in ROUTES
#   - prefix an entry in ROUTES with a ! to disable it
#
#gateway="default gw 192.168.0.1"
#ROUTES=(!gateway)
 
# Enable these network profiles at boot-up.  These are only useful
# if you happen to need multiple network configurations (ie, laptop users)
#   - set to 'menu' to present a menu during boot-up (dialog package required)
#   - prefix an entry with a ! to disable it
#
# Network profiles are found in /etc/network.d
#
# This now requires the netcfg package
#
NETWORKS=(vetco)

# -----------------------------------------------------------------------
# DAEMONS
# -----------------------------------------------------------------------
#
# Daemons to start at boot-up (in this order)
#   - prefix a daemon with a ! to disable it
#   - prefix a daemon with a @ to start it up in the background
#
DAEMONS=(syslog-ng net-profiles netfs crond fam hal alsa cups foldingathome sshd openntpd)

Hope this helps

virati

Member

Registered: 2008-04-14

Posts: 83

Re: Wireless dhcpcd timeout

Thanks, yeah that helped. So i executed the netcfg2 command and it seemed like everything went fine. My wlan0 interface went from Not Associated to having an address next to the Access Point.

Unfortunately when i try to ping through wlan0 i don't get anything (ping -I wlan0 -c 3 www.google.com). I can't really tell if this worked or not.

One more question: I want to add this wireless network as a second network; I still want to keep my eth1 connection. How would i edit rc.conf to reflect that?

Thanks.

synthead

Member

Registered: 2006-05-09

Posts: 1,337

Re: Wireless dhcpcd timeout

What happens when you try to run "dhcpcd your_interface"?

You can set up rc.conf to configure eth1 and use netcfg2 to configure your wireless   They should play nicely.

Tenken

Member

Registered: 2008-02-01

Posts: 126

Re: Wireless dhcpcd timeout

Is your router using any kind of encryption? That could allow you associate with the access point, but no actually make a connection to the wireless network. If your router is using WPA your might want to give this a read.