Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

plcstat/int6kstat: allow to query a powerline device for topology directly #119

Merged
merged 1 commit into from
Oct 27, 2018

Conversation

mhei
Copy link
Contributor

@mhei mhei commented Sep 21, 2018

In a switched network, i.e. when local powerline device(s) are not
connected directly to host, then using the Local Management Address
to determine the local devices might fail due to wrong or incomplete
forwarding by the switch.

In this case it would be desirable to address the local powerline
device directly which is not possible with both tools at the moment.

This patch fixes this issue by keeping current behaviour as much as
possible and also document it in the corresponding man pages.

Signed-off-by: Michael Heimpold [email protected]

@mhei mhei force-pushed the plcstat-direct-query branch from fb58f40 to 971eadb Compare September 21, 2018 09:33
@mhei mhei changed the title plcstat/int6kstat: allow to query a powerline directly plcstat/int6kstat: allow to query a powerline device for topology directly Sep 21, 2018
@mhei
Copy link
Contributor Author

mhei commented Sep 24, 2018

@n1000 @dvlemplgk @ch-aurich: would be nice if you could find the time for a review. Thanks.

plc/int6kstat.1 Outdated
Topology is always relative to the local host, or local hosts if present.
Powerline devices that appear on the command line are not used for this operation.
PHY rates displaye by this option may saturate at 255 mbps.
Topology is relative to the queried powerline device(s) given on the command lines. If no device is given explicitely,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  1. command line
  2. explicitly

plc/plcstat.1 Outdated
@@ -83,11 +82,13 @@ The default Link ID is \fB0xFC\fR.
.RB - t
Display network topology using VS_SW_VER and VS_NW_INFO messages.
This option is similar to option \fB-m\fR but provides complete network topology plus device hardware and firmware version.
Topology is always relative to the local host, or local hosts if present.
Powerline devices that appear on the command line are not used for this operation.
Topology is relative to the queried powerline device(s) given on the command lines. If no device is given explicitely,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  1. command line
  2. explicitly

@dvlemplgk
Copy link
Contributor

Functionality looks fine to me. There are some typos in the manual page (see inline comments).

…ectly

In a switched network, i.e. when local powerline device(s) are not
connected directly to host, then using the Local Management Address
to determine the local devices might fail due to wrong or incomplete
forwarding by the switch.

In this case it would be desirable to address the local powerline
device directly which is not possible with both tools at the moment.

This patch fixes this issue by keeping current behaviour as much as
possible and also document it in the corresponding man pages.

Signed-off-by: Michael Heimpold <[email protected]>
@mhei mhei force-pushed the plcstat-direct-query branch from 971eadb to 22d1870 Compare October 6, 2018 09:40
@mhei
Copy link
Contributor Author

mhei commented Oct 6, 2018

@dvlemplgk Thank you very much, I fixed the typos and pushed it to the branch.

Copy link
Member

@n1000 n1000 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I did not get to test this, but the changes look fine to me.

@n1000 n1000 merged commit 24d8f76 into qca:master Oct 27, 2018
@mhei mhei deleted the plcstat-direct-query branch November 2, 2018 23:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants