Chronological Thread 

< Chronological >      < Thread >

---

Hi Thomas,

The problem is solved! There were two causes of the error:

1. Problem with the last line of the file "/etc/hosts".
I don't know why, but sometimes the last mapping entry line of this file
does not function. So, in this particular case, the host name of the peer
could not be resolved and this was the cause of the error reported.

2. Problem with the network card of the peer whose entry did not function in
the "/etc/hosts".
Even when the first problem was solved, the connection could not be
established, but this time due to a problem with the network card of the
same host! The ping from any other host did not work with this interface.
After opening the PC case (and doing nothing with the card :)), closing it
again, and switching the PC on, the NIC was up again. I have no explanation
for this.

As just a small comment, to my understanding, the probability of the joint
event (1 and 2 happening together) is almost zero. But, it still happened
:-).

However, thank you for the advices.

Best regards,
Marjan


----- Original Message -----
From: "Thomas Dreibholz"
<dreibh AT exp-math.uni-essen.de>
To:
<rsplib-discussion AT sctp.de>
Sent: Tuesday, February 25, 2003 5:53 AM
Subject: Re: Fw: [RSPlib-Discusssion] unsupported address family


> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Am Donnerstag, 20. Februar 2003 05:05 schrieb Marjan Bozinovski:
> > The problem is that it had worked always fine until yesterday. I really
> > hadn't done any change in the software. Moreover, I think that it also
> > showed the same error but with "unsupported address family #6". Can this
> > happen due to a hardware problem? Can a network card be the problem?
>
> I think, there is a problem with the initialization of the sockaddr_*
> structure in the program. Try to print out all data of the sockaddr*
> structure provided to the ext_connect() call directly before the call.
> Example:
> printf("sin_family = %d\n",((struct sockaddr_in*)address)->sin_family);
> where "address" is the sockaddr* pointer given to ext_connect(). Here, I
> assumed you used IPv4 (sockaddr_in). For IPv6, use sockaddr_in6,
sin6_family
> etc..
> Try also to print out the port number and the IP address itself. If all
> information given to ext_connect() is correct, we have to make some
further
> examinations. Otherwise, your program does either not correctly initialize
> the sockaddr_* structure (e.g. by leaving fields uninitalized) or some
part
> of the program overwrites the values set.
>
> I am quite sure that this problem is not caused by a hardware fault.
>
>
> Best regards
> - --
> =======================================================================
> Dipl.-Inform. Thomas Dreibholz
>
> University of Essen, Room ES210
> Inst. for Experimental Mathematics Ellernstraße 29
> Computer Networking Technology Group D-45326 Essen/Germany
> - -----------------------------------------------------------------------
> E-Mail:
> dreibh AT exp-math.uni-essen.de
> Homepage: http://www.exp-math.uni-essen.de/~dreibh
> =======================================================================
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.0.7 (GNU/Linux)
>
> iD8DBQE+WvbA32BbsHYPLWURAlJ7AKC5ff/tOaZwTfi2JkqgmuttcMTqgwCgqJqG
> Ki7qUH7otm5TodXU562bFK0=
> =pikE
> -----END PGP SIGNATURE-----
>
> _______________________________________________
> rsplib-discussion mailing list
> rsplib-discussion AT sctp.de
> http://www.sctp.de/mailman/listinfo/rsplib-discussion

---

• [RSPlib-Discusssion] unsupported address family, Marjan Bozinovski, 02/20/2003
  • Re: [RSPlib-Discusssion] unsupported address family, Thomas Dreibholz, 02/20/2003
  • <Possible follow-up(s)>
  • Fw: [RSPlib-Discusssion] unsupported address family, Marjan Bozinovski, 02/20/2003
    • Re: Fw: [RSPlib-Discusssion] unsupported address family, Thomas Dreibholz, 02/25/2003
      • Re: Fw: [RSPlib-Discusssion] unsupported address family, Marjan Bozinovski, 02/26/2003

---

Archive powered by MHonArc 2.6.19+.