Error: failed to create socket

[Charles Trois]

le 6/09/03 19:25, yellowdog-general-request@lists.terrasoftsolutions.com =E0
yellowdog-general-request@lists.terrasoftsolutions.com a =E9crit=A0:

>=20
> Message: 5
> Date: Sat, 6 Sep 2003 01:45:07 -0400
> From: Bill Fink <billfink@mindspring.com>
> To: YellowDog Linux General <yellowdog-general@lists.terrasoftsolutions.c=
om>
> Cc: Bill Fink <billfink@mindspring.com>
> Subject: Re: Error: failed to create socket
> Reply-To: yellowdog-general@lists.terrasoftsolutions.com
>=20
> Hi Charles,
> =20
> This problem sounded familiar.  I believe I've encountered something
> similar with a different application.
>=20
> I downloaded speedbundle-1.0.tar.gz, unpacked it and searched for
> the string "failed to create socket":
>=20
> gwiz% grep -r 'failed to create socket' speedbundle-1.0
> speedbundle-1.0/ppp/pppd/plugins/pppoatm.c:             fatal("failed to
> create socket: %m");
>=20
> I then edited the pppoatm.c file and searched again for the string
> "failed to create socket".  This was the relevant section of code:
>=20
> fd =3D socket(AF_ATMPVC, SOCK_DGRAM, 0);
> if (fd < 0)
> fatal("failed to create socket: %m");
>=20
> The last argument to socket() is the protocol.  It used to be OK to
> just pass a 0 for the protocol argument, but the kernel is now more
> strict about this.  A value of 0 for protocol is actually PF_UNSPEC
> or protocol family unspecified.
>=20
> I believe it should be sufficient to just change the protocol argument
> of 0 to PF_ATMPVC.
> =20

Alas no; still the same error. Any further ideas?

Charles