Difference between revisions of "Dhcpd-plugin"
From LinuxMCE
| 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>It's a very simple script, it continuosly greps ''/var/log/syslog'' looking for DHCPREQUEST/DHCPACK lines. | + | <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 continuosly 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 10: | ||
/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 responsable to correctly configure Snom320, so it could be used almost imediatly. | That script is responsable to correctly configure Snom320, so it could be used almost imediatly. | ||
| + | |||
| + | == 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 (whith very different configurations) of same manufacturer share same IP range | ||
| + | :Now it's solved by asking the user what kind of device he plugged. | ||
| + | * 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) | ||
Revision as of 14:28, 18 May 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 continuosly 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 responsable to correctly configure Snom320, so it could be used almost imediatly.
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 (whith very different configurations) of same manufacturer share same IP range
- Now it's solved by asking the user what kind of device he plugged.
- 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)
