Displaying 20 results from an estimated 600 matches similar to: "LocalDiscovery"
2013 Dec 15
1
graphviz
Hi,
I propose that the "ad-hoc connections" (localdiscovery) are also
displayed in the graph (graphdumpfile) as it is useful for debugging.
I find the command-line tooling a bit cumbersome to find out where the
problem is - maybe a web-interface can be added to tincd? Implementing a
http server is trivial I found out.
Folkert van Heusden
--
Curious about the inner workings of your
2009 Apr 06
2
help needed for freebsd
Hi,
I'm trying to run tinc 1.0.9 on freebsd 7.1-RELEASE-p4.
I tried:
Device=/dev/net/tun0
DeviceType=tun
I tried it without the device-line, i tried the other
devicetype-options, none of them work. With all of them I get the
following error:
30311: open("/dev/net/tun0",O_RDWR|O_NONBLOCK,05024360414) = 3 (0x3)
30311: ioctl(3,TUNSIFHEAD,0xbfbfec58) ERR#45 'Operation not
2010 Nov 22
1
tinc: local address announcements
Hi,
I would like to give the new local address announcements a try. What I
mean is, the functionallity which discovers local vpn-endpoints of a vpn
to which you're already connected but only via a remote endpoint - to
improve speed etc.
Can I pull this version from svn or git somewhere? And does it have
debian stuff in it for easy replacing the debian version? And do I need
to configure
2010 Apr 14
1
ipv6 via tinc
Hi,
At my provider (xs4all) I've got an ipv6 tunnel working. Now I would
like to distribute ipv6 via the tinc tunnel.
My tinc.conf:
------------
Name=server
AddressFamily=ipv4
Device=/dev/net/tun
PrivateKeyFile=/etc/tinc/fvhglobalnet/rsa_key.priv
GraphDumpFile=|/usr/bin/dot -Tpng -o /var/www/htdocs.keetweej.vanheusden.com/stats/tinc-fvh-network-graph.png
Mode=switch
KeyExpire=299
2014 May 20
2
packet loss
Hi,
Something strange is happening at my place: I have lots of packet loss
in my tinc vpn.
Network layout:
laptop --- wifi --- other pc
ping from laptop to other pc OUTSIDE tinc: 0% packet loss
ping from laptop to other pc VIA tinc: 50% packet loss
What could be the cause of that?
Folkert van Heusden
--
Always wondered what the latency of your webserver is? Or how much more
latency you
2009 Feb 18
1
ssh -f & pid
Hi,
Ssh -f forks itself in the background. Very usefull if you would like to
e.g. tunnel munin over ssh. Now it's tricky to terminate one process if
you have multiple running.
It seems that ssh currently (looked at 5.1p1) has no write-pid-to-file
functionality
So I implemented a patch which do so. Tested it a little and it seems to
work. Hopefully it is of any use in my form or inspires the
2014 Aug 26
1
key size
Hi,
Tinc currently allows keys of > 4096 bit during creation.
But when running with those no connection can be setup.
Either there should be a limit set (or a warning at least) during
generation or tincd should not have that limit.
imho, of course.
Folkert van Heusden
--
Afraid of irssi? Scared of bitchx? Does xchat gives you bad shivers?
In all these cases take a look at
2013 Apr 17
0
proposal: unstable l2 mode
Hi,
I propose a configuration file change to the files containing the public
key and the setting for a host:
unstable_network_connection=true/false (enables the following
settings)
unc_backlog_size=x (where x is in MB)
unc_backlog_n=z (where z is number of packets)
unc_resent_interval=y (where y is n seconds, e.g 1.1)
unc_backoff_multi=b (with what factor to multiply y each y
2014 Jul 20
0
incorrect configuration may cause instability
Hi,
When two systems with the same name and key pair try to connect to a
tinc mesh, the whole mesh is dossed.
Situation: a vps is migrated to an other hoster. Access has been
disabled, vps is powered on. Then suddenly after a couple of weeks the
vps is powerd on again causing two vps'es trying to connect with the
same credentials.
I think the result should be that neither of those two nodes
2010 Nov 22
7
local address announcements
Hi everyone,
you can find the current version of my enhanced tinc using subversion:
svn://tardyon.mon-clan.de/tinc
I allowed anonymous read access, so feel free to download the sources.
Unfortunately, my enhancements are based on a rather old git-checkout from
Guus.
The version should run under windows and Debian/Ubuntu.
Best,
Daniel
-----Original Message-----
From: folkert [mailto:folkert
2017 Feb 14
2
LocalDiscovery flip flopping and network design tips
On Tue, Feb 14, 2017 at 1:46 PM, Guus Sliepen <guus at tinc-vpn.org> wrote:
> On Tue, Feb 14, 2017 at 11:21:34AM -0500, James Hartig wrote:
>
>> Those 2 boxes are in the same subnet and have addresses of 10.240.0.4 and
>> 10.240.0.5, respectively, on their eth0 interface. Port 655 on tcp and udp
>> is open to the world. The tinc_test_2 box has a ConnectTo of
2004 Aug 06
3
protocol description
Hi,
Do you have any documentation on the protocol used by the icecast-server?
I wrote a tool for multiplexing (proxying) shoutcast-sessions and I would
also like to convert it for icecast-sessions. This shoutcastproxy makes it
possible to listen with a couple of people to a session while only 1 is
retrieved from a shoutcastserver
(http://www.vanheusden.com/shoutcastproxy/).
<p>Folkert van
2004 Aug 06
3
protocol description
Hi,
Do you have any documentation on the protocol used by the icecast-server?
I wrote a tool for multiplexing (proxying) shoutcast-sessions and I would
also like to convert it for icecast-sessions. This shoutcastproxy makes it
possible to listen with a couple of people to a session while only 1 is
retrieved from a shoutcastserver
(http://www.vanheusden.com/shoutcastproxy/).
<p>Folkert van
2004 Aug 06
1
protocol description
> > Do you have any documentation on the protocol used by the icecast-server?
> > I wrote a tool for multiplexing (proxying) shoutcast-sessions and I would
> > also like to convert it for icecast-sessions. This shoutcastproxy makes it
> > possible to listen with a couple of people to a session while only 1 is
> > retrieved from a shoutcastserver
> >
2017 Feb 14
0
LocalDiscovery flip flopping and network design tips
On Tue, Feb 14, 2017 at 1:22 PM, Etienne Dechamps <etienne at edechamps.fr> wrote:
>
> Can you specify which version of tinc you're using? There are vast differences in the way LocalDiscovery works between 1.0 and 1.1. The former uses broadcast, the latter unicast to explicitly advertised local addresses.
I'm using tinc 1.1pre14. I noticed there's an option,
2004 Aug 06
1
protocol description
> Icecast will already relay an icecast or a shoutcast stream for
> you. And the client (listener) protocol is the same.
Is there any description of this protocol then? I'm having some troubles
getting things to work.
<p>Folkert van Heusden
+--------------------------------------------------------------------------+
| UNIX sysop? Then give MultiTail (
2010 Nov 22
1
weird routing issue
Hi,
I have the following tinc grid:
http://keetweej.vanheusden.com/stats/tinc-fvh-network-graph.png
Now a funny thing happens: bpsolxp routes traffic to clientbp via
'server', not directly. Both run 1.0.13. Bug?
Folkert.
--
Nagios user? Check CoffeeSaint, the versatile nagios status display-
monitor. http://vanheusden.com/java/CoffeeSaint/
2013 Jul 21
2
Possible improvements to LocalDiscovery
LocalDiscovery works by sending some of the MTU probe packets to the
broadcast address (255.255.255.255). If the destination node receives
one of these packets, it will update its UDP cache and reply, thus the
two nodes will start using their local addresses to communicate.
Now, I see two problems with this approach:
- In case the two nodes are behind the same NAT and can reach other
*but*
2001 Jun 18
2
not sure how to setup ext3 on a slackware 7.1 system
Hi all,
On my slackware 7.1 system, in rc.S fsck is started.
In fstab there's the following line:
/dev/hda2 / ext3 defaults,noatime 1 1
from the readme I figured that I should put the line
append="rw rootflags=journal=102"
in lilo.conf
The system boots up, but I get the error message that the
root partition is already rw.
Should I just skip the filesystem
2010 Feb 05
1
ssh -f and pid
I'd like to second the patch -- or functionality like it -- that
Folkert van Heusden proposed twelve months ago for the distribution.
Without ssh -f returning the pid to the caller, numerous daemon and
script monitor packages can't manage ssh, as they can countless other
daemons that properly return pid. A monitor needs to record the pids
of ssh processes it has started to kill them or