Changes between Version 9 and Version 10 of WARPnet1/RunningServer
- Timestamp:
- Aug 11, 2010, 10:47:45 PM (14 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
WARPnet1/RunningServer
v9 v10 14 14 The controllers and server connect using network sockets while the server connects to the nodes by either network sockets (if using a Backdoor Board) or PCAP (if using the main Ethernet connection). 15 15 16 To run the server navigate to the `warpnet_framework` directory. There are two ways to run the server. Either 17 {{{ 18 ./run_warpnet_server.sh pcapInterface controllerPort 19 }}} 20 or 16 To run the server navigate to the `warpnet_framework` directory. Run the following: 21 17 {{{ 22 18 python warpnet_server.py pcapInterface controllerPort pcapInterfaceMACaddress 23 19 }}} 24 20 25 The `pcapInterface` is the physical interface (eth0, en1 ) that the FPGA Boards are connected to over the switch. The `controllerPort` is the port on which the server listens for connections to controllers/clients. The first script will extract the MAC address of the `pcapInterface` and pass it to the server or in the second case you must pass it yourself.21 The `pcapInterface` is the physical interface (eth0, en1, etc.) that the FPGA Boards are connected to over the switch. The `controllerPort` is the port on which the server listens for connections to controllers/clients. The first script will extract the MAC address of the `pcapInterface` and pass it to the server or in the second case you must pass it yourself.
