Replies: 1 comment 1 reply
|
I don't think we are able to make a difference between an interface where autoneg is disabled and the information is not available. |
1 reply
|
Ok, thank you for your response, Vincent! I would also like to ask if it is possible to add a CLI to enable and disable the LAG, PHY/MAC options, because when we have '#ifdef ENABLE_DOT3', the LAG and PHY/MAC options are automatically included in the LLDP packet, regardless of whether you need them or not. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
background
In this repo, I know that the status of the interface is obtained using ethtool (such as autonegotiation, speed, etc.), and I am running this LLDP on the switch through Docker. During the build process, I included option dot3 in the program
Test Environment
lldpd 1.0.4
What I find
When accessing the OOB interface, here it is eth0, and there are no issues, as shown in the image form wireshare below.
Comparing it to directly using ethtool to detect eth0, it is correct.
But when I read the interfaces of other switch front ports (in here, i use Ethernet0 to explatin), the information has issues.
Comparing it to directly using ethtool to detect Ethernet0
I found that if these front ports support auto-negotiation, speed, etc., ethtool is unable to detect them.
Think
I am wondering if this is related to the fact that the switch front port is not directly connected to the Linux network interface card (NIC). Additionally, can we avoid sending this MAC/PHY option when the values read through ethtool are empty?
This is my first question, and if you need more detailed information, please let me know. Also, if I have offended you in any way, please inform me immediately; any information is helpful! I hope to receive a response and engage in discussion.
bebe weng
mail : kevin2622655@gmail.com
All reactions