| 1 |
Investigate integration with terminal server software. such as the RADIUS |
| 2 |
server. |
| 3 |
|
| 4 |
The current release of mrtg-dynip, mrtg-dynip-0.41b, appears to be stable, |
| 5 |
robust and free of major problems arising from misconfiguration and lack of |
| 6 |
response. |
| 7 |
|
| 8 |
While it might seem rather trivial to introduce changes to make mrtg-dynip |
| 9 |
more suitable as a front end to MRTG, this in a sense is somewhat trivial |
| 10 |
in terms of the design goal of mrtg-dynip, namely to enable mrtg-dynip to |
| 11 |
work in environments with inconsistent snmp target names for the same |
| 12 |
phyical interface. This design goal has been achieved. The goal of having |
| 13 |
a convenient and efficient 'front end' to MRTG and mrtg-dynip is a different |
| 14 |
design goal in itself. |
| 15 |
|
| 16 |
It is planned to investigate and test use of the 'ifLastChange' snmp object. |
| 17 |
|
| 18 |
It is planned to introduce configuration to indicate if a host or router has |
| 19 |
unvarying SNMP target numbers for its interfaces, or not. Suitable coding |
| 20 |
will reduce processing demands and reduce the amount of snmp traffic |
| 21 |
generated. This may be trialed with tesing use of the 'ifLastChange' snmp |
| 22 |
object |
| 23 |
|
| 24 |
There are plans to try out terminal server software, such as RADIUS server |
| 25 |
software, with a RADIUS client Livingstone emulator, and see if there are |
| 26 |
any special issues or convenient outcomes involved. |
| 27 |
|
| 28 |
There is much scope for introducing a menu based configuration. |
| 29 |
|
| 30 |
|
| 31 |
|
| 32 |
|