Issues connecting to the internet

seventwo · 2010-02-17 08:36:34

I have Arch installed on an Acer Aspire One Netbook A150 but I am unable to ping any websites, wired or wireless. Any idea on what could be wrong?

My ethernet info (not sure if this will be useful)

02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101E/RTL8102E PCI Express Fast Ethernet controller (rev 02)
03:00.0 Ethernet controller: Atheros Communications Inc. AR242x 802.11abg Wireless PCI Express Adapter (rev 01)

eth0      Link encap:Ethernet  HWaddr 00:23:8B:47:27:99  
          BROADCAST 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:251 Base address:0xe000 

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)

wlan0     Link encap:Ethernet  HWaddr 00:24:2B:14:FF:91  
          UP BROADCAST 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)

wmaster0  Link encap:UNSPEC  HWaddr 00-24-2B-14-FF-91-00-00-00-00-00-00-00-00-00-00  
          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)

my rc.conf file

#
# /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="local"
USEDIRECTISA="no"
TIMEZONE="America/Toronto"
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=()

# 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="nemesis"

# 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"
etho0="dhcp"
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"
#gateway="dhcp"
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=(main)

# -----------------------------------------------------------------------
# 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 network netfs crond @alsa)

EDIT:

It should also be noted that my wlan0 can `iwlist wlan0 scan` my wifi connection so I'm guessing it's probably just my settings.

Last edited by seventwo (2010-02-17 08:51:07)

chpln · 2010-02-17 10:02:23

From the ifconfig output, eth0 never seems to be associated with an IP address. I noticed a typo in rc.conf which may be related:

etho0="dhcp"

Wireless, I'm not sure. Could you give more detail as to how you're trying to bring the connection up and what happens?

seventwo · 2010-02-17 16:04:19

Thanks for pointing out my typo with eth0.
I changed it to eth0, but now when I try to restart the networkk, it fails.

>/etc/rc.d/network restart
:: Stopping Network [DONE]
:: Starting Network [BUSY]
eth0: timed out   [FAIL]

It also doesn't work on reboot so...

This is how I'm trying to get my wireless up:

>ifconfig wlan0 up
>iwlist wlan0 scan
>iwconfig wlan0 essid "linksys" key s:<password>
Error for wireless request "Set Encode" (8B2A) :
  SET failed on device wlan0 ; Invalid argument

perbh · 2010-02-17 20:24:32

I'm using a AAO as well - and have no problems whatsoever ...
First my /etc/rc.conf

eth0="dhcp"
wlan0="dhcp"
INTERFACES=(!eth0 !wlan0)
....
MODULES=(syslog-ng hal network wicd ...)

ie use 'wicd' to manage your network. After you have booted up - check state with 'ifconfig'.
If you allready have X up - then check the wicd-widget ...
Good luck!

pseudonomous · 2010-02-18 01:48:23

You could do what perbh recommends and use wicd (or networkmanager) to manage your network connections, but you probably should try and figure out how to set them up manually, this is usaully the easiest way to debug what's wrong with your network connection if there is any problem. (well, it has been for me, at least)

You are trying to connnect to linksys router of some sort right? I think you should concentrate on getting the wired connection to work first, then move on to setting up wireless. One thing to do would be to try and run dhcpcd manually:

run either as root or using sudo.

First make sure the network deamons are stopped so there's no conflict with running dhcpcd yourself:

# /etc/rc.d/network stop

then try and get an address from dhcpcd

# dhcpcd -L eth0

the -L option tells dhcpcd to quit if it can't get an address, if you do this you will see if your router is attempting to give you an address and, for some reason, your laptop refuses it, or if (more likely) you are not receiving an ip address offer at all. If the former is true, you need help from someone more knowledgeable than me, if the latter is true then read on.

You may need to check the configuration on your router, is it offering addresses through dhcp? Is it doing any MAC filtering, and if so have you added the MAC addresses for your wired and wireless interfaces to the list of allowed addresses? Pre-requisite to this of course, would be the ability to connect to the router with another computer. Does this work?

Also: routers and switches occassionally have bad ports, have you tried a different port on your router?

Okay, let's suppose you've figured out how to get:

# dhcpcd -L eth0

t
o suceed. you should then be able to get:

# /etc/rc.d/network start

to succeed as well, and get wired networking to run when you bootup, as long as you have the cable plugged in; arch won't, by default, automatically have dhcpcd try to rebind an address whenever you
plug a network cable in, so if you do start your laptop up unplugged, you will either have to run:

# /etc/rc.d/network restart

or

# dhcpcd -n eth0

=================================================================================

In regards to wireless configuration, iwconfig can handle wep encryption but that's it, it can't handle wpa, or wpa2, or any other encryption scheme. (for these you will need wpa_supplicant) It's also picky about the syntax of how you enter the key, if the key is a text string you must use the syntax above if it's a hex string DON'T use the "s:".

To be extra careful, you might want to pass arguments one at a time:

# iwconfig wlan0 essid "my network"
# iwconfig wlan0 key s:"my-passphrase"

Also, just to be careful, while iwlist can run as normal user, to set wireless settings with iwconfig you must run iwconfig as root or with "sudo".

If you are able to associate to a wireless access point, you will still need to acquire and ip address:

# dhcpcd -L wlan0

getting wireless configured to autostart is a little bit more involved, which is why you'll probably want to mangage that with netcfg, wicd, or networkmanager, all of which can also be used to manage your wired connection. You might ask then, "what's the point of getting it to work manually?", well ... when things go wrong, it still seems to me like going down to the command line networking tools is the best way to figure out what's wrong.

Arch Linux

#1 2010-02-17 08:36:34

Issues connecting to the internet

#2 2010-02-17 10:02:23

Re: Issues connecting to the internet

#3 2010-02-17 16:04:19

Re: Issues connecting to the internet

#4 2010-02-17 20:24:32

Re: Issues connecting to the internet

#5 2010-02-18 01:48:23

Re: Issues connecting to the internet

Board footer