You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I saw a wired MAC destination address "00:00:00:00:00:00" on the pktgen TUI when I was doing the pktgen test in the newest pktgen version (pktgen-24.07.1).
And then I found the version pktgen-24.05.0 shows the address like I want
pktgen-24.05.2 is the version started to become abnormal of this issue.
I don't know if there's a error in these changes, or if this is a corrected logic to say that the starting MAC destination address for port 1 as "00:00:00:00:00:00".
These are my tested ethernet devices:
Intel Ethernet Controller E810-C
Ethernet Controller X710 for 10GbE SFP+ 1572
XGMAC 10GbE Controller 1458
I really hope someone can help me here.
Sincerity,
The text was updated successfully, but these errors were encountered:
Thanks for your sincere reply. After I try the version of fix-startup, the issue is no longer occurs.
I hope this message finds you well.
May I kindly ask when you plan to merge this fix into the new version, and could you please let me know if the next version (24.11) will include this fix?
Please look at fixes-for-release branch it should contain all of the fixes I am hoping to get done this month. I was waiting for a few other people to suggest the other fixes(branches) are work before merge. Thanks
I saw a wired MAC destination address "00:00:00:00:00:00" on the pktgen TUI when I was doing the pktgen test in the newest pktgen version (pktgen-24.07.1).
And then I found the version pktgen-24.05.0 shows the address like I want
pktgen-24.05.2 is the version started to become abnormal of this issue.
I don't know if there's a error in these changes, or if this is a corrected logic to say that the starting MAC destination address for port 1 as "00:00:00:00:00:00".
These are my tested ethernet devices:
I really hope someone can help me here.
Sincerity,
The text was updated successfully, but these errors were encountered: