Cheers. The reason I wanted SNMP was so I could use tools which run as a service, rather than user programs. In fact I could run the monitoring from work keeping it completely independent of the home PC. , but that would mean opening telnet to the outside world, unless it could be done via ssh.
I used cron to convert 'user space tools' into a service. ;-)
cron -> script -> data.file
and a php script to export data as an actual http service
client <- http <- php <- data.file
But that was just a hacky workaround I came up with, because the SNMP was useless, but the CLI was featureful.
My open port/firewall/telnet/subnet issues were easily circumvented with an Openssh tunnel.
In the end the ease of just using openssh to handle authentication, encryption, tunneling and proxying was the clincher for me and why I plumped for ssh+expect instead of using the ( less featureful but ) more windows friendly plink, which for my use case required Linux at both ends.
For me that is a feature, not a bug.
Regarding the Billion SNMP support, the relevant mib that they support is VDSL-LINE-MIB (rather than ADSL as I'd have expected), and even more annoyingly the router returns values for all the parameters - it's just that most of them are returned as zeros. I find that really annoying, they've stuck in the SNMP code to support the correct MIB, but can't be bothered to return the correct answers, even though the data is available.
Indeed. Implementing stuff, but NOT implementing it fully/properly, is just a slap in the face to the customer who later tries to use it. grrr.
