Displaying 5 results from an estimated 5 matches for "jmuchemb".
2010 Sep 03
1
[PATCH] New '-o' option to configure server or hosts from command line
...is patch is against stable branch. Merging this patch to the 1.1
branch is trivial.
I use this patch on my Debian for several weeks.
Here is the ifupdown script I use (some information are obfuscated with
'X' or 'Y'):
#!/bin/sh -e
IP=X.X.X.X
post_up () {
[ -e /sys/class/net/jmuchemb ] && return
set -- -d -o ConnectTo=srv -o srv.Address=$IP \
-o ConnectTo=srv2 -o srv2.Address=Y.Y.Y.Y
case $LOGICAL in
wifi-amuchemb)
set -- -o ConnectTo=srv2 -o srv2.Address=192.168.1.1
;;
wifi-jmuchemb|eth-jmuchemb)
set -- -o ConnectTo=sr...
2012 Jun 26
1
Segmentation fault with latest 1.1 revision
Hello,
I am trying 1.1 branch and I experience a segmentation fault upon ALRM signal.
This looks like a race condition.
I have my tincd daemon instantiated manually in if-up.d/jmuchemb (without IF_TINC_NET) and when if-up.d/tinc runs, it sends a ALRM signal that makes tincd crash.
It fails here:
Core was generated by `tincd -D -n jmuchemb -d -o ConnectTo srv -o srv.Address 81.x.y.z -o Connect'.
Program terminated with signal 11, Segmentation fault.
#0 0x000000000040a685 in...
2010 Sep 10
2
Other feature requests
Hello,
Great to see that my patch for new '-o' command-line option has been accepted :)
It was the most important missing feature for me.
But there are other ones I'd like to see implemented:
1. push options to clients (see push/pull options of OpenVPN)
2. automatically execute routing commands to cause all outgoing IP traffic to be redirected over the VPN (see redirect-gateway of
2014 Jul 02
2
Error while waiting for input: Bad file descriptor
Hello,
Thanks to recent fix of 'Failed to decrypt and verify packet' issue by Etienne, I decided to upgrade tinc on a few nodes.
I had to go back to 1.1pre9 immediately because tinc on my laptop didn't survive the restart of other nodes. It aborted with the following message:
Error while waiting for input: Bad file descriptor
I could reproduce the issue. Here is strace output:
2014 Mar 25
1
Routing
Hello,
I think routing could be improved in several ways, at least, there lacks some documentation describing how Tinc routes packets.
In order to test Tinc, I setup the following virtual network:
- tinc 1.1pre9 with ExperimentalProtocol=yes
- use of network namespaces (actually python-nemu[1])
- star topology, where all nodes runs tinc except the center, which I use to filter communications,