1 May
2017
1 May
'17
1:24 p.m.
Interesting concept. Someday if we have enough memory I may try it, but
right now amprgw (an old machine) has only 4 GB of memory. It'd die swapping.
At the moment, I use the ipfw firewall to filter registered addresses; that saves
several context switches.
- Brian
On Mon, May 01, 2017 at 07:16:58PM +0200, Rob Janssen wrote:
With "only" 16 million addresses in AMPRnet,
why don't you use a 16-million entry array
holding the next hop for each IP in 44.x.x.x or zero for those addresses that have no
tunnel?
Then you only need a single index operation to get the next hop for a packet.
That requires 64MB of memory to store, hardly a significant amount today.
And it can double-up as the filter to forward traffic only to/from registered addresses.
Of course the update operation becomes more expensive, but it could probably be done
in-place
without disrupting packet forwarding. Or you could build a second table and then switch
to it after the build is complete (requiring 128MB).
Rob
_________________________________________
44Net mailing list
44Net(a)hamradio.ucsd.edu
http://hamradio.ucsd.edu/mailman/listinfo/44net