| Summary: | net-misc/dhcpcd-3* can't get info by name (dhcpcd -I seyko) | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Sergey Ya. Korshunoff <seyko2> |
| Component: | Current packages | Assignee: | Roy Marples (RETIRED) <uberlord> |
| Status: | RESOLVED NEEDINFO | ||
| Severity: | normal | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Sergey Ya. Korshunoff
2007-05-18 08:33:39 UTC
dhcpcd-2.x didn't set Client ID correctly, dhcpcd-3.x does. If you capture a wireshark trace of both dhcpcd-2.x and 3.x you can clearly see this. Re-open if you disagree, attaching the wireshark traces. (In reply to comment #1) > dhcpcd-2.x didn't set Client ID correctly, dhcpcd-3.x does. > > If you capture a wireshark trace of both dhcpcd-2.x and 3.x you can clearly see > this. > > Re-open if you disagree, attaching the wireshark traces. In my case: - with dhcpcd 3.xx Client ID is different each time and Client ID looks like random item (no any correlation with -I parameter) - with dhcpcd 2.xx Client Id is -I parameter prefixed with \000 PS; how to use wireshark to get a trace? |