Indeed, this is a corporate setup with Windows DHCP at the core.  
This is a site on the remote end of a VPN.  
The sysadmins were a bit on edge about sending DHCP across the VPN, so they 
asked that we stick it local on the remote site Mikrotik router....which works 
ok, though we hit a bit of a snag with the NAC, which likes to sniff DHCP 
traffic to help detect and identify devices on the segment, in addition to 
several other data sources. 

I may just nag the sysadmins to build this out in the core DHCP and this will 
solve itself.  
Just point DHCP Relay at both addresses and I think we'll be fine.  

___________________________
Mangled by my iPhone.
___________________________


> On Nov 22, 2015, at 5:13 PM, Paul Stewart <[email protected]> wrote:
> 
> Have never seen that work on any platforms I work with ... Cisco/Juniper
> etc...
> 
> -----Original Message-----
> From: Af [mailto:[email protected]] On Behalf Of George Skorup
> Sent: Sunday, November 22, 2015 1:40 PM
> To: [email protected]
> Subject: Re: [AFMUG] DHCP relay question
> 
> MikroTik? So you're asking for an /ip dhcp-server and an /ip dhcp-relay on
> the same interface? No idea if that will work, never tried it. You can
> certainly have multiple DHCP servers on the same broadcast domain. 
> Never had to do that outside of a large corporate environment for redundancy
> though, and that was just windows DHCP servers.
> 
>> On 11/22/2015 11:38 AM, Tyler Treat wrote:
>> Have a question regarding dhcp relay function.
>> Say we have local dhcp configured at a remote site, yet we have a network
> management tool that would like to see dhcp traffic for device detection
> purposes.
>> My question is this:   Is it possible for local dhcp to function, and have
> dhcp relay pointing to our NAC to assist it in detecting devices?(the NAC
> doesn't respond, just listens)
>> 
>> Thoughts?
>> 
>> 
>> Thanks
>> Tyler
>> ___________________________
>> Mangled by my iPhone.
>> ___________________________
>> 
>> Tyler Treat
>> Corn Belt Technologies, Inc.
>> 
>> [email protected]
>> ___________________________
>> 
> 
> 

Reply via email to