How sanishpoudel/sdn-gns3-ryu-implementation works
This repository contains two small Ryu controller apps for an OpenFlow 1.3 testbed. A user launches an app through Ryu; switch connection events trigger either ICMP-drop/normal-forwarding rules or a flow-table reset, which the app sends to the switch. The README also documents the GNS3/OVS ring, management connectivity, and STP loop prevention. The app behavior is visible in the sampled source; topology and STP relationships are based on README documentation.
Main entry points: drop.py Ping blocker · clear.py Flow reset
Components 9
Controller apps
- Ryu runtime
- Ping blocker
drop.py - Flow reset
clear.py
Switch fabric
- OVS switches
- Switch flow tables
Lab topology
- GNS3 network
- STP loop prevention
- Virtual PCs
Other components
- Operator
Connections 12
- Operator → Ryu runtime: launches app
README.md - Ryu runtime → Ping blocker: loads app
README.md - Ryu runtime → Flow reset: loads app
README.md - OVS switches → Ping blocker: sends connect events
drop.py - OVS switches → Flow reset: sends connect events
clear.py - Ping blocker → OVS switches: sends flow mods
drop.py - Flow reset → OVS switches: sends delete mod
clear.py - OVS switches → Switch flow tables: stores flows
README.md - GNS3 network → OVS switches: hosts switches
README.md - GNS3 network → Virtual PCs: hosts PCs
README.md - STP loop prevention → OVS switches: prevents loops
README.md - Ryu runtime → OVS switches: connects OpenFlow
README.md