Chronological Thread 

< Chronological >      < Thread >

---

Hi Michael,

> >Ahh... I kinda guessed that was the issue, and tried to do this on 2
> >machines, and got into another problem... I discovered that
> if I specify the
> >server address to be: 127.0.0.1, the programs (any pair) behave
> >differently... but if I specify the actual server address to
> be somewhat
> >reasonable, all works! This is why it didn't work on 2
> machines for me
> >initially.
> >
> >My question now would be, shouldn't the SCTP library translates the
> >127.0.0.1 to its real net address before sending packets to
> the client and
> >vice versa (well, really the client is another running server)??
> What is the "real net address"? This is a difficult question,
> especially
> if IPv6 comes into the game ...
hmm... well, the host IP address, but *not* the loopback address. I'm not
familiar with IPv6 at all, so cannot comment on that one. :( I would assume
that there is a unique IP address (be it v6 or not) that can uniquely
identify the host machine...

> Maybe it would be good for the demo applications that if you use no
> -s parameters all possible ip addresses would be used. Something which
> has nothing to do with the sctp stuff.
Or to have the demo server to check to see if there is a loopback address
specified? Or, should this be done in the SCTP library? Just that I can see
people using 127.0.0.1 as server address without realizing the consequences
of it.

---

• RE: Re(2): [SCTP-Discussion] appropriate usage of echo_server/ech o_clien t and discard_server/t erminal demo programs, Yiwen Jiang, 04/03/2001
  • Re: Re(2): [SCTP-Discussion] appropriate usage of echo_server/ech o_clien t and discard_server/t erminal demo programs, Andreas Jungmaier, 04/04/2001

---

Archive powered by MHonArc 2.6.19+.