Dear Neil, Attached file is our tcpdump. Now our secondary IP doesn't work. Please advise. Thanks. IP info: lksctp primary IP is 172.28.129.49 lksctp secondary IP is 172.28.129.176 Client IP is 10.82.29.240/10.82.29.241 Regards, Andrew On Thu, Nov 7, 2013 at 10:43 AM, tsoi andrew <tsoiandrew@xxxxxxxxx> wrote: > Dear Neil, > > For more information, our secondary IP doesn't response COOKIE_ECHO > also. Only our primary IP can response COOKIE_ECHO with COOKIE_ACK. > > Regards, > Andrew > > On Thu, Nov 7, 2013 at 10:36 AM, tsoi andrew <tsoiandrew@xxxxxxxxx> wrote: >> Dear Neil, >> >> Please find my network diagram first. >> Now at server side, can't see our lksctp client 4 connection but only >> 2 2 connection. The reason is that heartbeat ACK not found. >> >> Regards, >> Andrew >> >> On Mon, Nov 4, 2013 at 8:09 PM, Neil Horman <nhorman@xxxxxxxxxxxxx> wrote: >>> On Mon, Nov 04, 2013 at 09:59:44AM +0800, tsoi andrew wrote: >>>> Dear Sir, >>>> >>>> I got a problem when set multi-homing to active/active. >>>> That mean, It is expected that our lksctp server have 2 IP to connect >>>> 2 IP of destination client with total 4 connections. >>>> The flow is that client send "INIT" message with 2 (primary and >>>> secondary) IP to our server and lksctp server return INIT_ACK. But >>>> when second client send 'heartbeat' to us, lksctp server cannot return >>>> ACK. >>>> Moreover, we already proved our connectivity correct because when our >>>> lksctp server send heartbeat to both destination client and they can >>>> return ACK. >>>> Would you mind sharing if lksctp lib already configure those >>>> multi-homing purpose. >>>> >>> Can you provide a network diagram and a tcpdump of your connection? >>> Neil >>> >>>> >>>> >>>> Best Regards, >>>> Andrew Tsoi >>>> -- >>>> To unsubscribe from this list: send the line "unsubscribe linux-sctp" in >>>> the body of a message to majordomo@xxxxxxxxxxxxxxx >>>> More majordomo info at http://vger.kernel.org/majordomo-info.html >>>>
Attachment:
sctpmultiHomeNow.pcap
Description: Binary data
