You are not logged in.
Pages: 1
I installed Arch yesterday and dhcp was working fine for me. Somehow I decided to reinstall today to familiarize myself with Arch, and dhcp doesn't seem to work.
Before installation the correct tg3 driver for my ether card was loaded, but I could not go for the FTP installation (error fetching packages or something). Pinging Google with
ping -c 3 www.google.com
returned an "unknown host" message.
I chose to install from CD, and after successful installation I was still not able to connect. Pinging Google always gave me the same result, and pinging localhost sometimes yielded a "Network is unreachable" message.
I am connected to the net with dhcp under Ubuntu now. Issuing ifconfig gets me:
eth0 Link encap:以太网 硬件地址 00:1a:a0:ff:35:d6
inet 地址:158.143.185.35 广播:158.143.187.255 掩码:255.255.252.0
inet6 地址: fe80::21a:a0ff:feff:35d6/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 跃点数:1
接收数据包:6956 错误:0 丢弃:0 过载:0 帧数:0
发送数据包:599 错误:0 丢弃:0 过载:0 载波:0
碰撞:0 发送队列长度:1000
接收字节:1088072 (1.0 MB) 发送字节:110255 (107.6 KB)
中断:17
lo Link encap:本地环回
inet 地址:127.0.0.1 掩码:255.0.0.0
inet6 地址: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 跃点数:1
接收数据包:1960 错误:0 丢弃:0 过载:0 帧数:0
发送数据包:1960 错误:0 丢弃:0 过载:0 载波:0
碰撞:0 发送队列长度:0
接收字节:98000 (95.7 KB) 发送字节:98000 (95.7 KB)
wlan0 Link encap:以太网 硬件地址 00:1b:77:b9:5f:12
UP BROADCAST MULTICAST MTU:1500 跃点数:1
接收数据包:0 错误:0 丢弃:0 过载:0 帧数:0
发送数据包:0 错误:0 丢弃:0 过载:0 载波:0
碰撞:0 发送队列长度:1000
接收字节:0 (0.0 B) 发送字节:0 (0.0 B)
wmaster0 Link encap:未指定 硬件地址 00-1B-77-B9-5F-12-00-00-00-00-00-00-00-00-00-00
UP BROADCAST RUNNING MULTICAST MTU:1500 跃点数:1
接收数据包:0 错误:0 丢弃:0 过载:0 帧数:0
发送数据包:0 错误:0 丢弃:0 过载:0 载波:0
碰撞:0 发送队列长度:1000
接收字节:0 (0.0 B) 发送字节:0 (0.0 B)
Never mind the Chinese characters, but on the second line you can see that I am getting the correct addresses. Under Arch I could not get the inet line, and no inet6 line either. wlan0 and wmaster were also missing, but as I didn't set up wireless connections, maybe they shouldn't be there anyway.
Besides, I used the same configuration as I did yesterday, which worked flawlessly. Although as I said, I wasn't able to get a connection even before I tried to set up anything, so my own configuration might not be the problem.
Here is my rc.conf
#
# /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"
# 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.UTF-8"
HARDWARECLOCK="UTC"
TIMEZONE="Europe/London"
KEYMAP="dvorak"
CONSOLEFONT="default8x16"
CONSOLEMAP=
USECOLOR="yes"
#
# -----------------------------------------------------------------------
# HARDWARE
# -----------------------------------------------------------------------
#
# Scan hardware and load required modules at bootup
MOD_AUTOLOAD="yes"
# Module Blacklist - modules in this list will never be loaded by udev
MOD_BLACKLIST=(net-pf-10 pcspkr)
#
# Modules to load at boot-up (in this order)
# - prefix a module with a ! to blacklist it
#
MODULES=(tg3 iwl3945 snd-mixer-oss snd-pcm-oss snd-hwdep snd-page-alloc snd-pcm snd-timer snd snd-hda-intel soundcore)
# Scan for LVM volume groups at startup, required if you use LVM
USELVM="no"
#
# -----------------------------------------------------------------------
# NETWORKING
# -----------------------------------------------------------------------
#
HOSTNAME="arch"
#
# 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"
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-profiles
#
#NET_PROFILES=(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)
# End of file
hosts
#
# /etc/hosts: static lookup table for host names
#
#<ip-address> <hostname.domain.org> <hostname>
127.0.0.1 localhost.localdomain localhost arch
# End of file
Any idea?
Last edited by allbluedream (2008-04-10 01:57:19)
Offline
Have you checked /var/log/messages.log for any errors related to dhcpcd?
Offline
Thanks for the reply. I just got it to work by issuing this command before anything else:
dhcpcd -h arch -t 120 eth0
I don't think that the host part is relevant though. Previous attempts without specifying '-t' showed that it was a 'time out' problem.
I do wonder how to reconnect once dhcpcd timed out. I can't run dhcpcd twice, and Arch doesn't know how to do that by itself, e.g. later during FTP/HTTP installation, the installer told me that 'dhcp failed', apparently because I just did dhcpcd myself.
Currently I have to reboot if dhcp actually fails. I believe that there are better ways that I don't know of?
Offline
I do wonder how to reconnect once dhcpcd timed out. I can't run dhcpcd twice, and Arch doesn't know how to do that by itself, e.g. later during FTP/HTTP installation, the installer told me that 'dhcp failed', apparently because I just did dhcpcd myself.
Currently I have to reboot if dhcp actually fails. I believe that there are better ways that I don't know of?
You can kill dhcpcd with:
dhcpcd -x eth0
and then try again...
Offline
If dhcpcd times out with the default -t setting, edit it under /etc/conf.d/dhcpcd:
DHCPCD_ARGS="-R -t 30 -h $HOSTNAME"
Offline
Thank you both
Now that this problem is solved, many more are coming... Em, I guess this is the fun part of Arch
Offline
Pages: 1