similar to: Multicast and receive filtering in TUN/TAP

Please see the following thread to get some context on this http://marc.info/?l=linux-netdev&m=121564433018903&w=2 Basically the issue is that current multi-cast filtering stuff in the TUN/TAP driver is seriously broken. Original patch went in without proper review and ACK. It was broken and confusing to start with and subsequent patches broke it completely. To give you an idea of

Please see the following thread to get some context on this http://marc.info/?l=linux-netdev&m=121564433018903&w=2 Basically the issue is that current multi-cast filtering stuff in the TUN/TAP driver is seriously broken. Original patch went in without proper review and ACK. It was broken and confusing to start with and subsequent patches broke it completely. To give you an idea of

yes, ip_forward was turned on. iptables is defaulted to ACCEPT policy on all the 3 chains. On Sat, May 14, 2016 at 1:24 AM, Guus Sliepen <guus at tinc-vpn.org> wrote: > On Sat, May 14, 2016 at 12:06:51AM +0800, Terry T wrote: > > > I have a Debian 8 64-bit machine set up as a server and apt-got the tinc > > package. I configured tinc as a bridge and everything seems

This setup is rather complex, so apologies for the length of this mail. I'm also not at all sure where my problem is, so again I apologise if this is the wrong place to ask. I have a raspberry pi sitting in a remote office (hostname 'pi' below), a VPS hosted on someone's cloud (hostname 'vps' below) and my local laptop (hostname 'laptop'). The remote office then

I have a Debian 8 64-bit machine set up as a server and apt-got the tinc package. I configured tinc as a bridge and everything seems normal except that the tunnel does not forward multicast traffic. I used tcpdump to examine the br0, eth0 and tap interfaces. I could see multicast packets on both br0 and eth0, but there is no such packet present on the tap interface. I don't quite know why

Hi, I have seen http://www.tinc-vpn.org/pipermail/tinc-devel/2010-October/000473.html and so tried out for myself to see if multicast would work in tinc using routing mode. I'm using tinc 1.0.19. My test involved sending a ping out on 224.1.1.1 (as 224.0.0.0/24 is a special case), and while I could see the traffic reaching the other tinc daemons, it never seemed to go out to the local

Hi, I got problem while receiving multicast traffic on to my D-Link DFE-520TX PCI Fast Ethernet Adapter. Created bridge interface and attached the eth0 interface (D-link) to the bridge. H1------------------------eth0[LX-Bridge] Started Multicast traffic from H1 to Bridges eth0 port and the "tcpdump" doesn't who any packets If the eth0 interface is detached

On Fri, May 26, 2017 at 09:30:44AM +0800, Bright Zhao wrote: > Due to some routing rotation purpose, I use crontab to add below info: > > 0 * * * * echo Subnet = 54.169.128.0/17 >> /etc/tinc/myvpn/hosts/aws_sgp > 0 * * * * echo Subnet = 54.169.0.0/17 >> /etc/tinc/myvpn/hosts/aws_sgp > 1 * * * * /usr/sbin/tincd -n myvpn -k > 1 * * * * /usr/sbin/tincd -n myvpn

Hi, Guus Thanks a lot for your suggestion, actually I did something else as below. But one question here is if I don’t add "/sbin/ifconfig myvpn 10.0.0.1 netmask 255.255.255.0”, it seems the crontab wouldn’t trigger tinc-up, and then the ip addr of myvpn wouldn’t be configured, then it will prompt the error of "Can't write to Linux tun/tap device (tun mode) /dev/net/tun:

The problem with introducing checksum offload and gso to tun is they need to set dev->features to enable GSO and/or checksumming, which is supposed to be done before register_netdevice(), ie. as part of TUNSETIFF. Unfortunately, TUNSETIFF has always just ignored flags it doesn't understand, so there's no good way of detecting whether the kernel supports new IFF_ flags. This patch

The problem with introducing checksum offload and gso to tun is they need to set dev->features to enable GSO and/or checksumming, which is supposed to be done before register_netdevice(), ie. as part of TUNSETIFF. Unfortunately, TUNSETIFF has always just ignored flags it doesn't understand, so there's no good way of detecting whether the kernel supports new IFF_ flags. This patch

So we can configure a persistent tun and tinc on startup recognize this, tinc uses just present tun without problems ? Can you point me to Tinc-RedHat best practice method to do that please ? Thank you in advance Best Regards Roberto -----Original Message----- From: tinc [mailto:tinc-bounces at tinc-vpn.org] On Behalf Of Guus Sliepen Sent: domenica 24 gennaio 2016 09.53 To: tinc at

Hi, All Due to some routing rotation purpose, I use crontab to add below info: 0 * * * * echo Subnet = 54.169.128.0/17 >> /etc/tinc/myvpn/hosts/aws_sgp 0 * * * * echo Subnet = 54.169.0.0/17 >> /etc/tinc/myvpn/hosts/aws_sgp 1 * * * * /usr/sbin/tincd -n myvpn -k 1 * * * * /usr/sbin/tincd -n myvpn --debug=3 30 * * * * sed -i '/54.169.128.0\/17/d' /etc/tinc/myvpn/hosts/aws_sgp

Hi, I purchased a VPS with OpenVZ with infrastructure installed Centos 6.4 64bit. When I configure OpenVPN for remote access I can not because I do not get loaded into the interface modules tun / tap from console: #cat /dev/net/tun cat: /dev/net/tun: No such file or directory #lsmod | grep tun # # uname -r 2.6.32-042stab079.6 I have to ask for support to those who sold the VPS or can I fix

It is possible for tinc to made a persistent tun/tap or can I configure a persistent tun/tap by hand and tell to tinc to use that virtual interface device without starting up/shutting down tun/tap at every tincd start/stop ? Roberto -------------- parte successiva -------------- Un allegato HTML ? stato rimosso... URL:

Hello everyone! I have a PowerMac running 10.6.8 and I'd love to get it connected to my VPN. However, even by compiling tuntaposx by hand on the said MacPro, I see that the kernel module is apparently built for x86_64 systems: macintosh MacOS ?? pwd /Library/Extensions/tun.kext/Contents/MacOS macintosh MacOS ?? file tun tun: Mach-O 64-bit kext bundle x86_64 Because YES! The system is

The problem with introducing checksum offload and gso to tun is they need to set dev->features to enable GSO and/or checksumming, which is supposed to be done before register_netdevice(), ie. as part of TUNSETIFF. Unfortunately, TUNSETIFF has always just ignored flags it doesn't understand, so there's no good way of detecting whether the kernel supports new IFF_ flags. This patch

The problem with introducing checksum offload and gso to tun is they need to set dev->features to enable GSO and/or checksumming, which is supposed to be done before register_netdevice(), ie. as part of TUNSETIFF. Unfortunately, TUNSETIFF has always just ignored flags it doesn't understand, so there's no good way of detecting whether the kernel supports new IFF_ flags. This patch

I want to run a VPN software inside an lxc guest, but the required TUN/TAP device (/dev/net/tun) is missing in the container. Anyone knows how to enable this device ? Here is the definition XML: <domain type="lxc"> <name>centos</name> <memory unit="MiB">1024</memory> <os> <type>exe</type>

Hi all. I have an OpenVPN server: 2.2.1-1 x86_64 Server config: port 11223 dev tap proto udp tls-server ca keys/ca.crt cert keys/server.crt key keys/server.key dh keys/dh1024.pem server 1.2.3.3 255.255.255.0 push "route 192.168.0.0 255.255.255.0 1.2.3.4" keepalive 10 60 client-to-client duplicate-cn inactive 600 log /var/log/openvpn.log syslog status /var/log/openvpn-status.log user