DHCP doesn't work

arch_enemy · 2008-06-12 22:36:18

Hello,
i've installed archlinux on two computers. both of them are connected to network with DHCP service. on first machine everything works cool - i've just put eth0="dhcp", and comment section with gateways and routers in /etc/rc.conf.
But with the second machine i get some troubles:
first, some information:
both computers have identical network cards
i've put changes, on second computer, in rc.conf, as on first, after reboot - on second computer DHCPcd have generated resolv.conf (the same as on first).
#dhcpcd etho0
#err,eth0:dhcpcd already running on pid 3570 (/var/run/....)
and on more - i can still resolv hostnames, with, f.e., #dig google.com

So, please, give me some advice, in what direction i should search?

p.s. sorry for my english

Last edited by arch_enemy (2008-06-12 22:54:57)

SwimFr3ak · 2008-06-12 23:06:21

it sounds like dhcpcd has already been started on that interface.

try

 
$>killall dhcpcd
$>ifconfig eth0 down
$>ifconfig eth0 up
$>dhcpcd eth0

Also, do you have 'network' in rc.conf DAEMONS=()

Last edited by SwimFr3ak (2008-06-12 23:06:58)

arch_enemy · 2008-06-12 23:22:26

thnx, but its'n help.
i have checked /var/log/messages:
Jun 12 02:57:55 myhost dhcpcd[3500]: eth0: hardware address = 00:15:8a:00:56:84
Jun 12 02:57:55 myhost dhcpcd[3500]: eth0: broadcasting for a lease
Jun 12 02:57:55 myhost dhcpcd[3500]: eth0: offered 192.168.1.207 from 192.168.1.27
Jun 12 02:57:55 myhost dhcpcd[3500]: eth0: checking 192.168.1.207 is available on attached networks
Jun 12 02:57:56 myhost dhcpcd[3500]: eth0: leased 192.168.1.207 for 14400 seconds
Jun 12 02:57:56 myhost dhcpcd[3500]: eth0: adding IP address 192.168.1.207/22
Jun 12 02:57:56 myhost dhcpcd[3500]: eth0: adding default route via 192.168.2.16 metric 0
Jun 12 02:57:56 myhost dhcpcd[3500]: eth0: adding route to 169.254.0.0/16 metric 0
Jun 12 02:57:56 myhost dhcpcd[3500]: eth0: exiting
.....
Jun 12 04:06:14 myhost dhcpcd[3501]: eth0: received SIGTERM, stopping
Jun 12 04:06:14 myhost dhcpcd[3501]: eth0: removing default route via 192.168.2.16 metric 0
Jun 12 04:06:14 myhost dhcpcd[3501]: eth0: removing route to 169.254.0.0/16 metric 0
Jun 12 04:06:14 myhost dhcpcd[3501]: eth0: removing IP address 192.168.1.207/22
Jun 12 04:06:14 myhost dhcpcd[3501]: eth0: exiting

looks like everything fine.... the output almost the same as the on fist machine /var/log/messages (except IP address and some other information).

and, yes - i have "network" in daemons, it was there by default.

Last edited by arch_enemy (2008-06-12 23:38:31)

SwimFr3ak · 2008-06-12 23:39:26

Do you have the gateway and route settings commented out in rc.conf?

arch_enemy · 2008-06-12 23:51:54

#
# /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="yes"
TIMEZONE="Canada/Pacific"
KEYMAP="ru-utf"
CONSOLEFONT="Cyr_a8x16.psfu" 
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=(8139cp 8139too mii slhc ac97_bus snd-mixer-oss snd-pcm-oss snd-seq-oss snd-seq-device snd-seq-midi-event snd-seq snd-page-alloc snd-pcm snd-rawmidi snd-timer snd snd-mpu401-uart snd-mpu401 snd-ac97-codec snd-intel8x0 soundcore)

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

# 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="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.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 sshd network netfs crond)

rc.conf on both machines fully equal, except locales.
resolution of problem should be somewhere on the top... dhcpcd works fine, but not it al

Last edited by arch_enemy (2008-06-12 23:54:28)

zenlord · 2008-06-13 08:07:46

Odd...

Could you try the new net-profiles -way that Arch has adopted as default some months ago? With net-profiles you could also use dhclient instead of dhcpd.

Zl.

atomizer · 2008-06-13 20:58:50

arch_enemy wrote:

Hello,
But with the second machine i get some troubles:
first, some information:
both computers have identical network cards
i've put changes, on second computer, in rc.conf, as on first, after reboot - on second computer DHCPcd have generated resolv.conf (the same as on first).
#dhcpcd etho0
#err,eth0:dhcpcd already running on pid 3570 (/var/run/....)
and on more - i can still resolv hostnames, with, f.e., #dig google.com

What are the troubles? Maybe I just overlooked, but I can't understand what is it?
Are you getting an IP address from DHCP? try looking at ifconfig output.
since you are able to resolve names - I assume you ARE connected to the network and DNS service IS working fine.
try pinging something, like google.com or yahoo.com

Sorry if I did not understand something, I do want to help.

arch_enemy · 2008-06-13 21:27:50

2atomizer, yes, hostnames were resolving. ping doesn't work excetp ping to computers from local network.

And at last i've solved the problem
in rc.conf, i've manually added two default gateways. (netstat -rn on first machine-->get there def. gateway-->netstat -rn on second machine, get, some why, another gateway, and then put them in /etc/rc.conf )

and one more, as i understand, problem isn't in archlinux, troubles somewhere on the side of DHCP server in our company.

atomizer · 2008-06-13 21:42:56

Exactly! just wanted to say the same thing - in the DHCP packet sent out by the DHCP server the default gateways are usually written into.

Good job on resolving this!

also, it is a bit weird that first one started up correctly.

Arch Linux

#1 2008-06-12 22:36:18

DHCP doesn't work

#2 2008-06-12 23:06:21

Re: DHCP doesn't work

#3 2008-06-12 23:22:26

Re: DHCP doesn't work

#4 2008-06-12 23:39:26

Re: DHCP doesn't work

#5 2008-06-12 23:51:54

Re: DHCP doesn't work

#6 2008-06-13 08:07:46

Re: DHCP doesn't work

#7 2008-06-13 20:58:50

Re: DHCP doesn't work

#8 2008-06-13 21:27:50

Re: DHCP doesn't work

#9 2008-06-13 21:42:56

Re: DHCP doesn't work

Board footer