On Sat, Jun 11, 2016 at 10:27:53PM +0200, Sven Eckelmann wrote:
The replies from gateway server to gateway client are usually sent via unicast packets. This only works when the destination address for the reply is already known to the translation table. But usually the gateway replies are in response to the first known contact from a device to the gateway server. So it can happen that the TT entry was not yet created.
The gateway server has therefore use broadcast as fallback when the entry is not yet known. This makes the first responses from a DHCP server to a DHCP client more robost.
Signed-off-by: Sven Eckelmann sven@narfation.org
This is completely untested. The RFC was submitted to better explain a problem to Antonio. This problems was noticed in real world setups but these patches were not yet tested in these setups.
Hm, I'm wondering what kind of overhead implications this could have in larger mesh networks.
Didn't TT support temporary entries? Could the gateway server inject them into its global translation table after parsing an incoming DHCP packet?