![]() (see “facepalm conslusion,” at the end of the page!) The dnsmasq config files are in the /etc/dnsmasq.d/ directory. Setting these DHCP options is not possible via the GUI (graphical user interface), so we need to head to the command prompt. ![]() Now, ClearOS’s DHCP settings are managed via its webconfig interface. You would need to add a line to your DHCP configuration like this: dhcp-option=eth0,66,192.168.1.10 Suppose that your DHCP server is serving addresses on interface eth0 and your PBX’s IP address is 192.168.1.10. It turns out that the syntax for option 66 in dnsmasq is pretty simple. If you’re not using ClearOS the file names shown below might be slightly different, but any Linux distro using dnsmasq as DHCP server should be very similar to this so if you understand the concept, you should be able to adjust this as needed for your own router. I recently configured DHCP option 66 on a ClearOS 7 gateway / firewall. Many routers should be able to support this, so check your documentation or if you’re using a Linux-based router with dnsmasq, read on! So basically you need to add a DHCP configuration setting specifying your PBX server’s IP address for option 66. Option 66 allows you to specify the address of a TFTP server on your network, which is how Endpoint Manager serves configuration files to phones. When you plug your VOIP phone into your network, how is it going to know which address to reach out to for instructions? In other words, how will it know where the PBX is? The answer lies in DHCP option 66. But there’s one more piece of the puzzle that needs to be in place first for this all to come together, and that detail is the focus of this post. ![]() Obviously that’s a pretty general overview.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |