Autodetection doesn't work for the dracs I tried

[SEJeff]

I tried both a few idrac 6 series (R610) and 7 series (R720/620) to no avail.

In my local copy I've added a version flag that allows selecting 6 or 7 and it works. I'd also like to improve the autodection by logging in using the /data/login endpoint and then scraping /viewer.jnlp for iDRAC 6 / iDRAC 7.

Would you have any issues with me doing this and then sending pull requests?

[PaulMaddox]

Hi Jeff,

I originally had problems when I tried an automated login to /data/login.
I think if we could retrieve the viewer.jnlp from the DRAC, then we wouldn't need any auto-detection at all, we could just use the viewer.jnlp as-is.

[PaulMaddox]

I'm interested to see why the autodetection isn't working for you though.

If you look here:
https://github.com/PaulMaddox/drac-kvm/blob/master/drac.go#L58

Then you'll see it tries to GET a few URLs to detect the version.
Are those URLs available on your DRAC?

[SEJeff]

Yup we don't have those urls. I tried several newer R620 and R720 dracs with newish firmware of both Sandy Bridge and the Ivy Bridge (cpu) variety. I also tried a few older westmere R610s and again, same thing. I saved the jnlps of both and they were almost identical.

So I'd like to do 2 things. I've successfully added a flag to specify the drac version manually. I'm going to re-do that one again and submit it in another PR. That makes sense first and is simple enough.

Then I'm going to take a stab at making it login to /data/login, download the jnlp, and serve that to java. Is that ok with you?

[PaulMaddox]

Sounds great.

I found during testing that the DRAC has a blocking system that firewalls off the incoming IP after 2 or 3 failed logins to /data/login. If it hinders your experiments, you can disable it with:
racadm config -g cfgRacTuning -o cfgRacTuneIpBlkEnable 0