memory leak with vlan tagged traffic in switch mode

[Guus Sliepen]

On Thu, Jun 12, 2014 at 06:52:15AM +0200, Florian Schoedel wrote:

> I am trying to connect two segments with about 4 x 1000 mac addresses 
> (distributed on different vlans). I am always running out of memory on one 
> side. This happens only on the side where the arp requests come from.
> Currently there is no unicast traffic between the sides; only broadcasted 
> arp requests.
> It looks like tincd reserves memory with each arp request which isn't freed 
> afterwards or
> tincd builds internal structures for the arp cache, based on the wrong 
> information from the ethernet header, when I transport 8021q tagged traffic.

Tinc reserves memory for each MAC address it sees. Unfortunately, it's
not too space efficient with those, so if all 4000 MAC addresses are
being seen by tinc, that can easily cause tinc to allocate 1 megabyte of
memory. How much memory do you have and how much do you see tinc use in
your setup?

> If I change my config from switch to hub mode, everything works fine.
> Are there any drawbacks If I use hub mode when there are only two connected 
> sites?

If it's only two sites, there is no drawback to using hub mode.

-- 
Met vriendelijke groet / with kind regards,
     Guus Sliepen <guus at tinc-vpn.org>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://www.tinc-vpn.org/pipermail/tinc/attachments/20140615/f2b36938/attachment.sig>