<div dir="ltr">Running a DHCP server over a tinc VPN operating in router mode is a very weird setup. In theory one *might* be able to make it work, but since every node needs to be statically configured with tinc routing information anyway ("Subnet" configuration), that doesn't sound very useful to me.<br></div><div class="gmail_extra"><br><div class="gmail_quote">On 30 August 2016 at 11:56, <span dir="ltr"><<a href="mailto:albi@life.de" target="_blank">albi@life.de</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">> If you're using a TAP interface (i.e. layer 2, Ethernet) combined with router mode (an unusual setup, at least on<br>
> Linux),<br>
<br>
</span>Thanks,<br>
DeviceType = tap<br>
does the job.<br>
<span class=""><br>
<br>
> operating at layer 3, therefore tinc will strip any layer 2 header (including the MAC address) before sending the packet<br>
> across the VPN. As a result, changing the MAC address of the virtual interface will have pretty much no effect when<br>
> running in that mode.<br>
<br>
</span>Yes, but I like to run a central dhcp Server inside tinc vpn (relays will use the server) and the dhcp server will not<br>
start without mac address. isc-dhcp-server. Now it works fine.<br>
<br>
<br>
ALBI...<br>
<br>
</blockquote></div><br></div>