So I built a basic Zynq with Ethernet 0 enabled in PL. I created the platform in Vitis 2020.1. I created the LwIP UDP Perf Server and Built it and ran it. It asked me to run the perf client using the ip address 192.168.1.10 and port 5001. I downloaded iperf3 to my windows 10 computer which was configured to 192.168.1.20. I ran the command suggested but with iperf3. In wireshark it says it was using TCP protocol and the request is in red. I get a reply that the connection was rejected. I had already closed everything down and so I do not have the actual message. Hopefully what I am typing right now is enough. Have not found any tutorials on how to use UDP Perf so I have no idea what I am doing right or wrong. I did notice the command suggested did not include the -u option so I did run it again with -u for UDP but it also rejected the connection and still said TCP in wireshark. Any help would be awesome.
The ip address was changed because something on my system was forcing me to use 169.254.x.x ips for my network to communicate. Dont know enough about TCP IP to know what or why so I had changed my ips back for my network. So that is why the ips are different. But I had tried using both. Both being 192.168.1.x and 169.254.x.x
Question
MichelleNicholes
So I built a basic Zynq with Ethernet 0 enabled in PL. I created the platform in Vitis 2020.1. I created the LwIP UDP Perf Server and Built it and ran it. It asked me to run the perf client using the ip address 192.168.1.10 and port 5001. I downloaded iperf3 to my windows 10 computer which was configured to 192.168.1.20. I ran the command suggested but with iperf3. In wireshark it says it was using TCP protocol and the request is in red. I get a reply that the connection was rejected. I had already closed everything down and so I do not have the actual message. Hopefully what I am typing right now is enough. Have not found any tutorials on how to use UDP Perf so I have no idea what I am doing right or wrong. I did notice the command suggested did not include the -u option so I did run it again with -u for UDP but it also rejected the connection and still said TCP in wireshark. Any help would be awesome.
The ip address was changed because something on my system was forcing me to use 169.254.x.x ips for my network to communicate. Dont know enough about TCP IP to know what or why so I had changed my ips back for my network. So that is why the ips are different. But I had tried using both. Both being 192.168.1.x and 169.254.x.x
Edited by MichelleNicholesadded error messages
Link to comment
Share on other sites
3 answers to this question
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now