You are not logged in.
I have an Arch box that's acting as a router for my home network. As I've mentioned elsewhere, I have been using the old network syntax in a new rc.conf to get both my NICs working together - no other method worked when I set the machine up a week or so ago.
Today, I tried again to see if any updates improved on that and discovered that it still doesn't work, but that my problem is different.
Basically, my eth0 config is set up using netcfg to connect via dhcp:
CONNECTION='ethernet'
DESCRIPTION='A basic dhcp ethernet connection using iproute'
INTERFACE='eth0'
IP='dhcp'
DHCP_TIMEOUT=60Whenever I try and connect - whether through net-profiles or netcfg -u eth0-dhcp - it always fails to get an ip address from the cable modem. I have tried increasing the DHCP_TIMEOUT with no improvements.
Whenever I revert to the old syntax in my rc.conf and use that it is always able to get an ip reasonably quickly.
Any ideas on what the problem could be?
Offline
Are you using dhclient or dhcpcd with netcfg? Try using the other dhcp-client in netcfg, there is a setting per profile to use dhclient or not.
I know it has helped me before. HTH.
Last edited by zenlord (2011-08-12 14:13:58)
Offline
Thanks - I'll give that a go.
Offline
Obviously, it's taken me *ages* to get around to this. Mainly because the old network config worked and also because I couldn't be bothered to crawl around moving monitor cables from one computer to another.
However, I did try this today and it appears to have worked - so, thanks for that! :-)
Offline
In all fairness, though, I didn't check to see if any netcfg updates had meant that the previous config now worked - ah well! It's working now and I'm no longer using deprecated config.
Offline