Closed jwbensley closed 7 years ago
Sent response via email requesting more info;
Sorry for the delay in my response I have been away. I have opened an issue on the GitHub page here (https://github.com/jwbensley/Etherate/issues/22) in case you are experiencing a bug we can track it's progress there.
Please can you tell me a little bit about how you are running Etherate;
Are you running Etherate between two machines on the same LAN, or two Virtual Machines on the same bridge adapter?
When you run Etherate it says something like:
"Using device enp0s25 with address 3c:97:0e:bd:62:82, interface index 2"
What interface is Etherate using on each device?
Are both those interfaces up and running?
Are they in the same broadcast domain?
Hi James, I have attached the screenshot taken at both Tx and Rx. I'm running etherate between two machines on the same network.
Actually at Rx side it waits in a while loop indefinitely for the first test frame to be received. That’s why I don’t see any progress, after that in Rx side.
When I manually changed the FIRST_FRAME value to true, it works in Rx side.
I don’t know why the first test frame is lost at the Rx side. Even though I first run Rx and then run Tx.
@sudhanthiradasan Thanks for the info, when you change FIRST_FRAME
to true
and you say that it works, does the Rx side start to could up the same amount of data that Tx is sending, or does the duration increment Rx but it says it's recieving 0Mbps or traffic?
Many thanks.
Please can you also grab the latest version of Etherate as I have updated it with some bug fixes since you have initially reported this issue.
Even in the latest version I'm seeing the same issue
@sudhanthiradasan Thanks for your response. Can you please share the output of the following command from both machines:
lspci
sudo etherate -l
ip l
If you can provide this output I will try and make a patch over the coming weekend for you to test.
Hi, Attached the results from both the machines m1(ilx2) and m2(ilx1).
@sudhanthiradasan I am sorry for the MASSIVE delay! I have been very busy with my day job recently. This should now be fixed in the newest version. Are you still able to check?
I wasn't able to replicate the issue for a while and today a friend of mine experienced the same issue. I found a way to replicate the issue and fix it. Please let me know if this is fixed for you now.
Thanks jwbensley.. Its working fine with the current version
Thanks @sudhanthiradasan for taking the time to test this again!
Fixed in the commit to v 1.14 moving from beta to production ready: https://github.com/jwbensley/Etherate/commit/d67ffec29bf20d582abc8a4b7cd81b8d2e281759
Sent in via email: