StarWindX Auth/Session Bug?

[cypher2000]

Also noticed this discrepancy:

Code: Select all

-PartnerIP:"#p1=10.128.124.51:heartbeat:3260:1,10.255.255.4:heartbeat:3260:1;#p2=10.10.10.2:sync:3260:1"

#p1= and #p2= ended up in the same partner list...which is probably not correct. Checking what did that...the strange thing is, the $node I supply is correct:

Code: Select all

HostName           : 10.128.124.51
...
HBInterface        : #p1=10.128.124.50:3260,10.255.255.3:3260
SyncInterface      : #p1=10.10.10.1:3260
...

I also added debug code to spit out what it generates for #p1 and #p2 heartbeat values and they look correct:

Code: Select all

#p1=10.128.124.50:3260,10.255.255.3:3260
#p2=10.128.124.51:3260,10.255.255.4:3260

Yet the partner data above clearly shows #p1 with #p2's heartbeat values and #p2 with #p2's sync value.

[yaroslav (staff)]

Try reverting them. Node 1 should be referring to the counterpart's IPs.
Not sure what priorities mean; will just share to be on the same page viewtopic.php?t=5731.

[cypher2000]

are you saying the #p1= value should be the IPs from node 2 and vice versa?

[yaroslav (staff)]

Yes, give it a shot.