fix-for(E2E controller ignition over 1-hop RF sync link)

[banswamy]

Signed-off-by: bmswamy [email protected]

Prerequisites

• I have read the Contributing Guidelines.
• I have read the Code of Conduct.
• If this is a non-trivial change, I have already opened an accompanying Issue.
• If applicable, I have included documentation updates alongside my code changes.

Description

E2E controller ignition over 1-hop RF sync link

Test Plan

• Tested below command in e2e controller for link up
• tg link up -i PUMA_2_DN_2 -r PUMA_3_CN_3
• Tested below command for topology list
• tg topology ls

bash-5.0# tg topology ls
NodeName MacAddr PopNode NodeType Status SiteName

---

PUMA_1_DN_1 34:ef:b6:8a:0e:0e True DN ONLINE_INITIATOR PUMA_1_DN
PUMA_2_DN_2 34:ef:b6:45:fc:18 False DN ONLINE PUMA_2_DN
PUMA_3_CN_3 34:ef:b6:8a:10:a8 False CN ONLINE PUMA_3_CN

LinkName ANodeName ZNodeName Alive LinkType LinkupAttempts

---

link-PUMA_1_DN_1-PUMA_2_DN_2 PUMA_1_DN_1 PUMA_2_DN_2 True WIRELESS 1
link-PUMA_2_DN_2-PUMA_3_CN_3 PUMA_2_DN_2 PUMA_3_CN_3 True WIRELESS 1

SiteName Latitude Longitude Altitude Accuracy

---

PUMA_1_DN 37.4862 -122.146 -3.4 24.13
PUMA_2_DN 37.4862 -122.146 -3.4 24.13
PUMA_3_CN 37.4862 -122.146 -3.4 24.13

[elludraon]

I completely don't understand the reason for the POP_ADDR related changes.