Displaying 6 results from an estimated 6 matches for "feliksik".
2014 Dec 05
3
two tinc hosts behind same NAT
Dear all,
I have 3 nodes: A, B and C. C has external IP and A and B are behind NAT.
It turns out A and B route their traffic via the C, which they ConnectTo
with; this instead of getting connection details from one another and
contacting eachother directly (mesh style). The reason is, as I conclude
from tincd debug output, is that they see the peer as having a minimum MTU
of 0. I suspect this is
2014 Dec 05
0
two tinc hosts behind same NAT
...,
Which version are you using? I have similar issues with the newest 1.1pre10.
Did you check out the ?LocalDiscovery? option?
For 1.1, you also can get more information about the actual connection mode by using the ?info [node]? command.
Cheers,
Steffen
> Am 05.12.2014 um 12:26 schrieb Eric Feliksik <feliksik at gmail.com>:
>
> Dear all,
>
> I have 3 nodes: A, B and C. C has external IP and A and B are behind NAT.
>
> It turns out A and B route their traffic via the C, which they ConnectTo with; this instead of getting connection details from one another and contac...
2015 Jan 08
1
High-performant tinc (without encryption?)
I am looking to connect edge-routers in a VPN over the Internet, with
requirement:
- Mesh
- NAT-traversing
- 500 mbit throughput.
I'm using Tinc 1.0.23 and it does this very nicely (I think I could also
use 1.1, once it's considered stable) except for the througphut: the
edgerouters cannot encrypt this fast. So I want to relieve the edge routers
from this responsibility.
If the end hosts
2015 Feb 02
0
Tinc1.1 generates Port automatically when port is occupied
On Mon, Feb 02, 2015 at 07:46:11PM +0100, Eric Feliksik wrote:
> I like the config generator of tinc 1.1! An issue to consider on the
> default behavior:
>
> It turns out 'tinc -n mynet init mynodename' makes up a default Port=...
> when the standard port is taken:
> "Warning: could not bind to port 655. Tinc will instea...
2015 Feb 09
1
Tinc1.1 generates Port automatically when port is occupied
> The goal is to create a working setup as easily as possible.
>
This is going fairly well with 1.1 ;-) thank you.
> - if people are able to read it, you can just as well leave it to a
> warning
> > and suggest running again with a --autoport flag to enable automatic port
> > generation
>
> I'm sure I will get some emails from people complaining that if tinc
2015 Feb 02
2
Tinc1.1 generates Port automatically when port is occupied
I like the config generator of tinc 1.1! An issue to consider on the
default behavior:
It turns out 'tinc -n mynet init mynodename' makes up a default Port=...
when the standard port is taken:
"Warning: could not bind to port 655. Tinc will instead listen on port
22911".
It is nice that this is autodetected and warned, but I wonder whether it is
nice to let this