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
On Fri, Dec 03, 2010 at 10:16:34PM +, Barak A. Pearlmutter wrote:
or, if you wait a few months, i'll scrape up an hour to work up that
fix...
Today I've cloned the repo, but a fix is already there!
Thanks.
Cheers
--
Enrico Tassi
--
To UNSUBSCRIBE, email to
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
On Mon, 06 Dec 2010 12:41:01 +, 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.
Thanks, updated in the package's svn repo!
Cheers,
gregor
--
.''`.
On Thu, 02 Dec 2010 15:49:48 +0100, Enrico Tassi wrote:
iodine-start-client removes the default route replacing it with a default
route
that passes trough the tunnel.
## Remove default route via local router
ip -4 route del default via ${router} || ${continue_on_error}
Just after
Thanks for your bug report, and I agree with your suggestion.
Barak, what do you think about it?
sound reasonable. send a patch! (the repo is replicated as
github.com/barak/iodine-client so you don't even need to send the
patch, just a pull req.)
or, if you wait a few months, i'll scrape up
Package: iodine
Version: 0.6.0~rc1-2
Severity: normal
iodine-start-client removes the default route replacing it with a default route
that passes trough the tunnel.
## Remove default route via local router
ip -4 route del default via ${router} || ${continue_on_error}
Just after that line
7 matches
Mail list logo
