[Solved] Several installs and issues with DHCP issue every time.

ScottArch · 2010-01-22 09:28:58

Edited: more concise information!

Hi folks,

I was using Arch fine for months but decided to reinstall it fresh at the new year, but since then I have been plagued by connection issues. I install Arch and follow many of the tips found in these Wikis to set it up how I like then install preload and readahead.

Post-Installation Tips
http://wiki.archlinux.org/index.php/Pos … ation_Tips
- LCD filtered fonts
- Disable IPv6 (I use Chorus/NTL and they have a tip for improving Firefox that disables IPv6, so I think that this is not to blame)

Laptop
http://wiki.archlinux.org/index.php/Laptop
- Battery state monitoring utilities (acpi)
- Laptop-mode-toold
- Powernowd

Maximising Performance
http://wiki.archlinux.org/index.php/Max … erformance
- Swapiness
- Mount /tmp to RAM

My internet connection works fine, even when rebooting, but later I turn on my computer and WICD or networkmanager fails on "obtaining IP address. I really think that there is something in one of these tips that is causing this problem, but I am at a loss as to what. Like I say, I was using it happily for many months before these current issues. The only thing I did differently was systematically set up my computer with all the tips detailed above, where as before, I collected these tips over a period of time and did not do them all straight after installation. I have tried rolling back the changes and this has not fixed the issue.

I have had this issue over many reinstalls, using networkmanager or WICD and each time I was hoping that I was doing something wrong. I have an Ubuntu and work Windows laptop that both work fine, so I don.t think it is anything to do with the connection itself.

I am not sure what information you would need so I thought I would post both of these files. If you would like anything else, give me a shout and i can post it.

# 
# /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", any other value will result 
#   in the hardware clock being left untouched (useful for virtualization) 
# 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_GB.UTF-8" 
HARDWARECLOCK="UTC" 
TIMEZONE="Europe/Dublin" 
KEYMAP="uk" 
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=(acpi-cpufreq vboxdrv coretemp) 
 
# 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="laptop" 
 
# 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 
# 
 
#Static IP example 
#eth0="dhcp" 
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=(preload syslog-ng hal wicd @powernowd @laptop-mode @fam @alsa @sensors @readahead-list)

/etc/resolv.conf

# Generated by dhcpcd 
# /etc/resolv.conf.head can replace this line 
# /etc/resolv.conf.tail can replace this line

Thanks for your help,

Scott

Last edited by ScottArch (2010-02-14 12:30:25)

ScottArch · 2010-01-23 12:06:13

Hi folks,

A quick update that might help someone diagnose the problem.

I took the laptop to work and it connected to the work network fine. I took it home and it connected fine. I woke up this morning and it wont connect now. I am writing this using my home wireless, on my laptop, using a LAN cable connected to my work computer (which probably wont work this evening!).

It is almost like connecting somewhere else resets something and it works for a little bit (although I cannot connect my wireless now after connecting to my work compute through a LAN cable, so this may not be the case). I cannot really see any logic to what is going on, but I am hoping that this scenario rings a bell with someone.

Cheers,

Scott

Faither · 2010-01-23 21:13:16

Hey Scott!

I don't know if it is helpful in any way but I have a similar problem with my desktop PC.
I have two ethernet controllers installed and somtimes I had a Ip address assigned and sometimes I didn't.

One which is connected to the router and a 2nd one I use sporadically to connect additional computers.

The dhcpcd would fail to load even if I followed steps suggested from other forum members.
My temporary fix was to run:

 # dhcpcd

manually.

If this helps you might consider adding "dhcpcd" at the end of
/etc/rc.d/network

I know it's not really a fix but it helps me to get a working connection whoch otherwise would fail - or work if lucky but i don't like lucky with network/internet ^^

ScottArch · 2010-01-24 10:09:36

Hi Faither,

Thanks for the help. However, when I issue the command I get:

dhcpcd: version 5.1.4 starting
dhcpcd: wlan0: broadcasting for a lease
dhcpcd: eth0: waiting for carrier
dhcpcd: wlan0: carrier lost
dhcpcd: wlan0: carrier acquired
dhcpcd: wlan0: broadcasting for a lease
dhcpcd: control command: /sbin/dhcpcd -h laptop wlan0
dhcpcd: timed out

When I attempt to issue the control command, nothing happens.

Your mention of "lucky" makes me think that your problem is similar to mine actually. It's a shame that that tip did not work. Perhaps this output will give you (or anyone) some ideas on other possible fixes.

Once again, thanks for your help.

Cheers,

Scott

yprum · 2010-01-24 20:15:01

I think I've been suffering of something similar, Scott. Today I managed to solve it. IMHO there's been a problem with dhcp and no IP can be obtained then. I couldn't even get it with wired connection.

Today I connected instead of using dhcp a static IP address for my laptop. And it work perfectly normal. With that connection I have pacmanized the laptop ($ sudo pacman -Syu) and happily there were some new updates for dhcp packages. After that I restarted (old habit) and it works as some months ago.

I'm afraid I can't help much more... But maybe you should try this and see what happens, at least to check if the problem is with dhcp... it will not brake anything at all.

BTW, in order to make the connection with staticIP I've used Wicd as usual.

ScottArch · 2010-02-14 12:30:05

Hi folks,

An upgrade to the dhcp(d) program fixed all the issues. Happy Arching...

Scott

Arch Linux

#1 2010-01-22 09:28:58

[Solved] Several installs and issues with DHCP issue every time.

#2 2010-01-23 12:06:13

Re: [Solved] Several installs and issues with DHCP issue every time.

#3 2010-01-23 21:13:16

Re: [Solved] Several installs and issues with DHCP issue every time.

#4 2010-01-24 10:09:36

Re: [Solved] Several installs and issues with DHCP issue every time.

#5 2010-01-24 20:15:01

Re: [Solved] Several installs and issues with DHCP issue every time.

#6 2010-02-14 12:30:05

Re: [Solved] Several installs and issues with DHCP issue every time.

Board footer