similar to: tinc Digest, Vol 123, Issue 13

Hi, Thank you Guus, I think the /16 solution is the easier to apply so I modified my tinc-up in host A to be like #!/bin/sh ifconfig $INTERFACE 192.168.10.1 netmask 255.255.0.0 a route -a from HOST A shows: Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 0.0.0.0 178.62.128.1 0.0.0.0 UG 0 0 0 eth0 10.129.0.0

Hi, after trying for days I ended up with a working tinc configurazion of 2 subnets, now my goal is to add 2 more subnets and comunicate. I might seem dumb at this point but honestly I don't work in IT or Networking stuff, and so I dont have that deep knowledge. A little explanation of my configuration is HOST A (VPN server) Public IP: 1.2.3.4 tun0 Subnet = 192.168.10.0/24 tun0 IP =

Hello! I'm trying to make a wireless mesh network with b.a.t.m.a.n. protocol, and I would like to secure the wireless links with tinc. My test network is 2 wireless routers with OpenWRT Kamikaze firmware, and the network topology is the following: |CLIENT|eth0: 192.168.180| <--> |eth0: 192.168.1.1|MESH-NODE|ath0: 192.168.5.54| <~~> |ath0: 192.168.5.51|GW|eth1: 192.168.1.51|

Hi! Me and two friends are trying to get a VPN working, but we cant get routing between two tunnels. This is how it looks, all servers (192.168.*.1) are running IP Masquerade to enable the other computers behind them to access the internet. Both elayne and glenn are connecting to melc, and the tunnel between melc and glenn are running TCPOnly because that glenn doesnt have a public IP (it's

Hello Maxim, thanks for stepping in ! so, I am not even sure how it works for commit rights, because the people I was in touch with now forked the project to LEDE. Also, I always committed to OpenWrt packages but I see my commits are there also for LEDE. If you are on the mailing list of the OpenWrt/LEDE community you should understand how this is going to work in the future. I have no idea.

Hello Maxim, did you send the pull request ? Please send an email to the list when you do thank you Saverio 2016-11-05 10:09 GMT+01:00 Saverio Proto <zioproto at gmail.com>: > Hello Maxim, > thanks for stepping in ! > > so, I am not even sure how it works for commit rights, because the > people I was in touch with now forked the project to LEDE. > > Also, I always

Saverio, it looks I'm using tinc on OpenWRT packaged by you) Thank you for it Is something there in that task, what is harder than https://wiki.openwrt.org/doc/devel/packages ? Anyway, I want to try On Thu, Nov 3, 2016 at 5:57 PM, Guus Sliepen <guus at tinc-vpn.org> wrote: > On Thu, Nov 03, 2016 at 03:43:42PM +0100, Saverio Proto wrote: > > > I am not using OpenWrt a

Hi, Guus I don’t quite understand what you describe below, to me, no matter tinc or any other router/PC get an IP packet, it will go to check with its route table, to match the destination IP against the route table for the next hop, if I put "ip route add default via <C’s VPN IP address> dev $INTERFACE", I thought tinc will match the packet’s destination IP to the “default”, and

1. Compress should be in your hosts file, not your config file. 2. Since its a low-end CPU on the router, try using Compression=10 or 11 (fast/best lzo); I use 9 (max zlib) on my ASUS OpenWRT routers & ClearOS boxes. 3. If you're using Backfire OpenWRT, you should be able to use the version of tinc compiled in trunk http://downloads.openwrt.org/snapshots/trunk/ On 9/20/2010 5:22 PM,

Me and my son are running Tinc over 5 nodes, 3 of them got public address and we using them as server. Each node has its own Lan subnet 192.168.0.0/24. Originally we ran network on Openwrt routers with Tinc many years without any problem, but due to limited RAM on routes and change of one router to not Openwrt supported model, we decided to transfer Tinc installation on Raspberry Pi-s in LAN. In

> I have a * box with 2 nics in the following setup: > > Internet > | > 192.168.5.253 (firewall) > | > 192.168.5.xxx network (gw 192.168.5.253) > | > 192.168.5.10 (* nic 1) > 192.168.6.10 (* nic 2) > | > 192.168.6.xxx network > > The netmask for both networks is 255.255.255.0 > > The 192.168.6.xxx networks has a 48 port switch solely for the use

On Thu, Nov 03, 2016 at 03:43:42PM +0100, Saverio Proto wrote: > I am not using OpenWrt a lot anymore, and it is becoming difficult to > me to test quickly the tinc package and update OpenWrt when a new tinc > release is out. > > does anyone wants to step in as the new package Maintainer ? Thank you very much for maintaining the OpenWrt package up to now! -- Met vriendelijke

On Tue, Jan 19, 2016 at 07:40:34PM +0300, Yazeed Fataar wrote: > I have setup previously a few nodes running on Ubuntu. And work fine. Im > trying it now in openwrt and cant get tun interface. When I do "lsmod | > grep tun" I cant see tun interface. Do you know how to fix this? Does "modprobe tun" help? If not, it could be your kernel does not come with a tun module,

With pleasure we announce the release of tinc version 1.0.20. Here is a summary of the changes: * Use /dev/tap0 by default on FreeBSD and NetBSD when using switch mode. * Minor improvements and clarifications in the documentation. * Allow tinc to be cross-compiled with Android's NDK. * The discovered PMTU is now also applied to VLAN tagged traffic. * The LocalDiscovery option now

With pleasure we announce the release of tinc version 1.0.20. Here is a summary of the changes: * Use /dev/tap0 by default on FreeBSD and NetBSD when using switch mode. * Minor improvements and clarifications in the documentation. * Allow tinc to be cross-compiled with Android's NDK. * The discovered PMTU is now also applied to VLAN tagged traffic. * The LocalDiscovery option now

With pleasure we announce the release of tinc version 1.0.23. Here is a summary of the changes: * Start authentication immediately on outgoing connections (useful for sslh). * Fixed segfault when Name = $HOST but $HOST is not set. * Updated the build system and the documentation. * Clean up child processes left over from Proxy = exec. This version of tinc is compatible with 1.0pre8, 1.0

With pleasure we announce the release of tinc version 1.0.23. Here is a summary of the changes: * Start authentication immediately on outgoing connections (useful for sslh). * Fixed segfault when Name = $HOST but $HOST is not set. * Updated the build system and the documentation. * Clean up child processes left over from Proxy = exec. This version of tinc is compatible with 1.0pre8, 1.0

This may help... I see you're using a mix of the old and new tools. You could try use 'route' with ipconfig rather than 'ip route'. Or you could use 'ip link' instead of ipconfig. Mike Sent from my iPhone On 26 Apr 2018, at 4:59 am, Kvetoslav Jansík <kjansik at gmail.com<mailto:kjansik at gmail.com>> wrote: Me and my son are running Tinc over 5 nodes, 3

El 12 de febrero de 2016 16:51:59 CET, Eric Yau <ericyaukhy at hotmail.com> escribi?: >Hi All, > > > >I am trying to setup the site-to-site VPN with TINC for connect my home >network to company network. Here is the IP allocation and configuration >for >your reference. > > > >Home PC (192.168.1.2) ?-----? Home (OPENWRT Router, 192.168.1.1, >10.0.0.1)

I include 1.1 in my personal LEDE builds by adding the following to the makefile, in addition to changing the version: https://github.com/rmounce/openwrt-packages/commit/bd69c5dcd4428f2684e023462f23ec2dc7095041 +libncurses +libreadline + --with-curses \ + --with-readline Regards, Ryan Mounce On 18 December 2017 at 06:41, eldad hadas <eldadh at hadasbros.com> wrote: > > ----------