similar to: problems with routing via tinc

Hi Folks, Does anyone have a set of config files handy, using tinc in routed/tun mode (preferably DeviceType=utun) I'm particularly interested to see what the tinc-up and tinc-down files should look like when the vpn is not using tap mode. I have this, from my tap (switch mode tinc) , but it doesn't work for tun devices.    ifconfig $INTERFACE inet 10.10.101.2/24 up If I run my

Hey Folks, It seems that Homebrew for some reason arbitrarily decided to banish all of the --devel flavors from all of their installable packages.  I couldn't find any discussion as to why or what they intend to replace the function with. **update;  this is where they decided to do this; https://github.com/Homebrew/brew/pull/5060#issuecomment-428149176 But in the meantime, 1.1pre17 is

Hi, Can anyone explain why a shell-wrapper script of the following form breaks scp? Can this kind of thing be re-worked to fix the breakage? The wrapper does not produce output, and checks a shell.allow file to see if access to a real shell such as bash should be granted. ------------ eg : #!/bin/sh if [ grep $LOGNAME /etc/shell.allow 2>&1 > /dev/null ] then exec -a - /bin/bash

I have 2 nodes nodeA and nodeB I'm using tinc 1.1pre11 -- nodeA(fd80:2015:2105:abcd::1) : $ ip -6 route fd80:2015:2105:abcd::1 dev tun0 proto kernel metric 256 fd80:2015:2105:adcd::/64 dev tun0 metric 1024 fe80::/64 dev eth0 proto kernel metric 256 $ ping6 fd80:2015:2105:abcd::1 PING fd80:2015:2105:abcd::1(fd80:2015:2105:abcd::1) 56 data bytes 64 bytes from fd80:2015:2105:abcd::1:

Hi, I upgraded some of my Tinc nodes from 1.0.8 recently and found something strange. All of a sudden, the vpn would not work as a full-mesh. Certain nodes were not contactable. I re-generated my rsa-keys, and checked my configuration. My vpn uses the following in tinc.conf, as I am routing both ipv4 and v6. === name = node1 mode = switch AddressFamily = any PMTU = 1280 PMTUDiscovery = yes

Hi, I am running Tinc on debian squeeze, when I reboot, the tincd daemon is not running at all, despite having the right link in rc2.d: root at box /etc/rc2.d [9]# ls S03tinc* S03tinc When I do /etc/init.d/tinc start, it works fine. Any idea what is the problem? Best, -- Benjamin Henrion <bhenrion at ffii.org> FFII Brussels - +32-484-566109 - +32-2-4148403 "In July 2005, after

Guus Sliepen [2016-05-24 11:26 +0200] : > On Tue, May 24, 2016 at 08:17:07AM +0200, Niklaas Baudet von Gersdorff wrote: [...] > > A $ cat /usr/local/etc/tinc/klaas/tinc-up > > ifconfig $INTERFACE inet6 fd16:dcc0:f4cc:0:0:1:0:1 prefixlen 80 > > route -6 add -host fd16:dcc0:f4cc:0:0:2:0:1 fd16:dcc0:f4cc:0:0:1:0:1 > > route -6 add -net

Hi Ivo, --On Freitag, 23. Juni 2000 01:15 +0200 Ivo Timmermans <zarq@icicle.yi.org> wrote: > I'm not sure I fully understand your patch. This is not so important since I'm trying to get 1.0pre2 running. Although I had no luck so far, I'll point out what's going wrong at the end of this mail. > For instance, you force a > key exchange when the connection is made,

Hi, I have successfully setup a tinc vpn between two machines, which is great, and now need do the same to a machine behind a firewall (I do not control the firewall, alas). The firewall will allow port 80 out (via an http proxy), so I wish to use GNU http-tunnel (or similar) to tunnel through the firewall. I have also successfully used http-tunnel to tunnel a simple ppp over ssh connection.

You have a typo in your routes: fd80:2015:2105:adcd::/6 abcd vs. adcd On 21 May 2015, at 19:35, Martin <martinmoen at gmail.com<mailto:martinmoen at gmail.com>> wrote: I have 2 nodes nodeA and nodeB I'm using tinc 1.1pre11 -- nodeA(fd80:2015:2105:abcd::1) : $ ip -6 route fd80:2015:2105:abcd::1 dev tun0 proto kernel metric 256 fd80:2015:2105:adcd::/64 dev tun0 metric 1024

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On Thu, 12 Nov 2020, Graeme Tattersall wrote: > > Hi Folks, Hi Graeme, > Does anyone have a set of config files handy, using tinc in routed/tun > mode (preferably DeviceType=utun) I have 'DeviceType = tun', does that qualify? (running on linux) > > > I'm particularly interested to see what the tinc-up and

Hi list, I have a question regarding routing in Tinc 1.1. Please consider the following example of a small network: • 5 nodes: A, B, C, D, E • C and E are nodes with very small bandwidth Meta connection graph: A – B – C – D │ │ └─ E ───────┘ Node configuration: • StrictSubnets = yes • AutoConnect = yes • B has Forwarding = internal, all other nodes have Forwarding = off All nodes

Hello, I already consulted related lists @freebsd.org [1,2] but I have remained unsuccessful to solve the following issue: VPN works for an internal IPv4 subnet, but I doesn't for an internal IPv6 subnet with ULAs. To be honest, I don't have any experience setting up a local IPv6; so I guess that I'm doing something wrong here. For those that know FreeBSD: The main aim is to connect

I can't get IPv6 routing to configure correctly despite everything I've read saying it should This is my network config on a fully-updated CentOS 5.8 system: # cat /etc/sysconfig/network NETWORKING=yes NETWORKING_IPV6=yes HOSTNAME=my.hostname.com GATEWAY=aaa.bbb.ccc.ddd IPV6_DEFAULTGW=2a02:aaaa.bbbb::1 IPV6_DEFAULTDEV=eth0 # cat /etc/sysconfig/network-scripts/ifcfg-eth0

Hi everyone I'm looking for a bit of help I'm fairly new to Linux and completely new to Wine, but I installed Wine on Linux Mint 12 and then installed quickbooks 2003, Quickbooks runs ok but when I exit I get a message "Quickbooks has encountered an error" (Can't remember the rest) after that Quckbooks will not load again until I restart Linux I don't get any error

Hello, I have an old crossword program that runs OK on Win98, WinMe, and XP. I have installed, via yum, wine and wine-devel and the associated dependencies on my Fedora 8 system. I have copied all the files from the program's install floppy to a directory in my home folder, the same as installing it on XP. However, when the program tries to access the word files it fails and says to see

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

Hi List, I'm trying to configure two switches to provide redundancy (i.e. in case one switch goes down), and am wondering if there is a standard way to configure a CentOS box to use different gateways in a bonded interface, depending upon which physical nic is being used? A bit more detail might help answer the "And why do you want to do that?" questions... - Switch 1,

I've been trying out IPv6 networking with tinc and noticed that it will not route smaller segments than /48 If I try to run ip -6 route add aaaa:bbbb:cccc:dddd::/64 dev tun0 I get network unreachable However if I run ip -6 route add aaaa:bbbb:cccc::/48 dev tun0 it works fine Is this is a limitation in tinc or the kernel network stack itself? -------------- next part -------------- An HTML

On 28 July 2015 at 11:08, Michael S. Tsirkin <mst at redhat.com> wrote: > On Tue, Jul 28, 2015 at 10:44:02AM +0100, Graeme Gregory wrote: >> Added the match table and pointers for ACPI probing to the driver. >> >> This uses the same identifier for virt devices as being used for qemu >> ARM64 ACPI support. >> >>