search for: setup_vpn_in_socket

You might want to try with https://github.com/gsliepen/tinc/pull/120 - that said, this bug probably doesn't explain everything because tinc is supposed to log a message from setup_vpn_in_socket() anyway, but there's no such message in your log. In addition, I really don't see any way the "Received UDP packet from unknown source" message could be logged if the UDP socket isn't functional. On 14 July 2016 at 05:10, Petr Man <petr at madnetwork.org> wrote: >...

...nk its a hard work to do? > If not i could probably try to do it and propose a patch for that if you > think it is interesting. I think it is relatively easy to do. There are two places in src/net_socket.c where you would have to call setsockopt() with the SO_MARK option: configure_tcp() and setup_vpn_in_socket(). The first one is run for all incoming and outgoing TCP sockets, the second one sets up the UDP sockets. Try it out and see if it really allows you to do the mark-based routing you want. If it works, you can submit a patch or pull request. -- Met vriendelijke groet / with kind regards, Gu...

...hu, Jul 14, 2016 at 8:27 PM, Etienne Dechamps <etienne at edechamps.fr> > wrote: > >> You might want to try with https://github.com/gsliepen/tinc/pull/120 - >> that said, this bug probably doesn't explain everything because tinc is >> supposed to log a message from setup_vpn_in_socket() anyway, but there's no >> such message in your log. In addition, I really don't see any way the >> "Received UDP packet from unknown source" message could be logged if the >> UDP socket isn't functional. >> >> >> On 14 July 2016 at 05:10,...

...output... Petr On Thu, Jul 14, 2016 at 8:27 PM, Etienne Dechamps <etienne at edechamps.fr> wrote: > You might want to try with https://github.com/gsliepen/tinc/pull/120 - > that said, this bug probably doesn't explain everything because tinc is > supposed to log a message from setup_vpn_in_socket() anyway, but there's no > such message in your log. In addition, I really don't see any way the > "Received UDP packet from unknown source" message could be logged if the > UDP socket isn't functional. > > > On 14 July 2016 at 05:10, Petr Man <petr at mad...

I know i'm new to the list but i'd like to propose something for tincd daemon. I'd like to mark all sockets established by a tincd process with a mark passed as an argument in the command line. What could be the purpose of this new option? The goal of this option is to be able to have several tincd process running at the same time using the same port but using different ip. In

Have anything to do with firewall locations, meaning home vs work vs public vs lockdown. Probably not it at all. On Jul 13, 2016 3:22 PM, "Etienne Dechamps" <etienne at edechamps.fr> wrote: > That's strange. Can you post a detailed log from the affected node (run > tincd -d5 -D), especially the initialization phase? > > On 13 July 2016 at 16:17, Petr Man <petr

--- doc/tinc.conf.5.in | 3 +++ src/linux/device.c | 7 +++++++ 2 files changed, 10 insertions(+), 0 deletions(-) diff --git a/doc/tinc.conf.5.in b/doc/tinc.conf.5.in index 2bfd5fe..01f7f81 100644 --- a/doc/tinc.conf.5.in +++ b/doc/tinc.conf.5.in @@ -255,6 +255,9 @@ a lookup if your DNS server is not responding. This does not affect resolving hostnames to IP addresses from the host