ThingzDefense/IoT-Flock

Traffic is not being generated

Opened this issue · 2 comments

Hello,

I wanted to try out this tool to generate sample traffic and see how it does but I am unable to do so, I am using a VM that was provided in one of the earlier issues with IoTFlock precompiled. After generating use case and running it with sudo ./IoTFlock-Console usecases/test2.xml I am getting what looks like normal output:

QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
-----Device Details----
	 "Device_Name" : "a1"
	 "Protocol" : "MQTT"
	 "IP_Address" : "192.168.135.1"
	 "Num_Of_Devices" : "1"
	 "Is_AttackingEntity" : "0"
	 "Attack_Type" : ""
	 "Source_IP" : ""
	 "Target_IP" : ""
	 "Target_Port" : "873893328"
	 "Messages_Per_Sec" : "32765"
	 "Message" : ""
	 "MQTT" : "MQTT"
	 "Brooker_IP" : "https://test.mosquitto.org/"
	 "Is_Authentication_Require" : "0"
	 "User_Name" : ""
	 "Password" : ""
	 "Port" : "1883"
	 "Publish_Detail" : "Publish_Detail"
	 "Topic" : "CO-GAS"
	 "QoS" : "0"
	 "Time_Profile_Type" : "Periodic"
	 "Time_Profile_Interval" : "1"
	 "Time_Profile_RandomFrom" : "0"
	 "Time_Profile_RandomTo" : "0"
	 "Data_Profile_IsStartText" : "0"
	 "Data_Profile_StartText" : ""
	 "Data_Profile_IsRandom" : "1"
	 "Data_Profile_RandomFrom" : "0"
	 "Data_Profile_RandomTo" : "450"
	 "Data_Profile_IsEndText" : "0"
	 "Data_Profile_EndText" : ""
-----Device Details----
	 "Device_Name" : "a1"
	 "Protocol" : "MQTT"
	 "IP_Address" : "192.168.135.2"
	 "Num_Of_Devices" : "1"
	 "Is_AttackingEntity" : "0"
	 "Attack_Type" : ""
	 "Source_IP" : ""
	 "Target_IP" : ""
	 "Target_Port" : "873893328"
	 "Messages_Per_Sec" : "32765"
	 "Message" : ""
	 "MQTT" : "MQTT"
	 "Brooker_IP" : "https://test.mosquitto.org/"
	 "Is_Authentication_Require" : "0"
	 "User_Name" : ""
	 "Password" : ""
	 "Port" : "1883"
	 "Publish_Detail" : "Publish_Detail"
	 "Topic" : "CO-GAS"
	 "QoS" : "0"
	 "Time_Profile_Type" : "Periodic"
	 "Time_Profile_Interval" : "1"
	 "Time_Profile_RandomFrom" : "0"
	 "Time_Profile_RandomTo" : "0"
	 "Data_Profile_IsStartText" : "0"
	 "Data_Profile_StartText" : ""
	 "Data_Profile_IsRandom" : "1"
	 "Data_Profile_RandomFrom" : "0"
	 "Data_Profile_RandomTo" : "450"
	 "Data_Profile_IsEndText" : "0"
	 "Data_Profile_EndText" : ""
-----Device Details----
	 "Device_Name" : "attacker"
	 "Protocol" : "MQTT"
	 "IP_Address" : "192.168.135.3"
	 "Num_Of_Devices" : "1"
	 "Is_AttackingEntity" : "0"
	 "Attack_Type" : ""
	 "Source_IP" : ""
	 "Target_IP" : ""
	 "Target_Port" : "873893328"
	 "Messages_Per_Sec" : "32765"
	 "Message" : ""
	 "MQTT" : "MQTT"
	 "Brooker_IP" : "https://test.mosquitto.org/"
	 "Is_Authentication_Require" : "1"
	 "User_Name" : "rw"
	 "Password" : "readwrite"
	 "Port" : "1883"
shostname "192.168.135.1" 

hostname "https://test.mosquitto.org/" 

port 1883 

isAuthenticationRequire false 

username "" 

password "" 

1
shostname "192.168.135.2" 

hostname "https://test.mosquitto.org/" 

port 1883 

isAuthenticationRequire false 

username "" 

password "" 

1
shostname "192.168.135.3" 

hostname "https://test.mosquitto.org/" 

port 1883 

isAuthenticationRequire true 

username "rw" 

password "readwrite" 

1

but no traffic is generated - there are no packets visible in wireshark in any interface and I cannot find any files that the traffic is being saved to.

This is the output of ipconfig in VM:

ens33: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.135.128  netmask 255.255.255.0  broadcast 192.168.135.255
        inet6 fe80::3015:fbaf:3b0c:8d02  prefixlen 64  scopeid 0x20<link>
        ether 00:0c:29:61:36:44  txqueuelen 1000  (Ethernet)
        RX packets 9266  bytes 11622660 (11.6 MB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 4114  bytes 359741 (359.7 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

ens33:0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.135.1  netmask 255.255.255.0  broadcast 192.168.135.255
        ether 00:0c:29:61:36:44  txqueuelen 1000  (Ethernet)

ens33:1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.135.2  netmask 255.255.255.0  broadcast 192.168.135.255
        ether 00:0c:29:61:36:44  txqueuelen 1000  (Ethernet)

ens33:2: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.135.3  netmask 255.255.255.0  broadcast 192.168.135.255
        ether 00:0c:29:61:36:44  txqueuelen 1000  (Ethernet)

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 5969  bytes 566659 (566.6 KB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 5969  bytes 566659 (566.6 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

Thanks for any help or tips on how to properly use this software or fix this issue.

I am facing the same issue. Were you able to resolve it @aszalowski ?

Hey. If anyone is interested, the traffic IS in fact being generated but, I wasn't able to capture it from any interface on wireshark. So I tried putting the broker as the same ip address as my VM and when i checked the lo interface on wireshark i found the MQTT traffic. So maybe it's just a case of wireshark not being able to capture traffic from the virtual interface.