[L2SWITCH-82] arphandler unable to flood arp packet Created: 07/Sep/16 Updated: 19/Oct/17 Resolved: 05/Oct/16 |
|
| Status: | Resolved |
| Project: | l2switch |
| Component/s: | General |
| Affects Version/s: | unspecified |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Xu Ye | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| External issue ID: | 6655 |
| Priority: | Normal |
| Description |
|
To reproduce: 2) h1 ping h2 quickly enough before loopremover module to process the topology . 3) h1 ping h2 will always fail,because the controller doesn't packetout the arp-request packet. In the other hand, if the network topology changed which will change the StpStatus of the nodeconnectors ,arphandler module inventoryReader has no way to process this situation. |
| Comments |
| Comment by Geng Xingyuan [ 09/Sep/16 ] |
| Comment by Xu Ye [ 27/Sep/16 ] |
|
Another situation to reproduce this bug: 2) h1 ping h2 ,ok; 3) quit mininet,then bring mininet with one switch and 4 hosts,like: 4) h1 ping h4 or h1 ping h3 will always fail; Because the nodeconnector info of the node(openflow:1) in buffer inventoryReader.SwitchNodeConnectors() only contains connectors connected to h1 and h2. So when h1 ping h4,the arp-request can not flood to h4. |