You are not logged in.
- Topics: Active | Unanswered
Pages: 1
#1 2007-02-10 23:17:33
- zygon
- Member
- Registered: 2007-02-07
- Posts: 7
Ethernet with DHCP
Installed Arch recently and I can't get the Ethernet configured right. I'm not sure if the problem is with the driver or with the DHCP itself - could be either. I have a router using DHCP connecting two computers for a home DSL line. This Window's partition works fine. Was hoping for a hand. I booted it up and printed out a bunch of files and commands. Ive fiddled with a lot of them in the past couple days. These are fresh from a boot up at least.
I'm too used to automatic linux network configurations sadly but I've liked this trial by fire so far. Any help would be appreciated. I'm pretty excited about Arch if I can get over this hump.
-zygon
mii-tool eth0
eth0: negotiated 100baseTx-FD, link ok
product info: vendor 00:60:6e, model 4 rev 0
basic mode: autonegotiation enabled
basic status: autonegotiation complete, link ok
capabilities: 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD
advertising: 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD
link partner: 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD flow-controlroute
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Ifacelsmod (sorry, whole thing)
Module Size Used by
nls_cp437 5760 1
vfat 11008 1
fat 48540 1 vfat
snd_seq_oss 31716 0
snd_seq_midi_event 6400 1 snd_seq_oss
snd_seq 49996 4 snd_seq_oss,snd_seq_midi_event
shpchp 43872 0
pci_hotplug 25668 1 shpchp
hw_random 5144 0
snd_pcm_oss 38176 0
snd_mixer_oss 16384 1 snd_pcm_oss
joydev 8512 0
evdev 8192 0
intel_agp 21532 1
agpgart 27108 1 intel_agp
i2c_i801 7948 0
i2c_core 17792 1 i2c_i801
emu10k1_gp 3072 0
dmfe 19100 0
tulip 48672 0
ppdev 7812 0
lp 9856 0
uhci_hcd 29712 0
usbcore 116256 2 uhci_hcd
ppp_generic 27156 0
snd_emu10k1 118820 0
snd_rawmidi 20512 1 snd_emu10k1
snd_ac97_codec 94624 1 snd_emu10k1
snd_ac97_bus 2176 1 snd_ac97_codec
snd_pcm 78084 3 snd_pcm_oss,snd_emu10k1,snd_ac97_codec
slhc 6656 1 ppp_generic
analog 10144 0
snd_seq_device 6924 4 snd_seq_oss,snd_seq,snd_emu10k1,snd_rawmidi
snd_timer 20100 3 snd_seq,snd_emu10k1,snd_pcm
snd_page_alloc 8200 2 snd_emu10k1,snd_pcm
snd_util_mem 3840 1 snd_emu10k1
snd_hwdep 7428 1 snd_emu10k1
gameport 11656 3 emu10k1_gp,analog
snd 46432 11 snd_seq_oss,snd_seq,snd_pcm_oss,snd_mixer_oss,snd_emu10k1,snd_rawmidi,snd_ac97_codec,snd_pcm,snd_seq_device,snd_timer,snd_hwdep
irtty_sir 5632 0
soundcore 7776 1 snd
sir_dev 14668 1 irtty_sir
irda 126648 1 sir_dev
crc_ccitt 2176 1 irda
rtc 10932 0
parport_pc 25196 1
pcspkr 2948 0
xfs 593004 0
reiserfs 256880 0
jfs 187004 0
ext3 127880 1
jbd 56212 1 ext3
sata_qstor 7556 0
sata_promise 9092 0
sata_sil24 9476 0
sata_nv 7044 0
sata_mv 16008 0
sata_vsc 6148 0
sata_via 6020 0
sata_uli 4868 0
sata_svw 5764 0
sata_sx4 11780 0
sata_sis 5636 0
sata_sil 7432 0
DAC960 71360 0
cciss 29984 0
sx8 15756 0
cpqarray 19172 0
mptfc 10120 0
mptspi 6536 0
mptsas 16652 0
mptctl 23044 0
mptscsih 32336 3 mptfc,mptspi,mptsas
mptbase 46308 5 mptfc,mptspi,mptsas,mptctl,mptscsih
megaraid_mbox 25232 0
megaraid_sas 24492 0
megaraid_mm 9380 1 megaraid_mbox
ata_piix 8324 0
osst 51616 0
megaraid 37700 0
sym53c8xx 74260 0
atp870u 30848 0
aha152x 37304 0
aic79xx 272596 0
aic7xxx 177840 0
ahci 11396 0
pdc_adma 7556 0
libata 54284 15 sata_qstor,sata_promise,sata_sil24,sata_nv,sata_mv,sata_vsc,sata_via,sata_uli,sata_svw,sata_sx4,sata_sis,sata_sil,ata_piix,ahci,pdc_adma
raid_class 4992 0
nsp32 23828 0
aacraid 56832 0
ipr 59424 0
imm 11016 0
parport 33864 4 ppdev,lp,parport_pc,imm
3w_xxxx 25248 0
tmscsim 20800 0
dc395x 33552 0
3w_9xxx 31520 0
a100u2w 9408 0
BusLogic 23332 0
sr_mod 15140 0
qlogicfas408 6664 0
st 35744 0
sg 27804 0
dmx3191d 11392 0
lpfc 157120 0
scsi_transport_sas 15360 1 mptsas
qla1280 117132 0
sd_mod 14976 0
ide_floppy 16000 0
ide_cd 37792 0
cdrom 36144 2 sr_mod,ide_cd
ide_disk 14336 4
via82cxxx 8836 0 [permanent]
trm290 4228 0 [permanent]
triflex 3328 0 [permanent]
slc90e66 5248 0 [permanent]
sis5513 13196 0 [permanent]
siimage 10624 0 [permanent]
serverworks 8328 0 [permanent]
sc1200 6656 0 [permanent]
rz1000 2560 0 [permanent]
piix 9476 0 [permanent]
pdc202xx_old 9984 0 [permanent]
pdc202xx_new 8448 0 [permanent]
ns87415 4012 0 [permanent]
it821x 7684 0 [permanent]
hpt366 18048 0 [permanent]
hpt34x 4608 0 [permanent]
generic 4356 0 [permanent]
cy82c693 4228 0 [permanent]
cs5530 5120 0 [permanent]
cmd64x 10780 0 [permanent]
atiixp 5520 0 [permanent]
amd74xx 14364 0 [permanent]
alim15x3 11280 0 [permanent]
aec62xx 6912 0 [permanent]
ide_core 116940 27 ide_floppy,ide_cd,ide_disk,via82cxxx,trm290,triflex,slc90e66,sis5513,siimage,serverworks,sc1200,rz1000,piix,pdc202xx_old,pdc202xx_new,ns87415,it821x,hpt366,hpt34x,generic,cy82c693,cs5530,cmd64x,atiixp,amd74xx,alim15x3,aec62xxifconfig
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)/etc/rc.d/network start
no output because it fails and gives the version number of dhcpcd and its proper usage.
rc.conf
#
# /etc/rc.conf - Main Configuration for Arch Linux
#
MOD_AUTOLOAD="yes"
# Module Blacklist - modules in this list will never be loaded by udev
MOD_BLACKLIST=()
#
# Modules to load at boot-up (in this order)
# - prefix a module with a ! to blacklist it
#
MODULES=()
# Scan for LVM volume groups at startup, required if you use LVM
USELVM="no"
lo="lo 127.0.0.1"
eth0="dhcp"
#eth0="eth0 192.168.1.100 netmask 255.255.255.0 broadcast 192.168.1.255"
INTERFACES=(lo eth0)
#gateway="default gw 192.168.1.1"
#ROUTES=(!gateway)
DAEMONS=(syslog-ng hotplug pcmcia network netfs crond)modprobe.conf (attempting that driver, not sure if it is the right one)
# End of file
#
# /etc/modprobe.conf (for v2.6 kernels)
#
alias eth0 8139tooand finally, /etc/dhcpc/dhcpcd-eth0.info
IPADDR=192.168.1.100
NETMASK=255.255.255.0
NETWORK=192.168.1.0
BROADCAST=192.168.1.255
GATEWAY=192.168.1.1
DNS=71.243.0.12,68.237.161.12
DHCPSID=192.168.1.1
DHCPGIADDR=0.0.0.0
DHCPSIADDR=0.0.0.0
DHCPCHADDR=00:08:A1:1E:2F:99
DHCPSHADDR=00:06:25:E4:03:AB
DHCPSNAME=''
LEASETIME=6000
RENEWALTIME=3000
REBINDTIME=5250
INTERFACE='eth0'
CLASSID='Linux 2.6.16-ARCH i686'
CLIENTID=00:08:A1:1E:2F:99Offline
#2 2007-02-11 00:49:30
- vogt
- Member
- From: Toronto, Canada
- Registered: 2006-11-25
- Posts: 389
Re: Ethernet with DHCP
dhcp is working (you did get a lease after all)
The only thing I see that may be wrong could be that in rc.conf there may be a difference between an empty ROUTES and a nonexistant ROUTES, so
#ROUTES=(!gateway)should maybe be:
ROUTES=()Offline
#3 2007-02-11 01:44:38
- zygon
- Member
- Registered: 2007-02-07
- Posts: 7
Re: Ethernet with DHCP
No dice. I get the same error message when trying to restart the network. It gives the version number of dhcpcd and its correct usage.
So the Ethernet module is Ok then?
Last edited by zygon (2007-02-11 01:45:58)
Offline
#4 2007-02-11 02:19:14
- zygon
- Member
- Registered: 2007-02-07
- Posts: 7
Re: Ethernet with DHCP
Well i got the Eth0 mostly working. I believe it WAS that route=() and I thank you.
but now after just a little bit of time the network starts to lag horribly or stop all together.
i was trying to sync pacman and received two messages:
gethostbyname: Success
error: cannot connect to ftp.blah.blah
Any ideas on this one?
Offline
#5 2007-02-11 04:27:52
- normc
- Member
- From: Ottawa, Canada
- Registered: 2004-06-28
- Posts: 277
- Website
Re: Ethernet with DHCP
This is my setup works very well
lo="lo 127.0.0.1"
#eth0="eth0 192.168.0.2 netmask 255.255.255.0 broadcast 192.168.0.255"
eth0="dhcp"
INTERFACES=(lo 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)
Norm
Offline
#6 2007-02-11 04:37:57
- ralvez
- Member
- From: Canada
- Registered: 2005-12-06
- Posts: 1,718
- Website
Re: Ethernet with DHCP
Look at the file "/etc/pacman.conf" and you will find references to the preferred serves you have set up to download files. Change them to point to servers closer to you and that may help resolve your problem.
Offline
#7 2007-02-11 06:11:23
- zygon
- Member
- Registered: 2007-02-07
- Posts: 7
Re: Ethernet with DHCP
I'm pretty sure its a problem with the route. Right now route works at first but after attempting any network connection it just dies. I can ping the gateway about 40-50 times and then it stops.
Offline
#8 2007-02-11 08:01:13
- noriko
- Member
- From: In My Mind
- Registered: 2006-06-09
- Posts: 535
- Website
Re: Ethernet with DHCP
i had a similar issue..
turned out to be defective cable.
if your nic has a service light on it. then it should be on whether or not the eth0 is working/configured | loaded.
check it when the connection dies. if it's off i'd say it's most likely a datalink issue.
The.Revolution.Is.Coming - - To fight, To hunger, To Resist!
Offline
#9 2007-02-11 15:19:29
- ralvez
- Member
- From: Canada
- Registered: 2005-12-06
- Posts: 1,718
- Website
Re: Ethernet with DHCP
There are 3 things you may need to troubleshoot.
1. The Nic card itself
2. The cables
3. The switch you use to connect your machine to the router.
I had a switch once that would die (just like it happens to you) but only one port, all the others would continue to work and it was a pain to troubleshoot because the logical conclusion was that all the machines in that switch are working so it is not the switch.
I would take the short (fast) approach: swapping.
Change cables first (the easies to do), then the NiC then the switch.
Hope this helps.
Last edited by ralvez (2007-02-11 15:20:36)
Offline
#10 2007-02-11 17:09:14
- zygon
- Member
- Registered: 2007-02-07
- Posts: 7
Re: Ethernet with DHCP
Thanks for the input but I really can't imagine those would be the problem. Right now this second I'm using the same network card, same cables, and same router (no switch, just two PCs connected to the router then to the DSL modem).
I'm considering reinstalling Arch. Maybe I fiddled with something unknowingly.
Offline
#11 2007-02-11 21:32:19
- ralvez
- Member
- From: Canada
- Registered: 2005-12-06
- Posts: 1,718
- Website
Re: Ethernet with DHCP
If you are sharing the same hardware in Windows and works it may be either a misconfiguration or a matter of drivers.
Offline
#12 2007-02-13 00:56:42
- zygon
- Member
- Registered: 2007-02-07
- Posts: 7
Re: Ethernet with DHCP
I reinstalled Arch and had a little progress. I only added the eth0="dhcp" line in rc.conf and nothing else. I also powered down my router before booting up the machine. i was able to send out 900 packets before they started dropping like flies. 'route' didn't show anything at this point but i had an IP. resolv.conf had the correct servers. Any ideas? should i just keep playing with my router until it works fully? is there a list of more servers that might be closer to me within North America?
Also, if the machine is loading the interface module on boot automatically (tulip) should i add it to modprobe.conf?
Offline
#13 2007-02-13 02:53:06
- ralvez
- Member
- From: Canada
- Registered: 2005-12-06
- Posts: 1,718
- Website
Re: Ethernet with DHCP
Nope, if tulip is loaded you should be OK.
You have now a clean install, so if you issue:
"ifconfig" and "route" what do you get?
BTW in /etc/rc.conf you should have:
lo="lo 127.0.0.1"
eth0="dhcp"
INTERFACES=(lo eth0)
ROUTES=(!gateway)
Offline
#14 2007-02-14 13:09:47
- joaospinto
- Member
- Registered: 2007-02-13
- Posts: 40
Re: Ethernet with DHCP
see http://bbs.archlinux.org/viewtopic.php?id=29877
i had the same problem
i have already solved it
Offline
#15 2007-02-14 13:27:24
- .:B:.
- Forum Fellow
- Registered: 2006-11-26
- Posts: 5,819
- Website
Re: Ethernet with DHCP
dhcp is working (you did get a lease after all)
The only thing I see that may be wrong could be that in rc.conf there may be a difference between an empty ROUTES and a nonexistant ROUTES, so
#ROUTES=(!gateway)should maybe be:
ROUTES=()
If I understand correctly: the ROUTES= entry in the topic starter's rc.conf is not only commented, but also contains a value prefixed with an exclamation mark. That is as good as a double negation.
He does not need to specify manually the ROUTES= content, since DHCP will take care of that. So it doesn not matter whether ROUTES= is uncommented or not, as long as gateway has the exclamation mark in front of it.
Last edited by B (2007-02-14 13:32:24)
Got Leenucks? :: Arch: Power in simplicity :: Get Counted! Registered Linux User #392717 :: Blog thingy
Offline
#16 2007-02-19 02:31:02
- zygon
- Member
- Registered: 2007-02-07
- Posts: 7
Re: Ethernet with DHCP
It's been a while since I've had time to tinker with Arch. Today I was able to sync something (as I have before with pacman -Syu), wanted to update the kernel i believe. But once it started to actually try and download an update the connection would die. I still get the "gethostbyname Success" but fail to connect to any of the FTP's (including a closer one i added). This is pretty goofy. The network boots up fine along with Arch but when i try to rc.d/network restart it fails. So ifconfig was showing about 200 packets with about 100 packet errors (after trying to sync). I've been tinkering with the dhcpcd arguments with little success. I'd still appreciate any help/advice anyone could give. I might just can it for now and toss freebsd up but i really wanted to get Arch working. Thanks to everyone who has given a word.
-Z
Last edited by zygon (2007-02-19 02:55:31)
Offline
#17 2007-02-20 09:00:35
- RabidWolf
- Member
- From: WI,USA
- Registered: 2007-01-20
- Posts: 31
- Website
Re: Ethernet with DHCP
what kind of router do you have, is the default gateway indeed 192.168.0.1 ? I have a linksys and the gateway for the router is 192.168.1.1 not 192.168.0.1
the networking section of my rc.conf looks like this:
#
# -----------------------------------------------------------------------
# NETWORKING
# -----------------------------------------------------------------------
#
HOSTNAME="rabid0sbigbox"
#
# 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=(lo 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.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=(main)Last edited by RabidWolf (2007-02-20 09:03:29)
Offline
Pages: 1