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

feature_extraction #5

Open
Azizkac opened this issue Mar 17, 2024 · 2 comments
Open

feature_extraction #5

Azizkac opened this issue Mar 17, 2024 · 2 comments

Comments

@Azizkac
Copy link

Azizkac commented Mar 17, 2024

hello ,
I have set up an IoT network consisting of three low-energy devices that support IPv6 and IEEE 802.15.4 MAC addresses. Upon inspecting your PCAP files, it appears that you are using only IPv4 devices. I noticed that when I included my MAC address (example: '01:12:74:01:00:01:01:01':'lab1') in the MAC list and executed the code, it appeared to be malfunctioning.

Could you please clarify whether your approach is based solely on IPv4 devices or if the code supports IPv6 devices that work with all low-energy protocols?

@kahramankostas
Copy link
Owner

Hello, and thank you for reaching out with your question.

IoTDevID was initially developed and thoroughly tested using IPv4 datasets. Although the Aalto dataset includes non-IP devices operating on low-energy protocols, it's important to note that these devices were encapsulated under IPv4 during our testing and analysis. As a result, the features utilized by IoTDevID are primarily based on IPv4.

However, I understand your concern regarding IPv6 compatibility. While our current implementation focuses on IPv4, transitioning IoTDevID to support IPv6 devices is feasible. You can achieve this by adjusting the IP properties accordingly. Upon making such modifications, I anticipate that the feature extraction process should function properly with IPv6 devices.

If you encounter any difficulties or need assistance with this transition, please feel free to share a sample file via email along with specific details regarding the observed malfunction. I'll gladly assist you in developing a solution tailored to your requirements.

Thank you for your understanding and patience as we work towards enhancing the versatility of IoTDevID to accommodate a broader range of network configurations.

@Azizkac
Copy link
Author

Azizkac commented Mar 18, 2024

hello, and thank you too .
i'am now working on these and when i will do these transitioning and i will share with you the code .

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

2 participants