![]() Download the Magic Utilities app from here.Here’s the process of using the Magic Utilities application to get your Apple Trackpad working on your Windows PC: It does cost money, currently $5.99 a year for a single user but has a free trial. It includes Bluetooth support for Apple devices and Boot Camp compatibility so works fine with the Apple Magic Trackpad. In version 3.0 scanner scripts looks unchanged, so upgrading applies to web interface mostly.Magic Utilities is a third party software vendor that develops apps that help Windows and Mac play nicely together. Now I prefer not upgrade working server to SVN version, may be it will be upgraded when Cacti 1.0 comes out. Yes, it reports in plugin's list that it is version 3.0, but since I've used one of SVN versions - it may be something between 2.9 and 3.0. I'm not pretty sure about used mactrack version. Port name or port description should be used instead, but generic scanner didn't return it for SG. ![]() The 48 offset for port numbers looks strange. $device = "Data collection completed ok" $port_array = xform_mac_address($port_result) Mactrack_debug("Final cross check's now being performed.") įoreach($active_vlans as $active_vlan) -443,6 +443,7 = $portNumber I threw in a used / available supermicro server in theg hope to learn something new and you have been tremendous support).Ĭode: Select all - mactrack_ 22:04:28.000000000 -0400 I wanted to make this remote box usable to me to provide support to a very small business (I will $100 a month from them to monitor their network for up / down alerts and then login and help them remotely. Resolved Intel driver issues that surfaced as a result, then installed Chrome and changed http / ssl ports to non standard, added firewall etc. I also had updated CentOS 6.4 that came with CactiEZ to 6.8. It could be that the 3.0 that came with CactiEZ had some integation issues. I had installed using CactiEZ and the version 3.0 mactrack did not work at all for me. You mentioned earlier that your own implementations use mactrack 3.0. I assume the developers have a lot on their plate and they contribute when they have some personal time available, but anyone reading this thread, will be able to make their MacTrack work.įor SG switches, I find that they add 48 to the actual port number in the mib query response. But I think what you have done is worth writing in a small knowldgebase article as that is lacking in here. I had picked up couple of switches from work to test here. in this situation, I am not using any trunks or vlans. I assumed that any managed / vlan capable switch needs to use dot1q scanner. I first tried port scanner to be IOS dot1q and then generic dot1q. How to mark this as solved and credit it to you. Under all switch devices, I see user ports to be equal to total number of physical ports and then user ports up, to be one equal to total number of mac addresses learnt by switch (actual ports up in my case are 3 user ports and 1 uplink port for Cisco 2975).Ģ. I verified that they do support Bridge-Mib as well.ġ. Not sure as to what is the issue with SG series of switches. Again this worked, shows that it detected user ports and active mac addresses, but in this case, no mac addresses actually are reported. I then added a HP Procurve switch and it worked using scanner function of NG switch ports. Cisco switches support it and hence we were able to see mac addresses returned from them (of course using your fix of not populating under device type, system description match field). ![]() I verified by snmpwalk on these devices IP. ![]() I plugged in Mikrotik switch and DD WRT AP and as you pointed out, none of them are suitable for Mactrack as they do not support mib-2.17.4.3.1.2, hence no mac address is retrieved from them. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |