similar to: [Announcement] Version 1.0.14 released

Hello everyone, Today is exactly 10 years ago that tinc 1.0 was released. I would have hoped to celebrate this by releasing 1.0.22 and 1.1pre8 today, but this will instead happen in one week. Tinc 1.1 is close to becoming stable, and I hope to release 1.1.0 before the end of the year. The main features of tinc 1.1 are the improved security over tinc 1.0, and a much nicer interface that makes it

Hello everyone, Today is exactly 10 years ago that tinc 1.0 was released. I would have hoped to celebrate this by releasing 1.0.22 and 1.1pre8 today, but this will instead happen in one week. Tinc 1.1 is close to becoming stable, and I hope to release 1.1.0 before the end of the year. The main features of tinc 1.1 are the improved security over tinc 1.0, and a much nicer interface that makes it

With pleasure we announce the release of version 1.0.17. Here is a summary of the changes: * The DeviceType option can now be used to select dummy, raw socket, UML and VDE devices without needing to recompile tinc. * Allow multiple BindToAddress statements. * Decrement TTL value of IPv4 and IPv6 packets. * Add LocalDiscovery option allowing tinc to detect peers that are behind the

With pleasure we announce the release of version 1.0.17. Here is a summary of the changes: * The DeviceType option can now be used to select dummy, raw socket, UML and VDE devices without needing to recompile tinc. * Allow multiple BindToAddress statements. * Decrement TTL value of IPv4 and IPv6 packets. * Add LocalDiscovery option allowing tinc to detect peers that are behind the

Hi guys and gals, I just wanted to compile tinc with vde interface, but found src/vde is missing in tar balls of tinc-1.0.16 and tinc-1.0.14. I remember once I have compiled vde on tinc-1.0.14. Is it removed intentionally? I couldn't find an update in ChangeLog. Besides, the newest code in git fails to compile, because of a redefined extern static variable in src/vde/device.c. I need to

With pleasure we announce the release of tinc version 1.1pre5. Here is a summary of the changes: * Fixed long delays and possible hangs on Windows. * Fixed support for the tunemu device on iOS, the UML and VDE devices. * Small improvements to the documentation and error messages. * Fixed broadcast packets not reaching the whole VPN. * Tincctl now connects via a UNIX socket to the tincd

With pleasure we announce the release of tinc version 1.1pre5. Here is a summary of the changes: * Fixed long delays and possible hangs on Windows. * Fixed support for the tunemu device on iOS, the UML and VDE devices. * Small improvements to the documentation and error messages. * Fixed broadcast packets not reaching the whole VPN. * Tincctl now connects via a UNIX socket to the tincd

With pleasure we announce the release of version 1.0.10. Here is a summary of the changes: * Fixed potential crashes during shutdown and (in rare conditions) when other nodes disconnected from the VPN. * Improved NAT handling: tinc now copes with mangled port numbers, and will automatically fall back to TCP if direct UDP connection between nodes is not possible. The TCPOnly option

With pleasure we announce the release of version 1.0.10. Here is a summary of the changes: * Fixed potential crashes during shutdown and (in rare conditions) when other nodes disconnected from the VPN. * Improved NAT handling: tinc now copes with mangled port numbers, and will automatically fall back to TCP if direct UDP connection between nodes is not possible. The TCPOnly option

From: "Anthony G. Basile" <basile at opensource.dyc.edu> The current configure.in file does not correctly make use of these macros. The resulting configure file will therefore enable an item even if --disable-FEATURE is given. This patch restores the intended behavior. --- configure.in | 50 +++++++++++++++++++++++++++++++++----------------- 1 files changed, 33 insertions(+),

Hi all, I have a qemu-system-arm machine that I am currently starting using: qemu-system-arm -M versatilepb -nographic \ -hda img.qcow2 \ -net vde,vlan=0,sock=/var/run/qemu-vde.ctl \ -net nic,vlan=0,macaddr=52:54:00:12:34:22 \ -kernel vmlinuz-2.6.18-6-versatile \ -initrd initrd.img-2.6.18-6-versatile \ -append "root=/dev/sda1

Hi Erik, thanks for the solution provided. I tried that but unfortunately it spits out this error message: > Traceback (most recent call last): > File "/usr/share/virt-manager/virtManager/engine.py", line 588, in run_domain > vm.startup() > File "/usr/share/virt-manager/virtManager/domain.py", line 150, in startup > self._backend.create() >

I''m poring through the Dragonfly source code right now, trying to get a handle on how to apply the following technique there: Client uploads a Zip archive containing N images, PDF files, text files, etc. When that file arrives at the server, but before it is stored as an attachment to the current object, the Zip is burst open, contents are iterated over, and each contained file is saved

Hi, i''have started a discussion in dragonfly google group because of problems using dragonfly image processing gem with wicked_pdf. http://groups.google.com/group/dragonfly-users/browse_thread/thread/c8602007c3e43753 In these post I have linked to a public github project for testing this issue. There''s also a heroku app: http://wicked.heroku.com/projects.pdf debug mode of

On Wed, Sep 23, 2015 at 09:07:16AM +0200, borg at uu3.net wrote: > I wonder if someone here performe such large scale > tinc-vpn tests.. There are platforms like Imunes or CORE > to do generic Ethernet and IP testing and routing, but I found > that at least on Imunes it is problematic to start TAP iface > on vimage on FreeBSD (at least 4.11 with I use). What do you want to do

Facter 1.6.2 is a maintenance release containing fixes, updates and refactoring. Primary new features include updated facts for DragonFly BSD, Amazon Linux and Windows. A few other facts have been added and updated. Full release notes below. This release is available for download at: http://puppetlabs.com/downloads/facter/facter-1.6.2.tar.gz See the Verifying Puppet Download section at:

Hi, Can any one explain what the following can be used for ? I want to know , so that i can use it in the future :-) > Add support for VDE through libvdeplug. > > When compiled with vde/device.c, tinc will connect to a vde_switch instance > instead of using a tun/tap device. Perry

Hi all, I use libvirt-go in my agent to attach rbd volumes. I ofen suffer the issue of incosistent of domain dump xml and domain persistent xml file. For example, when I try to attach volume, the the domain by ?virConnectListAllDomains? api from libvirt tell me the vdf or 0x0a is empty, but when attach it with the vdf device or 0x0a address, qemu return the error duplicated with vdf or PCI

This patch to the balloon driver eliminates the need for a user-space program to slosh memory between domains and xen. This uses a proc file at /proc/xen/memory_target. When read it reports memory the domain owns in bytes. Writing a new value to the memory_target proc file will cause the domain to exchange memory with xen to reach the target. A xenolinux domain cannot grow bigger than it was

The Wine development release 1.5.6 is now available. What's new in this release (see below for details): - Automatic installation of the Mono add-on package. - Control panel applet for joysticks. - Device bitmap rendering now done through the DIB engine. - Support for video rendering through DirectX (VMR-9). - First steps towards a D3D shader compiler. - Build fixes for DragonFly