ref: a4fa14a9d8f604d3e1eb409091b4f0d879f9cf97
parent: b76d35401c0a056911aa192d4e4e6d86a15efa50
author: cinap_lenrek <cinap_lenrek@felloff.net>
date: Sat Apr 15 14:00:34 EDT 2023
ip: generalize Rproxy route handling, allowing non point-to-point arp proxy Generalize the arp proxy code, so one can create specific routes for ip ranges that we want to arp proxy for, not just for point-to-point interface routes. as we have source specific routes, this also gives some control over which requester we will reply to. one example for this is a vps where we booked another ip address on the ethernet, that we want to route into a vpn tunnel. the new ip is in subnet of the public ethernet interface, so all we now need todo is add a route for that ip into the vpn tunnel and set the proxy flag "y", and we will respond to arp for that ip on the public ethernet interface.