Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
being able to choose arp implementation #750
This enables someone to use a slightly different ARP implementation (named
The common functions to construct a stack,
This again shows to me how hard it is to use mirage in a modular way -- both tcpip.arpv4 and arp.mirage have the very same interface, but nevertheless we need to specify two devices, and in order to make it usable these devices need to live in the mirage cli. This means that the mirage cli has global (closed) knowledge over all devices, and using custom bits and pieces is hard (without modifying mirage.ml). Earlier I used to modify main.ml, but this is very painful if you run a handfull of unikernels.
Another issue, while being here, is optional arguments to the mirage functions: not all respect all, thus deciding globally on a specific arp/udp/time/clock is rather hard. I suspect we should follow the
I currently use this branch for my unikernels (nqsb.io/ns.nqsb.io/btc-pinata/...) (was tired of way too many ARP timeout log messages).