Somewhat related to this thread... Martin Kraft had the idea of using policy routing in conjunction with iodine to help address the issue of setting up and tearing down routes. The basic idea being to create a separate routing table (we could request that a label be added to the /etc/iproute2/rt_tables package in iproute2) and then have iodine mark packets destined for the iodine server so that they went through the table.
I just wanted to bring it up, as it might be a good mechanism to give iodine more control over the routing table. tony On 12/06/2010 04:41 AM, Barak A. Pearlmutter wrote: > Okay, I have made the tiny modification needed to address this issue, > and pushed to git://github.com/barak/iodine-client-start.git. > I'm not really sure how useful it will be, since other parts of the > route setup are also non-idempotent, but I don't see how it can mess > things up that wouldn't be fixed by taking the device down and up > again, which is the alternative without the patch. > > --Barak. > -- > Barak A. Pearlmutter > Hamilton Institute & Dept Comp Sci, NUI Maynooth, Co. Kildare, Ireland > http://www.bcl.hamilton.ie/~barak/ > > >
signature.asc
Description: OpenPGP digital signature
