> Which is not a problem just that people did not understand what you have > just explained. People were thus confused soo much that smartbrigdes removed > ips from view. > > Kind Regards, > > David
This was not my experience. The issue was not confusion, it was buggy software ..or something wrong with my network that simpleNMS could not handle. (I'll let you decide which) In SimpleNMS, I would almost *always* have one of the following errors: 1. A radio's MAC paired with the WRONG PUBLIC IP. Instead of the radio's MAC showing a private IP that the customer's Linksys router was handing out (192.168.1.x), it would show 66.228.37.xx ..a public IP that did NOT belong to the client in question. I could confirm this by using simpleMonitor to log into the client radio to confirm radio IP, radio MAC and bridge name. I could then log into the router remotely via the browser and confirm its IP address and the NAT'd subnet. I could then ARP -a and confirm the airbridge's MAC matched the public IP's MAC. ...and then look at simpleNMS and see the WRONG public IP matched to the radio's MAC. 2. Two or more radios' MAC addresses matched with the same public IP. I could ping the client's true IP address and confirm that the wrong MAC was displayed in simpleNMS. In my humble newbie opinion, the IP addresses were yanked because the feature was buggy. I believe SB confirmed that it was buggy. (and I see that they said so again today) I for one, would like to see it back (and working) along with the bridge name (hint, hint). Tim Foster www.AledoBroadBand.com Aledo's only high-speed ISP The PART-15.ORG smartBridges Discussion List To Join: mailto:[EMAIL PROTECTED] (in the body type subscribe smartBridges <yournickname> To Remove: mailto:[EMAIL PROTECTED] (in the body type unsubscribe smartBridges) Archives: http://archives.part-15.org
