Hello Simon,<br><br>Thanks for the info. However, I think I found an issue with this setup. On the routers, all the physical interfaces and the VPN interface are bridged together, so to dnsmasq it only sees one interface, if I'm reading this correctly. So, I can't tell it to ignore the vpn interface, since to it, it's all under the bigger bridged interface and I also can't tell it to ignore the bridged interface since then I'd have no dhcp for the entire network. Would you have any suggestions on how to get around this?<br><br>Thanks,<br>J Silverman<br><br><b><i>Simon Kelley <simon@thekelleys.org.uk></i></b> wrote:<blockquote class="replbq" style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left: 5px;"> J Silverman wrote:<br>> Hello Simon,<br>> <br>> I was just researching this a bit more and was thinking of using<br>> except-interface=<openvpn_interface>. Would the no-dhcp-interface be<br>> a better
choice?<br><br>Both will work: the difference is that except-interface tells dnsmasq to<br>ignore DNS queries arriving on that interface, as well as DHCP and TFTP.<br>no-dhcp-interface stops DHCP and TFTP, but allows DNS. In your case you<br>probably won't have DNS queries crossing the bridge, but there's no<br>particular reason to block them.<br><br>Cheers,<br><br>Simon.<br></openvpn_interface></blockquote><br><p> 
<hr size=1><a href="http://us.rd.yahoo.com/evt=48250/*http://searchmarketing.yahoo.com/arp/sponsoredsearch_v9.php?o=US2226&cmp=Yahoo&ctv=AprNI&s=Y&s2=EM&b=50">Pinpoint customers </a>who are looking for what you sell.