Difference between revisions of "Dhcpd-plugin"
From LinuxMCE
m (spelling corrections) |
|||
| Line 1: | Line 1: | ||
<table width="100%"> <tr><td bgcolor="#FFCFCF">This page was written by Pluto and imported with their permission when LinuxMCE branched off in February, 2007. In general any information should apply to LinuxMCE. However, this page should be edited to reflect changes to LinuxMCE and remove old references to Pluto.</td></tr> </table>== How it works == | <table width="100%"> <tr><td bgcolor="#FFCFCF">This page was written by Pluto and imported with their permission when LinuxMCE branched off in February, 2007. In general any information should apply to LinuxMCE. However, this page should be edited to reflect changes to LinuxMCE and remove old references to Pluto.</td></tr> </table>== How it works == | ||
| − | It's a very simple script, it | + | It's a very simple script, it continuously greps ''/var/log/syslog'' looking for DHCPREQUEST/DHCPACK lines. |
When finding one of those it tries to find out if it's a new device (not already added and not one of the ignored). | When finding one of those it tries to find out if it's a new device (not already added and not one of the ignored). | ||
| Line 9: | Line 9: | ||
After that somebody else will run the configuration script specified in DeviceTemplate. Something like: | After that somebody else will run the configuration script specified in DeviceTemplate. Something like: | ||
/usr/pluto/bin/configure_snom3xx.pl -d 47- i 192.168.80.253 -m 00:04:13:24:25:e9 | /usr/pluto/bin/configure_snom3xx.pl -d 47- i 192.168.80.253 -m 00:04:13:24:25:e9 | ||
| − | That script is | + | That script is responsible to correctly configure Snom320, so it could be used almost immediately. |
== New p&p devices == | == New p&p devices == | ||
| Line 18: | Line 18: | ||
== Possible problems == | == Possible problems == | ||
| − | * Two or more models ( | + | * Two or more models (with very different configurations) of same manufacturer share same IP range |
:Now it's solved by asking the user what kind of device he plugged. | :Now it's solved by asking the user what kind of device he plugged. | ||
| − | :In future an | + | :In future an auto detection script will be needed (like the one deciding what kind of cisco do we have 7960 or 7970 by getting the information from the phone itself), but it's still won't be a perfect solution because it relies on certain firmware versions and/or default passwords. |
* Same model may have different firmwares, meaning that sometimes the configuration script may fail. | * Same model may have different firmwares, meaning that sometimes the configuration script may fail. | ||
:This can't be solved right now. Usually firmware is not distributable, so you can't force to use a specific version with pluto. The firmware upgrade needs user interaction and is very delicate operation that may result in trashed equipment (for example power outage in the middle of upgrade) | :This can't be solved right now. Usually firmware is not distributable, so you can't force to use a specific version with pluto. The firmware upgrade needs user interaction and is very delicate operation that may result in trashed equipment (for example power outage in the middle of upgrade) | ||
Revision as of 16:35, 10 December 2006
| This page was written by Pluto and imported with their permission when LinuxMCE branched off in February, 2007. In general any information should apply to LinuxMCE. However, this page should be edited to reflect changes to LinuxMCE and remove old references to Pluto. |
It's a very simple script, it continuously greps /var/log/syslog looking for DHCPREQUEST/DHCPACK lines.
When finding one of those it tries to find out if it's a new device (not already added and not one of the ignored). Then it sends DCE Event #53(New Mac Address Detected) with params #5(MAC) and #28(IP) to DCERouter.
As far as I know then it's processed somewhere in General_Info_Plugin (asking for device type, room and other such stuff), after that it creates device with status set to **RUN_CONFIG**.
After that somebody else will run the configuration script specified in DeviceTemplate. Something like:
/usr/pluto/bin/configure_snom3xx.pl -d 47- i 192.168.80.253 -m 00:04:13:24:25:e9
That script is responsible to correctly configure Snom320, so it could be used almost immediately.
New p&p devices
For each device that needs to be plug&play device we need to:
- create a device template
- add a mac range in device template to include such devices
- create a script that will be called as described above that will configure the device to be used with pluto
Possible problems
- Two or more models (with very different configurations) of same manufacturer share same IP range
- Now it's solved by asking the user what kind of device he plugged.
- In future an auto detection script will be needed (like the one deciding what kind of cisco do we have 7960 or 7970 by getting the information from the phone itself), but it's still won't be a perfect solution because it relies on certain firmware versions and/or default passwords.
- Same model may have different firmwares, meaning that sometimes the configuration script may fail.
- This can't be solved right now. Usually firmware is not distributable, so you can't force to use a specific version with pluto. The firmware upgrade needs user interaction and is very delicate operation that may result in trashed equipment (for example power outage in the middle of upgrade)
