Arch network setup problem. SO FRUSTRATING! --- [SOLVED]

bgc1954 · 2008-02-29 19:44:36

if you don't have a WM then wifi-radar isn't going to do much for you.. It took me ages to get wifi working on my old Thinkpad but the simplest thing for me personally was using wifi-radar to connect wirelessly. I also had WPA to contend with which can be a real pain in the %$^. If this is frustrating you, perhaps you should get your WM of choice working and then chip away at the wireless later. Just a suggestion. I think you will be quite happy with Arch compared to Ubuntu once you get it going.

junglepeanut · 2008-03-01 06:36:46

This means one is already running probably the one from boot.

Error, wlan0: dhcpch already running on pid 5673 (/var/run/dhcpcd-wlan0.pid)

Try now (to remove the info that one is running)
pkill dhcpcd

then restart it with
dhcpcd -d wlan0

See what it prints out as it tries to connect.

You can also just to be sure before doing the above do this.

iwconfig wlan0 essid <yourrouter> key <yourkey>

just to make sure it looks right...I am guessing there is no key since you did not mention anything about the key/off above.

If you are using a key are you trying wep or wap?

Romashka · 2008-03-02 17:03:33

Misbah wrote:

bgc1954 - I've reinstalled ARCH a few times just to play around with the partitions and file systems, and get the options I want and stuff. None of the times though has a /zoneinfo file or directory been created. I presume I'm selecting all packages, because I select all, and then select all by default. But I will use pacman -S tzdata to see if I have the package, as someone else also told me that is the package responsible for that, thanks for the help!

tzdata package is required by glibc, so I wonder how you've managed to install glibc without tzdata

Misbah · 2008-03-10 06:21:19

deleted

Last edited by Misbah (2012-02-14 05:59:06)

Misbah · 2008-03-10 06:50:19

deleted

Last edited by Misbah (2012-02-14 05:58:51)

Misbah · 2008-03-10 07:55:35

deleted

Last edited by Misbah (2012-02-14 05:58:39)

calef13 · 2008-03-10 10:44:52

I would recommend you try netcfg2 with profiles. The link is here: http://wiki.archlinux.org/index.php/Network_Profiles

You will need the netcfg2 package, you can enable the testing repository or you can get it from here: ftp://ftp.archlinux.org/testing/os/i686/ look for the netcfg package. Once downloaded run 'pacman -A netcfg-2.0.6-1-i686.pkg.tar.gz' as root in the folder where you downloaded it and follow the instructions in the above wiki. Someone said earlier you should remove network from the daemons line and replace it with net-profiles once you start using netcfg, but that isn't in the wiki page although it could be out of date, I haven't had a chance to reboot my computer yet and check, but netcfg <profile> works perfectly for my wpa network. So that should get wireless connecting on boot.

Last edited by calef13 (2008-03-10 10:45:50)

iphitus · 2008-03-10 11:03:40

another vote for netcfg2, but i'm terribly biased, it's primarily my work.

Misbah · 2008-03-10 15:20:14

deleted

Last edited by Misbah (2012-02-14 05:58:27)

junglepeanut · 2008-03-11 04:11:49

I also vote for netcfg2 and just use the exclusive protocol. Or with the netcfg ( i.e. not using testing) then just make sure everything is setup properly...netcfg supports multiple as well (explained in wiki and rc.conf) If you do not want the menu (for mutliple) just put the name of the profile in rc.conf there with everything filled out properly in the profile. (i.e. on the first page it looks like net-profiles is commented out)

Then it should just work. I have never messed with the conf.d/wireless file as even with a single profile I think it cleaner (especially if you visit someone often) to create simple profiles (/etc/network-profiles/ I don't remember if there were examples in there so below I found some old files..I can't quarantee the format is right since I now have netcfg2 setup but it should be the same , also remember mine is eth1 so that is a little different but I think essentially the same) for each so I don't need to type it each time.

/etc/conf.d/wireless

#
# Settings for wireless cards
#
# For each wireless interface declared in INTERFACES (in rc.conf), declare
# a wlan_${IF} variable that contains the arguments to be passed to
# iwconfig(8).  Then list the original interface name in the
# WLAN_INTERFACES array.
#

#wlan_eth0="eth0 mode managed essid default"
#WLAN_INTERFACES=(eth0)

/etc/network-profiles/myprofile

#
# Network Profile
#

DESCRIPTION="myprofile"

# Network Settings
INTERFACE=eth1
HOSTNAME=KingKong

# Interface Settings (use IFOPTS="dhcp" for DHCP)
IFOPTS="dhcp"
GATEWAY=

# DNS Settings (optional)
#DOMAIN=localdomain
#DNS1=192.168.0.1
#DNS2=

# Wireless Settings (optional)
ESSID=sillyrabbit
KEY="tricks are for kids"
IWOPTS="mode managed essid $ESSID key $KEY"

#WIFI_INTERFACE=wlan0   # use this if you have a special wireless interface
                        # that is linked to the real $INTERFACE

#WIFI_WAIT=5            # seconds to wait for the wireless card to
                        # associate before bringing the interface up
#USEWPA="yes"           # start wpa_supplicant with the profile
#WPAOPTS=""             # use "" for normal operation or specify additional
                        # options (eg, "-D ipw")
                        # see /etc/wpa_supplicant.conf for configuration
#AUTOWPA="yes"          # automatically configure WPA
#PASSKEY=""             # wpa passkey/phrase. for use with AUTOWPA

my rc.conf has changed so much I can't recall enough to put back but copying yours I think try something like this

# -----------------------------------------------------------------------
# NETWORKING
# -----------------------------------------------------------------------
#
HOSTNAME="mesh"
#
# 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
#
# Note: to use DHCP, set your interface to be "dhcp" (eth0="dhcp")
#
lo="lo 127.0.0.1"
#eth0="dhcp"
#ra0="dhcp"
wlan0="dhcp"
#wlan_ra0="mode managed"
#wlan_ra0="ra0 key xxx"
#WLAN_INTERFACES=(ra0)
INTERFACES=(lo !eth0 wlan0)

#
# 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.1.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-profiles
#
NET_PROFILES=(someprofile)

#
# -----------------------------------------------------------------------

/etc/network-profiles/myprofile

#
# Network Profile
#

DESCRIPTION="myprofile"

# Network Settings
INTERFACE=wlan0
HOSTNAME=mesh
# Interface Settings (use IFOPTS="dhcp" for DHCP)
IFOPTS="dhcp"
GATEWAY=

# DNS Settings (optional)
#DOMAIN=localdomain
#DNS1=192.168.0.1
#DNS2=

# Wireless Settings (optional)
ESSID=lynksys
KEY=
IWOPTS="mode managed essid $ESSID" #maybe needs the blank key $KEY but I doubt it

iphitus · 2008-03-11 05:58:16

netcfg v2 is an almost total rewrite of netcfg v1 and the performance of netcfg v1 is not indicative of that for netcfg v2.

Further, in a matter of weeks, netcfg1 will be removed, replaced by netcfg v2.

Misbah · 2008-03-11 08:12:12

deleted

Last edited by Misbah (2012-02-14 05:58:11)

iphitus · 2008-03-11 12:14:15

1) netcfg v2 can replace all your networking needs. (almost, see 3)

2) Don't worry about ifopts, it's offering more control for those who need it.
Regarding the timeouts, there's two stages in a typicalwireless connection
- association
- getting an IP
TIMEOUT is for association, DHCP_TIMEOUT is for getting an IP (using dhcp). You don't need to change these, they're just the maximum time netcfg v2 will allow either of those to go before failing. If it's finishing before that, great

3) You still need /etc/hosts. Best to have lines with both localhost, as well as whatever hostname you want to use in it.

Misfit138 · 2008-03-11 12:30:28

To emphasize what Iphitus said, you NEED etc/hosts. Removing it will cause some unexpected slowdowns.

Misbah · 2008-03-11 21:19:20

deleted

Last edited by Misbah (2012-02-14 05:57:53)

Valok · 2009-08-08 23:26:21

I'm having exactly the same problem, except I'm not using a wireless connection, but rather a wired one through a linksys router.

And obviously because of this I can't use one of the commands used to fix the problem above because it pertains only to wireless connections. Anyone have advice for someone experiencing this error through a wired connection?

Arch Linux

#26 2008-02-29 19:44:36

Re: Arch network setup problem. SO FRUSTRATING! --- [SOLVED]

#27 2008-03-01 06:36:46

Re: Arch network setup problem. SO FRUSTRATING! --- [SOLVED]

#28 2008-03-02 17:03:33

Re: Arch network setup problem. SO FRUSTRATING! --- [SOLVED]

#29 2008-03-10 06:21:19

Re: Arch network setup problem. SO FRUSTRATING! --- [SOLVED]

#30 2008-03-10 06:50:19

Re: Arch network setup problem. SO FRUSTRATING! --- [SOLVED]

#31 2008-03-10 07:55:35

Re: Arch network setup problem. SO FRUSTRATING! --- [SOLVED]

#32 2008-03-10 10:44:52

Re: Arch network setup problem. SO FRUSTRATING! --- [SOLVED]

#33 2008-03-10 11:03:40

Re: Arch network setup problem. SO FRUSTRATING! --- [SOLVED]

#34 2008-03-10 15:20:14

Re: Arch network setup problem. SO FRUSTRATING! --- [SOLVED]

#35 2008-03-11 04:11:49

Re: Arch network setup problem. SO FRUSTRATING! --- [SOLVED]

#36 2008-03-11 05:58:16

Re: Arch network setup problem. SO FRUSTRATING! --- [SOLVED]

#37 2008-03-11 08:12:12

Re: Arch network setup problem. SO FRUSTRATING! --- [SOLVED]

#38 2008-03-11 12:14:15

Re: Arch network setup problem. SO FRUSTRATING! --- [SOLVED]

#39 2008-03-11 12:30:28

Re: Arch network setup problem. SO FRUSTRATING! --- [SOLVED]

#40 2008-03-11 21:19:20

Re: Arch network setup problem. SO FRUSTRATING! --- [SOLVED]

#41 2009-08-08 23:26:21

Re: Arch network setup problem. SO FRUSTRATING! --- [SOLVED]

Board footer