diff options
author | Tom Gundersen <teg@jklm.no> | 2014-07-03 22:47:51 +0200 |
---|---|---|
committer | Tom Gundersen <teg@jklm.no> | 2014-07-03 22:55:05 +0200 |
commit | 4958aee4977f325be19f0e1e4b424922c3cada5f (patch) | |
tree | 29fdfb0dd66be1deb4a23ea52cec9263299fa6e5 /src/tmpfiles | |
parent | 393c0c5e64d0cb85ce14f25a06fa8958c9e119e7 (diff) |
networkd: properly track addresses when first added
When doing a NEWADDR, the reply we get back is the NEWADDR itself, rather
than just an empty ack (unlike how NEWLINK works). For this reason, the
process that did the NEWADDR does not get the broadcast message.
We were only listening for broadcast messages, and hence not tracking the
addresses we added ourselves. This went unnoticed as the kernel will usually
send NEWADDR messages from time to time anyway, so things would mostly work,
but in the worst case we would not notice that a routable address was available
and consider ourselves offline.
Diffstat (limited to 'src/tmpfiles')
0 files changed, 0 insertions, 0 deletions