Omada Controller NO wan snmp?

What am I missing?
I can use snmp on local GW lan..
Can snmp be used with a remote snmp server?
Via openvpn vtun0 or port forward?
Or is it locked down?
I cant get any access and the GW CLI is useless...
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content

Hi @dajocka
Thanks for posting here.
1. Selecting the Listening IP Address
- WAN IP: If remote management via the external network is required, the SNMP service must be bound to the WAN IP. However, note the following:
- Security Ris*: Exposing SNMP directly to the internet may lead to attacks (recommended to use ACLs/IP whitelisting).
- Dynamic IP Issue: If the WAN IP is dynamically assigned (e.g., PPPoE), additional configurations like DDNS or dynamic adaptation may be needed.
- LAN IP: If management is only needed within the internal network, binding to the LAN IP is more secure but prevents external access.
2. Port Number
- Default Port: SNMP typically uses UDP 161 (for agent requests) and UDP 162 (for Trap messages).
- Custom Port: It can be changed to avoid scanning (ensure consistency between client and device configurations).
3. Firewall Configuration
- If listening on the WAN IP, ensure the router/firewall allows inbound UDP traffic on the specified port (e.g., `WAN → Device_IP:161`).
- Copy Link
- Report Inappropriate Content

Hi @dajocka
Thanks for posting here.
1. Selecting the Listening IP Address
- WAN IP: If remote management via the external network is required, the SNMP service must be bound to the WAN IP. However, note the following:
- Security Ris*: Exposing SNMP directly to the internet may lead to attacks (recommended to use ACLs/IP whitelisting).
- Dynamic IP Issue: If the WAN IP is dynamically assigned (e.g., PPPoE), additional configurations like DDNS or dynamic adaptation may be needed.
- LAN IP: If management is only needed within the internal network, binding to the LAN IP is more secure but prevents external access.
2. Port Number
- Default Port: SNMP typically uses UDP 161 (for agent requests) and UDP 162 (for Trap messages).
- Custom Port: It can be changed to avoid scanning (ensure consistency between client and device configurations).
3. Firewall Configuration
- If listening on the WAN IP, ensure the router/firewall allows inbound UDP traffic on the specified port (e.g., `WAN → Device_IP:161`).
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content

Information
Helpful: 0
Views: 28
Replies: 2
Voters 0
No one has voted for it yet.