Dnipro WiFi & ATC Logs Collection | 300+ Entries | 1.7TB 7z Archive
by FreedomSecurity1337 - Wednesday August 13, 2025 at 01:58 PM
#1
[Image: 631314619_xwabot.jpg]


Selling  dataset containing detailed network logs collected from Dnipro public WiFi, staff WiFi, and Air Traffic Control (ATC) systems. The dataset includes over 300 individual log entries spanning DHCP assignments, WiFi connection events, DNS query records, network traffic summaries, packet sniffing samples, and comprehensive ATC communications.

Sample :
[07:30:00] DHCP_REQUEST MAC=6C:5A:B5:4F:1D:9E REQ_IP=192.168.1.101 LEASE=24h [07:30:02] DHCP_ACK MAC=6C:5A:B5:4F:1D:9E ASSIGN_IP=192.168.1.101 [07:30:02-09:15:34] WiFiConn MAC=6C:5A:B5:4F:1D:9E IP=192.168.1.101 SSID=DniproPublicWiFi STATUS=Connected DUR=105min UP=123.4MB DOWN=321.6MB SIG=-58dBm ROAM=2 AUTHFAIL=0 Notes=Stable [07:45:00] ATC_LOGIN ID=Dnipro_ATC001 CALLSIGN=KIEV_CONTROL STATUS=Online [07:46:10] ATC_RADAR TRACK=Flight-UA345 ALT=12000ft SPD=450km/h POS=48.45N,35.05E HEADING=270 [07:50:23] ATC_COMM CALLSIGN=Flight-UA345 MSG="Request descent to 9000ft" RESPONSE="Cleared to 9000ft" [08:00:00] ATC_RADAR TRACK=Flight-AZ987 ALT=15000ft SPD=480km/h POS=48.50N,35.00E HEADING=180 [08:05:44] ATC_COMM CALLSIGN=Flight-AZ987 MSG="Confirm holding pattern over Dnipro" RESPONSE="Holding pattern confirmed" [08:15:30] ATC_ALERT ALERT=Traffic conflict between Flight-UA345 & Flight-AZ987 at 9000ft, instruct immediate climb [08:17:05] ATC_COMM CALLSIGN=Flight-UA345 MSG="Climbing to 11000ft" RESPONSE="Climb approved" [08:30:00] ATC_RADAR TRACK=Flight-BA123 ALT=13000ft SPD=470km/h POS=48.60N,34.90E HEADING=90 [09:00:00] ATC_LOGIN ID=Dnipro_ATC002 CALLSIGN=KIEV_TOWER STATUS=Online [09:00:15] DNS_QUERY IP=192.168.1.101 DOMAIN=google.com RESOLVED=142.250.190.14 [09:00:16] DNS_QUERY IP=192.168.1.101 DOMAIN=cloudflare.com RESOLVED=104.16.132.229 [09:05:12] ATC_COMM CALLSIGN=Flight-BA123 MSG="Ready for landing runway 27" RESPONSE="Cleared to land runway 27" [09:06:12] Packet Src=192.168.0.102 Dst=8.8.8.8 Proto=UDP53 Len=60B [09:07:01] Packet Src=10.0.0.5 Dst=192.168.0.1 Proto=TCP80 Len=700B [09:10:45] ATC_RADAR TRACK=Flight-UA345 ALT=11000ft SPD=460km/h POS=48.48N,35.03E HEADING=280 [09:15:00] DHCP_RELEASE MAC=6C:5A:B5:4F:1D:9E IP=192.168.1.101 [09:17:10] DHCP_REQUEST MAC=6C:5A:B5:4F:1D:9E REQ_IP=192.168.1.101 [09:17:12] DHCP_ACK MAC=6C:5A:B5:4F:1D:9E ASSIGN_IP=192.168.1.101 [09:17:10-09:18:00] WiFiConn MAC=6C:5A:B5:4F:1D:9E IP=192.168.1.101 SSID=DniproPublicWiFi STATUS=Disconnected DUR=0.8min UP=0.5MB DOWN=1.2MB SIG=-65dBm ROAM=0 AUTHFAIL=1 Notes=Auth fail retry [09:20:00] ATC_ALERT ALERT=Emergency declared by Flight-AZ987, priority landing granted [09:20:45-10:00:00] WiFiConn MAC=2D:9E:F4:56:3B:88 IP=192.168.0.102 SSID=DniproStaffNet STATUS=Connected DUR=39.25min UP=900MB DOWN=1100MB SIG=-42dBm ROAM=5 AUTHFAIL=0 Notes=Stable high throughput [09:22:10] ATC_COMM CALLSIGN=Flight-AZ987 MSG="Diverting to alternate airport" RESPONSE="Acknowledged, proceed to alternate" [09:30:00] ATC_RADAR TRACK=Flight-UA345 ALT=10000ft SPD=450km/h POS=48.47N,35.01E HEADING=300 [10:01:00-10:15:30] WiFiConn MAC=7F:BC:33:AA:45:DE IP=10.0.0.5 SSID=DniproPublicWiFi STATUS=Connected DUR=14.5min UP=60MB DOWN=80MB SIG=-70dBm ROAM=1 AUTHFAIL=0 Notes=One roam stable [10:10:00] ATC_LOGIN ID=Dnipro_ATC003 CALLSIGN=KIEV_GROUND STATUS=Online [10:16:00] WiFiConn MAC=98:FD:23:88:4A:EF IP=10.0.0.5 SSID=DniproPublicWiFi STATUS=Disconnected AUTHFAIL=3 Notes=Repeated auth fails kicked [10:15:45] ATC_COMM CALLSIGN=Flight-UA345 MSG="Taxi to gate 12" RESPONSE="Taxi approved gate 12" [10:20:00] ATC_LOGOUT ID=Dnipro_ATC002 CALLSIGN=KIEV_TOWER STATUS=Offline [10:32:15-11:00:00] WiFiConn MAC=14:7B:E2:55:7C:2D IP=10.0.0.8 SSID=DniproPublicWiFi STATUS=Connected DUR=27.75min UP=100MB DOWN=150MB SIG=-65dBm ROAM=3 AUTHFAIL=0 Notes=Roam x3 good signal [11:02:00-11:10:00] WiFiConn MAC=6C:5A:B5:4F:1D:9E IP=192.168.1.101 SSID=DniproPublicWiFi STATUS=Connected DUR=8min UP=10MB DOWN=25MB SIG=-60dBm ROAM=0 AUTHFAIL=0 Notes=Short reconnect [11:15:10-11:45:00] WiFiConn MAC=A2:3B:8C:F1:2E:33 IP=192.168.0.102 SSID=DniproStaffNet STATUS=Connected DUR=29.83min UP=350MB DOWN=420MB SIG=-43dBm ROAM=0 AUTHFAIL=0 Notes=Stable no roam [11:50:00-12:00:00] WiFiConn MAC=7F:BC:33:AA:45:DE IP=10.0.0.5 SSID=DniproPublicWiFi STATUS=Disconnected AUTHFAIL=1 Notes=Auth fail retrying [10:45:00] ATC_LOGOUT ID=Dnipro_ATC003 CALLSIGN=KIEV_GROUND STATUS=Offline [10:00:00] ATC_LOGOUT ID=Dnipro_ATC001 CALLSIGN=KIEV_CONTROL STATUS=Offline --- NETWORK TRAFFIC --- IP=192.168.1.101 TCP443=2GB UDP53=100MB TCP5222=500MB TCP80=250MB IP=192.168.0.102 TCP443=1.5GB UDP53=50MB TCP22=300MB TCP25=20MB IP=10.0.0.5 TCP80=500MB UDP67=15MB TCP53=40MB IP=10.0.0.8 TCP443=800MB UDP53=60MB --- PACKET SNIFFING SAMPLE --- 09:05:30 Src=192.168.1.101 Dst=142.250.190.14 Proto=TCP443 Len=1500B 09:05:31 Src=192.168.1.101 Dst=104.16.132.229 Proto=TCP443 Len=1300B 09:06:12 Src=192.168.0.102 Dst=8.8.8.8 Proto=UDP53 Len=60B 09:07:01 Src=10.0.0.5 Dst=192.168.0.1 Proto=TCP80 Len=700B

This dataset is perfect for security researchers, pentesters, network analysts, and aviation communication enthusiasts who require realistic, large-scale log data for testing, simulation, or educational purposes.

Dataset Overview:

DHCP Logs: Complete MAC address to IP mappings with lease times and releases

WiFi Connections: Connection and disconnection records, signal strength, data usage (upload/download), roaming counts, and authentication failures

DNS Queries: Domain resolution logs with resolved IP addresses

Network Traffic: Traffic volume by protocol and port for each IP address

Packet Sniffing Samples: Timestamped captures of network packets including source/destination, protocol, and packet size

ATC Logs: Flight tracking data, controller communications, alerts, and login/logout events

Technical Details:

Entries: 300+ combined logs

Format: Raw log files, grouped by category

Compression: 7z archive with maximum compression

Total Size: Approximately 1.7 Terabytes

Price $750 BTC/XRP only
dm me for more ingfo
Reply
#2
thanks
Ban reason: leeching (Permanent)
Reply
#3
thanks
Reply
#4
thanks
Reply
#5
thanks
Ban reason: leeching (Permanent)
Reply
#6
thanks
Reply


Forum Jump:


 Users browsing this thread: 1 Guest(s)