1 |
I just updated my older ~amd64 machine and I'm seeing weird behavior when |
2 |
using nfs and ssh services to communicate with my newer ~amd64 machine. |
3 |
|
4 |
Both mount.nfs and ssh are telling my newer machine that they are talking |
5 |
from an obsolete ip address :/ |
6 |
|
7 |
To clarify: my wireless router dispenses ip addresses based on some formula |
8 |
I don't understand, but it clearly depends on which method each localhost |
9 |
uses to contact the wireless router. |
10 |
|
11 |
i.e. does it use dhcpcd, or dhcpd, or some other method invoked by systemd |
12 |
or maybe wpa_supplicant? |
13 |
|
14 |
So, looking at the system logs on the newer machine, I can see that the older |
15 |
machine is advertising (somehow) that it's still using an ip address that *was* |
16 |
correct in the past, but now my wireless router has assigned a newer one due to |
17 |
some updated package (no idea which package). |
18 |
|
19 |
To be specific: nfs.mount is claiming that its clientaddr is the old address, |
20 |
and ssh is claiming that its rhost is also the same old address. |
21 |
|
22 |
So, how are these two different packages claiming the same, obsolete, ip address? |
23 |
Where are they getting it? It must be cached somewhere on the older machine, but |
24 |
where? |