A Blockchain-based Decentralized SDN Control Plane to Mitigate Single-Point-of-Failure DDoS Attacks in Vehicular Networks
Budget: ₹1,500 – ₹12,500 INR
I’m putting together a lightweight, consortium-based blockchain layer to decentralize the control plane of a software-defined vehicular ad-hoc network (VANET) for ddos attack. The architecture must place enhanced security front and center—specifically, it has to guarantee data integrity, robust authentication and strong privacy protection for every message that moves between vehicles, roadside units and cloud edges.
Because we are working with a consortium blockchain, I expect permissioned membership management, rapid consensus and low latency that fits the tight timing windows of vehicular communication. Open public chains are off the table; the solution has to remain controllable by a defined set of stakeholders such as OEMs, infrastructure operators and municipalities.
Here is what I need from you:
• A complete architectural blueprint that shows how the decentralized SDN controller clusters, the consortium chain, and the VANET data plane interact.
• A protocol flow detailing how integrity, authentication and privacy are enforced end-to-end.
• Performance and security analysis—simulated or analytically reasoned—to demonstrate that the design stays lightweight enough for on-board units while still scaling city-wide.
Divide the City: Split your map (e.g., a 5km x 5km area) into 4 zones. Each zone gets its own "Local Boss" (SDN Controller).
The "Handshake": When a car enters Zone A, the Zone A controller creates a small "Digital ID" for it.
The "Shared Diary" (Blockchain): The ID is written onto a blockchain. Now, Zone B, C, and D can see that this car is "Friendly."
The Attack: A "Bad Car" starts flooding Zone A with 10,000 requests per second (DDoS).
The Block & Sync: Zone A identifies the bully, writes "BAD ID" in the shared diary, and tells the other zones. Even if Zone A crashes, the "Bad Car" is already blocked from entering Zone B.
2. How to Implement It (Simple Steps)
You don't need to build a real city. You will use three software "Lego blocks" on your laptop:
Step A: Create the "World" (SUMO + Mininet-WiFi)
What to do: Open SUMO and draw a simple grid of roads.
The Action: Use Mininet-WiFi to place "Roadside Units" (like WiFi towers) along those roads.
Simple Words: This is your virtual playground where digital cars drive around.
Step B: Set up the "Local Bosses" (ONOS Controllers)
What to do: Run 3 or 4 instances of an SDN controller called ONOS.
The Action: Assign each controller to a specific group of Roadside Units.
Simple Words: You are giving each neighborhood its own brain instead of one brain for the whole city.
Step C: The "Shared Diary" (Lightweight Blockchain)
What to do: Use a simple Python-based blockchain (search for "Simple Python Blockchain" on GitHub).
The Action: Write a script where, every time an ONOS controller blocks an IP address, it sends that IP to the Python blockchain.
Simple Words: This ensures all controllers are reading from the same "Blacklist."
Step D: The "DDoS" Test
What to do: Use a tool like Scapy or Low Orbit Ion Cannon (LOIC) script in your simulation.
The Action: Target one controller and watch it struggle.
The Result: Show that the other controllers are still working perfectly and that the "Bad Car" is blocked everywhere else.
Because we are working with a consortium blockchain, I expect permissioned membership management, rapid consensus and low latency that fits the tight timing windows of vehicular communication. Open public chains are off the table; the solution has to remain controllable by a defined set of stakeholders such as OEMs, infrastructure operators and municipalities.
Here is what I need from you:
• A complete architectural blueprint that shows how the decentralized SDN controller clusters, the consortium chain, and the VANET data plane interact.
• A protocol flow detailing how integrity, authentication and privacy are enforced end-to-end.
• Performance and security analysis—simulated or analytically reasoned—to demonstrate that the design stays lightweight enough for on-board units while still scaling city-wide.
Divide the City: Split your map (e.g., a 5km x 5km area) into 4 zones. Each zone gets its own "Local Boss" (SDN Controller).
The "Handshake": When a car enters Zone A, the Zone A controller creates a small "Digital ID" for it.
The "Shared Diary" (Blockchain): The ID is written onto a blockchain. Now, Zone B, C, and D can see that this car is "Friendly."
The Attack: A "Bad Car" starts flooding Zone A with 10,000 requests per second (DDoS).
The Block & Sync: Zone A identifies the bully, writes "BAD ID" in the shared diary, and tells the other zones. Even if Zone A crashes, the "Bad Car" is already blocked from entering Zone B.
2. How to Implement It (Simple Steps)
You don't need to build a real city. You will use three software "Lego blocks" on your laptop:
Step A: Create the "World" (SUMO + Mininet-WiFi)
What to do: Open SUMO and draw a simple grid of roads.
The Action: Use Mininet-WiFi to place "Roadside Units" (like WiFi towers) along those roads.
Simple Words: This is your virtual playground where digital cars drive around.
Step B: Set up the "Local Bosses" (ONOS Controllers)
What to do: Run 3 or 4 instances of an SDN controller called ONOS.
The Action: Assign each controller to a specific group of Roadside Units.
Simple Words: You are giving each neighborhood its own brain instead of one brain for the whole city.
Step C: The "Shared Diary" (Lightweight Blockchain)
What to do: Use a simple Python-based blockchain (search for "Simple Python Blockchain" on GitHub).
The Action: Write a script where, every time an ONOS controller blocks an IP address, it sends that IP to the Python blockchain.
Simple Words: This ensures all controllers are reading from the same "Blacklist."
Step D: The "DDoS" Test
What to do: Use a tool like Scapy or Low Orbit Ion Cannon (LOIC) script in your simulation.
The Action: Target one controller and watch it struggle.
The Result: Show that the other controllers are still working perfectly and that the "Bad Car" is blocked everywhere else.