Hi,
I want to auto-discover the CPEs on the network.
All CPE have a loopback ip address (/32) and all are in a network range of /24 bit, and are reacheble from the WLAN side.
The problem is that many of this have the same LAN address (eg 192.168.1.1/24) and after Dude discover the first CPE is unable to discover the other devices, because all of this have the same LAN address.
There is a way to automaticly avoid the discover of the LAN address (I already try with blacklist, but dosen't works!)

regards
Stefano

Here is an easy way to not auto discover some address.

You can put specific range of addresses in if you just put a dash between them like "192.168.10.66-192.168.10.78". ... I don't think you can put a comma separated list of address ranges in one "auto-discover" but you can easily add multiple individual ranges to discover on the general ... And if it falls on a class boundry "The Dude" will change your range to a /27 or what ever the boundary is. i.e. 192.167.10.64/27.

NO, the problem is different.

the loopback and the WLAN address are in an other range: 10.10.255.0/24 for loopback and 10.10.99.0/24 for the WLAN.
I start the discovery on 10.10.255.0/24, the first CPE will be discovered (lets say 10.10.255.1) and with SNMP will be found that he has a ETH1 with the IP 192.168.1.1, then the second will be discovered (lets say 10.10.255.2) and he has the same ETH1, so DUDE will not put the second CPE in the map.


regards
Stefano

Damn, well it is probably picking up the 192.168.x.x from the mac address table.. I am curious can you shut that interface down? Obviously changing all those addresses will be a bit of work. What is going on with E1 anyhow if they all have the same IP, do you use that for local management?

I am fortunate enough to only have about 200 devices and I don't like how auto discover works so I just built it all manually.

Hi lebowski,
no, I can't shut down this interfaces, these are the customer interfaces!

I prevere to add manualy the device too, but in this case where there is many CPE connected it will be nice to do it automaticaly...

The only way I findout is to modify the snmp comunity, so the cpe will be discovered only with the IP address, but in this case it will be impossible to realy manage the CPE (only ping!).

Stefano

I know it would be a huge pain to change all the E1 interfaces to different networks... but there is an upside. I don't know how I would go about fixing this. Let us know what you decide.