Spoofing MAC address 26:11:35:1D:11:58 (No registered vendor)

You have specified some options that require raw socket access.
These options will not be honored for TCP Connect scan.
# Nmap 7.80 scan initiated Mon Jul 8 07:49:59 2024 as: nmap -sT -v -Pn --spoof-mac
0 -D192.168.1.5,10.5.1.2,172.1.2.4,3.4.2.1 -oN /home/fucker/Desktop/cunt.txt
192.168.140.124/24 192.168.1.5
RTTVAR has grown to over 2.3 seconds, decreasing to 2.0
RTTVAR has grown to over 2.3 seconds, decreasing to 2.0
RTTVAR has grown to over 2.3 seconds, decreasing to 2.0
adjust_timeouts2: packet supposedly had rtt of 9599687 microseconds. Ignoring
time.
adjust_timeouts2: packet supposedly had rtt of 9599687 microseconds. Ignoring
time.
adjust_timeouts2: packet supposedly had rtt of 9479610 microseconds. Ignoring
time.
adjust_timeouts2: packet supposedly had rtt of 9479610 microseconds. Ignoring
time.
RTTVAR has grown to over 2.3 seconds, decreasing to 2.0
RTTVAR has grown to over 2.3 seconds, decreasing to 2.0
RTTVAR has grown to over 2.3 seconds, decreasing to 2.0
RTTVAR has grown to over 2.3 seconds, decreasing to 2.0
RTTVAR has grown to over 2.3 seconds, decreasing to 2.0
RTTVAR has grown to over 2.3 seconds, decreasing to 2.0
RTTVAR has grown to over 2.3 seconds, decreasing to 2.0
RTTVAR has grown to over 2.3 seconds, decreasing to 2.0
RTTVAR has grown to over 2.3 seconds, decreasing to 2.0
RTTVAR has grown to over 2.3 seconds, decreasing to 2.0
RTTVAR has grown to over 2.3 seconds, decreasing to 2.0
RTTVAR has grown to over 2.3 seconds, decreasing to 2.0
RTTVAR has grown to over 2.3 seconds, decreasing to 2.0
RTTVAR has grown to over 2.3 seconds, decreasing to 2.0
RTTVAR has grown to over 2.3 seconds, decreasing to 2.0
RTTVAR has grown to over 2.3 seconds, decreasing to 2.0
RTTVAR has grown to over 2.3 seconds, decreasing to 2.0
adjust_timeouts2: packet supposedly had rtt of 9600947 microseconds. Ignoring
time.
adjust_timeouts2: packet supposedly had rtt of 9600947 microseconds. Ignoring
time.
adjust_timeouts2: packet supposedly had rtt of 9504619 microseconds. Ignoring
time.
adjust_timeouts2: packet supposedly had rtt of 9504619 microseconds. Ignoring
time.
adjust_timeouts2: packet supposedly had rtt of 9375575 microseconds. Ignoring
time.
adjust_timeouts2: packet supposedly had rtt of 9375575 microseconds. Ignoring
time.
RTTVAR has grown to over 2.3 seconds, decreasing to 2.0
RTTVAR has grown to over 2.3 seconds, decreasing to 2.0
RTTVAR has grown to over 2.3 seconds, decreasing to 2.0
RTTVAR has grown to over 2.3 seconds, decreasing to 2.0
RTTVAR has grown to over 2.3 seconds, decreasing to 2.0
RTTVAR has grown to over 2.3 seconds, decreasing to 2.0
adjust_timeouts2: packet supposedly had rtt of 9503213 microseconds. Ignoring
time.
adjust_timeouts2: packet supposedly had rtt of 9503213 microseconds. Ignoring
time.
adjust_timeouts2: packet supposedly had rtt of 9341777 microseconds. Ignoring
time.
adjust_timeouts2: packet supposedly had rtt of 9341777 microseconds. Ignoring
time.
adjust_timeouts2: packet supposedly had rtt of 9214381 microseconds. Ignoring
time.
adjust_timeouts2: packet supposedly had rtt of 9214381 microseconds. Ignoring
time.
Nmap scan report for 192.168.140.0
Host is up (2.5s latency).
All 1000 scanned ports on 192.168.140.0 are filtered

Nmap scan report for 192.168.140.1

Host is up (1.4s latency).
All 1000 scanned ports on 192.168.140.1 are filtered

Nmap scan report for 192.168.140.2

Host is up (3.7s latency).
All 1000 scanned ports on 192.168.140.2 are filtered

Nmap scan report for 192.168.140.3

Host is up (1.1s latency).
All 1000 scanned ports on 192.168.140.3 are filtered

Nmap scan report for 192.168.140.4

Host is up (1.6s latency).
All 1000 scanned ports on 192.168.140.4 are filtered

Nmap scan report for 192.168.140.5

Host is up (0.72s latency).
All 1000 scanned ports on 192.168.140.5 are filtered

Nmap scan report for 192.168.140.6

Host is up (1.1s latency).
All 1000 scanned ports on 192.168.140.6 are filtered

Nmap scan report for 192.168.140.7

Host is up (2.7s latency).
All 1000 scanned ports on 192.168.140.7 are filtered

Nmap scan report for 192.168.140.8

Host is up (2.4s latency).
All 1000 scanned ports on 192.168.140.8 are filtered

Nmap scan report for 192.168.140.9

Host is up (1.4s latency).
All 1000 scanned ports on 192.168.140.9 are filtered

Nmap scan report for 192.168.140.10

Host is up (1.8s latency).
All 1000 scanned ports on 192.168.140.10 are filtered

Nmap scan report for 192.168.140.11

Host is up (2.2s latency).
All 1000 scanned ports on 192.168.140.11 are filtered

Nmap scan report for 192.168.140.12

Host is up (1.4s latency).
All 1000 scanned ports on 192.168.140.12 are filtered

Nmap scan report for 192.168.140.13

Host is up (1.6s latency).
All 1000 scanned ports on 192.168.140.13 are filtered

Nmap scan report for 192.168.140.14

Host is up (1.7s latency).
All 1000 scanned ports on 192.168.140.14 are filtered

Nmap scan report for 192.168.140.15

Host is up (0.97s latency).
All 1000 scanned ports on 192.168.140.15 are filtered

Nmap scan report for 192.168.140.16

Host is up (1.6s latency).
All 1000 scanned ports on 192.168.140.16 are filtered

Nmap scan report for 192.168.140.17

Host is up (1.8s latency).
All 1000 scanned ports on 192.168.140.17 are filtered

Nmap scan report for 192.168.140.18

Host is up (1.3s latency).
All 1000 scanned ports on 192.168.140.18 are filtered

Nmap scan report for 192.168.140.19

Host is up (1.7s latency).
All 1000 scanned ports on 192.168.140.19 are filtered

Nmap scan report for 192.168.140.20

Host is up (1.6s latency).
All 1000 scanned ports on 192.168.140.20 are filtered

Nmap scan report for 192.168.140.21

Host is up (1.9s latency).
All 1000 scanned ports on 192.168.140.21 are filtered

Nmap scan report for 192.168.140.22

Host is up (1.6s latency).
All 1000 scanned ports on 192.168.140.22 are filtered

Nmap scan report for 192.168.140.23

Host is up (1.6s latency).
All 1000 scanned ports on 192.168.140.23 are filtered

Nmap scan report for 192.168.140.24

Host is up (1.6s latency).
All 1000 scanned ports on 192.168.140.24 are filtered

Nmap scan report for 192.168.140.25

Host is up (1.2s latency).
All 1000 scanned ports on 192.168.140.25 are filtered

Nmap scan report for 192.168.140.26

Host is up (2.1s latency).
All 1000 scanned ports on 192.168.140.26 are filtered

Nmap scan report for 192.168.140.27

Host is up (1.7s latency).
All 1000 scanned ports on 192.168.140.27 are filtered
Nmap scan report for 192.168.140.28
Host is up (1.5s latency).
All 1000 scanned ports on 192.168.140.28 are filtered

Nmap scan report for 192.168.140.29

Host is up (2.0s latency).
All 1000 scanned ports on 192.168.140.29 are filtered

Nmap scan report for 192.168.140.30

Host is up (1.8s latency).
All 1000 scanned ports on 192.168.140.30 are filtered

Nmap scan report for 192.168.140.31

Host is up (1.8s latency).
All 1000 scanned ports on 192.168.140.31 are filtered

Nmap scan report for 192.168.140.32

Host is up (1.4s latency).
All 1000 scanned ports on 192.168.140.32 are filtered

Nmap scan report for 192.168.140.33

Host is up (1.8s latency).
All 1000 scanned ports on 192.168.140.33 are filtered

Nmap scan report for 192.168.140.34

Host is up (1.4s latency).
All 1000 scanned ports on 192.168.140.34 are filtered

Nmap scan report for 192.168.140.35

Host is up (1.7s latency).
All 1000 scanned ports on 192.168.140.35 are filtered

Nmap scan report for 192.168.140.36

Host is up (1.3s latency).
All 1000 scanned ports on 192.168.140.36 are filtered

Nmap scan report for 192.168.140.37

Host is up (1.5s latency).
All 1000 scanned ports on 192.168.140.37 are filtered

Nmap scan report for 192.168.140.38

Host is up (1.0s latency).
All 1000 scanned ports on 192.168.140.38 are filtered

Nmap scan report for 192.168.140.39

Host is up (2.3s latency).
All 1000 scanned ports on 192.168.140.39 are filtered

Nmap scan report for 192.168.140.40

Host is up (1.8s latency).
All 1000 scanned ports on 192.168.140.40 are filtered

Nmap scan report for 192.168.140.41

Host is up (3.7s latency).
All 1000 scanned ports on 192.168.140.41 are filtered

Nmap scan report for 192.168.140.42

Host is up (0.84s latency).
All 1000 scanned ports on 192.168.140.42 are filtered
Nmap scan report for 192.168.140.43
Host is up (1.7s latency).
All 1000 scanned ports on 192.168.140.43 are filtered

Nmap scan report for 192.168.140.44

Host is up (1.7s latency).
All 1000 scanned ports on 192.168.140.44 are filtered

Nmap scan report for 192.168.140.45

Host is up (1.2s latency).
All 1000 scanned ports on 192.168.140.45 are filtered

Nmap scan report for 192.168.140.46

Host is up (1.8s latency).
All 1000 scanned ports on 192.168.140.46 are filtered

Nmap scan report for 192.168.140.47

Host is up (2.0s latency).
All 1000 scanned ports on 192.168.140.47 are filtered

Nmap scan report for 192.168.140.48

Host is up (1.7s latency).
All 1000 scanned ports on 192.168.140.48 are filtered

Nmap scan report for 192.168.140.49

Host is up (1.6s latency).
All 1000 scanned ports on 192.168.140.49 are filtered

Nmap scan report for 192.168.140.50

Host is up (2.3s latency).
All 1000 scanned ports on 192.168.140.50 are filtered

Nmap scan report for 192.168.140.51

Host is up (2.5s latency).
All 1000 scanned ports on 192.168.140.51 are filtered

Nmap scan report for 192.168.140.52

Host is up (1.2s latency).
All 1000 scanned ports on 192.168.140.52 are filtered

Nmap scan report for 192.168.140.53

Host is up (1.9s latency).
All 1000 scanned ports on 192.168.140.53 are filtered

Nmap scan report for 192.168.140.54

Host is up (1.6s latency).
All 1000 scanned ports on 192.168.140.54 are filtered

Nmap scan report for 192.168.140.55

Host is up (1.4s latency).
All 1000 scanned ports on 192.168.140.55 are filtered

Nmap scan report for 192.168.140.56

Host is up (1.4s latency).
All 1000 scanned ports on 192.168.140.56 are filtered

Nmap scan report for 192.168.140.57

Host is up (1.7s latency).
All 1000 scanned ports on 192.168.140.57 are filtered

Nmap scan report for 192.168.140.58

Host is up (1.6s latency).
All 1000 scanned ports on 192.168.140.58 are filtered

Nmap scan report for 192.168.140.59

Host is up (1.0s latency).
All 1000 scanned ports on 192.168.140.59 are filtered

Nmap scan report for 192.168.140.60

Host is up (1.7s latency).
All 1000 scanned ports on 192.168.140.60 are filtered

Nmap scan report for 192.168.140.61

Host is up (2.6s latency).
All 1000 scanned ports on 192.168.140.61 are filtered

Nmap scan report for 192.168.140.62

Host is up (2.2s latency).
All 1000 scanned ports on 192.168.140.62 are filtered

Nmap scan report for 192.168.140.63

Host is up (2.3s latency).
All 1000 scanned ports on 192.168.140.63 are filtered

RTTVAR has grown to over 2.3 seconds, decreasing to 2.0

RTTVAR has grown to over 2.3 seconds, decreasing to 2.0
RTTVAR has grown to over 2.3 seconds, decreasing to 2.0
RTTVAR has grown to over 2.3 seconds, decreasing to 2.0
RTTVAR has grown to over 2.3 seconds, decreasing to 2.0
RTTVAR has grown to over 2.3 seconds, decreasing to 2.0
adjust_timeouts2: packet supposedly had rtt of 9214766 microseconds. Ignoring
time.
adjust_timeouts2: packet supposedly had rtt of 9214766 microseconds. Ignoring
time.
adjust_timeouts2: packet supposedly had rtt of 9343285 microseconds. Ignoring
time.
adjust_timeouts2: packet supposedly had rtt of 9343285 microseconds. Ignoring
time.
Increasing send delay for 192.168.140.108 from 0 to 5 due to 67 out of 223 dropped
probes since last increase.
Increasing send delay for 192.168.140.108 from 5 to 10 due to 11 out of 11 dropped
probes since last increase.
Increasing send delay for 192.168.140.108 from 10 to 20 due to 11 out of 11 dropped
probes since last increase.
Increasing send delay for 192.168.140.108 from 20 to 40 due to 11 out of 11 dropped
probes since last increase.
Increasing send delay for 192.168.140.108 from 40 to 80 due to 11 out of 11 dropped
probes since last increase.
Increasing send delay for 192.168.140.108 from 80 to 160 due to 11 out of 11
dropped probes since last increase.
Increasing send delay for 192.168.140.108 from 160 to 320 due to 11 out of 23
dropped probes since last increase.
Increasing send delay for 192.168.140.108 from 320 to 640 due to 11 out of 11
dropped probes since last increase.
Increasing send delay for 192.168.140.108 from 640 to 1000 due to 11 out of 11
dropped probes since last increase.
RTTVAR has grown to over 2.3 seconds, decreasing to 2.0
adjust_timeouts2: packet supposedly had rtt of 9279827 microseconds. Ignoring
time.
adjust_timeouts2: packet supposedly had rtt of 9279827 microseconds. Ignoring
time.
RTTVAR has grown to over 2.3 seconds, decreasing to 2.0
RTTVAR has grown to over 2.3 seconds, decreasing to 2.0
Nmap scan report for 192.168.140.64
Host is up (1.9s latency).
All 1000 scanned ports on 192.168.140.64 are filtered

Nmap scan report for 192.168.140.65

Host is up (2.4s latency).
All 1000 scanned ports on 192.168.140.65 are filtered

Nmap scan report for 192.168.140.66

Host is up (1.6s latency).
All 1000 scanned ports on 192.168.140.66 are filtered

Nmap scan report for 192.168.140.67

Host is up (1.6s latency).
All 1000 scanned ports on 192.168.140.67 are filtered

Nmap scan report for 192.168.140.68

Host is up (1.9s latency).
All 1000 scanned ports on 192.168.140.68 are filtered

Nmap scan report for 192.168.140.69

Host is up (1.5s latency).
All 1000 scanned ports on 192.168.140.69 are filtered

Nmap scan report for 192.168.140.70

Host is up (1.2s latency).
All 1000 scanned ports on 192.168.140.70 are filtered

Nmap scan report for 192.168.140.71

Host is up (1.5s latency).
All 1000 scanned ports on 192.168.140.71 are filtered

Nmap scan report for 192.168.140.72

Host is up (1.5s latency).
All 1000 scanned ports on 192.168.140.72 are filtered

Nmap scan report for 192.168.140.73

Host is up (2.3s latency).
All 1000 scanned ports on 192.168.140.73 are filtered

Nmap scan report for 192.168.140.74

Host is up (1.3s latency).
All 1000 scanned ports on 192.168.140.74 are filtered

Nmap scan report for 192.168.140.75

Host is up (1.6s latency).
All 1000 scanned ports on 192.168.140.75 are filtered

Nmap scan report for 192.168.140.76

Host is up (1.9s latency).
All 1000 scanned ports on 192.168.140.76 are filtered

Nmap scan report for 192.168.140.77

Host is up (1.8s latency).
All 1000 scanned ports on 192.168.140.77 are filtered

Nmap scan report for 192.168.140.78

Host is up (1.0s latency).
All 1000 scanned ports on 192.168.140.78 are filtered

Nmap scan report for 192.168.140.79

Host is up (1.5s latency).
All 1000 scanned ports on 192.168.140.79 are filtered

Nmap scan report for 192.168.140.80

Host is up (1.8s latency).
All 1000 scanned ports on 192.168.140.80 are filtered

Nmap scan report for 192.168.140.81

Host is up (2.1s latency).
All 1000 scanned ports on 192.168.140.81 are filtered

Nmap scan report for 192.168.140.82

Host is up (1.5s latency).
All 1000 scanned ports on 192.168.140.82 are filtered

Nmap scan report for 192.168.140.83

Host is up (1.5s latency).
All 1000 scanned ports on 192.168.140.83 are filtered

Nmap scan report for 192.168.140.84

Host is up (1.1s latency).
All 1000 scanned ports on 192.168.140.84 are filtered

Nmap scan report for 192.168.140.85

Host is up (1.1s latency).
All 1000 scanned ports on 192.168.140.85 are filtered

Nmap scan report for 192.168.140.86

Host is up (1.4s latency).
All 1000 scanned ports on 192.168.140.86 are filtered

Nmap scan report for 192.168.140.87

Host is up (1.9s latency).
All 1000 scanned ports on 192.168.140.87 are filtered

Nmap scan report for 192.168.140.88

Host is up (2.4s latency).
All 1000 scanned ports on 192.168.140.88 are filtered

Nmap scan report for 192.168.140.89

Host is up (2.1s latency).
All 1000 scanned ports on 192.168.140.89 are filtered

Nmap scan report for 192.168.140.90

Host is up (2.2s latency).
All 1000 scanned ports on 192.168.140.90 are filtered

Nmap scan report for 192.168.140.91

Host is up (1.9s latency).
All 1000 scanned ports on 192.168.140.91 are filtered
Nmap scan report for 192.168.140.92
Host is up (1.7s latency).
All 1000 scanned ports on 192.168.140.92 are filtered

Nmap scan report for 192.168.140.93

Host is up (1.3s latency).
All 1000 scanned ports on 192.168.140.93 are filtered

Nmap scan report for 192.168.140.94

Host is up (1.2s latency).
All 1000 scanned ports on 192.168.140.94 are filtered

Nmap scan report for 192.168.140.95

Host is up (1.7s latency).
All 1000 scanned ports on 192.168.140.95 are filtered

Nmap scan report for 192.168.140.96

Host is up (2.3s latency).
All 1000 scanned ports on 192.168.140.96 are filtered

Nmap scan report for 192.168.140.97

Host is up (1.9s latency).
All 1000 scanned ports on 192.168.140.97 are filtered

Nmap scan report for 192.168.140.98

Host is up (1.1s latency).
All 1000 scanned ports on 192.168.140.98 are filtered

Nmap scan report for 192.168.140.99

Host is up (1.5s latency).
All 1000 scanned ports on 192.168.140.99 are filtered

Nmap scan report for 192.168.140.100

Host is up (1.3s latency).
All 1000 scanned ports on 192.168.140.100 are filtered

Nmap scan report for 192.168.140.101

Host is up (2.1s latency).
All 1000 scanned ports on 192.168.140.101 are filtered

Nmap scan report for 192.168.140.102

Host is up (1.7s latency).
All 1000 scanned ports on 192.168.140.102 are filtered

Nmap scan report for 192.168.140.103

Host is up (1.7s latency).
All 1000 scanned ports on 192.168.140.103 are filtered

Nmap scan report for 192.168.140.104

Host is up (2.1s latency).
All 1000 scanned ports on 192.168.140.104 are filtered

Nmap scan report for 192.168.140.105

Host is up (1.7s latency).
All 1000 scanned ports on 192.168.140.105 are filtered

Nmap scan report for 192.168.140.106

Host is up (2.0s latency).
All 1000 scanned ports on 192.168.140.106 are filtered
Nmap scan report for pop-os (192.168.140.107)
Host is up (0.00022s latency).
Not shown: 997 closed ports
PORT STATE SERVICE
3389/tcp open ms-wbt-server
6881/tcp open bittorrent-tracker
32769/tcp open filenet-rpc

Nmap scan report for 192.168.140.108

Host is up (0.082s latency).
All 1000 scanned ports on 192.168.140.108 are filtered (869) or closed (131)

Nmap scan report for 192.168.140.109

Host is up (2.4s latency).
All 1000 scanned ports on 192.168.140.109 are filtered

Nmap scan report for 192.168.140.110

Host is up (2.3s latency).
All 1000 scanned ports on 192.168.140.110 are filtered

Nmap scan report for 192.168.140.111

Host is up (1.9s latency).
All 1000 scanned ports on 192.168.140.111 are filtered

Nmap scan report for 192.168.140.112

Host is up (1.9s latency).
All 1000 scanned ports on 192.168.140.112 are filtered

Nmap scan report for 192.168.140.113

Host is up (3.0s latency).
All 1000 scanned ports on 192.168.140.113 are filtered

Nmap scan report for 192.168.140.114

Host is up (2.8s latency).
All 1000 scanned ports on 192.168.140.114 are filtered

Nmap scan report for 192.168.140.115

Host is up (1.7s latency).
All 1000 scanned ports on 192.168.140.115 are filtered

Nmap scan report for 192.168.140.116

Host is up (1.1s latency).
All 1000 scanned ports on 192.168.140.116 are filtered

Nmap scan report for 192.168.140.117

Host is up (1.9s latency).
All 1000 scanned ports on 192.168.140.117 are filtered

Nmap scan report for 192.168.140.118

Host is up (1.7s latency).
All 1000 scanned ports on 192.168.140.118 are filtered

Nmap scan report for 192.168.140.119

Host is up (1.1s latency).
All 1000 scanned ports on 192.168.140.119 are filtered

Nmap scan report for 192.168.140.120

Host is up (2.0s latency).
All 1000 scanned ports on 192.168.140.120 are filtered

Nmap scan report for 192.168.140.121

Host is up (1.8s latency).
All 1000 scanned ports on 192.168.140.121 are filtered

Nmap scan report for 192.168.140.122

Host is up (1.6s latency).
All 1000 scanned ports on 192.168.140.122 are filtered

Nmap scan report for 192.168.140.123

Host is up (1.6s latency).
All 1000 scanned ports on 192.168.140.123 are filtered

Nmap scan report for _gateway (192.168.140.124)

Host is up (0.0062s latency).
Not shown: 999 closed ports
PORT STATE SERVICE
53/tcp open domain

Nmap scan report for 192.168.140.125

Host is up (2.1s latency).
All 1000 scanned ports on 192.168.140.125 are filtered

Nmap scan report for 192.168.140.126

Host is up (1.7s latency).
All 1000 scanned ports on 192.168.140.126 are filtered

Nmap scan report for 192.168.140.127

Host is up (1.8s latency).
All 1000 scanned ports on 192.168.140.127 are filtered

RTTVAR has grown to over 2.3 seconds, decreasing to 2.0

RTTVAR has grown to over 2.3 seconds, decreasing to 2.0
RTTVAR has grown to over 2.3 seconds, decreasing to 2.0
adjust_timeouts2: packet supposedly had rtt of 9213679 microseconds. Ignoring
time.
adjust_timeouts2: packet supposedly had rtt of 9213679 microseconds. Ignoring
time.
adjust_timeouts2: packet supposedly had rtt of 8192254 microseconds. Ignoring
time.
adjust_timeouts2: packet supposedly had rtt of 8192254 microseconds. Ignoring
time.
RTTVAR has grown to over 2.3 seconds, decreasing to 2.0
RTTVAR has grown to over 2.3 seconds, decreasing to 2.0
RTTVAR has grown to over 2.3 seconds, decreasing to 2.0
RTTVAR has grown to over 2.3 seconds, decreasing to 2.0
adjust_timeouts2: packet supposedly had rtt of 9341812 microseconds. Ignoring
time.
adjust_timeouts2: packet supposedly had rtt of 9341812 microseconds. Ignoring
time.
adjust_timeouts2: packet supposedly had rtt of 9533999 microseconds. Ignoring
time.
adjust_timeouts2: packet supposedly had rtt of 9533999 microseconds. Ignoring
time.
adjust_timeouts2: packet supposedly had rtt of 9663838 microseconds. Ignoring
time.
adjust_timeouts2: packet supposedly had rtt of 9663838 microseconds. Ignoring
time.
RTTVAR has grown to over 2.3 seconds, decreasing to 2.0
adjust_timeouts2: packet supposedly had rtt of 9484387 microseconds. Ignoring
time.
adjust_timeouts2: packet supposedly had rtt of 9484387 microseconds. Ignoring
time.
RTTVAR has grown to over 2.3 seconds, decreasing to 2.0
RTTVAR has grown to over 2.3 seconds, decreasing to 2.0
adjust_timeouts2: packet supposedly had rtt of 9759571 microseconds. Ignoring
time.
adjust_timeouts2: packet supposedly had rtt of 9759571 microseconds. Ignoring
time.
RTTVAR has grown to over 2.3 seconds, decreasing to 2.0
RTTVAR has grown to over 2.3 seconds, decreasing to 2.0
RTTVAR has grown to over 2.3 seconds, decreasing to 2.0
RTTVAR has grown to over 2.3 seconds, decreasing to 2.0
RTTVAR has grown to over 2.3 seconds, decreasing to 2.0
RTTVAR has grown to over 2.3 seconds, decreasing to 2.0
RTTVAR has grown to over 2.3 seconds, decreasing to 2.0
RTTVAR has grown to over 2.3 seconds, decreasing to 2.0
RTTVAR has grown to over 2.3 seconds, decreasing to 2.0
RTTVAR has grown to over 2.3 seconds, decreasing to 2.0
RTTVAR has grown to over 2.3 seconds, decreasing to 2.0
RTTVAR has grown to over 2.3 seconds, decreasing to 2.0
RTTVAR has grown to over 2.3 seconds, decreasing to 2.0
RTTVAR has grown to over 2.3 seconds, decreasing to 2.0
adjust_timeouts2: packet supposedly had rtt of 9727586 microseconds. Ignoring
time.
adjust_timeouts2: packet supposedly had rtt of 9727586 microseconds. Ignoring
time.
adjust_timeouts2: packet supposedly had rtt of 9438868 microseconds. Ignoring
time.
adjust_timeouts2: packet supposedly had rtt of 9438868 microseconds. Ignoring
time.
RTTVAR has grown to over 2.3 seconds, decreasing to 2.0
RTTVAR has grown to over 2.3 seconds, decreasing to 2.0
RTTVAR has grown to over 2.3 seconds, decreasing to 2.0
RTTVAR has grown to over 2.3 seconds, decreasing to 2.0
RTTVAR has grown to over 2.3 seconds, decreasing to 2.0
RTTVAR has grown to over 2.3 seconds, decreasing to 2.0
RTTVAR has grown to over 2.3 seconds, decreasing to 2.0
RTTVAR has grown to over 2.3 seconds, decreasing to 2.0
RTTVAR has grown to over 2.3 seconds, decreasing to 2.0
RTTVAR has grown to over 2.3 seconds, decreasing to 2.0
RTTVAR has grown to over 2.3 seconds, decreasing to 2.0
RTTVAR has grown to over 2.3 seconds, decreasing to 2.0
RTTVAR has grown to over 2.3 seconds, decreasing to 2.0
RTTVAR has grown to over 2.3 seconds, decreasing to 2.0
RTTVAR has grown to over 2.3 seconds, decreasing to 2.0
RTTVAR has grown to over 2.3 seconds, decreasing to 2.0
RTTVAR has grown to over 2.3 seconds, decreasing to 2.0
RTTVAR has grown to over 2.3 seconds, decreasing to 2.0
RTTVAR has grown to over 2.3 seconds, decreasing to 2.0
RTTVAR has grown to over 2.3 seconds, decreasing to 2.0
RTTVAR has grown to over 2.3 seconds, decreasing to 2.0
RTTVAR has grown to over 2.3 seconds, decreasing to 2.0
RTTVAR has grown to over 2.3 seconds, decreasing to 2.0
adjust_timeouts2: packet supposedly had rtt of 9375593 microseconds. Ignoring
time.
adjust_timeouts2: packet supposedly had rtt of 9375593 microseconds. Ignoring
time.
adjust_timeouts2: packet supposedly had rtt of 9247901 microseconds. Ignoring
time.
adjust_timeouts2: packet supposedly had rtt of 9247901 microseconds. Ignoring
time.
RTTVAR has grown to over 2.3 seconds, decreasing to 2.0
RTTVAR has grown to over 2.3 seconds, decreasing to 2.0
RTTVAR has grown to over 2.3 seconds, decreasing to 2.0
RTTVAR has grown to over 2.3 seconds, decreasing to 2.0
RTTVAR has grown to over 2.3 seconds, decreasing to 2.0
RTTVAR has grown to over 2.3 seconds, decreasing to 2.0
RTTVAR has grown to over 2.3 seconds, decreasing to 2.0
Nmap scan report for 192.168.140.128
Host is up (1.7s latency).
All 1000 scanned ports on 192.168.140.128 are filtered

Nmap scan report for 192.168.140.129

Host is up (1.4s latency).
All 1000 scanned ports on 192.168.140.129 are filtered

Nmap scan report for 192.168.140.130

Host is up (1.3s latency).
All 1000 scanned ports on 192.168.140.130 are filtered

Nmap scan report for 192.168.140.131

Host is up (1.7s latency).
All 1000 scanned ports on 192.168.140.131 are filtered

Nmap scan report for 192.168.140.132

Host is up (1.7s latency).
All 1000 scanned ports on 192.168.140.132 are filtered

Nmap scan report for 192.168.140.133

Host is up (1.9s latency).
All 1000 scanned ports on 192.168.140.133 are filtered

Nmap scan report for 192.168.140.134

Host is up (1.6s latency).
All 1000 scanned ports on 192.168.140.134 are filtered

Nmap scan report for 192.168.140.135

Host is up (1.6s latency).
All 1000 scanned ports on 192.168.140.135 are filtered

Nmap scan report for 192.168.140.136

Host is up (2.4s latency).
All 1000 scanned ports on 192.168.140.136 are filtered

Nmap scan report for 192.168.140.137

Host is up (2.9s latency).
All 1000 scanned ports on 192.168.140.137 are filtered

Nmap scan report for 192.168.140.138

Host is up (1.5s latency).
All 1000 scanned ports on 192.168.140.138 are filtered

Nmap scan report for 192.168.140.139

Host is up (2.2s latency).
All 1000 scanned ports on 192.168.140.139 are filtered
Nmap scan report for 192.168.140.140
Host is up (1.7s latency).
All 1000 scanned ports on 192.168.140.140 are filtered

Nmap scan report for 192.168.140.141

Host is up (2.4s latency).
All 1000 scanned ports on 192.168.140.141 are filtered

Nmap scan report for 192.168.140.142

Host is up (0.78s latency).
All 1000 scanned ports on 192.168.140.142 are filtered

Nmap scan report for 192.168.140.143

Host is up (0.54s latency).
All 1000 scanned ports on 192.168.140.143 are filtered

Nmap scan report for 192.168.140.144

Host is up (1.5s latency).
All 1000 scanned ports on 192.168.140.144 are filtered

Nmap scan report for 192.168.140.145

Host is up (1.4s latency).
All 1000 scanned ports on 192.168.140.145 are filtered

Nmap scan report for 192.168.140.146

Host is up (1.2s latency).
All 1000 scanned ports on 192.168.140.146 are filtered

Nmap scan report for 192.168.140.147

Host is up (0.84s latency).
All 1000 scanned ports on 192.168.140.147 are filtered

Nmap scan report for 192.168.140.148

Host is up (2.1s latency).
All 1000 scanned ports on 192.168.140.148 are filtered

Nmap scan report for 192.168.140.149

Host is up (1.8s latency).
All 1000 scanned ports on 192.168.140.149 are filtered

Nmap scan report for 192.168.140.150

Host is up (1.4s latency).
All 1000 scanned ports on 192.168.140.150 are filtered

Nmap scan report for 192.168.140.151

Host is up (2.4s latency).
All 1000 scanned ports on 192.168.140.151 are filtered

Nmap scan report for 192.168.140.152

Host is up (1.3s latency).
All 1000 scanned ports on 192.168.140.152 are filtered

Nmap scan report for 192.168.140.153

Host is up (1.4s latency).
All 1000 scanned ports on 192.168.140.153 are filtered

Nmap scan report for 192.168.140.154

Host is up (1.0s latency).
All 1000 scanned ports on 192.168.140.154 are filtered

Nmap scan report for 192.168.140.155

Host is up (2.1s latency).
All 1000 scanned ports on 192.168.140.155 are filtered

Nmap scan report for 192.168.140.156

Host is up (1.7s latency).
All 1000 scanned ports on 192.168.140.156 are filtered

Nmap scan report for 192.168.140.157

Host is up (1.7s latency).
All 1000 scanned ports on 192.168.140.157 are filtered

Nmap scan report for 192.168.140.158

Host is up (2.3s latency).
All 1000 scanned ports on 192.168.140.158 are filtered

Nmap scan report for 192.168.140.159

Host is up (1.4s latency).
All 1000 scanned ports on 192.168.140.159 are filtered

Nmap scan report for 192.168.140.160

Host is up (1.1s latency).
All 1000 scanned ports on 192.168.140.160 are filtered

Nmap scan report for 192.168.140.161

Host is up (2.3s latency).
All 1000 scanned ports on 192.168.140.161 are filtered

Nmap scan report for 192.168.140.162

Host is up (1.4s latency).
All 1000 scanned ports on 192.168.140.162 are filtered

Nmap scan report for 192.168.140.163

Host is up (2.0s latency).
All 1000 scanned ports on 192.168.140.163 are filtered

Nmap scan report for 192.168.140.164

Host is up (1.4s latency).
All 1000 scanned ports on 192.168.140.164 are filtered

Nmap scan report for 192.168.140.165

Host is up (2.0s latency).
All 1000 scanned ports on 192.168.140.165 are filtered

Nmap scan report for 192.168.140.166

Host is up (1.9s latency).
All 1000 scanned ports on 192.168.140.166 are filtered

Nmap scan report for 192.168.140.167

Host is up (2.1s latency).
All 1000 scanned ports on 192.168.140.167 are filtered

Nmap scan report for 192.168.140.168

Host is up (1.5s latency).
All 1000 scanned ports on 192.168.140.168 are filtered

Nmap scan report for 192.168.140.169

Host is up (1.6s latency).
All 1000 scanned ports on 192.168.140.169 are filtered

Nmap scan report for 192.168.140.170

Host is up (0.66s latency).
All 1000 scanned ports on 192.168.140.170 are filtered

Nmap scan report for 192.168.140.171

Host is up (1.8s latency).
All 1000 scanned ports on 192.168.140.171 are filtered

Nmap scan report for 192.168.140.172

Host is up (1.9s latency).
All 1000 scanned ports on 192.168.140.172 are filtered

Nmap scan report for 192.168.140.173

Host is up (1.7s latency).
All 1000 scanned ports on 192.168.140.173 are filtered

Nmap scan report for 192.168.140.174

Host is up (1.7s latency).
All 1000 scanned ports on 192.168.140.174 are filtered

Nmap scan report for 192.168.140.175

Host is up (1.2s latency).
All 1000 scanned ports on 192.168.140.175 are filtered

Nmap scan report for 192.168.140.176

Host is up (1.3s latency).
All 1000 scanned ports on 192.168.140.176 are filtered

Nmap scan report for 192.168.140.177

Host is up (1.7s latency).
All 1000 scanned ports on 192.168.140.177 are filtered

Nmap scan report for 192.168.140.178

Host is up (2.0s latency).
All 1000 scanned ports on 192.168.140.178 are filtered

Nmap scan report for 192.168.140.179

Host is up (1.9s latency).
All 1000 scanned ports on 192.168.140.179 are filtered

Nmap scan report for 192.168.140.180

Host is up (2.1s latency).
All 1000 scanned ports on 192.168.140.180 are filtered

Nmap scan report for 192.168.140.181

Host is up (1.3s latency).
All 1000 scanned ports on 192.168.140.181 are filtered

Nmap scan report for 192.168.140.182

Host is up (1.9s latency).
All 1000 scanned ports on 192.168.140.182 are filtered

Nmap scan report for 192.168.140.183

Host is up (1.5s latency).
All 1000 scanned ports on 192.168.140.183 are filtered
Nmap scan report for 192.168.140.184
Host is up (1.5s latency).
All 1000 scanned ports on 192.168.140.184 are filtered

Nmap scan report for 192.168.140.185

Host is up (1.9s latency).
All 1000 scanned ports on 192.168.140.185 are filtered

Nmap scan report for 192.168.140.186

Host is up (1.7s latency).
All 1000 scanned ports on 192.168.140.186 are filtered

Nmap scan report for 192.168.140.187

Host is up (1.8s latency).
All 1000 scanned ports on 192.168.140.187 are filtered

Nmap scan report for 192.168.140.188

Host is up (2.0s latency).
All 1000 scanned ports on 192.168.140.188 are filtered

Nmap scan report for 192.168.140.189

Host is up (1.6s latency).
All 1000 scanned ports on 192.168.140.189 are filtered

Nmap scan report for 192.168.140.190

Host is up (1.3s latency).
All 1000 scanned ports on 192.168.140.190 are filtered

Nmap scan report for 192.168.140.191

Host is up (1.4s latency).
All 1000 scanned ports on 192.168.140.191 are filtered

RTTVAR has grown to over 2.3 seconds, decreasing to 2.0

RTTVAR has grown to over 2.3 seconds, decreasing to 2.0
RTTVAR has grown to over 2.3 seconds, decreasing to 2.0
RTTVAR has grown to over 2.3 seconds, decreasing to 2.0
RTTVAR has grown to over 2.3 seconds, decreasing to 2.0
RTTVAR has grown to over 2.3 seconds, decreasing to 2.0
RTTVAR has grown to over 2.3 seconds, decreasing to 2.0
RTTVAR has grown to over 2.3 seconds, decreasing to 2.0
RTTVAR has grown to over 2.3 seconds, decreasing to 2.0
RTTVAR has grown to over 2.3 seconds, decreasing to 2.0
RTTVAR has grown to over 2.3 seconds, decreasing to 2.0
RTTVAR has grown to over 2.3 seconds, decreasing to 2.0
adjust_timeouts2: packet supposedly had rtt of 9278928 microseconds. Ignoring
time.
adjust_timeouts2: packet supposedly had rtt of 9278928 microseconds. Ignoring
time.
RTTVAR has grown to over 2.3 seconds, decreasing to 2.0
adjust_timeouts2: packet supposedly had rtt of 9215408 microseconds. Ignoring
time.
adjust_timeouts2: packet supposedly had rtt of 9215408 microseconds. Ignoring
time.
RTTVAR has grown to over 2.3 seconds, decreasing to 2.0
RTTVAR has grown to over 2.3 seconds, decreasing to 2.0
RTTVAR has grown to over 2.3 seconds, decreasing to 2.0
RTTVAR has grown to over 2.3 seconds, decreasing to 2.0
RTTVAR has grown to over 2.3 seconds, decreasing to 2.0
RTTVAR has grown to over 2.3 seconds, decreasing to 2.0
RTTVAR has grown to over 2.3 seconds, decreasing to 2.0
RTTVAR has grown to over 2.3 seconds, decreasing to 2.0
RTTVAR has grown to over 2.3 seconds, decreasing to 2.0
RTTVAR has grown to over 2.3 seconds, decreasing to 2.0
RTTVAR has grown to over 2.3 seconds, decreasing to 2.0
RTTVAR has grown to over 2.3 seconds, decreasing to 2.0
RTTVAR has grown to over 2.3 seconds, decreasing to 2.0
RTTVAR has grown to over 2.3 seconds, decreasing to 2.0
RTTVAR has grown to over 2.3 seconds, decreasing to 2.0
RTTVAR has grown to over 2.3 seconds, decreasing to 2.0
RTTVAR has grown to over 2.3 seconds, decreasing to 2.0
RTTVAR has grown to over 2.3 seconds, decreasing to 2.0
RTTVAR has grown to over 2.3 seconds, decreasing to 2.0
RTTVAR has grown to over 2.3 seconds, decreasing to 2.0
adjust_timeouts2: packet supposedly had rtt of 9470677 microseconds. Ignoring
time.
adjust_timeouts2: packet supposedly had rtt of 9470677 microseconds. Ignoring
time.
adjust_timeouts2: packet supposedly had rtt of 9247046 microseconds. Ignoring
time.
adjust_timeouts2: packet supposedly had rtt of 9247046 microseconds. Ignoring
time.
RTTVAR has grown to over 2.3 seconds, decreasing to 2.0
RTTVAR has grown to over 2.3 seconds, decreasing to 2.0
RTTVAR has grown to over 2.3 seconds, decreasing to 2.0
RTTVAR has grown to over 2.3 seconds, decreasing to 2.0
RTTVAR has grown to over 2.3 seconds, decreasing to 2.0
RTTVAR has grown to over 2.3 seconds, decreasing to 2.0
RTTVAR has grown to over 2.3 seconds, decreasing to 2.0
adjust_timeouts2: packet supposedly had rtt of 9247806 microseconds. Ignoring
time.
adjust_timeouts2: packet supposedly had rtt of 9247806 microseconds. Ignoring
time.
RTTVAR has grown to over 2.3 seconds, decreasing to 2.0
RTTVAR has grown to over 2.3 seconds, decreasing to 2.0
RTTVAR has grown to over 2.3 seconds, decreasing to 2.0
RTTVAR has grown to over 2.3 seconds, decreasing to 2.0
RTTVAR has grown to over 2.3 seconds, decreasing to 2.0
RTTVAR has grown to over 2.3 seconds, decreasing to 2.0
Nmap scan report for 192.168.140.192
Host is up (1.5s latency).
All 1000 scanned ports on 192.168.140.192 are filtered

Nmap scan report for 192.168.140.193

Host is up (1.2s latency).
All 1000 scanned ports on 192.168.140.193 are filtered

Nmap scan report for 192.168.140.194

Host is up (0.67s latency).
All 1000 scanned ports on 192.168.140.194 are filtered

Nmap scan report for 192.168.140.195

Host is up (1.5s latency).
All 1000 scanned ports on 192.168.140.195 are filtered

Nmap scan report for 192.168.140.196

Host is up (1.8s latency).
All 1000 scanned ports on 192.168.140.196 are filtered
Nmap scan report for 192.168.140.197
Host is up (1.6s latency).
All 1000 scanned ports on 192.168.140.197 are filtered

Nmap scan report for 192.168.140.198

Host is up (1.9s latency).
All 1000 scanned ports on 192.168.140.198 are filtered

Nmap scan report for 192.168.140.199

Host is up (2.1s latency).
All 1000 scanned ports on 192.168.140.199 are filtered

Nmap scan report for 192.168.140.200

Host is up (2.2s latency).
All 1000 scanned ports on 192.168.140.200 are filtered

Nmap scan report for 192.168.140.201

Host is up (1.2s latency).
All 1000 scanned ports on 192.168.140.201 are filtered

Nmap scan report for 192.168.140.202

Host is up (1.1s latency).
All 1000 scanned ports on 192.168.140.202 are filtered

Nmap scan report for 192.168.140.203

Host is up (1.4s latency).
All 1000 scanned ports on 192.168.140.203 are filtered

Nmap scan report for 192.168.140.204

Host is up (0.90s latency).
All 1000 scanned ports on 192.168.140.204 are filtered

Nmap scan report for 192.168.140.205

Host is up (2.6s latency).
All 1000 scanned ports on 192.168.140.205 are filtered

Nmap scan report for 192.168.140.206

Host is up (1.9s latency).
All 1000 scanned ports on 192.168.140.206 are filtered

Nmap scan report for 192.168.140.207

Host is up (1.3s latency).
All 1000 scanned ports on 192.168.140.207 are filtered

Nmap scan report for 192.168.140.208

Host is up (1.9s latency).
All 1000 scanned ports on 192.168.140.208 are filtered

Nmap scan report for 192.168.140.209

Host is up (2.3s latency).
All 1000 scanned ports on 192.168.140.209 are filtered

Nmap scan report for 192.168.140.210

Host is up (1.3s latency).
All 1000 scanned ports on 192.168.140.210 are filtered

Nmap scan report for 192.168.140.211

Host is up (2.2s latency).
All 1000 scanned ports on 192.168.140.211 are filtered
Nmap scan report for 192.168.140.212
Host is up (1.6s latency).
All 1000 scanned ports on 192.168.140.212 are filtered

Nmap scan report for 192.168.140.213

Host is up (2.2s latency).
All 1000 scanned ports on 192.168.140.213 are filtered

Nmap scan report for 192.168.140.214

Host is up (1.3s latency).
All 1000 scanned ports on 192.168.140.214 are filtered

Nmap scan report for 192.168.140.215

Host is up (1.5s latency).
All 1000 scanned ports on 192.168.140.215 are filtered

Nmap scan report for 192.168.140.216

Host is up (1.4s latency).
All 1000 scanned ports on 192.168.140.216 are filtered

Nmap scan report for 192.168.140.217

Host is up (1.2s latency).
All 1000 scanned ports on 192.168.140.217 are filtered

Nmap scan report for 192.168.140.218

Host is up (1.7s latency).
All 1000 scanned ports on 192.168.140.218 are filtered

Nmap scan report for 192.168.140.219

Host is up (1.8s latency).
All 1000 scanned ports on 192.168.140.219 are filtered

Nmap scan report for 192.168.140.220

Host is up (0.90s latency).
All 1000 scanned ports on 192.168.140.220 are filtered

Nmap scan report for 192.168.140.221

Host is up (1.4s latency).
All 1000 scanned ports on 192.168.140.221 are filtered

Nmap scan report for 192.168.140.222

Host is up (1.9s latency).
All 1000 scanned ports on 192.168.140.222 are filtered

Nmap scan report for 192.168.140.223

Host is up (1.8s latency).
All 1000 scanned ports on 192.168.140.223 are filtered

Nmap scan report for 192.168.140.224

Host is up (1.5s latency).
All 1000 scanned ports on 192.168.140.224 are filtered

Nmap scan report for 192.168.140.225

Host is up (2.1s latency).
All 1000 scanned ports on 192.168.140.225 are filtered

Nmap scan report for 192.168.140.226

Host is up (0.88s latency).
All 1000 scanned ports on 192.168.140.226 are filtered

Nmap scan report for 192.168.140.227

Host is up (3.6s latency).
All 1000 scanned ports on 192.168.140.227 are filtered

Nmap scan report for 192.168.140.228

Host is up (1.8s latency).
All 1000 scanned ports on 192.168.140.228 are filtered

Nmap scan report for 192.168.140.229

Host is up (0.69s latency).
All 1000 scanned ports on 192.168.140.229 are filtered

Nmap scan report for 192.168.140.230

Host is up (1.8s latency).
All 1000 scanned ports on 192.168.140.230 are filtered

Nmap scan report for 192.168.140.231

Host is up (0.62s latency).
All 1000 scanned ports on 192.168.140.231 are filtered

Nmap scan report for 192.168.140.232

Host is up (2.9s latency).
All 1000 scanned ports on 192.168.140.232 are filtered

Nmap scan report for 192.168.140.233

Host is up (2.1s latency).
All 1000 scanned ports on 192.168.140.233 are filtered

Nmap scan report for 192.168.140.234

Host is up (0.86s latency).
All 1000 scanned ports on 192.168.140.234 are filtered

Nmap scan report for 192.168.140.235

Host is up (2.2s latency).
All 1000 scanned ports on 192.168.140.235 are filtered

Nmap scan report for 192.168.140.236

Host is up (0.73s latency).
All 1000 scanned ports on 192.168.140.236 are filtered

Nmap scan report for 192.168.140.237

Host is up (0.54s latency).
All 1000 scanned ports on 192.168.140.237 are filtered

Nmap scan report for 192.168.140.238

Host is up (1.4s latency).
All 1000 scanned ports on 192.168.140.238 are filtered

Nmap scan report for 192.168.140.239

Host is up (2.4s latency).
All 1000 scanned ports on 192.168.140.239 are filtered

Nmap scan report for 192.168.140.240

Host is up (1.2s latency).
All 1000 scanned ports on 192.168.140.240 are filtered

Nmap scan report for 192.168.140.241

Host is up (0.96s latency).
All 1000 scanned ports on 192.168.140.241 are filtered

Nmap scan report for 192.168.140.242

Host is up (2.2s latency).
All 1000 scanned ports on 192.168.140.242 are filtered

Nmap scan report for 192.168.140.243

Host is up (1.2s latency).
All 1000 scanned ports on 192.168.140.243 are filtered

Nmap scan report for 192.168.140.244

Host is up (2.0s latency).
All 1000 scanned ports on 192.168.140.244 are filtered

Nmap scan report for 192.168.140.245

Host is up (2.0s latency).
All 1000 scanned ports on 192.168.140.245 are filtered

Nmap scan report for 192.168.140.246

Host is up (2.1s latency).
All 1000 scanned ports on 192.168.140.246 are filtered

Nmap scan report for 192.168.140.247

Host is up (0.73s latency).
All 1000 scanned ports on 192.168.140.247 are filtered

Nmap scan report for 192.168.140.248

Host is up (2.6s latency).
All 1000 scanned ports on 192.168.140.248 are filtered

Nmap scan report for 192.168.140.249

Host is up (1.8s latency).
All 1000 scanned ports on 192.168.140.249 are filtered

Nmap scan report for 192.168.140.250

Host is up (1.4s latency).
All 1000 scanned ports on 192.168.140.250 are filtered

Nmap scan report for 192.168.140.251

Host is up (1.9s latency).
All 1000 scanned ports on 192.168.140.251 are filtered

Nmap scan report for 192.168.140.252

Host is up (1.5s latency).
All 1000 scanned ports on 192.168.140.252 are filtered

Nmap scan report for 192.168.140.253

Host is up (1.3s latency).
All 1000 scanned ports on 192.168.140.253 are filtered

Nmap scan report for 192.168.140.254

Host is up (2.0s latency).
All 1000 scanned ports on 192.168.140.254 are filtered

Nmap scan report for 192.168.140.255

Host is up (0.000018s latency).
All 1000 scanned ports on 192.168.140.255 are filtered
Nmap scan report for 192.168.1.5
Host is up (0.15s latency).
All 1000 scanned ports on 192.168.1.5 are filtered

Read data files from: /usr/bin/../share/nmap

# Nmap done at Mon Jul 8 11:29:00 2024 -- 257 IP addresses (257 hosts up) scanned
in 13140.42 seconds