Uploaded image for project: 'PROFINET Core'
  1. PROFINET Core
  2. PSPNCORE-223

Invalid PeerPortId value when Non-Profinet neighboor attached

          Details

          • Type: Bug
          • Status: Closed
          • Priority: Minor
          • Resolution: Fixed
          • Affects Version/s: None
          • Fix Version/s: V1.7.5.0, V1.8.0.0
          • Component/s: None
          • Labels:
            None
          • Account:
            SPC Profinet Core (SPCPROFINET)

            Description

            The encoding function for PDPortDataReal record object data may use an invalid coding for the PeerPortId value when a Non-Profinet neighboor is connected. The problem occurs since the function does not validate the PortId coding of the peer.

            It is expected that if the peer does not use a Profinet conformant LLDP Port Id coding, no port id value is reported.

              Attachments

                Issue Links

                blocks

                Change - PSPNSV4-940 Update Profinet Core to V1.7.5.0

                • Minor - Minor loss of function, or other problem where easy workaround is present.
                • Closed
                is blocked by

                Bug - A problem which impairs or prevents the functions of the product. PSPNSV4-936 PDRealData read response may contain unexpected PeerPortName in case of Non-Profinet neighbor

                • Minor - Minor loss of function, or other problem where easy workaround is present.
                • Closed

                  Expenses

                    Activity

                      Status Description

                        People

                        • Reporter:
                          AMesser Andreas Messer
                        • Votes:
                          0 Vote for this issue
                          Watchers:
                          0 Start watching this issue

                          Dates

                          • Created:
                            Updated:
                            Resolved: