SNMP on ER8411

SNMP on ER8411

SNMP on ER8411
SNMP on ER8411
3 weeks ago
Tags: #SNMP
Model: ER8411  
Hardware Version: V1
Firmware Version: 1.2.1 Build 20240308 Rel.75819

Hello all,

 

This is to follow up on the SNMP issue on TP-Link ER8411, recently highlighted in a previous thread.

 

https://community.tp-link.com/en/business/forum/topic/604876

 

I'm using PRTG to monitor all our network devices (including the TP-Link device). However, I cannot monitor the utilization of interfaces, processors, etc.

 

 

Is there a way to get those (via SNMP) to my PRTG?

 

Alex Kota Kinabalu, Sabah Malaysia
  0      
  0      
#1
Options
9 Reply
Re:SNMP on ER8411
3 weeks ago

Hi @bambinotenchie 

Thanks for posting in our business forum.

It is not a private MIB string. You can use the public MIB for the traffic stats you would like to monitor.

Best Regards! If you are new to the forum, please read: Howto - A Guide to Use Forum Effectively. Read Before You Post. Look for a model? Search your model NOW Official and Beta firmware. NEW features! Subscribe for the latest update!Download Beta Here☚ ☛ ★ Configuration Guide ★ ☚ ☛ ★ Knowledge Base ★ ☚ ☛ ★ Troubleshooting Manual ★ ☚ ● Be kind and nice. ● Stay on the topic. ● Post details. ● Search first. Don't be a lazy asker. ● Please don't take it for granted. ● No email confidentiality should be violated. ● S/N, MAC, and your true public IP should be mosaiced.
  1  
  1  
#2
Options
Re:SNMP on ER8411
2 weeks ago

  @Clive_A 

 

When I run SNMP tools, it gives me this results:

 

----------------------- New Test -----------------------
Paessler SNMP Tester - 23.3.87.552 Computername: ENOCH Interface: 10.250.95.161
27/8/2024 12:13:00 PM (2 ms) : Device: 10.22.2.248
27/8/2024 12:13:00 PM (6 ms) : SNMP v2c
27/8/2024 12:13:00 PM (9 ms) : Scaninterfaces
Scanning Standard Interfaces...
27/8/2024 12:13:00 PM Port Scan: Start Scan
27/8/2024 12:13:00 PM Host: 10.22.2.248
27/8/2024 12:13:00 PM Community: dvgr
27/8/2024 12:13:00 PM SNMP Version: V2
27/8/2024 12:13:00 PM Delay: 0
27/8/2024 12:13:00 PM Force32: No
27/8/2024 12:13:00 PM Single Get: No
27/8/2024 12:13:00 PM GET[OIDVal]: 1.3.6.1.2.1.1.3.0
27/8/2024 12:13:00 PM GET[OIDVal]: Try 1
27/8/2024 12:13:00 PM DoRequest[ 0] Init Session
27/8/2024 12:13:00 PM DoRequest[ 0] Init; Host: 10.22.2.248:161, Timeout: 2000000, Version: 2
27/8/2024 12:13:00 PM DoRequest[ 0] Session: Open
27/8/2024 12:13:00 PM DoRequest[ 0] Session: Send Request
27/8/2024 12:13:00 PM DoRequest[ 0] Session: Send Done
27/8/2024 12:13:00 PM DoRequest[ 0] SynchResponse[13794752] Start
27/8/2024 12:13:02 PM DoRequest[ 0] SynchResponse[13794752] Done:  Status=2
27/8/2024 12:13:02 PM DoRequest[ 0] Timeout
27/8/2024 12:13:02 PM GET[OIDVal]: Try 2
27/8/2024 12:13:02 PM DoRequest[ 0] Init Session
27/8/2024 12:13:02 PM DoRequest[ 0] Init; Host: 10.22.2.248:161, Timeout: 2000000, Version: 2
27/8/2024 12:13:02 PM DoRequest[ 0] Session: Open
27/8/2024 12:13:02 PM DoRequest[ 0] Session: Send Request
27/8/2024 12:13:02 PM DoRequest[ 0] Session: Send Done
27/8/2024 12:13:02 PM DoRequest[ 0] SynchResponse[13794704] Start
27/8/2024 12:13:04 PM DoRequest[ 0] SynchResponse[13794704] Done:  Status=2
27/8/2024 12:13:04 PM DoRequest[ 0] Timeout
27/8/2024 12:13:04 PM GET[OIDVal]: Try 3
27/8/2024 12:13:04 PM DoRequest[ 0] Init Session
27/8/2024 12:13:04 PM DoRequest[ 0] Init; Host: 10.22.2.248:161, Timeout: 2000000, Version: 2
27/8/2024 12:13:04 PM DoRequest[ 0] Session: Open
27/8/2024 12:13:04 PM DoRequest[ 0] Session: Send Request
27/8/2024 12:13:04 PM DoRequest[ 0] Session: Send Done
27/8/2024 12:13:05 PM DoRequest[ 0] SynchResponse[13795016] Start
27/8/2024 12:13:07 PM DoRequest[ 0] SynchResponse[13795016] Done:  Status=2
27/8/2024 12:13:07 PM DoRequest[ 0] Timeout
27/8/2024 12:13:07 PM GET[OIDVal]: Try 4
27/8/2024 12:13:07 PM DoRequest[ 0] Init Session
27/8/2024 12:13:07 PM DoRequest[ 0] Init; Host: 10.22.2.248:161, Timeout: 2000000, Version: 2
27/8/2024 12:13:07 PM DoRequest[ 0] Session: Open
27/8/2024 12:13:07 PM DoRequest[ 0] Session: Send Request
27/8/2024 12:13:07 PM DoRequest[ 0] Session: Send Done
27/8/2024 12:13:07 PM DoRequest[ 0] SynchResponse[13794560] Start
27/8/2024 12:13:09 PM DoRequest[ 0] SynchResponse[13794560] Done:  Status=2
27/8/2024 12:13:09 PM DoRequest[ 0] Timeout
27/8/2024 12:13:09 PM GET[OIDVal]: Try 5
27/8/2024 12:13:09 PM DoRequest[ 0] Init Session
27/8/2024 12:13:09 PM DoRequest[ 0] Init; Host: 10.22.2.248:161, Timeout: 2000000, Version: 2
27/8/2024 12:13:09 PM DoRequest[ 0] Session: Open
27/8/2024 12:13:09 PM DoRequest[ 0] Session: Send Request
27/8/2024 12:13:09 PM DoRequest[ 0] Session: Send Done
27/8/2024 12:13:09 PM DoRequest[ 0] SynchResponse[13795016] Start
27/8/2024 12:13:11 PM DoRequest[ 0] SynchResponse[13795016] Done:  Status=2
27/8/2024 12:13:11 PM DoRequest[ 0] Timeout
Result: #O244

Found standard interfaces:
No standard interfaces found

 

 

This results from using the default SNMP walk on the interface of our router. I think the current firmware has a bug.

 

Thanks

Alex Kota Kinabalu, Sabah Malaysia
  0  
  0  
#4
Options
Re:SNMP on ER8411
2 weeks ago

Hi @bambinotenchie 

Thanks for posting in our business forum.

bambinotenchie wrote

  @Clive_A 

 

When I run SNMP tools, it gives me this results:

 

----------------------- New Test -----------------------
Paessler SNMP Tester - 23.3.87.552 Computername: ENOCH Interface: 10.250.95.161
27/8/2024 12:13:00 PM (2 ms) : Device: 10.22.2.248
27/8/2024 12:13:00 PM (6 ms) : SNMP v2c
27/8/2024 12:13:00 PM (9 ms) : Scaninterfaces
Scanning Standard Interfaces...
27/8/2024 12:13:00 PM Port Scan: Start Scan
27/8/2024 12:13:00 PM Host: 10.22.2.248
27/8/2024 12:13:00 PM Community: dvgr
27/8/2024 12:13:00 PM SNMP Version: V2
27/8/2024 12:13:00 PM Delay: 0
27/8/2024 12:13:00 PM Force32: No
27/8/2024 12:13:00 PM Single Get: No
27/8/2024 12:13:00 PM GET[OIDVal]: 1.3.6.1.2.1.1.3.0
27/8/2024 12:13:00 PM GET[OIDVal]: Try 1
27/8/2024 12:13:00 PM DoRequest[ 0] Init Session
27/8/2024 12:13:00 PM DoRequest[ 0] Init; Host: 10.22.2.248:161, Timeout: 2000000, Version: 2
27/8/2024 12:13:00 PM DoRequest[ 0] Session: Open
27/8/2024 12:13:00 PM DoRequest[ 0] Session: Send Request
27/8/2024 12:13:00 PM DoRequest[ 0] Session: Send Done
27/8/2024 12:13:00 PM DoRequest[ 0] SynchResponse[13794752] Start
27/8/2024 12:13:02 PM DoRequest[ 0] SynchResponse[13794752] Done:  Status=2
27/8/2024 12:13:02 PM DoRequest[ 0] Timeout
27/8/2024 12:13:02 PM GET[OIDVal]: Try 2
27/8/2024 12:13:02 PM DoRequest[ 0] Init Session
27/8/2024 12:13:02 PM DoRequest[ 0] Init; Host: 10.22.2.248:161, Timeout: 2000000, Version: 2
27/8/2024 12:13:02 PM DoRequest[ 0] Session: Open
27/8/2024 12:13:02 PM DoRequest[ 0] Session: Send Request
27/8/2024 12:13:02 PM DoRequest[ 0] Session: Send Done
27/8/2024 12:13:02 PM DoRequest[ 0] SynchResponse[13794704] Start
27/8/2024 12:13:04 PM DoRequest[ 0] SynchResponse[13794704] Done:  Status=2
27/8/2024 12:13:04 PM DoRequest[ 0] Timeout
27/8/2024 12:13:04 PM GET[OIDVal]: Try 3
27/8/2024 12:13:04 PM DoRequest[ 0] Init Session
27/8/2024 12:13:04 PM DoRequest[ 0] Init; Host: 10.22.2.248:161, Timeout: 2000000, Version: 2
27/8/2024 12:13:04 PM DoRequest[ 0] Session: Open
27/8/2024 12:13:04 PM DoRequest[ 0] Session: Send Request
27/8/2024 12:13:04 PM DoRequest[ 0] Session: Send Done
27/8/2024 12:13:05 PM DoRequest[ 0] SynchResponse[13795016] Start
27/8/2024 12:13:07 PM DoRequest[ 0] SynchResponse[13795016] Done:  Status=2
27/8/2024 12:13:07 PM DoRequest[ 0] Timeout
27/8/2024 12:13:07 PM GET[OIDVal]: Try 4
27/8/2024 12:13:07 PM DoRequest[ 0] Init Session
27/8/2024 12:13:07 PM DoRequest[ 0] Init; Host: 10.22.2.248:161, Timeout: 2000000, Version: 2
27/8/2024 12:13:07 PM DoRequest[ 0] Session: Open
27/8/2024 12:13:07 PM DoRequest[ 0] Session: Send Request
27/8/2024 12:13:07 PM DoRequest[ 0] Session: Send Done
27/8/2024 12:13:07 PM DoRequest[ 0] SynchResponse[13794560] Start
27/8/2024 12:13:09 PM DoRequest[ 0] SynchResponse[13794560] Done:  Status=2
27/8/2024 12:13:09 PM DoRequest[ 0] Timeout
27/8/2024 12:13:09 PM GET[OIDVal]: Try 5
27/8/2024 12:13:09 PM DoRequest[ 0] Init Session
27/8/2024 12:13:09 PM DoRequest[ 0] Init; Host: 10.22.2.248:161, Timeout: 2000000, Version: 2
27/8/2024 12:13:09 PM DoRequest[ 0] Session: Open
27/8/2024 12:13:09 PM DoRequest[ 0] Session: Send Request
27/8/2024 12:13:09 PM DoRequest[ 0] Session: Send Done
27/8/2024 12:13:09 PM DoRequest[ 0] SynchResponse[13795016] Start
27/8/2024 12:13:11 PM DoRequest[ 0] SynchResponse[13795016] Done:  Status=2
27/8/2024 12:13:11 PM DoRequest[ 0] Timeout
Result: #O244

Found standard interfaces:
No standard interfaces found

 

 

This results from using the default SNMP walk on the interface of our router. I think the current firmware has a bug.

 

Thanks

First, before we have some substantial evidence to prove it is a bug, I think you should not use the term bug here. Even if this is not available, it is a missing feature instead of a bug. I don't know why the "bug" is spammed so badly in the 21st century.

It does not support and it should be called a "missing feature" or "not supported".

 

Second, you are after the traffic stats of the interfaces, is that correct for you to use the keywords standard interfaces to search for the OID? At least you should use interface as the keyword.

Third, I checked this with the team and got an answer to confirm that this is supported and is using the public MIB. You should look this up in a public MIB. You can refer to the authoritative source of the MIB.

Best Regards! If you are new to the forum, please read: Howto - A Guide to Use Forum Effectively. Read Before You Post. Look for a model? Search your model NOW Official and Beta firmware. NEW features! Subscribe for the latest update!Download Beta Here☚ ☛ ★ Configuration Guide ★ ☚ ☛ ★ Knowledge Base ★ ☚ ☛ ★ Troubleshooting Manual ★ ☚ ● Be kind and nice. ● Stay on the topic. ● Post details. ● Search first. Don't be a lazy asker. ● Please don't take it for granted. ● No email confidentiality should be violated. ● S/N, MAC, and your true public IP should be mosaiced.
  1  
  1  
#5
Options
Re:SNMP on ER8411
a week ago

Out of curiosity, I scanned our router to see whether SNMP port 161 was opened. To my surprise, it wasn't, even though I had enabled the SNMP setting. There is no firewall in front of the router. My Access Control, Remote Management and SNMP settings are set and enabled. Therefore, any suggestion for me to fix this issue?

 

Thank you.

 

NMAP scan result

 

Starting Nmap 7.95 ( nmaporg ) at 2024-09-02 17:33 Malay Peninsula Standard Time
NSE: Loaded 157 scripts for scanning.
NSE: Script Pre-scanning.
Initiating NSE at 17:34
Completed NSE at 17:34, 0.00s elapsed
Initiating NSE at 17:34
Completed NSE at 17:34, 0.00s elapsed
Initiating NSE at 17:34
Completed NSE at 17:34, 0.00s elapsed
Initiating Ping Scan at 17:34
Scanning 10.22.2.248 [4 ports]
Completed Ping Scan at 17:34, 0.15s elapsed (1 total hosts)
Initiating Parallel DNS resolution of 1 host. at 17:34
Completed Parallel DNS resolution of 1 host. at 17:34, 0.03s elapsed
Initiating SYN Stealth Scan at 17:34
Scanning 10.22.2.248 [1000 ports]
Discovered open port 443/tcp on 10.22.2.248
Discovered open port 80/tcp on 10.22.2.248
Discovered open port 2000/tcp on 10.22.2.248
Discovered open port 5060/tcp on 10.22.2.248
Completed SYN Stealth Scan at 17:34, 1.94s elapsed (1000 total ports)
Initiating UDP Scan at 17:34
Scanning 10.22.2.248 [1000 ports]
Increasing send delay for 10.22.2.248 from 0 to 50 due to max_successful_tryno increase to 5
Increasing send delay for 10.22.2.248 from 50 to 100 due to max_successful_tryno increase to 6
Warning: 10.22.2.248 giving up on port because retransmission cap hit (6).
Increasing send delay for 10.22.2.248 from 100 to 200 due to 11 out of 11 dropped probes since last increase.
Discovered open port 500/udp on 10.22.2.248
Increasing send delay for 10.22.2.248 from 200 to 400 due to 11 out of 12 dropped probes since last increase.
UDP Scan Timing: About 6.24% done; ETC: 17:42 (0:07:46 remaining)
Increasing send delay for 10.22.2.248 from 400 to 800 due to 11 out of 18 dropped probes since last increase.
UDP Scan Timing: About 9.31% done; ETC: 17:44 (0:09:54 remaining)
UDP Scan Timing: About 12.57% done; ETC: 17:46 (0:10:33 remaining)
UDP Scan Timing: About 18.26% done; ETC: 17:47 (0:11:16 remaining)
UDP Scan Timing: About 29.59% done; ETC: 17:49 (0:10:31 remaining)
UDP Scan Timing: About 35.93% done; ETC: 17:49 (0:09:45 remaining)
UDP Scan Timing: About 41.76% done; ETC: 17:49 (0:08:57 remaining)
UDP Scan Timing: About 47.50% done; ETC: 17:49 (0:08:09 remaining)
UDP Scan Timing: About 52.87% done; ETC: 17:49 (0:07:22 remaining)
UDP Scan Timing: About 58.53% done; ETC: 17:49 (0:06:32 remaining)
UDP Scan Timing: About 63.96% done; ETC: 17:49 (0:05:42 remaining)
UDP Scan Timing: About 66.70% done; ETC: 17:55 (0:07:09 remaining)
UDP Scan Timing: About 71.30% done; ETC: 17:55 (0:06:04 remaining)
UDP Scan Timing: About 76.21% done; ETC: 17:54 (0:04:57 remaining)
UDP Scan Timing: About 81.20% done; ETC: 17:54 (0:03:52 remaining)
UDP Scan Timing: About 86.24% done; ETC: 17:54 (0:02:48 remaining)
UDP Scan Timing: About 91.36% done; ETC: 17:54 (0:01:44 remaining)
UDP Scan Timing: About 96.40% done; ETC: 17:54 (0:00:43 remaining)
Completed UDP Scan at 17:54, 1227.80s elapsed (1000 total ports)
Initiating Service scan at 17:54
Scanning 19 services on 10.22.2.248
Discovered open port 4500/udp on 10.22.2.248
Discovered open|filtered port 4500/udp on 10.22.2.248 is actually open
Service scan Timing: About 30.00% done; ETC: 17:57 (0:02:25 remaining)
Service scan Timing: About 35.00% done; ETC: 17:59 (0:03:00 remaining)
Completed Service scan at 17:56, 102.68s elapsed (20 services on 1 host)
Initiating OS detection (try #1) against 10.22.2.248
Retrying OS detection (try #2) against 10.22.2.248
Initiating Traceroute at 17:56
Completed Traceroute at 17:56, 0.06s elapsed
Initiating Parallel DNS resolution of 5 hosts. at 17:56
Completed Parallel DNS resolution of 5 hosts. at 17:56, 0.03s elapsed
NSE: Script scanning 10.22.2.248.
Initiating NSE at 17:56
NSOCK ERROR [1339.4190s] mksock_bind_addr(): Bind to 0.0.0.0:4500 failed (IOD #4): An attempt was made to access a socket in a way forbidden by its access permissions.  (10013)
NSOCK ERROR [1340.6660s] mksock_bind_addr(): Bind to 0.0.0.0:500 failed (IOD #58): An attempt was made to access a socket in a way forbidden by its access permissions.  (10013)
NSOCK ERROR [1340.9030s] mksock_bind_addr(): Bind to 0.0.0.0:4500 failed (IOD #64): An attempt was made to access a socket in a way forbidden by its access permissions.  (10013)
NSOCK ERROR [1342.0860s] mksock_bind_addr(): Bind to 0.0.0.0:500 failed (IOD #76): An attempt was made to access a socket in a way forbidden by its access permissions.  (10013)
NSOCK ERROR [1342.3070s] mksock_bind_addr(): Bind to 0.0.0.0:4500 failed (IOD #77): An attempt was made to access a socket in a way forbidden by its access permissions.  (10013)
NSOCK ERROR [1343.5100s] mksock_bind_addr(): Bind to 0.0.0.0:500 failed (IOD #78): An attempt was made to access a socket in a way forbidden by its access permissions.  (10013)
NSOCK ERROR [1343.7620s] mksock_bind_addr(): Bind to 0.0.0.0:4500 failed (IOD #79): An attempt was made to access a socket in a way forbidden by its access permissions.  (10013)
NSOCK ERROR [1344.9580s] mksock_bind_addr(): Bind to 0.0.0.0:500 failed (IOD #82): An attempt was made to access a socket in a way forbidden by its access permissions.  (10013)
NSOCK ERROR [1346.6590s] mksock_bind_addr(): Bind to 0.0.0.0:500 failed (IOD #83): An attempt was made to access a socket in a way forbidden by its access permissions.  (10013)
NSOCK ERROR [1353.8900s] mksock_bind_addr(): Bind to 0.0.0.0:500 failed (IOD #85): An attempt was made to access a socket in a way forbidden by its access permissions.  (10013)
NSOCK ERROR [1368.0420s] mksock_bind_addr(): Bind to 0.0.0.0:500 failed (IOD #87): An attempt was made to access a socket in a way forbidden by its access permissions.  (10013)
NSOCK ERROR [1382.0540s] mksock_bind_addr(): Bind to 0.0.0.0:500 failed (IOD #89): An attempt was made to access a socket in a way forbidden by its access permissions.  (10013)
NSOCK ERROR [1396.0870s] mksock_bind_addr(): Bind to 0.0.0.0:500 failed (IOD #91): An attempt was made to access a socket in a way forbidden by its access permissions.  (10013)
NSOCK ERROR [1410.1010s] mksock_bind_addr(): Bind to 0.0.0.0:500 failed (IOD #93): An attempt was made to access a socket in a way forbidden by its access permissions.  (10013)
NSOCK ERROR [1424.1220s] mksock_bind_addr(): Bind to 0.0.0.0:500 failed (IOD #95): An attempt was made to access a socket in a way forbidden by its access permissions.  (10013)
NSOCK ERROR [1438.1530s] mksock_bind_addr(): Bind to 0.0.0.0:500 failed (IOD #97): An attempt was made to access a socket in a way forbidden by its access permissions.  (10013)
NSOCK ERROR [1452.1730s] mksock_bind_addr(): Bind to 0.0.0.0:500 failed (IOD #99): An attempt was made to access a socket in a way forbidden by its access permissions.  (10013)
NSOCK ERROR [1466.1980s] mksock_bind_addr(): Bind to 0.0.0.0:500 failed (IOD #101): An attempt was made to access a socket in a way forbidden by its access permissions.  (10013)
NSOCK ERROR [1480.2200s] mksock_bind_addr(): Bind to 0.0.0.0:500 failed (IOD #103): An attempt was made to access a socket in a way forbidden by its access permissions.  (10013)
NSOCK ERROR [1494.2520s] mksock_bind_addr(): Bind to 0.0.0.0:500 failed (IOD #105): An attempt was made to access a socket in a way forbidden by its access permissions.  (10013)
NSOCK ERROR [1508.2820s] mksock_bind_addr(): Bind to 0.0.0.0:500 failed (IOD #107): An attempt was made to access a socket in a way forbidden by its access permissions.  (10013)
NSOCK ERROR [1522.2990s] mksock_bind_addr(): Bind to 0.0.0.0:500 failed (IOD #109): An attempt was made to access a socket in a way forbidden by its access permissions.  (10013)
Completed NSE at 17:59, 196.94s elapsed
Initiating NSE at 17:59
Completed NSE at 17:59, 1.19s elapsed
Initiating NSE at 17:59
Completed NSE at 17:59, 0.00s elapsed
Nmap scan report for 10.22.2.248
Host is up (0.047s latency).
Not shown: 995 closed tcp ports (reset), 984 closed udp ports (port-unreach)
PORT      STATE         SERVICE      VERSION
80/tcp    open          http         OpenWrt uHTTPd (TP-LINK router http config)
|_http-title: Site doesn't have a title (text/html).
| http-methods:
|_  Supported Methods: GET HEAD POST OPTIONS
443/tcp   open          ssl/http     OpenWrt uHTTPd (TP-LINK router http config)
| ssl-cert: Subject: commonName=TP-Link/stateOrProvinceName=ShenZhen/countryName=CN
| Issuer: commonName=TP-Link/stateOrProvinceName=ShenZhen/countryName=CN
| Public Key type: rsa
| Public Key bits: 1024
| Signature Algorithm: sha256WithRSAEncryption
| Not valid before: 2018-01-01T08:00:22
| Not valid after:  2037-09-18T08:00:22
| MD5:   884c:96c2:2565:296f:5791:f65b:8e46:6097
|_SHA-1: 2f69:b83e:b482:8dd3:32b7:3a33:5e8e:c4ed:6f91:4540
|_ssl-date: TLS randomness does not represent time
| http-methods:
|_  Supported Methods: GET HEAD POST OPTIONS
|_http-title: Site doesn't have a title (text/html).
445/tcp   filtered      microsoft-ds
2000/tcp  open          tcpwrapped
5060/tcp  open          tcpwrapped
53/udp    open|filtered domain
500/udp   open          isakmp       StrongSwan ISAKMP
4500/udp  open          isakmp       StrongSwan ISAKMP
5050/udp  open|filtered mmcc
5060/udp  open|filtered sip
17207/udp open|filtered unknown
19650/udp open|filtered unknown
21344/udp open|filtered unknown
21383/udp open|filtered unknown
30697/udp open|filtered unknown
37602/udp open|filtered unknown
38615/udp open|filtered unknown
40708/udp open|filtered unknown
40732/udp open|filtered unknown
49194/udp open|filtered unknown
49201/udp open|filtered unknown
Device type: general purpose|storage-misc|firewall|proxy server|broadband router|PBX|WAP
Running (JUST GUESSING): Linux 2.6.X|3.X (91%), Dell embedded (89%), Cisco embedded (89%), Riverbed embedded (89%), Zhone embedded (89%), Ruckus embedded (89%)
OS CPE: cpe:/o:linux:linux_kernel:2.6.32 cpe:/h:dell:dr4100 cpe:/o:linux:linux_kernel:2.6 cpe:/h:cisco:sa520 cpe:/h:riverbed:steelhead_200 cpe:/h:cisco:uc320w cpe:/h:ruckus:7363 cpe:/o:linux:linux_kernel:3.0
Aggressive OS guesses: Linux 2.6.32 (91%), Linux 2.6.18 (91%), Linux 2.6.9 - 2.6.18 (90%), Linux 2.6.9 (90%), Linux 2.6.5 (89%), Dell DR4100 backup appliance (89%), Cisco SA520 firewall (Linux 2.6) (89%), Linux 2.6.28 (89%), Linux 2.6.8 (89%), Linux 2.6.9 - 2.6.27 (89%)
No exact OS matches for host (test conditions non-ideal).
Uptime guess: 2.462 days (since Sat Aug 31 06:54:55 2024)
Network Distance: 6 hops
TCP Sequence Prediction: Difficulty=261 (Good luck!)
IP ID Sequence Generation: All zeros
Service Info: OS: Linux; Device: broadband router; CPE: cpe:/o:linux:linux_kernel

TRACEROUTE (using port 3389/tcp)
HOP RTT      ADDRESS
1   1.00 ms  10.250.95.254
2   1.00 ms  xxx.xxx.xxx.xxx
3   1.00 ms  xxx.xxx.xxx.xxx
4   1.00 ms  xxx.xxx.xxx.xxx
5   45.00 ms xxx.xxx.xxx.xxx
6   46.00 ms 10.22.2.248

NSE: Script Post-scanning.
Initiating NSE at 17:59
Completed NSE at 17:59, 0.00s elapsed
Initiating NSE at 17:59
Completed NSE at 17:59, 0.00s elapsed
Initiating NSE at 17:59
Completed NSE at 17:59, 0.00s elapsed
Read data files from: C:\Program Files (x86)\Nmap
OS and Service detection performed. Please report any incorrect results at nmaporg/submit .
Nmap done: 1 IP address (1 host up) scanned in 1537.52 seconds
           Raw packets sent: 2590 (121.993KB) | Rcvd: 2118 (120.184KB)

 

 

Access Control settings

 

 

 

 

Remote Management settings

 

 

 

SNMP settings

 

 

Alex Kota Kinabalu, Sabah Malaysia
  0  
  0  
#6
Options
Re:SNMP on ER8411
a week ago

Hi @bambinotenchie 

Thanks for posting in our business forum.

Best Regards! If you are new to the forum, please read: Howto - A Guide to Use Forum Effectively. Read Before You Post. Look for a model? Search your model NOW Official and Beta firmware. NEW features! Subscribe for the latest update!Download Beta Here☚ ☛ ★ Configuration Guide ★ ☚ ☛ ★ Knowledge Base ★ ☚ ☛ ★ Troubleshooting Manual ★ ☚ ● Be kind and nice. ● Stay on the topic. ● Post details. ● Search first. Don't be a lazy asker. ● Please don't take it for granted. ● No email confidentiality should be violated. ● S/N, MAC, and your true public IP should be mosaiced.
  0  
  0  
#7
Options
Re:SNMP on ER8411
a week ago

  @Clive_A 

 

I tried but still no luck. Maybe I have to reset to factory default and start again.

 

 

Starting Nmap 7.95 ( https://nmaporg ) at 2024-09-03 10:36 Malay Peninsula Standard Time
NSE: Loaded 157 scripts for scanning.
NSE: Script Pre-scanning.
Initiating NSE at 10:36
Completed NSE at 10:36, 0.00s elapsed
Initiating NSE at 10:36
Completed NSE at 10:36, 0.00s elapsed
Initiating NSE at 10:36
Completed NSE at 10:36, 0.00s elapsed
Initiating Ping Scan at 10:36
Scanning 10.22.2.248 [4 ports]
Completed Ping Scan at 10:36, 0.15s elapsed (1 total hosts)
Initiating Parallel DNS resolution of 1 host. at 10:36
Completed Parallel DNS resolution of 1 host. at 10:36, 0.03s elapsed
Initiating SYN Stealth Scan at 10:36
Scanning 10.22.2.248 [1000 ports]
Discovered open port 443/tcp on 10.22.2.248
Discovered open port 80/tcp on 10.22.2.248
Discovered open port 2000/tcp on 10.22.2.248
Discovered open port 5060/tcp on 10.22.2.248
Completed SYN Stealth Scan at 10:36, 2.02s elapsed (1000 total ports)
Initiating UDP Scan at 10:36
Scanning 10.22.2.248 [1000 ports]
Increasing send delay for 10.22.2.248 from 0 to 50 due to max_successful_tryno increase to 5
Increasing send delay for 10.22.2.248 from 50 to 100 due to max_successful_tryno increase to 6
Warning: 10.22.2.248 giving up on port because retransmission cap hit (6).
Increasing send delay for 10.22.2.248 from 100 to 200 due to 11 out of 11 dropped probes since last increase.
Increasing send delay for 10.22.2.248 from 200 to 400 due to 11 out of 11 dropped probes since last increase.
UDP Scan Timing: About 6.20% done; ETC: 10:45 (0:07:49 remaining)
Increasing send delay for 10.22.2.248 from 400 to 800 due to 11 out of 11 dropped probes since last increase.
UDP Scan Timing: About 9.10% done; ETC: 10:48 (0:10:09 remaining)
UDP Scan Timing: About 12.16% done; ETC: 10:49 (0:10:58 remaining)
UDP Scan Timing: About 32.07% done; ETC: 10:52 (0:10:18 remaining)
UDP Scan Timing: About 38.33% done; ETC: 10:52 (0:09:31 remaining)
UDP Scan Timing: About 44.37% done; ETC: 10:52 (0:08:40 remaining)
UDP Scan Timing: About 49.80% done; ETC: 10:52 (0:07:53 remaining)
UDP Scan Timing: About 55.00% done; ETC: 10:52 (0:07:05 remaining)
UDP Scan Timing: About 60.20% done; ETC: 10:52 (0:06:18 remaining)
UDP Scan Timing: About 65.46% done; ETC: 10:52 (0:05:30 remaining)
UDP Scan Timing: About 70.57% done; ETC: 10:52 (0:04:42 remaining)
UDP Scan Timing: About 75.79% done; ETC: 10:52 (0:03:52 remaining)
Discovered open port 500/udp on 10.22.2.248
UDP Scan Timing: About 81.09% done; ETC: 10:52 (0:03:01 remaining)
UDP Scan Timing: About 86.29% done; ETC: 10:52 (0:02:12 remaining)
UDP Scan Timing: About 91.34% done; ETC: 10:52 (0:01:23 remaining)
UDP Scan Timing: About 96.46% done; ETC: 10:53 (0:00:34 remaining)
Completed UDP Scan at 10:53, 1001.29s elapsed (1000 total ports)
Initiating Service scan at 10:53
Scanning 19 services on 10.22.2.248
Discovered open port 4500/udp on 10.22.2.248
Discovered open|filtered port 4500/udp on 10.22.2.248 is actually open
Service scan Timing: About 30.00% done; ETC: 10:57 (0:02:25 remaining)
Service scan Timing: About 35.00% done; ETC: 10:58 (0:03:02 remaining)
Completed Service scan at 10:55, 102.72s elapsed (20 services on 1 host)
Initiating OS detection (try #1) against 10.22.2.248
Retrying OS detection (try #2) against 10.22.2.248
Initiating Traceroute at 10:55
Completed Traceroute at 10:55, 0.06s elapsed
Initiating Parallel DNS resolution of 5 hosts. at 10:55
Completed Parallel DNS resolution of 5 hosts. at 10:55, 0.03s elapsed
NSE: Script scanning 10.22.2.248.
Initiating NSE at 10:55
NSOCK ERROR [1114.7290s] mksock_bind_addr(): Bind to 0.0.0.0:500 failed (IOD #18): An attempt was made to access a socket in a way forbidden by its access permissions.  (10013)
NSOCK ERROR [1114.9700s] mksock_bind_addr(): Bind to 0.0.0.0:4500 failed (IOD #25): An attempt was made to access a socket in a way forbidden by its access permissions.  (10013)
NSOCK ERROR [1116.1610s] mksock_bind_addr(): Bind to 0.0.0.0:500 failed (IOD #65): An attempt was made to access a socket in a way forbidden by its access permissions.  (10013)
NSOCK ERROR [1116.3940s] mksock_bind_addr(): Bind to 0.0.0.0:4500 failed (IOD #69): An attempt was made to access a socket in a way forbidden by its access permissions.  (10013)
NSOCK ERROR [1117.5730s] mksock_bind_addr(): Bind to 0.0.0.0:500 failed (IOD #75): An attempt was made to access a socket in a way forbidden by its access permissions.  (10013)
NSOCK ERROR [1117.8130s] mksock_bind_addr(): Bind to 0.0.0.0:4500 failed (IOD #77): An attempt was made to access a socket in a way forbidden by its access permissions.  (10013)
NSOCK ERROR [1118.9890s] mksock_bind_addr(): Bind to 0.0.0.0:500 failed (IOD #78): An attempt was made to access a socket in a way forbidden by its access permissions.  (10013)
NSOCK ERROR [1119.2380s] mksock_bind_addr(): Bind to 0.0.0.0:4500 failed (IOD #79): An attempt was made to access a socket in a way forbidden by its access permissions.  (10013)
NSOCK ERROR [1121.7270s] mksock_bind_addr(): Bind to 0.0.0.0:4500 failed (IOD #82): An attempt was made to access a socket in a way forbidden by its access permissions.  (10013)
NSOCK ERROR [1128.9730s] mksock_bind_addr(): Bind to 0.0.0.0:4500 failed (IOD #84): An attempt was made to access a socket in a way forbidden by its access permissions.  (10013)
NSOCK ERROR [1143.1220s] mksock_bind_addr(): Bind to 0.0.0.0:4500 failed (IOD #86): An attempt was made to access a socket in a way forbidden by its access permissions.  (10013)
NSOCK ERROR [1157.1470s] mksock_bind_addr(): Bind to 0.0.0.0:4500 failed (IOD #88): An attempt was made to access a socket in a way forbidden by its access permissions.  (10013)
NSOCK ERROR [1171.1770s] mksock_bind_addr(): Bind to 0.0.0.0:4500 failed (IOD #90): An attempt was made to access a socket in a way forbidden by its access permissions.  (10013)
NSOCK ERROR [1185.2090s] mksock_bind_addr(): Bind to 0.0.0.0:4500 failed (IOD #92): An attempt was made to access a socket in a way forbidden by its access permissions.  (10013)
NSOCK ERROR [1199.2320s] mksock_bind_addr(): Bind to 0.0.0.0:4500 failed (IOD #94): An attempt was made to access a socket in a way forbidden by its access permissions.  (10013)
NSOCK ERROR [1213.2510s] mksock_bind_addr(): Bind to 0.0.0.0:4500 failed (IOD #96): An attempt was made to access a socket in a way forbidden by its access permissions.  (10013)
NSOCK ERROR [1227.2910s] mksock_bind_addr(): Bind to 0.0.0.0:4500 failed (IOD #98): An attempt was made to access a socket in a way forbidden by its access permissions.  (10013)
NSOCK ERROR [1241.3190s] mksock_bind_addr(): Bind to 0.0.0.0:4500 failed (IOD #100): An attempt was made to access a socket in a way forbidden by its access permissions.  (10013)
NSOCK ERROR [1255.3580s] mksock_bind_addr(): Bind to 0.0.0.0:4500 failed (IOD #102): An attempt was made to access a socket in a way forbidden by its access permissions.  (10013)
NSOCK ERROR [1269.3840s] mksock_bind_addr(): Bind to 0.0.0.0:4500 failed (IOD #104): An attempt was made to access a socket in a way forbidden by its access permissions.  (10013)
NSOCK ERROR [1283.4280s] mksock_bind_addr(): Bind to 0.0.0.0:4500 failed (IOD #106): An attempt was made to access a socket in a way forbidden by its access permissions.  (10013)
NSOCK ERROR [1297.4590s] mksock_bind_addr(): Bind to 0.0.0.0:4500 failed (IOD #108): An attempt was made to access a socket in a way forbidden by its access permissions.  (10013)
Completed NSE at 10:58, 197.06s elapsed
Initiating NSE at 10:58
Completed NSE at 10:58, 1.22s elapsed
Initiating NSE at 10:58
Completed NSE at 10:58, 0.00s elapsed
Nmap scan report for 10.22.2.248
Host is up (0.045s latency).
Not shown: 995 closed tcp ports (reset), 984 closed udp ports (port-unreach)
PORT      STATE         SERVICE       VERSION
80/tcp    open          http          OpenWrt uHTTPd (TP-LINK router http config)
|_http-title: Site doesn't have a title (text/html).
| http-methods:
|_  Supported Methods: GET HEAD POST OPTIONS
443/tcp   open          ssl/http      OpenWrt uHTTPd (TP-LINK router http config)
| ssl-cert: Subject: commonName=TP-Link/stateOrProvinceName=ShenZhen/countryName=CN
| Issuer: commonName=TP-Link/stateOrProvinceName=ShenZhen/countryName=CN
| Public Key type: rsa
| Public Key bits: 1024
| Signature Algorithm: sha256WithRSAEncryption
| Not valid before: 2018-01-01T08:00:22
| Not valid after:  2037-09-18T08:00:22
| MD5:   884c:96c2:2565:296f:5791:f65b:8e46:6097
|_SHA-1: 2f69:b83e:b482:8dd3:32b7:3a33:5e8e:c4ed:6f91:4540
|_ssl-date: TLS randomness does not represent time
|_http-title: Site doesn't have a title (text/html).
| http-methods:
|_  Supported Methods: GET HEAD POST OPTIONS
445/tcp   filtered      microsoft-ds
2000/tcp  open          tcpwrapped
5060/tcp  open          tcpwrapped
42/udp    open|filtered nameserver
53/udp    open|filtered domain
500/udp   open          isakmp        StrongSwan ISAKMP
626/udp   open|filtered serialnumberd
2223/udp  open|filtered rockwell-csp2
4500/udp  open          isakmp        StrongSwan ISAKMP
5060/udp  open|filtered sip
17824/udp open|filtered unknown
19683/udp open|filtered unknown
22029/udp open|filtered unknown
27707/udp open|filtered unknown
36458/udp open|filtered unknown
39217/udp open|filtered unknown
45247/udp open|filtered unknown
49198/udp open|filtered unknown
59846/udp open|filtered unknown
Device type: general purpose|storage-misc|firewall|proxy server|broadband router|PBX|WAP
Running (JUST GUESSING): Linux 2.6.X|3.X (91%), Dell embedded (89%), Cisco embedded (89%), Riverbed embedded (89%), Zhone embedded (89%), Ruckus embedded (89%)
OS CPE: cpe:/o:linux:linux_kernel:2.6.32 cpe:/h:dell:dr4100 cpe:/o:linux:linux_kernel:2.6 cpe:/h:cisco:sa520 cpe:/h:riverbed:steelhead_200 cpe:/h:cisco:uc320w cpe:/h:ruckus:7363 cpe:/o:linux:linux_kernel:3.0
Aggressive OS guesses: Linux 2.6.32 (91%), Linux 2.6.18 (91%), Linux 2.6.9 - 2.6.18 (90%), Linux 2.6.9 (90%), Linux 2.6.5 (89%), Dell DR4100 backup appliance (89%), Cisco SA520 firewall (Linux 2.6) (89%), Linux 2.6.28 (89%), Linux 2.6.8 (89%), Linux 2.6.9 - 2.6.27 (89%)
No exact OS matches for host (test conditions non-ideal).
Uptime guess: 3.169 days (since Sat Aug 31 06:54:54 2024)
Network Distance: 6 hops
TCP Sequence Prediction: Difficulty=261 (Good luck!)
IP ID Sequence Generation: All zeros
Service Info: OS: Linux; Device: broadband router; CPE: cpe:/o:linux:linux_kernel

TRACEROUTE (using port 993/tcp)
HOP RTT      ADDRESS
1   1.00 ms  10.250.95.254
2   1.00 ms  xxx.xxx.xxx.xxx
3   1.00 ms  xxx.xxx.xxx.xxx
4   1.00 ms  xxx.xxx.xxx.xxx
5   45.00 ms xxx.xxx.xxx.xxx
6   45.00 ms 10.22.2.248

NSE: Script Post-scanning.
Initiating NSE at 10:58
Completed NSE at 10:58, 0.00s elapsed
Initiating NSE at 10:58
Completed NSE at 10:58, 0.00s elapsed
Initiating NSE at 10:58
Completed NSE at 10:58, 0.00s elapsed
Read data files from: C:\Program Files (x86)\Nmap
OS and Service detection performed. Please report any incorrect results at https://nmaporg/submit/ .
Nmap done: 1 IP address (1 host up) scanned in 1312.73 seconds
           Raw packets sent: 2578 (122.369KB) | Rcvd: 2125 (120.915KB)

 

Alex Kota Kinabalu, Sabah Malaysia
  0  
  0  
#8
Options
Re:SNMP on ER8411
a week ago

Hi @bambinotenchie 

Thanks for posting in our business forum.

I didn't experience any SNMP problems on the ER8411 which I just tested it.

Best Regards! If you are new to the forum, please read: Howto - A Guide to Use Forum Effectively. Read Before You Post. Look for a model? Search your model NOW Official and Beta firmware. NEW features! Subscribe for the latest update!Download Beta Here☚ ☛ ★ Configuration Guide ★ ☚ ☛ ★ Knowledge Base ★ ☚ ☛ ★ Troubleshooting Manual ★ ☚ ● Be kind and nice. ● Stay on the topic. ● Post details. ● Search first. Don't be a lazy asker. ● Please don't take it for granted. ● No email confidentiality should be violated. ● S/N, MAC, and your true public IP should be mosaiced.
  0  
  0  
#9
Options
Re:SNMP on ER8411
a week ago
If so, I have to reset it to the factory default. Maybe it works. Are you using the same firmware releases? My router's firmware is still using v1.2.1
Alex Kota Kinabalu, Sabah Malaysia
  0  
  0  
#10
Options
Re:SNMP on ER8411
a week ago

Hi @bambinotenchie 

Thanks for posting in our business forum.

bambinotenchie wrote

If so, I have to reset it to the factory default. Maybe it works. Are you using the same firmware releases? My router's firmware is still using v1.2.1

Yes.

Best Regards! If you are new to the forum, please read: Howto - A Guide to Use Forum Effectively. Read Before You Post. Look for a model? Search your model NOW Official and Beta firmware. NEW features! Subscribe for the latest update!Download Beta Here☚ ☛ ★ Configuration Guide ★ ☚ ☛ ★ Knowledge Base ★ ☚ ☛ ★ Troubleshooting Manual ★ ☚ ● Be kind and nice. ● Stay on the topic. ● Post details. ● Search first. Don't be a lazy asker. ● Please don't take it for granted. ● No email confidentiality should be violated. ● S/N, MAC, and your true public IP should be mosaiced.
  0  
  0  
#11
Options

Information

Helpful: 0

Views: 184

Replies: 9

Tags

Related Articles