SCTP Discussions

Text archives Help


Re: [SCTP-Discussion] sctplib1.3.1, add/delete ip


Chronological Thread 
  • From: Ilknur Aydin <aydin AT mail.eecis.udel.edu>
  • To: Andreas Jungmaier <ajung AT iem.uni-due.de>
  • Cc: discussion AT sctp.de, Chien-chung Shen <cshen AT mail.eecis.udel.edu>
  • Subject: Re: [SCTP-Discussion] sctplib1.3.1, add/delete ip
  • Date: Wed May 4 01:32:02 2005
  • List-id: SCTP Discussions <discussion.sctp.de>

On Mon, 2 May 2005, Andreas Jungmaier wrote:

And as far as I understand, no matter what, whenever there is a change in
the routing table, asconf should at least be triggered in the sctplib. But
it seems, triggering is not happening.

That indeed is not so: ASCONF is triggered only if addresses
are added/removed, *not* when the routing table changes (as that
does not "interest" SCTP - SCTP assumes that routing works somehow).


My understanding from the source file, the way an asconf chunk is sent is as follows:

dispatch_event() --calls-->
adl_treat_routing_socket_event() when EVENTTCB_TYPE_ROUTING --calls-->
adl_SendLocalAddressChangeToClients() --calls-->
adl_send_unix_message() with UNIX_MESSAGE_SCTP_LOCAL_ADDRESS_CHANGE --calls->
mdi_localAddressChange() --calls-->
asc_addIP() or asc_deleteIP: asconf chunk is sent to the peer

Initially, the routing table has one entry:

[root@localhost programs]# route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
127.0.0.0 * 255.0.0.0 U 0 0 0 lo

After activating the eth0 with ifconfig, there is another entry in the routing table:

[root@localhost programs]# route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.0.0 * 255.255.255.0 U 0 0 0 eth0
127.0.0.0 * 255.0.0.0 U 0 0 0 lo

This change is an ADD, right ?

This should cause dispatch_event() to call adl_treat_routing_socket_event(). This does not happen in the first place. What do you think the reason could be?


Thanks,
ilknur





Archive powered by MHonArc 2.6.19+.

Top of page