-
Notifications
You must be signed in to change notification settings - Fork 141
BetaReleaseRegressionTests
'''Regression Tests'''
This page describes how each feature was tested. This document identifies the test number, notes the test developer that wrote each test, describes the test in detail, identifies the location in the automated regression suite that calls the test, lists any known bugs with the test, and provides the date when the task was completed.
All of the following tests should be conducted under CentOS 4.4. All tests should be tested on kernel versions XXX with both non-SMP and SMP versions.
- Owner :
- Description :
- Location :
- Regression suite :
- Known bugs/issues :
- Status
- Target Release :
- Due date :
- Owner :
- Description :
nf2.ko should be installed in /lib/modules/`uname -r`/kernel/drivers/nf2.ko
- Location :
- Regression suite :
- Known bugs/issues :
- Due date :
- Owner :
- Description :
Test using ls /sys/class/net and searching for nf2c
Test using ifconfig -a and searching for nf2c
- Prerequisites :
- Location :
- Regression suite :
- Release :
- Known bugs/issues :
- Due date :
- Owner :
- Description :
Note: Driver loading on boot uses modprobe. A success for test " nf2c[0-3] interfaces present in system with one NetFPGA card " implies success for this test.
- Invocation :
- Output :
- Regression suite :
- Known bugs/issues :
- Due date :
- Owner :
- Description :
On a system with at least 1 NetFPGA card and the driver installed, run:
ifconfig nf2c0
One of the lines should display the MTU. The MTU should state 1500 bytes. Example:
UP BROADCAST RUNNING MULTICAST <b>MTU:1500</b> Metric:1
- Location :
- Regression suite :
- Known bugs/issues :
- Due date :
- Owner :
- Description :
- Location :
reference_router/regress/test_interface
- Output :
Testing IP assignment to nf2c0...Success Testing IP assignment to nf2c1...Success Testing IP assignment to nf2c2...Success Testing IP assignment to nf2c3...Success
- Regression suite :
- Target :
- Known bugs/issues :
- Due date :
- Owner :
- Description :
- Prerequisites :
- Invocation :
cd ${NF2_ROOT}/projects/reference_nic/regress/test_loopback_random ./run
- Output :
Test PASSES.
- Regression suite :
- Known bugs/issues :
- Due date :
- Owner :
- Description :
- Prerequisites :
- Invocation :
cd ${NF2_ROOT}/projects/reference_nic/regress/test_loopback_maxsize ./run
- Output :
Test PASSES.
- Regression suite :
- Known bugs/issues :
- Due date :
- Owner :
- Description :
- Prerequisites :
- Invocation :
cd ${NF2_ROOT}/projects/reference_nic/regress/test_loopback_minsize ./run
- Output :
Test PASSES.
- Regression suite :
- Known bugs/issues :
- Due date :
Test 2.1.4: Tx/Rx Random Length Packets and with bad CRCs Check Tx/Rx Counters and Drop Counters Using PHY Loopback
- Owner :
- Description :
Send packets 10000 random length (60-1514 w/o CRC) packets from software out to the device with the PHY set in external loopback back mode and the MAC set to not generate the CRC. Check that the packet/byte Tx/Rx counters are correct and that all these packets were dropped.
Reenable CRC generation and send packets 10000 random length (60-1514 w/o CRC) packets from software out to the device with the PHY set in external loopback back mode. Check that the packet/byte Tx/Rx counters are correct and that none of these packets were dropped.
- Prerequisites :
- Invocation :
cd ${NF2_ROOT}/projects/reference_nic/regress/test_loopback_crc ./run
- Output :
Test PASSES.
- Regression suite :
- Known bugs/issues :
- Due date :
- Owner :
- Description :
- Set PHY to loopback via MDIO
- Disable output queues
- Send in 10,000 maximum sized packets (1514 bytes) equally distributed between all four ports. This should be sufficient to fill up all SRAM queues. (1,514 * 10,000 = 15,140,000 bytes = 15 MB approx).
- Read byte counters and verify:
- Number of bytes received is correct
- Number of bytes arriving at SRAM output queues is identical to bytes exiting Ethernet MAC queues
- Number of bytes dropped + number of bytes stored = number of bytes sent
- Verify that packets can still be sent/received through NetFPGA interfaces
- Location :
- Regression suite :
- Known bugs/issues :
- Due date :
- Owner :
- Description :
- Invocation :
cd ${NF2_ROOT}/projects/reference_nic/regress/test_interface ./run
- Output :
Testing IP assignment to nf2c0...Success Testing IP assignment to nf2c1...Success Testing IP assignment to nf2c2...Success Testing IP assignment to nf2c3...Success
- Regression suite : Yes
- Target : Alpha
- Known bugs/issues :
- Due date : Complete
- Owner :
- Description :
- Connect nf2c0 to eth1 and nf2c1 to eth2
- put the PHY for ports 2 and 3 in internal loopback mode
- Send 10000 packets of random lengths out of the nf2cX interfaces
- Check that all packets were received at eth1/2 for packets sent out of nf2c0/1
- Check that all packets were received at nf2c2/3 for packets sent out of nf2c2/3 (due to loopback and LPM miss)
- Check that the Tx MAC counters show 10000 packets sent on each port
- Check that the Tx MAC counters show the correct number of bytes sent on each port
- Check that output port lookup counters show 40000 packets sent from the CPU
- Prerequisites :
- Location :
- Output :
Test PASSES
- Regression suite :
- Known bugs/issues :
- Due date :
- Owner :
- Description :
- Initialize netfpga hardware
- Send 300 packet with wrong DA with random size from external ethernet port to router port
- Get the drop counter for the router port.
- Check that drop counter is 300.
- Repeat test for other router port.
- Prerequisites :
- Location :
- Output :
SUCCESS!
- Regression suite :
- Known bugs/issues :
- Due date :
- Owner :
- Description :
- Initialize netfpga hardware
- Send 300 packet with EtherType= 0x802 with random size from external ethernet port to router port
- Get the drop counter for the router port.
- Check that packet are forwarded to CPU
- Check that drop counter is 300.
- Repeat test for other router port.
- Prerequisites :
- Location :
- Output :
SUCCESS!
- Regression suite :
- Known bugs/issues :
- Due date :
- Owner :
- Description :
- Initialize netfpga hardware
- Send 300 packet with IP_Version = 0x5 with random size from external ethernet port to router port
- Check that packet are forwarded to CPU
- Get the drop counter for the router port.
- Check that drop counter is 300.
- Repeat test for other router port.
- Prerequisites :
- Location :
- Output :
SUCCESS!
- Regression suite :
- Known bugs/issues :
- Due date :
- Owner : Surender
- Description : Send 300 packets to each interface from an external card with IP time-to-live=1 or 0. Packets should be sent to the CPU. Check the counters.
<br /># Initialize netfpga hardware <br /># Send 300 packet with TTL = 0x0 with random size from external ethernet port to router port <br /># Check that packet are forwarded to CPU <br /># Get the drop counter for the router port. <br /># Check that drop counter is 300. <br /># Repeat test for other router port.
- Prerequisites :
- Location :
- Output :
SUCCESS!
- Regression suite : Yes
- Known bugs/issues :
- Due date :
- Owner : Adam
- Description : Send 300 packets to each interface from an external card to an IP address that does not match in the routing table. Packets should be sent to the CPU. Check LPM miss counter.
- Prerequisites : Run as root, Reference Router bitfile is loaded
- Location : projects/reference_router/regress/test_lpm_misses
- Output :
SUCCESS!
- Regression suite : Yes
- Known bugs/issues : Ignore 'Scalars leaked: 1'
- Due date : Complete
- Owner : Adam
- Description : Send 300 packets to each interface from an external card such that the routing table matches, but the ARP table misses. Packets should be sent to the CPU. Check ARP miss counter.
- Prerequisites : Run as root, Reference Router bitfile is loaded
- Location : /projects/reference_router/regress/test_arp_misses
- Output :
SUCCESS!
- Regression suite : Yes
- Known bugs/issues : Ignore 'Scalars leaked: 1'
- Due date : Complete
- Owner : Surender
- Description : Send 300 IP packets to each interface from an external card with a bad IP header checksum. Check that the packets are all dropped. Check the counters.
<br /># Initialize netfpga hardware <br /># Send 300 packet with bad ip checksum with random size from external ethernet port to router port <br /># Get the drop counter for the router port. <br /># Check that drop counter is 300. <br /># Repeat test for other router port.
- Prerequisites :
- Location :
- Output :
SUCCESS!
- Regression suite : Yes
- Known bugs/issues :
- Due date :
- Owner : Surender
- Description : Send 300 packets to each interface from an external card destined to IP addresses in the destination IP filter table (such as the router's IP addresses). Packets should be sent to the CPU. Check the counters.
- Prerequisites :
- Location :
- Output :
SUCCESS
- Regression suite : Yes
- Known bugs/issues :
- Due date :
- Owner : Adam
- Description : Send 1000 packets to each eth1 with the routing table and arp table entries to route the traffic to eth2. Send 1000 packets to each eth2 with the routing table and arp table entries to route the traffic to eth1. This generates a routing table and an ARP table hit.
- Prerequisites : Run as root, Reference Router bitfile loaded
- Location : /projects/reference_router/regress/test_packet_fowarding
- Output :
SUCCESS!
- Regression suite : Yes
- Known bugs/issues : Ignore 'Scalars leaked: 1'
- Due date : Complete
- Owner : Adam
- Description : Insert two entries in the table with one entry being a subnet of the other. Send 100 packets matching the longer prefix and check that it was received on the correct interface.
- Prerequisites : Run as root, Reference Router bitfile loaded
- Location : /project/reference_router/regress/test_lpm
- Output :
SUCCESS!
- Regression suite : Yes
- Known bugs/issues : Ignore 'Scalars leaked: 1'
- Due date : Complete
- Owner : Adam
- Description : Insert an entry in the routing table with next hop 0.0.0.0 then send 100 packets to that subnet. Check that the packets are being sent with the next hop set as the destination address.
- Prerequisites : Run as root, Reference Router bitfile loaded
- Location : /project/reference_router/regress/test_lpm_next_hop
- Output :
SUCCESS!
- Regression suite : Yes
- Known bugs/issues : Ignore 'Scalars leaked: 1'
- Due date : Complete
- Owner : Glen
- Description : Verify that packets are dropped correctly and only at the SRAM output queues. Test using loopback functionality on PHY.
<br /># Set PHY to loopback via MDIO <br /># Disable output queues <br /># Send in 1000 maximum sized packets (1514 bytes) equally distributed between all four ports. This should be sufficient to fill up all SRAM queues. (1,514 * 1000 = 1,514,000 bytes = 1.5 MB approx. Each queue is 512 KB). <br /># Read byte counters and verify: <br />#* Number of bytes received is correct <br />#* Number of bytes arriving at SRAM output queues is identical to bytes exiting Ethernet MAC queues <br />#* Number of bytes dropped + number of bytes stored = number of bytes sent <br /># Verify that packets can still be sent/received through NetFPGA interfaces
- Location : reference_nic/regress/test_loopback_drop
- Regression suite : yes
- Known bugs/issues :
- Due date : 10/03/07
- Owner : Jad
- Description :
<br /># Set the maximum number of packets in the output queues to 10 <br /># Disable servicing the output queues <br /># Send 10 packets that should be forwarded out of each port <br /># Check the counters to verify that there are 10 packets in each output queue <br /># Send 10 more packets to each output queue <br /># Enable the output queues to receive the first 10 packets sent <br /># Check the counters to verify that 10 packets were dropped at each output queue <br /># Reset the output queues limits to 0xffffffff
- Prerequisites :
- Location : projects/reference_router/regress/test_oq_limit
- Output :
Test PASSES
- Regression suite : Yes
- Known bugs/issues :
- Due date : Complete
- Owner : Jad
- Description :
<br /># Insert 192.168.4.1, 192.168.5.1, and 143.123.123.123 into the IP Destination Address Filter table <br /># Send 10 packets to each of these IP addresses on each port. <br /># Check that the packets are received by the CPU from each port <br /># Remove 192.168.4.1 from the table, and add it in the routing table and the ARP table. <br /># Repeat step 2, and check that the packets destined to 192.168.4.1 are forwarded.
- Prerequisites :
- Location : projects/reference_router/regress/test_ipdest_filter
- Output :
Test PASSES
- Regression suite : Yes
- Known bugs/issues :
- Due date : Completed
- Owner : Jianying
- Description :
<br /># Clear the ARP table and the Routing Table <br /># Set nf2c2 and nf2c3 PHYs in the loopback mode <br /># Clear all four CPU Output Queues' dropped packet counter and dequeued packet counter <br /># Set all four CPU Output Queue sizes to 12KB each. Disable CPU Output Queue dequeuing service <br /># Generate 9 packets for each interface of eth1, eth2, nf2c2, nf2c3. Every packet is of size (1024-8)=1016 bytes. Send these packets out of the interfaces eth1, eth2, nf2c2, nf2c3 <br /># Check each CPU Output Queue stored packet counter is 8 packet and the dropped packet counter is 1 <br /># Then enable all four CPU Output Queue dequeuing service, check each CPU Output Queue dequeued packet counter is 8, and the first 8 packets sent out at eth1, eth2, nf2c2, nf2c3 match the 8 packets which the driver receives from the CPU Output Queues for nf2c0, nf2c1, nf2c2, nf2c3
- Prerequisites : Run as root
- Location : projects/reference_router/regress/test_oq_sram_sz_cpu
- Output :
Test PASSES
- Regression suite : Yes
- Known bugs/issues :
- Due date : Completed
- Owner : Jianying
- Description :
<br /># Clear the ARP table and the Routing Table <br /># Set nf2c2 and nf2c3 PHYs in the loopback mode <br /># Clear all four MAC Output Queues' dropped packet counter and dequeued packet counter <br /># Set all four MAC Output Queue sizes to 8KB each. Disable MAC Output Queue dequeuing service <br /># Generate 5 packets for each interface of nf2c0, nf2c1, nf2c2, nf2c3. Every packet is of size (1024-8)=1016 bytes. Make the driver send these packets out of the interfaces nf2c0, nf2c1, nf2c2, nf2c3 <br /># Check each MAC Output Queue stored packet counter is 4 packet and the dropped packet counter is 1 <br /># Then enable all four MAC Output Queue dequeuing service, check each MAC Output Queue dequeued packet counter is 4, and the first 4 packets the driver sent out at nf2c0, nf2c1, nf2c2, nf2c3 match the 4 packets which the driver receives from eth1, eth2 and CPU Output Queues for nf2c2, nf2c3
- Prerequisites : Run as root
- Location : projects/reference_router/regress/test_oq_sram_sz_mac
- Output :
Test PASSES
- Regression suite : Yes
- Known bugs/issues :
- Due date : Completed
- Owner : Brandon
- Description :
<br /># Clear the ARP table and the routing Table <br /># Set all ports to loopback mode <br /># Clear all MAC counters <br /># Set ARP table and routing table to loop packets within an interface, until TTL goes to zero <br /># Send 128B packets for up to (timeout) seconds, attempting to load each queue to 75% full <br /># Send packets, attempting to maintain each queue at 75% full <br /># Wait for packets to finish looping <br /># Print statistics for each interface <br /># Reset PHY
- Prerequisites : Run as root
- Location : projects/reference_router/regress/test_burn_small
- Output :
Test PASSES
- Regression suite : Yes
- Known bugs/issues :
- Due date : Completed
- Owner : Brandon
- Description :
<br /># Clear the ARP table and the routing Table <br /># Set all ports to loopback mode <br /># Clear all MAC counters <br /># Set ARP table and routing table to loop packets within an interface, until TTL goes to zero <br /># Send 512B packets for up to (timeout) seconds, attempting to load each queue to 75% full <br /># Send packets, attempting to maintain each queue at 75% full <br /># Wait for packets to finish looping <br /># Print statistics for each interface <br /># Reset PHY
- Prerequisites : Run as root
- Location : projects/reference_router/regress/test_burn_small
- Output :
Test PASSES
- Regression suite : Yes
- Known bugs/issues :
- Due date : Completed
- Owner : Brandon
- Description :
<br /># Clear the ARP table and the routing Table <br /># Set all ports to loopback mode <br /># Clear all MAC counters <br /># Set ARP table and routing table to loop packets within an interface, until TTL goes to zero <br /># Send 1496B packets for up to (timeout) seconds, attempting to load each queue to 75% full <br /># Send packets, attempting to maintain each queue at 75% full <br /># Wait for packets to finish looping <br /># Print statistics for each interface <br /># Reset PHY
- Prerequisites : Run as root
- Location : projects/reference_router/regress/test_burn_small
- Output :
Test PASSES
- Regression suite : Yes
- Known bugs/issues :
- Due date : Completed
- Owner : David
- Description : Software Router Compiles without errors
- Location : /projects/scone/regress/test_build
- Output :
- Regression suite :
- Target :
- Known bugs/issues :
- Due date : Completed
- Owner : David
- Description : Ensure that the software router component sets the MAC address registers in the hardware
- Location : /projects/scone/regress/test_mac_set
- Output : Returns 0 else returns 1 and prints error message
- Regression suite : will be called by Glen's Master suite (regression)
- Target :
- Known bugs/issues :
- Due date : Completed
- Owner : David
- Description : Ensure that the software router component sets the IP address registers in the hardware
- Location : /projects/scone/regress/test_ip_set
- Output :
- Regression suite :
- Target :
- Known bugs/issues :
- Due date : Nov 2, 2007
- Owner : David
- Description : Ensure that the software router component sets any default routes into the hardware. Set default routes in the rtable file, after the software component has launched ensure that the routes are pushed into the hardware route table registers
- Location : /projects/scone/regress/test_rtable_set
- Output :
- Regression suite :
- Target :
- Known bugs/issues :
- Due date : Completed
- Owner : David
- Description : Create a route that accepts packets in eth0 (nf2c0) and forwards them out eth1 (nf2c1). Disable eth1 (nf2c1), send packets to eth0 (nf2c0) that based on the routing rules will come out eth1 (nf2c1), ensure no packets come out of eth1 (nf2c1)
- Location : /projects/scone/regress/test_disabled_interfaces
- Output :
- Regression suite :
- Target :
- Known bugs/issues :
- Due date : Completed
- Owner : Jianying
- Description : Ensure that ethernet packets whose next protocol is not ip or arp are dropped
- Location : projects/scone/regress/test_noniparp_ethtype
- Output : SUCCESS
- Regression suite : Yes
- Target :
- Known bugs/issues :
- Due date : Completed
- Owner : Jianying
- Description : Sending an arp request in to the software router for one of the ip addresses of its interfaces returns a correct arp reply out the same interface the arp request was received on
- Location : projects/scone/regress/test_arp_rpl
- Output : SUCCESS
- Regression suite : Yes
- Target :
- Known bugs/issues :
- Due date : Completed
- Owner : Jianying
- Description : Sending an arp request in to the software router for an ip address that is not one of its interfaces does not return an arp reply
- Location : projects/scone/regress/test_arp_norpl
- Output : SUCCESS
- Regression suite : Yes
- Target :
- Known bugs/issues :
- Due date : Completed
- Owner : Jianying
- Description : Create a route from interface 1 to interface 2. Send a packet in interface 1 that is destined for an ip on the route out of interface 2, an arp request should come out interface 2, reply with an arp reply, then ensure that the arp cache table in hardware is updated.
- Location : projects/scone/regress/test_arp_quepkt
- Output : SUCCESS
- Regression suite : Yes
- Target :
- Known bugs/issues :
- Due date : Completed
- Owner : Jianying
- Description : Create a route from interface 1 to interface 2. Send 2 packets in interface 1 that are destined for an ip on the route out of interface 2, an arp request should come out interface 2, reply with an arp reply, then ensure that both packets are sent out of interface 2 with the correct ethernet mac destinations.
- Location : projects/scone/regress/test_arp_quepkt
- Output : SUCCESS
- Regression suite : Yes
- Target :
- Known bugs/issues :
- Due date : Completed
- Owner : Jianying
- Description : Create 4 individual packets, one that is IP but not version 4, one with IPv4 header option, one that is fragmented, one with a bad checksum, and ensure none of them is routed.
- Location : projects/scone/regress/test_ip_error
- Output : SUCCESS
- Regression suite : Yes
- Target :
- Known bugs/issues :
- Due date : Completed
- Owner : Jianying
- Description : Send a packet in to the software component that will not get an rtable hit and confirm that an icmp destination unreachable packet comes out
- Location : projects/scone/regress/test_ip_rtblmiss
- Output : SUCCESS
- Regression suite : Yes
- Target :
- Known bugs/issues :
- Due date : Completed
- Owner : Jianying
- Description : Create an rtable entry for a specific IP address to interface 1. Send a packet in to interface 1 for that destination IP. The packet should be dropped because the incoming interface matches the outgoing interface. An ICMP packet of network unreachable is generated and sent out of interface 1.
- Location : projects/scone/regress/test_ip_intfc
- Output : SUCCESS
- Regression suite : Yes
- Target :
- Known bugs/issues :
- Due date : Completed
- Owner : Jianying
- Description : Ensure routed packets have decremented TTL's
- Location : projects/scone/regress/test_arp_quepkt
- Output : SUCCESS
- Regression suite : Yes
- Target :
- Known bugs/issues :
- Due date : Completed
- Owner : Sara
- Description : Ensure routed packets have correct ip checksums
- Location :
<br /> projects/scone/regress/test_ip_checksum
- Output :
<br /> SUCCESS
- Regression suite :
- Target :
- Known bugs/issues :
- Due date : Completed
- Owner : Sara
- Description : Ensure that a packet with ttl 1 sent to the software component received an icmp ttl expired message
- Pseudocode
- Location :
<br /> /projects/scone/regress/test_ttl_expired
- Output :
<br /> Success
- Regression suite :
- Target :
- Test issues :
- Known bugs/issues :
- Due date : Nov 6
- Owner : Sara
- Description : Ensure that a packet moving through the software component that gets an rtable hit and an arp table hit is correctly sent out
- Location :
<br /> /projects/scone/regress/test_send_receive
- Output :
<br /> SUCCESS
- Regression suite :
- Target :
- Known bugs/issues :
- Due date : Completed
- Owner : Sara
- Description : Ensure a packet sent in to be routed that does not have an existing ARP table entry generates a proper arp request
- Location :
<br /> /projects/scone/regress/test_arp_req
- Output :
<br /> SUCCESS
- Regression suite :
- Target :
- Known bugs/issues :
- Due date : Nov 6
- Owner : Sara
- Description : Ensure that the software component replies to a TCP connection setup packet to any of its ips to ports 23/80 for telnet and http
- Location :
<br /> /projects/scone/regress/test_tcp_port
- Output :
<br /> SUCCESS
- Regression suite :
- Target :
- Known bugs/issues :
- Due date : Nov 6
- Owner : Sara
- Description : Ensure any udp packets destined to the interface's ips reply with port unreachable
- Location :
<br /> project/scone/regress/test_udp_packet
- Output :
<br /> SUCCESS
- Regression suite :
- Target :
- Known bugs/issues :
- Completed
- Owner : Sara
- Description : Ensure any IP packets that are not pwospf/tcp/udp/icmp get dropped
- Location :
<br /> projects/scone/regress/test_unknown_ip
- Output :
<br /> SUCCESS
- Regression suite :
- Target :
- Known bugs/issues :
- Due date : Nov 6
- Owner : Sara
- Description : Ensure the software component replies to software icmp echo requests
<br /> check if echo reply icmp packet is generated
- Location :
<br /> projects/scone/regress/test_icmp_echo
- Output :
<br /> SUCCESS
- Regression suite :
- Target :
- Known bugs/issues :
- Owner : Sara
- Description : Ensure that icmp packets destined to the software router that are not echo request/replies get dropped
- Pseudocode
- Location :
<br /> projects/scone/regress/test_icmp_notecho
- Output :
<br /> SUCCESS
- Regression suite :
- Target :
- Known bugs/issues :
- Due date : Nov 6
- Owner : Neda
- Description : Checks if the GUI window appears on the screen
- Location : projects/gui_scone/regress/test_main_frame
- Regression suite : Yes
- Target : RR Alpha 1.0
- Known bugs/issues : None
- Due date : Done
- Owner : Neda
- Description : Checks if changes in Routing Table are reflected in hardware
- Location : projects/gui_scone/regress/test_routing_table
- Regression suite : Yes
- Target : RR Alpha 1.0
- Known bugs/issues : Changes in the output port columns are not reflected in registers until user changes the selected (highlighted row).
- Due date : Done
- Owner : Neda
- Description : Checks if changes in ARP Table are reflected in hardware.
- Location : projects/gui_scone/regress/test_arp_table
- Regression suite : Yes
- Target : RR Alpha 1.0
- Known bugs/issues : None
- Due date : Done
- Owner : Neda
- Description : Checks if changes in Configuration Table are reflected in hardware
- Location : projects/gui_scone/regress/test_port_config_table
- Commands to Enter
- Regression suite : Yes
- Target : RR Alpha 1.0
- Known bugs/issues : None
- Due date : Done
- Owner : Neda
- Description : Checks if all windows can be opened
- Location : projects/gui_scone/regress/test_popup
- Regression suite : Yes
- Target : RR Alpha 1.0
- Known bugs/issues : None
- Due date : Done
- Owner : David
- Description : Builds Router Kit in the host environment
- Prerequisites :
- Location : projects/router_kit/regress/test_00_make
- Output :
- Regression suite : Yes
- Known bugs/issues :
- Due date : Complete
- Owner : David
- Description : Parses IP addresses from the nf2cX interfaces and sets them in the IP destination filter table on the NetFPGA
- Prerequisites :
- Location : projects/router_kit/regress/test_01_ip_dst_filter
- Output :
- Regression suite : Yes
- Known bugs/issues :
- Due date : Complete
- Owner : David
- Description : Parses the Linux kernel's routing table and places any routes that have an nf2cX interface as the exit port into the route table on the NetFPGA
- Prerequisites :
- Location : projects/router_kit/regress/test_02_route_table
- Output :
- Regression suite : Yes
- Known bugs/issues :
- Due date : Complete
- Owner : David
- Description : Parses the Linux kernel's ARP table and places the entries into the ARP table on the NetFPGA
- Prerequisites :
- Location : projects/router_kit/regress/test_03_arp_table
- Output :
- Regression suite : Yes
- Known bugs/issues :
- Due date : Complete
- Owner : David
- Description : Tests the ability to forward packets generated on eth1 through the NetFPGA (the first couple through the Linux kernel), then back out of the NetFPGA to be detected on eth2
- Prerequisites :
- Location : projects/router_kit/regress/test_04_ip_packets
- Output :
- Regression suite : Yes
- Known bugs/issues :
- Due date : Complete