[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[lwip-devel] [task #13508] Implement IPv4 Address Conflict Detection
|
From: |
Simon Goldschmidt |
|
Subject: |
[lwip-devel] [task #13508] Implement IPv4 Address Conflict Detection |
|
Date: |
Mon, 13 Aug 2018 15:29:55 -0400 (EDT) |
|
User-agent: |
Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/68.0.3440.106 Safari/537.36 |
Follow-up Comment #5, task #13508 (project lwip):
OK, from reading the code, it looks mostly ok. Here are my thoughts:
- etharp_input: don't respond to "from_use" -> how do we defend? This needs a
description in etharp_input
- some C++ comments slipped in
- drop the //--- lines
- we *need* 2 instances when using DHCP and AutoIP or else defend/retreat
won't work on an AutoIP which is in passive use after getting a DHCP address
-> e.g. embed the ACD struct into struct AutoIP and DHCP and don't call
directly into the AutoIP module from etharp_input.
_______________________________________________________
Reply to this item at:
<http://savannah.nongnu.org/task/?13508>
_______________________________________________
Message sent via Savannah
https://savannah.nongnu.org/