I meant the target device !
 i'am already monitoring my fortigate using his public ip address 

Le mardi 12 mai 2020 09:00:18 UTC+1, Brian Candler a écrit :
>
> You said before that your firewall is blocking ping from your host, so it 
> sounds like it *isn't* allowing all services.  If you can get to the point 
> where you can ping your firewall, you'll have a better change of being sure 
> that you can open SNMP.
>
> When you say "host to prometheus" I don't understand what you're saying.  
> I think you were talking about two things:
> - the host where you are running prometheus and snmpwalk
> - the target device that prometheus/snmpwalk is trying to communicate with 
> via SNMP (i.e. the Fortigate).
>
> The SNMP UDP query originates at the prometheus host, and arrives at the 
> target device with destination port 161. The response UDP packet will have 
> source port 161, but any half-decent stateful firewall will allow the 
> response automatically.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Prometheus Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/prometheus-users/e1a0e292-aa1d-4ee2-903e-469483a0c296%40googlegroups.com.

Reply via email to