Software defined network
An Internet Exchange Point (IXP) is defined as a common point for different Internet Service Providers (ISPs) to connect their networks together and exchange internet traffic between them. Each ISP is considered as an Autonomous System (AS) by itself and within the IXP, different ASes will peer with...
Saved in:
| 主要作者: | |
|---|---|
| 其他作者: | |
| 格式: | Final Year Project |
| 語言: | English |
| 出版: |
2018
|
| 主題: | |
| 在線閱讀: | http://hdl.handle.net/10356/74366 |
| 標簽: |
添加標簽
沒有標簽, 成為第一個標記此記錄!
|
| 總結: | An Internet Exchange Point (IXP) is defined as a common point for different Internet Service Providers (ISPs) to connect their networks together and exchange internet traffic between them. Each ISP is considered as an Autonomous System (AS) by itself and within the IXP, different ASes will peer with each other to allow the exchange of network traffic. These peering(s) are made possible with the use of Border Gateway Protocol (BGP). However, BGP does not allow flexibility in the configuration of the IXP and there is a constrain on how the traffic can be delivered across the network. Therefore, by applying the configurability and flexibility of a Software Defined Network (SDN), it would be possible to configure and control how traffic is being routed across the IXP. The project will look at the usage of the OpenFlow protocol as well as the deployment of Faucet as the controller for the SDN. Both Mininet and Miniedit will be used as the network emulator to build and simulate the network topology. The project will also look at the usage of the Access Control List in Faucet to perform policy based forwarding. It will also look at within a resilient network, how will Faucet function accordingly to link failures within the network. |
|---|