> Anyone familiar with the Teletronics Xi-1500 radio will > tell you that when you are dealing with bridges the IP > changes depending on which direction you are looking at > the device, and what is on the other side of it. > > For example, on a backhaul link the status on the Xi-1500 > shows that the link is connected to 192.168.253.110, which > is in fact the correct address of the radio on the other > side of the link. When I connect to that radio and look at > it's status page, it should show 192.168.253.109, which is > the radio that I just checked, but in fact it shows the IP > address of the workstation I'm connecting to it from. > > It's not a bug, it's the nature of the beast, and it just > may not be possible to get it to display the way that we > think it should. That, I believe is why SB took it out. > Their programming efforts are best spent on more critical > aspects of the firmware. If somewhere along the line they > should figure out a way to do it, so much the better for us. > > Kevin Summers > KISTech Internet Services Inc. > www.kistech.com
I'm not familiar with the Teletronics, so maybe it's me and my flawed understanding of bridges. Maybe I'm not understanding what you're saying, but what you're describing still doesn't match my experience. Here's what I have on my network (more or less. Well, ok. Less. Numbers are fictitious, but you get the point.): NOC++++++++++++++++++++++++++++++++++= Win2K IP: 66.123.2.1 ClientA+++++++++++++++++++++++++++++++++++++++ [antenna]->[radio]->[Linksys router] -> -> -> [3 computers] Radio IP: 192.168.2.3 MAC: 00-30-1A-00-00-03 Router WAN IP: 66.123.2.3 MAC: 00-06-25-00-00-03 Router LAN IP: 192.168.1.1 MAC: 00-06-25-00-00-02 Computer IPS: 192.168.1.101, 192.168.1.102, 192.168.103 ... ClientB+++++++++++++++++++++++++++++++++++++++ [antenna]->[radio]->[Linksys router] -> -> -> [2 computers] Radio IP: 192.168.2.4 MAC: 00-30-1A-00-00-04 Router WAN IP: 66.123.2.4 MAC: 00-06-25-00-00-04 Router LAN IP: 192.168.1.1 MAC: 00-06-25-00-00-03 Computer IPS: 192.168.1.101, 192.168.1.102, 192.168.103 ... ClientC+++++++++++++++++++++++++++++++++++++++ [antenna]->[radio]->[Linksys router] -> -> -> [5 computers] Radio IP: 192.168.2.5 MAC: 00-30-1A-00-00-05 Router WAN IP: 66.123.2.5 MAC: 00-06-25-00-00-05 Router LAN IP: 192.168.1.1 MAC: 00-06-25-00-00-04 Computer IPS: 192.168.1.101, 192.168.1.102, 192.168.103 ... +++++++++++++++++++++++++++++++++++++++ Here's what SimpleNMS would show: 66.123.2.5 -> 00-30-1A-00-00-05 66.123.2.5 -> 00-30-1A-00-00-04 (*should* show 66.123.12.4) 66.123.2.5 -> 00-30-1A-00-00-03 (*should* show 66.123.12.3) So my question is ...why was SimpleNMS showing that a radio's mac would have a neighbor's public IPs? At no time was my Win2K box at the NOC using a client's public IP. Why did SimpleNMS insist that a radio's MAC had a neighbor's public IP? If those were private IPs (like the kind that show up in simpleMonitor), then that's no problem. I can understand that a bridge may display a public IP or may just show it's own private IP. But it's somebody *else's* public IP?? If it's me, just say so, and I'll go google "Bridging 101" and stop wasting everyone's time. I'm still "a pupil in an intro class". Hope I'm not wasting everyone's time beating this dead horse.... 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
