On Mon, May 1, 2017 at 9:42 AM, Brian Kantor Brian@ucsd.edu wrote:
Three times an hour, a background process fetches the encap routing table from the portal, and if it has changed, signals the router process to update its routing table. The routing table update seems to take about 3 msec during which packets can't be looked up and so are not forwarded.
When the table is updated, does it reload the whole table or touch only the changed routes?
Why is it limited to three times per hour? This seems arbitrarily long when the process itself only takes 3ms. It would be nice for those of us on dynamic IPs if the update frequency was 1 minute* or less. *1 minute is also an arbitrary number--the lower the better.
Rather than (or in addition to) polling the encap table from the portal on a timer, the portal could offer an HTTP longpoll API (or various other push messaging protocols) so that address updates are near instantaneous.
Tom KD7LXL