Why not just create static NATs with unique internal IP addresses for each of the remote systems?  Then, you'll have the added benefit of always being able to connect to each unique IP/system for loads of other tools and uses as well.

-Chris
On 1/13/14 9:06 AM, Bogdan Ghita wrote:
Hello

I'm trying to setup a monitoring system for two networks that have several devices each (mostly switches) behind a NAT router; unfortunately I am limited on the ports, so had to use SSH tunnelling from the Observium machine to each of the networks in order to access all the devices. I followed the instructions from  http://vfamilyserver.org/blog/2013/03/snmp-hell-part-1-proxy-to-multiple-devices/ to setup the SNMP proxying and it all works quite well, I can snmpwalk each of the devices behind one of the two NAT routers only by changing the community name (haven't yet setup the second one). However, I'm not sure how/if it's possible for Observium to see the different devices - I've added the NAT router with add_device.php (I used command line rather than web interface due to SNMP running over TCP) and was recorded as 127.0.0.1 (which does make sense, as it's the tunnelled from the local host); then, when I tried to run the command with one of the other community strings, it returned an "Already got device 127.0.0.1". Further, although I haven't yet set it up, I will probably have the same problem when adding the tunnelled NAT router on the second network.

Is there a configuration/workaround that would allow to differentiate between these multiple instances of what appears to be the same [local]host?

Best regards
Bogdan



_______________________________________________
observium mailing list
observium@observium.org
http://postman.memetic.org/cgi-bin/mailman/listinfo/observium