You are not logged in.
Hello, I dont know why, but my arch linux dont want an IP from DHCP Server when I try to connect to LAN. Everytime it says timed out. On windows the server assigns with no problem. I tried to set a static IP, that was given to windows, but it dont work either. Can anybody know what to do? Thanks in advance.
Last edited by Pjotrik (2009-11-20 14:29:31)
Offline
Which interface are you using, and what is the errormessage you are getting?
Good ideas do not need lots of lies told about them in order to gain public acceptance.
Offline
Its an eth0, during the boot I'm getting message Dhcpcd: Timed out. Here are my settings in /etc/rc.conf :
eth0="dhcp"
INTERFACES=(eth0)
Offline
Check if the driver for your network card is loaded. Helpful commands are hwdetect, lspci, lsmod and modinfo.
Edit: Actually, all you need is lspci -v. Then look for the entry for "Ethernet controller". Ideally it will say something like
02:00.0 Ethernet controller: Attansic Technology Corp. L1 Gigabit Ethernet Adapter (rev b0)
...
Kernel driver in use: atl1
Kernel modules: atl1Last edited by grey (2009-11-07 01:38:00)
Good ideas do not need lots of lies told about them in order to gain public acceptance.
Offline
I believe my driver and network card is working without problems. Because I remember that at home I managed to connect PC with my notebook(I cannot get an IP on notebook) and it was working well. Here is an output from lspci -v :
00:19.0 Ethernet controller: Intel Corporation 82566MM Gigabit Network Connection (rev 03)
Subsystem: Lenovo ThinkPad T61
Flags: bus master, fast devsel, latency 0, IRQ 31
Memory at fe200000 (32-bit, non-prefetchable) [size=128K]
Memory at fe225000 (32-bit, non-prefetchable) [size=4K]
I/O ports at 1840 [size=32]
Capabilities: <access denied>
Kernel driver in use: e1000e
Kernel modules: e1000eLast edited by Pjotrik (2009-11-07 09:56:04)
Offline
Next step is to check that loading the driver worked:
$ dmesg | grep e1000eIf there are no problems, bring up the interface with (as root) "ifconfig eth0 up", then check its state with "ifconfig eth0" or "ifconfig -a". If it looks OK, try to get a lease for the interface using dhcpcd.
Good ideas do not need lots of lies told about them in order to gain public acceptance.
Offline
1) try dhclient instead of dhcpcd. later one is doesnt ever get a lease with my router
2) for static ip you have to configure the interface, a route to the gateway and probably a dns server
rc.conf:
eth0="eth0 192.168.2.20 netmask 255.255.255.0 broadcast 192.168.2.255"
INTERFACES=(eth0)
gateway="default gw 192.168.2.1"
ROUTES=(gateway)resolve.conf:
nameserver 192.168.2.1Offline
Thanks for help, but the problem was with dhcpcd, there is probably some bug. With dhclient there is no problem with assigning IP.
Offline
I'm having the same problem too. eth0 won't connect on a new install of Arch. What a pain in the ass. ![]()
joe@trusktr.io - joe at true skater dot io.
Offline
Please stop pulling up threads with "I have the same problem" posts, especially when the OP solved its problem. You started one yourself already, link to threads that may be interesting from there instead.
Offline
Alright, will do. Sorry.
joe@trusktr.io - joe at true skater dot io.
Offline