Gavin McCullagh
2011-03-08 12:31:18 UTC
Hi,
attached to this email are
dllogin
dlrancid
which are modified versions of fnrancid and fnlogin. These work with a
number of the D-Link models which we have here:
# DES-3010F - success (telnet, ssh)
# DES-3052P - success (telnet, ssh, ... a little slow)
# DES-3526 - success (telnet, ssh)
# DES-3550 - success (telnet, ssh)
# DES-3250TG - fail (there's no command to print config)
# DGS-3324SR - success (telnet, ssh)
# DGS-3100 - fail (but probably not too big a job to fix)
This is just a first go, but it's working well enough for us to use now. If
anyone has feedback, I'd love to hear it.
The only other modification was to add
'dlink' => 'dlrancid',
to %vendortable in rancid-fe and then use "dlink" to describe switches in
router.db.
Thanks for rancid, we're already seeing benefits.
Gavin
attached to this email are
dllogin
dlrancid
which are modified versions of fnrancid and fnlogin. These work with a
number of the D-Link models which we have here:
# DES-3010F - success (telnet, ssh)
# DES-3052P - success (telnet, ssh, ... a little slow)
# DES-3526 - success (telnet, ssh)
# DES-3550 - success (telnet, ssh)
# DES-3250TG - fail (there's no command to print config)
# DGS-3324SR - success (telnet, ssh)
# DGS-3100 - fail (but probably not too big a job to fix)
This is just a first go, but it's working well enough for us to use now. If
anyone has feedback, I'd love to hear it.
The only other modification was to add
'dlink' => 'dlrancid',
to %vendortable in rancid-fe and then use "dlink" to describe switches in
router.db.
Thanks for rancid, we're already seeing benefits.
Gavin