Changes between Version 3 and Version 4 of MultihopReferenceDesign
- Timestamp:
- Apr 2, 2007, 4:02:23 PM (17 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
MultihopReferenceDesign
v3 v4 1 1 = Multi-hop OFDM Networking Reference Design = 2 2 3 By default, this project creates a custom wireless ethernet hub between computers attached to two WARP boards and uses a third WARP node has a relay. The project treats ethernet packets as payload only; the WARP board performs no IP processing whatsoever. The following are two example applications. 3 By default, this project creates a custom wireless ethernet hub between computers attached to two WARP boards and uses a third WARP node has a relay. The project treats ethernet packets as payload only; the WARP board performs no IP processing whatsoever. The following is an example configuration. 4 5 [[Image(multihop.jpg, align=center, 800)]] 4 6 5 7 6 8 == Example System Configuration 1 == 7 9 8 The user will need to supply two computers and t woWARP nodes (1 node = 1 FPGA[v1.2] + 1 Radio[v1.4]). The computers need to be configured to have hardcoded IP addresses within each other's addressable range. In other words, they must be in each other's subnet to be able to talk to one another. For example, one computer can be 10.0.0.8 and the other can be 10.0.0.9 and each can have a subnet mask of 255.255.255.0.10 The user will need to supply two computers and three WARP nodes (1 node = 1 FPGA[v1.2] + 1 Radio[v1.4]). The computers need to be configured to have hardcoded IP addresses within each other's addressable range. In other words, they must be in each other's subnet to be able to talk to one another. For example, one computer can be 10.0.0.8 and the other can be 10.0.0.9 and each can have a subnet mask of 255.255.255.0. 9 11 10 One FPGA board '''must''' by configured as Node 0, and other as Node 1, using the on-board dip switches. The switch closest to the power supplies represents the node value. When the program is downloaded, the seven-segment LCDs should show the node values. 12 One FPGA board '''must''' by configured as Node 0, and other as Node 1, using the on-board dip switches. The switch closest to the power supplies represents the node value. When the program is downloaded, the seven-segment LCDs should show the node values. These nodes must be connected to the computer terminals via Ethernet, as shown above. A third, Node 2, must be configured with the bitstream and stand alone. Being the relay, it needs no computer to connect to. 11 13 12 Using ethernet, connect one PC to one board, and the other PC to the other board.Note, if the PCs are using older network cards that do not support auto MDI/MDI-X, the user may need to provide crossover ethernet cables instead of standard cables. Once the boards are connected and configures, any traffic directed to one computer's IP address from the other computer will be forwarded.14 Note, if the PCs are using older network cards that do not support auto MDI/MDI-X, the user may need to provide crossover ethernet cables instead of standard cables. Once the boards are connected and configures, any traffic directed to one computer's IP address from the other computer will be forwarded. 13 15 14 == Example System Configuration 2 ==15 16 The user will need to supply one computer and two WARP nodes. Enable DHCP on the computer (most likely already enabled, unless the user tried the first configuration).17 18 One FPGA board '''must''' by configured as Node 0, and other as Node 1, using the on-board dip switches. The switch closest to the power supplies represents the node value. When the program is downloaded, the seven-segment LCDs should show the node values.19 20 Connect the PC to a board using a standard or crossover ethernet cable. Connect the other board to an internet source (e.g. the wall, a router, etc). The computer will then be able to access network resources via the WARP OFDM link.21 16 22 17