similar to: [PATCH] Use /dev/tap0 by default on BSD if mode != router

Hi, I have two concerns about tinc's behavior regarding MAC addresses in router mode: - Looking at the code, it appears that tinc is always sending each packet with its Ethernet header, even if tinc is operating in router mode. It is my understanding that in router mode, all routing is done at the IP level, thus we do not need Ethernet information. This seems like unnecessary overhead.

--- 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

Below is a patch for vorbis-tools-1.0beta4 ogg123. It adds support for using the rc file (like /etc/ogg123.rc) for configuring the device-options. In addition, comments can be used (when they start a line). My ~/.ogg123rc: default_device=oss default_options=dsp:/dev/audio Please share your comments. Jeremy C. Reed http://www.reedmedia.net/ diff -u

On 25-02-15 15:14, Emil Velikov wrote: > On 24 February 2015 at 09:01, Maarten Lankhorst > <maarten.lankhorst at ubuntu.com> wrote: >> While I've closed off most races in a previous patch, a small race still existed >> where importing then unreffing cound cause an invalid bo. Add a test for this case. >> >> Racing sequence fixed: >> >> - thread 1

If running without `--net', the (global) variable `netname' is NULL. This creates a segmentation fault because this NULL-pointer is passed to strdup: Program terminated with signal 11, Segmentation fault. #0 0xb7d30463 in strlen () from /lib/tls/i686/cmov/libc.so.6 (gdb) bt #0 0xb7d30463 in strlen () from /lib/tls/i686/cmov/libc.so.6 #1 0xb7d30175 in strdup () from

Hi. I created a patch for Bug #4 (ogg123 not honoring /etc/ogg123rc) and uploaded it to Bugzilla, but I have the feeling that the Bugzilla is somewhat neglected... so I just send the patch here. The changes are very simple, one typo (I guess) was fixed (from "/etc/ogg123.rc" to "/etc/og123rc" as it's documented), and I changed an if to a while-loop to make it read the

On 24 February 2015 at 09:01, Maarten Lankhorst <maarten.lankhorst at ubuntu.com> wrote: > While I've closed off most races in a previous patch, a small race still existed > where importing then unreffing cound cause an invalid bo. Add a test for this case. > > Racing sequence fixed: > > - thread 1 releases bo, refcount drops to zero, blocks on acquiring nvdev->lock.

Hello, The code in tinc for BSD device has no way to handle the fact that several tun devices are already used., since it always try to open the specified device which might already be in use. The following patch makes it try to open the various available tun devices before giving up. Hope that helps, -- Ga?l Roualland -+- gael.roualland@oleane.net -------------- next part -------------- diff

While I've closed off most races in a previous patch, a small race still existed where importing then unreffing cound cause an invalid bo. Add a test for this case. Racing sequence fixed: - thread 1 releases bo, refcount drops to zero, blocks on acquiring nvdev->lock. - thread 2 increases refcount to 1. - thread 2 decreases refcount to zero, blocks on acquiring nvdev->lock. At this

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Good morning, I am not sure if this is a known issue or if I should raise as a bug. When using libvirt 1.2.11 on FreeBSD 10.1-RELEASE with bhyve, I have notice that a machine which defines: <interface type='bridge'> <mac address='52:54:00:88:44:08'/> <source bridge='bridge10'/>

On Mon, Apr 30, 2001 at 03:57:25AM +0000, cuBe wrote: > Having some probs with setting up tap0: > > aibo:~# ifconfig tap0 hw ether fe:fd:00:00:00:00 > SIOCSIFHWADDR: No such device > > Now, I;ve checked everthing, and it all seems in order. I have compiled in > theUniversal TAP/TUN support, and Netlink (including CONFIG_NETLINK_DEV), > but to no avil, that error always

On 01/14/2017 06:30 AM, Govert wrote: > Hi, > > I'm trying to control the name of the 'tap0' device that gets created > as I start a domain that uses bridged networking. The XML > specification of the domain contains the following configuration > > <interface type='bridge'> > <source bridge='br0'/> >

Hi All, I have a weird issue I''m not sure how to solve.  I''ve got Xen 3.2.1 working under RHEL 5.2 x86_64 just fine.  I fired off a CentOS 5.2 PV install and everything went smoothly... except that when I fire up the PV, the tap0 for bridging isn''t being created.  This results in the CentOS 5.2 domU''s bridged eth0 only being able to ping the RHEL5

Hello! What is exactly "tap0" in the host ifconfig? Thank you! _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

Hi, I'm trying to control the name of the 'tap0' device that gets created as I start a domain that uses bridged networking. The XML specification of the domain contains the following configuration <interface type='bridge'> <source bridge='br0'/> </interface> The libvirt documentation (

Thanks !! This clarifies completely what is happening. I'll look into running virsh as root/attaching to qemu:///system. Or, perhaps I can 'statically' create tun devices, to which the domains attach when started (although I have no idea weather this is possible). Best, Govert 2017-01-17 20:46 GMT+01:00 Laine Stump <laine@laine.org>: > On 01/14/2017 06:30 AM, Govert wrote:

Package: xen-utils-4.0 Version: 4.0.0-2 Severity: important xend does not start because of a bug in option parsing. Error described here: http://www.gossamer-threads.com/lists/xen/devel/172035 Patch: --- a/tools/python/xen/xend/XendOptions.py Mon Apr 26 12:13:23 2010 +0100 +++ b/tools/python/xen/xend/XendOptions.py Wed Apr 28 16:54:04 2010 +0200 @@ -207,18 +207,18 @@ def

Options given on the command line have precedence over configuration from files. This can be useful, for example, for a roaming node, for which 'ConnectTo' and <host>.Address depends on its location. --- This patch is against stable branch. Merging this patch to the 1.1 branch is trivial. I use this patch on my Debian for several weeks. Here is the ifupdown script I use (some

Resent of mail sent on 28.04. xend: fix bug in option parsing If you enable legacy tcp xmlrpc in xend''s config but omit to enable ssl the following backtrace is generated when starting xend: [2010-04-28 16:09:04 15754] ERROR (SrvDaemon:349) Exception starting xend (''NoneType'' object has no attribute ''rfind'') Traceback (most recent call last): File