Le sam, 16 sep 2000, P. Damien a �crit :
> Bonjour.
> Utilisateur d'une distribution """"concurente""" de Mandrake j'ai apr�s
> avoir lu tant d'�loges sur la Mandrake de la tester.
> Mon premier probl�me:
> Je n'arrive pas � me conect� � mon provider.
> J'ai configurer Kppp � l'identique que sur ma Suse mais j'obtiens, quand je
> tente de me conect� :
>
> Sep 11 22:28:23 linux_mandrake pppd[7666]: pppd 2.3.11 started by root, uid
> 0
> Sep 11 22:28:23 linux_mandrake pppd[7666]: Using interface ppp0
> Sep 11 22:28:23 linux_mandrake pppd[7666]: Connect: ppp0 <--> /dev/ttyS0
> Sep 11 22:28:26 linux_mandrake pppd[7666]: Remote message: Login Succeeded
> Sep 11 22:28:26 linux_mandrake pppd[7666]: Peer is not authorized to use
remote address 212.147.20.195 ^^^^^^^^^^^^^^^^^^^^^^^^^^
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
extrait de man pppd:
SECURITY
pppd provides system administrators with sufficient access
control that PPP access to a server machine can be pro�
vided to legitimate users without fear of compromising the
security of the server or the network it's on. This con�
trol is provided through restrictions on which IP
addresses the peer may use, based on its authenticated
identity (if any), and through restrictions on which
options a non-privileged user may use. Several of pppd's
options are privileged, in particular those which permit
potentially insecure configurations; these options are
only accepted in files which are under the control of the
system administrator, or if pppd is being run by root.
The default behaviour of pppd is to allow an unauthenti�
cated peer to use a given IP address only if the system
does not already have a route to that IP address. For
example, a system with a permanent connection to the wider
internet will normally have a default route, and thus all
peers will have to authenticate themselves in order to set
up a connection.
etc..........
Le probl�me se situe peut-�tre de ce c�t�?
--
Amicalement,
Andr� Sala�n.
