Hello,

We have The Dude set up using ping to query remote devices that have public IPs....works like a charm.

Now comes the next step...whether it is possible to query or receiving status from devices that are behind a router performing NAT(and a private IP scheme). These devices are APs...and some of them have SNMP functions.

My understanding is that I will need these devices to transmit TRAP information to our server(running The Dude).

I have a couple calls into the manufacture tech support for these APs, but was also wanting to touch base here.

Any linkage to articles that can help decifer how to set up SNMP would be greatly appreciated.

/cheers

I dont actualy understand how snmp trap notifications work but i think the dude cant use them. when the dude uses snmp it asks for the information then gets it the dude is never just waiting for info out of the blue. Unless you are using the beta with integrated syslog server. Then it can receive syslog info whenever a device decides to send it

hi,

any update on how to monitor mikrotik devices behind NAT using Dude?

What about to run some kind of tunnel? I use sstp between such devices and network where dude runs and it works.

can you please share the SSTP settings on any one of your router behind NAT.

server:

ros code

/ppp profile
add name=sstp use-compression=yes use-encryption=yes use-vj-compression=yes

/ppp secret
add local-address=192.168.222.1 name=client1 password=pass1 profile=sstp remote-address=192.168.222.2 routes=192.168.222.0/30 service=sstp

/interface sstp-server
add name=client1-in user=client1

/interface sstp-server server
set authentication=mschap2 default-profile=sstp enabled=yes keepalive-timeout=10 max-mru=1600 max-mtu=1600 mrru=1600 port=444

+manual route that sends traffic to the clients internal ip trhu the client1-in interface
+firewall rule accepting incoming traffic on port 444.

client:

ros code

/interface sstp-client
add add-default-route=no authentication=mschap2 certificate=none connect-to=*public.ip.address.of.server*:444 dial-on-demand=no disabled=no http-proxy=0.0.0.0:444 keepalive-timeout=10 max-mru=1500 max-mtu=1600 mrru=1600 \
    name=sstp-server password=pass1 profile=default-encryption user=client1 verify-server-address-from-certificate=no verify-server-certificate=no

+manual route that sends traffic to the servers internal network range trhu the sstp-server interface.

names and passwords are fake. There are of course more clients connected to the server side. All of the clients are behind nats.

And the important thing: Clients are 6.18, server is 6.21.1

thank you for sharing.... will try it out and see.