search for: subnet_mac

...rwarding database of tinc currently is not aware of vlans, this leads to conflicting subnet entries for the router mac pointing to one of the bridge nodes. Thus, only one subnet will work at a time. To resolve this, please find attached a patch that enables tinc to have the VLAN-id included in its SUBNET_MAC entries. For backward compatibility, adding the VLAN-id to SUBNET_MAC entries needs to be enabled using a configuration option. The patch is based on tinc 1.0.25. Any comments? Regards, M. Braun -------------- next part -------------- A non-text attachment was scrubbed... Name: tinc-add-vlan-f...

...atabase of tinc currently is not aware of vlans, this leads to conflicting subnet entries for the router mac pointing to one of the bridge nodes. Thus, only one subnet will work at a time. > > To resolve this, please find attached a patch that enables tinc to have the VLAN-id included in its SUBNET_MAC entries. > For backward compatibility, adding the VLAN-id to SUBNET_MAC entries needs to be enabled using a configuration option. This is an interesting problem. I wonder how you would solve it if you would have a real (managed) switch instead of tinc to connect the access points and bridge nod...

.../tinc/src/subnet.c --- /tmp/tinc/src/subnet.c 2005-03-31 00:49:40.318462040 +0200 +++ /home/mbarenh/daten/tinc/src/subnet.c 2005-03-31 01:01:54.595834912 +0200 @@ -247,6 +247,10 @@ { cp(); + /* check if we have a subnet */ + if (!subnet) + return false; + switch (subnet->type) { case SUBNET_MAC: snprintf(netstr, len, "%hx:%hx:%hx:%hx:%hx:%hx", @@ -421,10 +425,12 @@ } } else { if(net2str(netstr + 7, sizeof netstr - 7, subnet)) - execute_script(name, envp); - } + execute_script(name, envp); } + + /* do this only if we have a subnet (subnet != NULL) */ + if(subnet)...

Hi, thanks for the feedback. > This is an interesting problem. I wonder how you would solve it if you > would have a real (managed) switch instead of tinc to connect the > access points and bridge nodes together? in the backbone we have HP ProCurve switches and all of them (except for the oldest series from more than 10 years ago) separate their forwarding database per vlan. HP calls