Chronological Thread 

< Chronological >      < Thread >

---

Hi Michael,

the routing socket should become readable, but the address should not be incorporated into
the association sue to the address scoping, which is going on.

sorry, but I could not understand your reply. Could you elaborate more please. You are saying that since the assoc. starts with local addresses, the private ip address is not added into the association ?


Thanks,
ilknur

On May 1, 2005, at 7:09 PM, Ilknur Aydin wrote:

Hello Andreas,

I am working with sctplib1.3.1 on the add/delete ip feature. Previously, I had read the source files on how add/delete ip feature is triggered. As far as I see, a routing socket is opened by sctplib and whenever there is change (add/delete) in the routing table, sending of an asconf add/delete ip chunk is triggered.

I had run echo_server and terminal programs and by using ifconfig, I was be able to observe paths added/deleted into the association. However, these were not consistent. For I while, I worked on some other things, and later needed to go back and check add/delete ip feature again, and now, I can not observe the feature at all :(.

The configuration, I use is like in Figure-1 (of the attached .pdf file).

I try the steps 1-5 below.
---------------------------------------
1- Initially, eth0 is not active, there is only loop back address in the routing table (see below).

[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
[root@localhost programs]# ifconfig
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:585875 errors:0 dropped:0 overruns:0 frame:0
TX packets:585875 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:45330936 (43.2 Mb) TX bytes:45330936 (43.2 Mb)


2- then, I ran echo_server and terminal on the loop back address as below, and communication is established between them.

./echo_server -V -s 127.0.0.1
1 : Communication up (10 In-Streams, 10 Out-Streams, 1 Paths)
1 : Network status change notification: path 1 status is ACTIVE STATE (0)


./terminal -V -d 127.0.0.1 -s 127.0.0.1
1 : Communication up (1 paths, 10 In-Streams, 10 Out-Streams)
1 : Network status change notification: path 1 state is ACTIVE STATE (0)


3- then I activated eth0 with the ifconfig command below.

[root@localhost programs]# ifconfig eth0 up


4- the result is that eth0 is activated with the private IP address (192.168.0.158).

[root@localhost programs]# ifconfig
eth0 Link encap:Ethernet HWaddr 00:0F:1F:10:8B:96
inet addr:192.168.0.158 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:1873 errors:0 dropped:0 overruns:0 frame:0
TX packets:189 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:474075 (462.9 Kb) TX bytes:21144 (20.6 Kb)
Interrupt:11 Base address:0xe000 Memory:faffe000-fafff080

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:586221 errors:0 dropped:0 overruns:0 frame:0
TX packets:586221 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:45357419 (43.2 Mb) TX bytes:45357419 (43.2 Mb)
[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


5- However , though the routing table changes, I do not see "Network status change notification: " printed in neither echo_server nor "terminal" windows. That is, it is as if sctplib is not informed about the changes in the routing table.

Do you think that somehow the configuration in Figure-1 is not proper to observe add/delete ip feature ??

Now, I am trying to introduce a wireless interface to the laptop and try the set up like in Figure-2. Later, I will try to turn on and off the wireless interface and try to observe the add/delete ip. Do you think this set up would help observing add/delete ip feature ? Can you foresee any problems with this set up?

What kind configuration you had use while testing this feature ??

Thanks,
ilknur
<q.to.andreas.pdf>

---

• [SCTP-Discussion] sctplib1.3.1, add/delete ip, Ilknur Aydin, 05/01/2005
  • Re: [SCTP-Discussion] sctplib1.3.1, add/delete ip, Michael Tuexen, 05/01/2005
    • Re: [SCTP-Discussion] sctplib1.3.1, add/delete ip, Ilknur Aydin, 05/01/2005
      • Re: [SCTP-Discussion] sctplib1.3.1, add/delete ip, Michael Tuexen, 05/01/2005
        • Re: [SCTP-Discussion] sctplib1.3.1, add/delete ip, Ilknur Aydin, 05/01/2005
          • Re: [SCTP-Discussion] sctplib1.3.1, add/delete ip, Michael Tuexen, 05/02/2005
          • Message not available
            • Re: [SCTP-Discussion] sctplib1.3.1, add/delete ip, Ilknur Aydin, 05/04/2005

---

Archive powered by MHonArc 2.6.19+.