Hello Simon, I tried the following on 2.53-test8:
tag-if= set:fixedport, tag:puerto3, tag:switch1
dhcp-range=net:switch1,net:puerto3,10.10.35.2,10.10.35.5,255.255.255.0
#dhcp-option=net:switch1,net:puerto3,54,10.10.35.251
dhcp-circuitid=puerto3,b9:06:00:00:01:01:01:03
Hi,
I've been having problems with DNSMASQ when using VPN. The general
problem is I only want DNS entries for work resolved across my VPN
server. However, I have run across several challenges I'm hoping there
are simple solutions.
Right now the main problems I am trying to address are:
-
ignacio.br...@belden.com wrote:
Hello Simon, I tried the following on 2.53-test8:
tag-if= set:fixedport, tag:puerto3, tag:switch1
dhcp-range=net:switch1,net:puerto3,10.10.35.2,10.10.35.5,255.255.255.0
#dhcp-option=net:switch1,net:puerto3,54,10.10.35.251
Bill C Riemers wrote:
Hi,
I've been having problems with DNSMASQ when using VPN. The general
problem is I only want DNS entries for work resolved across my VPN
server. However, I have run across several challenges I'm hoping there
are simple solutions.
Right now the main problems I am
Resending this e-mail because it's very relevant to the broken
behavior noted by Ignacio in the test release.
Ignacio, why not configure you switch to relay all ports? Then you can
block broadcasts without problems. You don't have to have special
configuration in dnsmasq for all the ports, it