Wifi infra with new network file spec #11
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…WITH MASTER - LR-WPAN netdevices and SixLowPan being installed on required nodes - TCP/UDP server/clients now using ipv6 and ipv4 addresses - PROBLEM: No communication between server and clients at this point. Changing the way LR-WPAN netdevices and SixLowPan are installed to see if that fixes anything.
- Wifi being installed on required nodes - Packets being sent and received over wifi in the wireless network at the end node. - This is only a toy example. More testing needs to be done to make sure this works reliably.
-Wi-Fi seems to be working -The servers need to be modified so that they can use multiple ipv4 addresses. One for WiFi and one for non-wifi. The packets are being delivered right not, but the non-wifi addresses if being used. This needs to be fixed. -Routing for the WiFi network needs to be setup, this will be done using OSLR. -Better file structures need creation for the wifi-network.
-MultiClientTcpServer and TcpClient have both been changed so that they use use ipv4 only, but MultiClientTcpServer creates 2 sockets, 1 for primary network and one for the wiki network. -Useful helper methods created to make life easier. - NS3Netsim changed so that it now works with the modified TCP application.
- TCP applications and UDP applications ready to go with wifi net devices - Tested with multiple networks very close to each other which could cause interference - Routing within wifi still needs to be done so packets can be routed to the server if server and client are not in direct contact.
…n-multiple-ipv4-addresses Apps change listen on multiple ipv4 addresses
- Started creation of Config reader, this will read the file passed into the simulator once - Class to store the information on a node has also been created - Tests for the node have also been created
…c_type and access_point added - Node is now immutable, none of the member values can be changed, easier to perform validation - NIC type added, network interface type added, this can also be none - Access point added in case NIC is wifi - Started on NetworConnection
- Node has been updated to store multiple types of NICs - Node test cases have been updated - Validation functions have been moved out of Node and into their own file
- Network Connection class finished - Network Connection class is immutable - Network Connection class has been tested using the tests created. - More validation code has been moved to Valication Functions and more validation functions have been created to validate NetworkConnections
- NIC Classes created - Tests for the NIC classes created - Node Updated - Node NIC validation function updated - Node tests updated
- App Connections class finsihed - App Connections class validates the parameters of the init - App Connections test cases finished
- Config reader started - Nodes are being read - Nodes are checked to make sure there are no duplicate power id or network id - Node and NIC expanded so that == and != work properly and __str__ also overridden - Test cases expanded for NIC and Node to test == and != - Test cases created for Config reader to test Valid Nodes, Duplicate Nodes and a wrong type of NIC
- Network Connection reading finished. - Test cases for NetworkConnection and nodes finished/expanded.
- Config reads app connections - Verifies that nodes in the app connections exist and that the path type is valid - Tests for Config App Connections finished - Added ==, != operator to AppConnections and AppConnectionTypes. - Added test for == and != for AppConnections
- When config reads a wifi ap/non-ap pair. Check to see if the distance is equal to or more than 50m, if distance is not less than 50m, an error is thrown. - Tests added to test distance validation.
- Re-orged the files - Changed all the dates in the config folder to be YYYY.MM.DD
…nnections as json.
- All the network is included in a network node. - No difference between the primary network and th secondary network, its all just one network - Tests changed to reflect new file spec.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hello all, i am trying to run the wifi scenario using your co-simulation tool but i get the following error.
Can you please help me?
Thanks a lot!
ERROR: [Errno 104] Connection reset by peer: Simulator "PktNetSim-0" closed its connection.
Mosaik terminating