Date: Thu, 13 Sep 2007 09:48:54 -0400 From: Randall Stewart <rrs@cisco.com> To: sazzadur rahman <rahman.sazzadur@gmail.com> Cc: freebsd-net@freebsd.org Subject: Re: A query regarding dynamic address configuration in SCTP Message-ID: <46E93FC6.4080003@cisco.com> In-Reply-To: <82bdb5ec0709122128r2d789050j7926109a84ec2033@mail.gmail.com> References: <82bdb5ec0709122128r2d789050j7926109a84ec2033@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Sazzadur: No I don't think your expectation is wrong.. this may be a bug in the code. Not sure whats up but I will test this scenario and see if I can recreate it. Once you get the addr made primary .. this should be the primary address.. Let me try this here in my lab and see if I get the same results. By the way. What version of the code are you on.. is it the Current 7.0 code.. or is it a patch from sctp.org on 6.x? If a patch, what is the name (date) of the patch.. Thanks R sazzadur rahman wrote: > Hello, > > I am trying to test a dynamic address configuration scenario between a sctp > server and a sctp client. > The scenario is like: > > > sctp_server(129.15.78.125) > sctp_client(129.15.78.114) > > 1. > <------------------------------------------------------------------------ > connect > accept > -----------------------------------------------------------------------> > > 2. > <--------------------------------------------------------------------- data > > sack > -----------------------------------------------------------------------> > > sctp_server > creates an ipalias > of 129.15.78.126 > > 3. addip(129.15.78.126 > )--------------------------------------------------------> > > <-------------------------------------------------------------------------asconf_ack > > > 4. setpeerprimary(129.15.78.126)-------------------------------------------> > > <-------------------------------------------------------------------------asconf_ack > > > 5. > <------------------------------------------------------------------------ > data (still it sends data to peers > > 129.15.78.125 instead of 129.15.78.126) > > I was expecting that in step 5, sctp_client would send data to sctp_server > in 129.15.78.126 IP address > which has been set primary by peer. But it still sends data to the old ip > address 129.15.78.125. > > I found add ip and setpeerprimary operations were successful as sctp_server > gets successful asconf_ack after each > operations. I also found that sctp_client gets SCTP_PEER_ADDR_CHANGE event > with states SCTP_ADDR_ADDED and SCTP_ADDR_CONFIRMED after addip operation > by sctp_server and SCTP_ADDR_MADE_PRIM state after set_peer_primary_address > operation by sctp_server. Hence, I guess every operations worked perfect. > > > So, is my expectation wrong in this scenario? What else should I do to make > sctp_client send data to 129.15.78.126 ip address instead of > 129.15.78.125ip address? > > I would appriciate any help in this regard. > > Best Regards, > Sazzadur Rahman, > Graduate Student, > School of computer science, > University of Oklahoma, > Norman, USA > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" > -- Randall Stewart NSSTG - Cisco Systems Inc. 803-345-0369 <or> 803-317-4952 (cell)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?46E93FC6.4080003>