Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

nmap扫描插排地址导致插排重启 #47

Closed
everything411 opened this issue Oct 7, 2019 · 3 comments
Closed

nmap扫描插排地址导致插排重启 #47

everything411 opened this issue Oct 7, 2019 · 3 comments
Assignees

Comments

@everything411
Copy link

everything411 commented Oct 7, 2019

固件版本(必填):v1.0.0

App版本(与app控制有关时必填):

Android版本(与app控制有关时必填):

是否使用服务器(必填):
路由器搭建内网的mosquito mqtt server

问题描述(包含复现issue方式):

无聊尝试nmap扫描插排地址,结果nmap运行过程中,插排断电重启

复现:对插排ip使用nmap必复现 nmap 192.168.1.105

如果作者大大觉得这问题太无聊没有修复的价值就Close吧)

膜大佬给设备开发固件 tql

@a2633063
Copy link
Owner

a2633063 commented Oct 8, 2019

没用过nmap,能否提供软件以及说明给我尝试复现下,如果有必要也是考虑修复的...
最好是windows下的

@everything411
Copy link
Author

everything411 commented Oct 8, 2019

https://nmap.org/download.html

有windows版本可用,但是我后来发现只有在我的openwrt路由器(也是插排连接的路由器)上执行命令才会这样,从Windows或者linux电脑设备上对其执行nmap不会导致其重启。

猜测可能收到来自网关的某种数据包会重启?还是说Openwrt上移植的nmap与其它系统的实现有一定差异?

不过这样看来好像没什么修复价值就是了:)

nmap 192.168.1.105 
# 其中192.168.1.105是插排ip
root@OpenWrt:~# nmap -v 192.168.1.105
Starting Nmap 7.70 ( https://nmap.org ) at 2019-10-08 05:12 UTC
Initiating ARP Ping Scan at 05:12
Scanning 192.168.1.105 [1 port]
Completed ARP Ping Scan at 05:12, 0.25s elapsed (1 total hosts)
Initiating Parallel DNS resolution of 1 host. at 05:12
Completed Parallel DNS resolution of 1 host. at 05:12, 0.00s elapsed
Initiating SYN Stealth Scan at 05:12
Scanning zTC1_e21e.lan (192.168.1.105) [1000 ports]
Connection reset by 192.168.1.1 port 22

最后这里是我和路由器的ssh断开,由于路由器也接在插排上,插排重启,路由器也关机了,自然ssh就断了

@liyiecho
Copy link

liyiecho commented Oct 8, 2019

在openwrt中使用nmap扫描插排相应的IP,2台均已复现,固件版本v1.0.2。

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants