FS#40408 - [dhcpcd] Intel Corporation Ethernet Connection I217-V (rev 05) doesn't get ip Address

Attached to Project: Arch Linux
Opened by Alejandro (mealejan) - Saturday, 17 May 2014, 13:29 GMT
Last edited by Jan de Groot (JGC) - Wednesday, 04 October 2017, 18:22 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To Ronald van Haren (pressh)
Architecture x86_64
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
After connecting the network-cable I don't get an IP-Address. I tried it with NetworkManager and dhcpcd.
You only get a IP-Address when you try a new router.

Additional info:
Linux Kernel 1.3 and 1.4
NetworkManager until 0.9.8.10-1
Dhcpcd 6.3.2-1

Steps to reproduce:
Plug in the cable and wait
This task depends upon

Closed by  Jan de Groot (JGC)
Wednesday, 04 October 2017, 18:22 GMT
Reason for closing:  No response
Comment by Doug Newgard (Scimmia) - Saturday, 17 May 2014, 14:29 GMT
Plug in the cable and wait? That won't work.

What does "You only get a IP-Address when you try a new router." mean?

I'm going to assume you mean kernels 3.13 and 3.14, since 1.3 and 1.4 were long before Arch existed.
Comment by Alejandro (mealejan) - Saturday, 17 May 2014, 14:41 GMT
I have three different routers. When I connect my Laptop to a new one I usually get an ip. Same happens when I change the port of the router to whom I am connected.
Comment by Doug Newgard (Scimmia) - Saturday, 17 May 2014, 14:47 GMT
ok, so when don't you get an IP address?
Comment by Alejandro (mealejan) - Saturday, 17 May 2014, 14:52 GMT
When I change the ports of the router.
Every time I want to reconnect i don't receive one.
For example:
-I got an ip at work. The next day I reconnect my Laptop to the same port and I don't get one. I choose a other port and I get one. Then I connect to the old port and I get one. I tried it with different cables.
Comment by Doug Newgard (Scimmia) - Saturday, 17 May 2014, 14:58 GMT
Are you rebooting? Using ifplugd with dhcpcd? Just NM?
Comment by Alejandro (mealejan) - Saturday, 17 May 2014, 15:04 GMT
Things I tried so far:
1. Configure the system with networkmanager (systemctl enable ...) try to get an ip. Didn't work. Reboot. Wait for ip, didn't get one. Shutdown. Disconnect from power wait. Tried again.
2. Configure the system with dhcpcd (systemctl disable NM enable dhcpcd@enp0s25) repeat procedure from 1.
3. Change naming convention to old eth repeat 1. and 2.
Comment by Ronald van Haren (pressh) - Wednesday, 20 April 2016, 13:00 GMT
Is this still in issue?

Loading...