When running jdiameter as a server with two address:
<LocalPeer>
...
<IPAddresses>
<IPAddress value="1.2.3.4" />
<IPAddress value="5.6.7.8" />
</IPAddresses>
....
</LocalPeer>
Peer (2.3.4.5/6.7.8.9) sends INIT to 1.2.3.4 with:
IPv4 address parameter 2.3.4.5.
IPv4 address parameter 6.7.8.9
Server (jdiameter 1.2.3.4/5.6.7.8) responds with INIT ACK with NO IPv4 address parameters, although:
ENDPT SOCK STY SST HBKT LPORT UID INODE LADDRS
ffff8800d8bbd900 ffff8800da973800 2 10 63 3868 0 51257 2.3.4.5
ffff8800d8936200 ffff8800da8c2b40 2 10 63 3868 0 51254 6.7.8.9
When checking the logs jdiameter is running two separate server sockets for those IPs as matches above, instead of adding the 6.7.8.9 as a secondary address....
When running freeDiameter:
ffff88011a3ab000 ffff8800d9e3d080 2 1 3 36 4 0 0 0 12811 3868 49128 1.2.3.4 5.6.7.8 <-> *2.3.4.5 6.7.8.9 1500 8 8 4 0 0 21 1 0 212992 212992
So JDiameter is not binding the address to the same socket to give true multi-homing
When running jdiameter as a server with two address:
Peer (2.3.4.5/6.7.8.9) sends INIT to 1.2.3.4 with:
IPv4 address parameter 2.3.4.5.
IPv4 address parameter 6.7.8.9
Server (jdiameter 1.2.3.4/5.6.7.8) responds with INIT ACK with NO IPv4 address parameters, although:
When checking the logs jdiameter is running two separate server sockets for those IPs as matches above, instead of adding the 6.7.8.9 as a secondary address....
When running freeDiameter:
ffff88011a3ab000 ffff8800d9e3d080 2 1 3 36 4 0 0 0 12811 3868 49128 1.2.3.4 5.6.7.8 <-> *2.3.4.5 6.7.8.9 1500 8 8 4 0 0 21 1 0 212992 212992So JDiameter is not binding the address to the same socket to give true multi-homing