Workaround for broken IEEE OUI db search

[lewekleonek]

First of all. Thanks go to Merlin for all your hard work with the custom firmware for ASUS routers.

In my case I use RT-N66U version; it works like a charm, except for one thing - the equipment manufacturer look-up.
I did some research and I know that this is an external issue with the way the ieee.org site answers the following queries:
http://standards.ieee.org/cgi-bin/ouisearch?22-E3-1F

Please refer to:
http://www.snbforums.com/threads/as...asus-rt-n66u-firmware.7047/page-16#post-44126

I started to look for a workaround, but I need some pointers.
Is the query actually executed by running http://standards.ieee.org/cgi-bin/ouisearch?##-##-## ?
Put aside a legality and feasibility of the project but let's say what if I came up with a mock REST web service that provides the same data and it actually works.
Then I would have it running off of a local web server to test this whole thing, but I would bind the standard.ieee.org to a local web server instead of the IEEE's in the router. I know it's a rather nasty trick but I'd like to give it a shot.

The IEEE appears to be much better in allowing you download the whole oui.txt file than in responding properly to the above mentioned web queries.

 

[lewekleonek]

I'm replying to myself, but wth...
If you the query: http://standards.ieee.org/cgi-bin/ouisearch?##-##-## without the dashes in the MAC number sections, it appears to work better, but in some cases the results don't show up at all.

Example that works:
http://standards.ieee.org/cgi-bin/ouisearch?001E90

00-1E-90 (hex) Elitegroup Computer Systems Co
001E90 (base 16) Elitegroup Computer Systems Co
No.239, Sec. 2, Ti Ding Blvd
Taipei 11493
TW


And the one that does not:
http://standards.ieee.org/cgi-bin/ouisearch?002258

(I get the blank page in response, though the IEEE's oui.txt file contains the record for it:
00-22-58 (hex) Taiyo Yuden Co., Ltd.
002258 (base 16) Taiyo Yuden Co., Ltd.
8-1 Sakae-Cho

JP
)

 

[RMerlin]

I spent about two hours last night looking into this, and couldn't figure out the root problem. Part of it has indeed to do with the dashes having to be removed to obtain an accurate result, however it seems that the page itself doesn't return anything when queried through XMLHTTP, and I have no idea why.

 

[lewekleonek]

I think it's on their end:
GET https://services13.ieee.org/RST/sta...wnload/?registry=MA-L&format=html&text=002258 500 (Internal Server Error) <- Chrome Dev Tools Console

I see 500 internal server error on some attempts; while it works from time to time it does fail with 500 quite often.

 

[lewekleonek]

How about this: http://www.macvendorlookup.com/api
Would this even be feasible? They return XML, JSON, CSV and PIPE delimited responses.

Example:
http://www.macvendorlookup.com/api/v2/002258/pipe

Though I wonder about their business model... I clicked on his ads to help him

 

[sfx2000]

I spent about two hours last night looking into this, and couldn't figure out the root problem. Part of it has indeed to do with the dashes having to be removed to obtain an accurate result, however it seems that the page itself doesn't return anything when queried through XMLHTTP, and I have no idea why.

Better not to dip into an external off-site DB, but to keep a local flatfile that can be polled/updated from time to time...

 

[sfx2000]

And we don't want to get into a mess where a 3rd party could be impacted - would be better perhaps if Asus just hosted their version in their Cloud stuff..

 

[lewekleonek]

Better not to dip into an external off-site DB, but to keep a local flatfile that can be polled/updated from time to time...

I would agree with this one, if it's feasible.
Currently the size of the oui.txt file pulled off of the ieee site is 3.14 MB