If you initiate an association to 127.0.0.1 you can not list or add addresses with link-local or global scope.
Hi Michael,
thanks for your replies.
I have checked the ID. May be I am not very clear with the problem explained in section 3.2 and may be we do not comply with section 3.3 and 3.4, while adding a level 3 (private IP address) in to the association; however, I do not see association being aborted.
It should only be triggered when an IP-address is added or deleted to one of the interfaces. Then SCTP filters if this address
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.
You can use private addresses. They have the same level.
Another question: if I have a set up like I mentioned in my previous email (like in Figure-2), i.e., where all the ip addresses are private (i.e., both client and server are behind the NAT) and client and server runs on separate machines. I dont think that I would cause a black-hole problem, but could I have the system work?
Thanks,
ilknur
On Sun, 1 May 2005, Michael Tuexen wrote:
Hi Ilknur,
I'm attaching the expired ID. Randy and I will update it and resubmit
it soon. It will also cover
IPv6 adresses.
Please note that it does not cover ADDIP, but the same applies to
ADDIP what is described for
the INIT/INIT-ACK.
I hope this makes things a bit clearer.
Best regards
Michael
Archive powered by MHonArc 2.6.19+.