1 |
I upgraded from net-misc/dhcpcd-3.2.3 to net-misc/dhcpcd-4.0.1-r1. I noticed |
2 |
that the vram USE flag is now removed and the compat USE flag added (to |
3 |
enable command line compatibility with the dhcpcd-3.x version). |
4 |
|
5 |
Unfortunately, this change was also noticed by my router, which will no longer |
6 |
serve the static IP address that I have set up on it for my laptop. I recall |
7 |
a similar problem occurring with a previous version and the solution was to |
8 |
add the vram USE flag. I could of course ring up the router manufacturers |
9 |
and have a go at their router implementation - but hey, they may just find my |
10 |
behaviour a tad unreasonable. ;-) |
11 |
|
12 |
What happens is that without the vram flag the router reads not the MAC |
13 |
address of, say: |
14 |
|
15 |
01:00:1B:2F:A7:01:DF |
16 |
|
17 |
but something like this instead: |
18 |
|
19 |
FD:65:74:68:90:00:01:01:00:0E:95:9F:D7:01:00:1B:2F:A7:01:DF |
20 |
|
21 |
In other words, the router receives a ClientID probably based on the DUID |
22 |
field which is not recognised by the router as the correct MAC. |
23 |
|
24 |
I can set the correct IP address manually at the laptop, but what I'd rather |
25 |
have is a dhcpcd implementation that works with, not against my router and |
26 |
the fields that it expects to read. What shall I do, have a go at the router |
27 |
manufacturer all the same? |
28 |
-- |
29 |
Regards, |
30 |
Mick |