On Wed, 2012-07-25 at 14:00 -0500, Ty Featherling wrote: > Facepalm! I just realized I do have a public on this one as well. That > actually leads me to a different question. > > This is my primary DHCP server. It currently handles our entire network > except for the handful of sites I have routed now. I had some trouble when > I initially set it up and found that adding a public address to the > interface that is within the network it is handing out addresses for solved > it. As a result I have several public IPs assigned to this interface. Is > this necessary? Somehow I doubt it but couldn't get it going otherwise and > was in a crunch to do so. > > Thoughts?
There is a really LONG way to answer this question. The short answer, however, is that on RouterOS, you must have an IP assigned in the range you want to provide dhcp services for UNLESS you are simply using this as a relay server. That being said, I'd suggest a good firewall, such as the one that can be found at http://store.wispgear.net/ :-) -- ******************************************************************** * Butch Evans * Professional Network Consultation * * http://www.butchevans.com/ * Network Engineering * * http://store.wispgear.net/ * Wired or Wireless Networks * * http://blog.butchevans.com/ * ImageStream, Mikrotik and MORE! * * NOTE THE NEW PHONE NUMBER: 702-537-0979 * ******************************************************************** _______________________________________________ Mikrotik mailing list [email protected] http://www.butchevans.com/mailman/listinfo/mikrotik Visit http://blog.butchevans.com/ for tutorials related to Mikrotik RouterOS
