1
- [ crates-badge ] : https://img.shields.io/crates/v/nemio .svg
2
- [ crates-url ] : https://crates.io/crates/nemio
1
+ [ crates-badge ] : https://img.shields.io/crates/v/nrev .svg
2
+ [ crates-url ] : https://crates.io/crates/nrev
3
3
4
- # nemio [ ![ Crates.io] [ crates-badge ]] [ crates-url ]
4
+ # nrev [ ![ Crates.io] [ crates-badge ]] [ crates-url ]
5
5
Simple and Fast Network Mapper. Written in Rust.
6
6
Designed to be used in network mapping, probe, and security tests.
7
7
@@ -23,52 +23,52 @@ Designed to be used in network mapping, probe, and security tests.
23
23
### Install prebuilt binaries via shell script
24
24
25
25
``` sh
26
- curl --proto ' =https' --tlsv1.2 -LsSf https://github.com/shellrow/nemio /releases/latest/download/nemio -installer.sh | sh
26
+ curl --proto ' =https' --tlsv1.2 -LsSf https://github.com/shellrow/nrev /releases/latest/download/nrev -installer.sh | sh
27
27
```
28
28
29
29
### Install prebuilt binaries via powershell script
30
30
31
31
``` sh
32
- irm https://github.com/shellrow/nemio /releases/latest/download/nemio -installer.ps1 | iex
32
+ irm https://github.com/shellrow/nrev /releases/latest/download/nrev -installer.ps1 | iex
33
33
```
34
34
35
35
### Install prebuilt binaries via Homebrew
36
36
37
37
``` sh
38
- brew install shellrow/tap-nemio/nemio
38
+ brew install shellrow/tap-nrev/nrev
39
39
```
40
40
41
41
### From Releases
42
- You can download archives of precompiled binaries from the [ releases] ( https://github.com/shellrow/nemio /releases ) .
42
+ You can download archives of precompiled binaries from the [ releases] ( https://github.com/shellrow/nrev /releases ) .
43
43
44
44
### Cargo
45
- If you have Rust and the Cargo package manager installed on your system, you can install (download and build) ` nemio ` with the following command:
45
+ If you have Rust and the Cargo package manager installed on your system, you can install (download and build) ` nrev ` with the following command:
46
46
```
47
- cargo install nemio
47
+ cargo install nrev
48
48
```
49
49
50
- Or you can use [ binstall] ( https://github.com/cargo-bins/cargo-binstall ) for install nemio from github release.
50
+ Or you can use [ binstall] ( https://github.com/cargo-bins/cargo-binstall ) for install nrev from github release.
51
51
```
52
- cargo binstall nemio
52
+ cargo binstall nrev
53
53
```
54
54
55
55
## Basic Usage
56
56
### Default Port Scan
57
57
To scan the default 1000 ports on a target, simply specify the target
58
58
```
59
- nemio --target scanme.nmap.org
59
+ nrev --target scanme.nmap.org
60
60
```
61
61
62
62
Sub-commands and Options
63
63
```
64
- Usage: nemio [OPTIONS] [COMMAND]
64
+ Usage: nrev [OPTIONS] [COMMAND]
65
65
66
66
Commands:
67
- port Scan port. nemio port --help for more information
68
- host Scan host in specified network or host-list. nemio host --help for more information
69
- ping Ping to specified host. nemio ping --help for more information
70
- trace Traceroute to specified host. nemio trace --help for more information
71
- subdomain Find subdomains. nemio subdomain --help for more information
67
+ port Scan port. nrev port --help for more information
68
+ host Scan host in specified network or host-list. nrev host --help for more information
69
+ ping Ping to specified host. nrev ping --help for more information
70
+ trace Traceroute to specified host. nrev trace --help for more information
71
+ subdomain Find subdomains. nrev subdomain --help for more information
72
72
nei Resolve IP address to MAC address
73
73
interfaces Show network interfaces
74
74
interface Show default network interface
@@ -90,119 +90,119 @@ Options:
90
90
### Port scan
91
91
Scan default 1000 ports
92
92
```
93
- nemio port scanme.nmap.org
93
+ nrev port scanme.nmap.org
94
94
```
95
95
96
96
Specify the ports
97
97
```
98
- nemio port scanme.nmap.org --ports 22,80,443,5000,8080
98
+ nrev port scanme.nmap.org --ports 22,80,443,5000,8080
99
99
```
100
100
101
101
Specify the range
102
102
```
103
- nemio port scanme.nmap.org --range 20-100
103
+ nrev port scanme.nmap.org --range 20-100
104
104
```
105
105
106
106
Scan well-known ports
107
107
```
108
- nemio port scanme.nmap.org --wellknown
108
+ nrev port scanme.nmap.org --wellknown
109
109
```
110
110
111
111
#### Settings
112
- By default, nemio determines the waiting time until packet reception (before concluding the scan task) based on the results of the initial PING.
112
+ By default, nrev determines the waiting time until packet reception (before concluding the scan task) based on the results of the initial PING.
113
113
The initial PING is executed in the order of ICMP Ping, UDP Ping, TCP Ping (on port 80), and if successful, proceeds to the next scan task.
114
- If all PING attempts fail, nemio exits before executing the scan. This step can be skipped by setting the ` --noping ` flag.
115
- For other settings, please refer to ` nemio port -h` for details.
114
+ If all PING attempts fail, nrev exits before executing the scan. This step can be skipped by setting the ` --noping ` flag.
115
+ For other settings, please refer to ` nrev port -h` for details.
116
116
117
117
### Host scan
118
118
ICMP Host scan
119
119
```
120
- nemio host 192.168.1.0/24
120
+ nrev host 192.168.1.0/24
121
121
```
122
122
```
123
- nemio host <path-to-host-list>
123
+ nrev host <path-to-host-list>
124
124
```
125
125
126
126
TCP Host scan
127
127
```
128
- nemio host 192.168.1.0/24 -P TCP --port 80
128
+ nrev host 192.168.1.0/24 -P TCP --port 80
129
129
```
130
130
131
131
### Ping
132
132
Default ICMP Ping
133
133
```
134
- nemio ping 1.1.1.1
134
+ nrev ping 1.1.1.1
135
135
```
136
136
137
137
UDP Ping
138
138
```
139
- nemio ping 1.1.1.1 -P UDP
139
+ nrev ping 1.1.1.1 -P UDP
140
140
```
141
141
142
142
TCP Ping
143
143
```
144
- nemio ping 1.1.1.1:443 -P TCP
144
+ nrev ping 1.1.1.1:443 -P TCP
145
145
```
146
146
147
147
### Traceroute
148
148
TCP Ping
149
149
```
150
- nemio trace 8.8.8.8
150
+ nrev trace 8.8.8.8
151
151
```
152
152
153
153
You can specify the interval in milliseconds for faster trace.
154
154
```
155
- nemio trace 8.8.8.8 --rate 500
155
+ nrev trace 8.8.8.8 --rate 500
156
156
```
157
157
158
158
### Subdomain scan
159
159
```
160
- nemio subdomain google.com
160
+ nrev subdomain google.com
161
161
```
162
162
163
163
### Neighbor (ARP/NDP)
164
164
```
165
- nemio nei 192.168.1.1
165
+ nrev nei 192.168.1.1
166
166
```
167
167
168
168
### Specify the network interface
169
169
```
170
- nemio -i tun0 port 10.10.11.14
170
+ nrev -i tun0 port 10.10.11.14
171
171
```
172
172
173
173
## Privileges
174
- ` nemio ` uses a raw socket which require elevated privileges. Execute with administrator privileges.
174
+ ` nrev ` uses a raw socket which require elevated privileges. Execute with administrator privileges.
175
175
176
176
### Note for Linux Users
177
- ` nemio ` requires elevated privileges to send/receive raw-packet. On Linux, you can configure these privileges using two main methods:
177
+ ` nrev ` requires elevated privileges to send/receive raw-packet. On Linux, you can configure these privileges using two main methods:
178
178
179
179
#### 1. Using ` setcap `
180
180
181
- Granting capabilities to the ` nemio ` binary allows it to operate with the necessary privileges without requiring ` sudo ` for each execution.
181
+ Granting capabilities to the ` nrev ` binary allows it to operate with the necessary privileges without requiring ` sudo ` for each execution.
182
182
This method is recommended for single-user machines or in environments where all users are trusted.
183
183
184
- Assign necessary capabilities to the nemio binary
184
+ Assign necessary capabilities to the nrev binary
185
185
``` sh
186
- sudo setcap ' cap_sys_ptrace,cap_dac_read_search,cap_net_raw,cap_net_admin+ep' $( command -v nemio )
186
+ sudo setcap ' cap_sys_ptrace,cap_dac_read_search,cap_net_raw,cap_net_admin+ep' $( command -v nrev )
187
187
```
188
188
189
- Run nemio as an unprivileged user:
189
+ Run nrev as an unprivileged user:
190
190
``` sh
191
- nemio
191
+ nrev
192
192
```
193
193
194
194
#### Capabilities Explained:
195
- - ` cap_sys_ptrace,cap_dac_read_search ` : Allows ` nemio ` to access ` /proc/<pid>/fd/ ` to identify which open port belongs to which process.
195
+ - ` cap_sys_ptrace,cap_dac_read_search ` : Allows ` nrev ` to access ` /proc/<pid>/fd/ ` to identify which open port belongs to which process.
196
196
- ` cap_net_raw,cap_net_admin ` : Enables packet capturing capabilities.
197
197
198
198
#### 2. Using ` sudo ` (for multi-user environments)
199
- For environments with multiple users, requiring privilege escalation each time nemio is run can enhance security.
199
+ For environments with multiple users, requiring privilege escalation each time nrev is run can enhance security.
200
200
```
201
- sudo nemio
201
+ sudo nrev
202
202
```
203
203
204
204
### Note for macOS Users
205
- On macOS, managing access to the Berkeley Packet Filter (BPF) devices is necessary for ` nemio ` to send/receive raw-packet
205
+ On macOS, managing access to the Berkeley Packet Filter (BPF) devices is necessary for ` nrev ` to send/receive raw-packet
206
206
Alternatively, of course, you can also use ` sudo ` to temporarily grant the necessary permissions.
207
207
#### Install ` chmod-bpf ` to automatically manage permissions for BPF devices:
208
208
@@ -227,7 +227,7 @@ sudo chmod-bpf install
227
227
```
228
228
229
229
### Note for Windows Users
230
- - Ensure that you have [ Npcap] ( https://npcap.com/#download ) installed, which is necessary for ` nemio ` to send/receive raw-packet on Windows
230
+ - Ensure that you have [ Npcap] ( https://npcap.com/#download ) installed, which is necessary for ` nrev ` to send/receive raw-packet on Windows
231
231
- Download and install Npcap from [ Npcap] ( https://npcap.com/#download ) . Choose the "Install Npcap in WinPcap API-compatible Mode" during installation.
232
232
- Build Dependencies:
233
233
- Place the Packet.lib file from the [ Npcap SDK] ( https://npcap.com/#download ) or WinPcap Developers pack in a directory named lib at the root of this repository.
0 commit comments