| View previous topic :: View next topic |
| Author |
Message |
Tony Clifton
l33t
Joined: 07 Jul 2004
Posts: 686
Location: Rennes
|
 Posted: Mon Nov 08, 2004 11:53 pm Post subject: [PPPD] Configuration d'un sagem fast 800 (résolu) |
 |
|
Je suis en train de configurer le pc d'un pote qui a un modem sagem fast 800. J'ai donc installé le driver eagle-usb en utilisant la doc dispo sur le wiki (http://fr.gentoo-wiki.com/HOWTO_Installer_les_drivers_pour_modem_eagle-usb).
Mais je n'arrive tout de même pas à activer la connexion, j'obtient le message suivant :
| Code: | # /etc/init.d/eagle-usb start
* Starting eagle-usb ...... [ ok ]
* Loading firmware, DSP and trying to sync ... [ ok ]
* Launching PPP daemon ...
* Failed to start pppd daemon. [ !! ] |
J'ai une connexion wanadoo adsl (que j'utilise habituellement en pppoe) et j'utilise le noyau 2.6.7-r11 compilé avec genkernel
Last edited by Tony Clifton on Tue Nov 09, 2004 12:17 pm; edited 1 time in total |
|
| Back to top |
|
 |
befa
Apprentice
Joined: 28 Oct 2004
Posts: 208
Location: rennes
|
| Posted: Tue Nov 09, 2004 1:16 am Post subject: |
|
|
sans doute une question con....mais tu es alle verifier dans | Code: | | /etc/ppp/pap-secrets |
que tes identifiants sont les bons?
_________________
Open Minds! Open Sources! Open Future!
think_tux@jabber.org |
|
| Back to top |
|
|
Sleeper
l33t
Joined: 12 Nov 2002
Posts: 667
|
| Posted: Tue Nov 09, 2004 7:59 am Post subject: |
|
|
| Tu peux aussi regarder si tu n'as pas de message dans ton /var/log/syslog indiquant une erreur d'authentification .. |
|
| Back to top |
|
|
Tony Clifton
l33t
Joined: 07 Jul 2004
Posts: 686
Location: Rennes
|
| Posted: Tue Nov 09, 2004 10:34 am Post subject: |
|
|
Pour mon pap-secret j'ai mis un truc comme ça :
| Code: | # cat /etc/ppp/chap-secrets
"fti/xxxxxxx" MyPeer "xxxxxxx" |
Je vais essayer de voir avec le log ce que ça me donne. |
|
| Back to top |
|
|
Tony Clifton
l33t
Joined: 07 Jul 2004
Posts: 686
Location: Rennes
|
| Posted: Tue Nov 09, 2004 10:46 am Post subject: |
|
|
Et dans mon log j'ai ça :
| Code: | Nov 9 11:36:43 localhost kernel: [eagle-usb] driver V2 loaded
Nov 9 11:36:43 localhost kernel: [eagle-usb] New USB ADSL device detected, waiting for DSP code...
Nov 9 11:36:43 localhost kernel: [eagle-usb] Interface 0 accepted.
Nov 9 11:36:43 localhost kernel: [eagle-usb] created proc entry at : /proc/driver/eagle-usb/001-002
Nov 9 11:36:43 localhost kernel: usbcore: registered new driver eagle-usb
Nov 9 11:37:35 localhost kernel: [eagle-usb] ioctl EU_IO_OPTIONS received
Nov 9 11:37:36 localhost kernel: [eagle-usb] ioctl EU_IO_DSP received
Nov 9 11:37:36 localhost kernel: [eagle-usb] Loading DSP code to device...
Nov 9 11:37:36 localhost kernel: [eagle-usb] DSP code successfully loaded to device
Nov 9 11:37:52 localhost kernel: [eagle-usb] Modem operational !!
Nov 9 11:37:52 localhost kernel: [eagle-usb] Ethernet device eth1 created.
Nov 9 11:37:52 localhost eagle-usb: Using synchro timeout: 120
Nov 9 11:37:52 localhost eagle-usb: Sending options to device /proc/bus/usb/001/002
Nov 9 11:37:52 localhost eagle-usb: Options successfully sent to driver.
Nov 9 11:37:52 localhost eagle-usb: Sending DSP code to device /proc/bus/usb/001/002
Nov 9 11:37:52 localhost eagle-usb: Using DSP code for POTS line
Nov 9 11:37:52 localhost eagle-usb: DSP code successfully loaded.
Nov 9 11:37:52 localhost eagle-usb: Waiting for synchro...
Nov 9 11:37:52 localhost eagle-usb: OK .. Modem is synchronized.
Nov 9 11:37:52 localhost net.agent[7687]: add event not handled
Nov 9 11:37:53 localhost eagle-usb: Starting Link eagle
Nov 9 11:37:53 localhost pppd[7702]: pppd 2.4.1 started by root, uid 0
Nov 9 11:37:53 localhost pppd[7702]: Using interface ppp0
Nov 9 11:37:53 localhost pppd[7702]: Connect: ppp0 <--> /dev/pts/0
Nov 9 11:37:54 localhost eagle-usb: Waiting for link eagle (ppp0) to start: 1 of 160
Nov 9 11:37:55 localhost eagle-usb: Waiting for link eagle (ppp0) to start: 2 of 160
Nov 9 11:37:56 localhost eagle-usb: Waiting for link eagle (ppp0) to start: 3 of 160
Nov 9 11:37:57 localhost eagle-usb: Waiting for link eagle (ppp0) to start: 4 of 160
Nov 9 11:37:58 localhost eagle-usb: Waiting for link eagle (ppp0) to start: 5 of 160
Nov 9 11:37:59 localhost eagle-usb: Waiting for link eagle (ppp0) to start: 6 of 160 |
Je trouve bizare qu'il me créée une interface eth1 (avec comme @IP 192.168.60.30) alors qu'il devrait créer une interface ppp0 (enfin je pense). |
|
| Back to top |
|
|
mic006fr
Tux's lil' helper
Joined: 16 Sep 2004
Posts: 135
Location: FRANCE - Toulouse
|
| Posted: Tue Nov 09, 2004 10:54 am Post subject: |
|
|
le eth1 est normal, c'est une interface virtuelle vers ppp0
dans mon chap-secrets, j'ai
| Code: | | <login> * <motdepasse> * |
et pareil dans le pap-secrets
Sinon le modem se synchronise bien ? Le voyant ADSL est fixe ? |
|
| Back to top |
|
|
Tony Clifton
l33t
Joined: 07 Jul 2004
Posts: 686
Location: Rennes
|
| Posted: Tue Nov 09, 2004 11:17 am Post subject: |
|
|
J'ai modifié les fichiers pap-secrets et chap-secrets en mettant :
| Code: | | <login> fti/xxxxxxx <passwd> xxxxxxx |
Mais j'obtiens toujours "Waiting for link eagle (ppp0) to start: xxx of 160"
Sinon le modem synchronise bien, la led ne clignote pas. |
|
| Back to top |
|
|
Sleeper
l33t
Joined: 12 Nov 2002
Posts: 667
|
| Posted: Tue Nov 09, 2004 11:55 am Post subject: |
|
|
1) Essaie sans le fti/xxxx mais avec des *
2) ajoute "debug" aux options pppd (dans /etc/ppp/peers/dsl.peer de tete) |
|
| Back to top |
|
|
Tony Clifton
l33t
Joined: 07 Jul 2004
Posts: 686
Location: Rennes
|
| Posted: Tue Nov 09, 2004 12:16 pm Post subject: |
|
|
Ah c'est bon ça marche, merci.
c'était bien le pap-secrets et le chap-secrets. |
|
| Back to top |
|
|
maciunio
n00b
Joined: 09 Dec 2004
Posts: 7
Location: Poland
|
| Posted: Mon Dec 13, 2004 7:45 am Post subject: Modem is synchronised but no connection :( |
|
|
Hi,
I have the same situation with eagle-usb 2.0.0.
My login and password are correct in both files /etc/ppp/pap-secrets and .../chap-secrets.
Any ideas? |
|
| Back to top |
|
|
Sleeper
l33t
Joined: 12 Nov 2002
Posts: 667
|
| Posted: Mon Dec 13, 2004 10:56 am Post subject: |
|
|
| No trace in syslog ?? Try also enabling debugging options of ppd and to see if this produces traces in syslog file .. |
|
| Back to top |
|
|
maciunio
n00b
Joined: 09 Dec 2004
Posts: 7
Location: Poland
|
| Posted: Mon Dec 13, 2004 5:46 pm Post subject: |
|
|
Yes of course I have some trace:
| Quote: |
Dec 13 17:55:22 domek pppd[14846]: pppd 2.4.3 started by root, uid 0
Dec 13 17:55:22 domek pppd[14846]: Using interface ppp0
Dec 13 17:55:22 domek pppd[14846]: Connect: ppp0 <--> /dev/pts/3
Dec 13 17:55:53 domek pppd[14846]: LCP: timeout sending Config-Requests
Dec 13 17:55:53 domek pppd[14846]: Connection terminated.
Dec 13 17:55:53 domek pppd[14846]: Using interface ppp0
Dec 13 17:55:53 domek pppd[14846]: Connect: ppp0 <--> /dev/pts/4
Dec 13 17:55:54 domek pppoa[14847]: Packet not from driver (mac: 00:60:4C:15:F2:3D)
Dec 13 17:55:57 domek pppoa[14847]: Packet not from driver (mac: 00:60:4C:15:F2:3D)
Dec 13 17:55:58 domek pppd[14846]: tcflush failed: Bad file descriptor
Dec 13 17:55:58 domek pppd[14846]: Exit.
Dec 13 17:55:58 domek pppoa[14917]: read (AsyncReadFromPPP): Input/output error
Dec 13 17:55:58 domek pppoa[14847]: read (AsyncReadFromPPP): Input/output error
|
but 2 minutes later after 'stopadsl' and startadsl':
| Quote: | Dec 13 17:57:05 domek pppd[15204]: pppd 2.4.3 started by root, uid 0
Dec 13 17:57:05 domek pppd[15204]: Using interface ppp0
Dec 13 17:57:05 domek pppd[15204]: Connect: ppp0 <--> /dev/pts/3
Dec 13 17:57:21 domek pppd[15204]: CHAP authentication succeeded
Dec 13 17:57:21 domek pppd[15204]: local IP address 83.31.176.241
Dec 13 17:57:21 domek pppd[15204]: remote IP address 213.25.2.3
Dec 13 17:57:21 domek pppd[15204]: primary DNS address 194.204.152.34
Dec 13 17:57:21 domek pppd[15204]: secondary DNS address 217.98.63.164
|
and few minutes later:
| Quote: |
Dec 13 18:05:26 domek pppd[15268]: Terminating on signal 15
Dec 13 18:05:26 domek pppd[15268]: Connect time 8.1 minutes.
Dec 13 18:05:26 domek pppd[15268]: Sent 6129090 bytes, received 17289596 bytes.
Dec 13 18:05:27 domek pppd[15268]: Connection terminated.
Dec 13 18:05:31 domek pppoa[15205]: read (AsyncReadFromPPP): Input/output error
Dec 13 18:05:35 domek pppd[23378]: pppd 2.4.2 started by root, uid 0
Dec 13 18:05:35 domek pppd[23378]: Using interface ppp0
Dec 13 18:05:35 domek pppd[23378]: Connect: ppp0 <--> /dev/pts/3
Dec 13 18:05:39 domek pppd[23378]: CHAP authentication succeeded
Dec 13 18:05:40 domek pppd[23378]: local IP address 83.31.130.98
Dec 13 18:05:40 domek pppd[23378]: remote IP address 213.25.2.3
Dec 13 18:05:40 domek pppd[23378]: primary DNS address 194.204.152.34
Dec 13 18:05:40 domek pppd[23378]: secondary DNS address 217.98.63.164
|
And yesterday's log:
| Quote: |
Dec 12 11:03:21 domek pppd[12704]: pppd 2.4.3 started by root, uid 0
Dec 12 11:03:21 domek pppd[12704]: Using interface ppp0
Dec 12 11:03:21 domek pppd[12704]: Connect: ppp0 <--> /dev/pts/2
Dec 12 11:03:22 domek eagle-usb: Waiting for link eagle (ppp0) to start: 1 of 160
......
Dec 12 11:03:51 domek eagle-usb: Waiting for link eagle (ppp0) to start: 29 of 160
Dec 12 11:03:52 domek eagle-usb: Waiting for link eagle (ppp0) to start: 30 of 160
Dec 12 11:03:52 domek pppd[12704]: LCP: timeout sending Config-Requests
Dec 12 11:03:52 domek pppd[12704]: Connection terminated.
Dec 12 11:03:52 domek pppd[12704]: Using interface ppp0
Dec 12 11:03:52 domek pppd[12704]: Connect: ppp0 <--> /dev/pts/3
Dec 12 11:03:53 domek eagle-usb: Waiting for link eagle (ppp0) to start: 31 of 160
Dec 12 11:03:53 domek pppoa[12707]: Packet not from driver (mac: 00:60:4C:15:F2:3D)
Dec 12 11:03:54 domek eagle-usb: Waiting for link eagle (ppp0) to start: 32 of 160
Dec 12 11:03:55 domek eagle-usb: Waiting for link eagle (ppp0) to start: 33 of 160
Dec 12 11:03:56 domek eagle-usb: Waiting for link eagle (ppp0) to start: 34 of 160
Dec 12 11:03:56 domek pppoa[12707]: Packet not from driver (mac: 00:60:4C:15:F2:3D)
Dec 12 11:03:57 domek eagle-usb: Waiting for link eagle (ppp0) to start: 35 of 160
Dec 12 11:03:57 domek pppd[12704]: tcflush failed: Bad file descriptor
Dec 12 11:03:58 domek pppoa[12933]: read (AsyncReadFromPPP): Input/output error
Dec 12 11:03:58 domek pppd[12704]: Exit.
Dec 12 11:03:58 domek pppoa[12707]: read (AsyncReadFromPPP): Input/output error
Dec 12 11:03:58 domek eagle-usb: Waiting for link eagle () to start: 36 of 160
Dec 12 11:03:59 domek eagle-usb: Waiting for link eagle () to start: 37 of 160
....
Dec 12 11:06:04 domek eagle-usb: Waiting for link eagle () to start: 161 of 160
Dec 12 11:06:04 domek eagle-usb: Link eagle () failed to start
Dec 12 11:06:04 domek rc-scripts: Failed to start pppd daemon.
|
I have this stuff for long time (about month) and have lost any concept. |
|
| Back to top |
|
|
maciunio
n00b
Joined: 09 Dec 2004
Posts: 7
Location: Poland
|
| Posted: Wed Dec 15, 2004 5:05 pm Post subject: more... |
|
|
| i've reemerged ppp, dhcp and eagle-usb. but it didnt help. |
|
| Back to top |
|
|
Sleeper
l33t
Joined: 12 Nov 2002
Posts: 667
|
| Posted: Fri Dec 17, 2004 8:29 pm Post subject: |
|
|
Wow .. Seems strange .. Never seen the first error (tcflush failed: Bad file descriptor ) ..
Concerning the other ones: it seems that for some reason the pppd daeimon has been terminating (signal 15 is SIGTERM).
And then again this tcflush problem... Do you have any "exotic" things on your network, like IPv6/GRE/..etc.. ? |
|
| Back to top |
|
|
maciunio
n00b
Joined: 09 Dec 2004
Posts: 7
Location: Poland
|
| Posted: Tue Dec 21, 2004 6:48 am Post subject: sadly. |
|
|
| nope. nothing exotic or strange. just iptables, ipv4, shorewall. i have noticed that it happens with the regularity of IP changes from my isp. before that 'error' my ip changed 3-4 times a day, and this stuff happens... 3-4 times a day. the worst thing is that between those 'errors' all works fine! and then... bum, no connection and problems with raising it up. reboot usually helps. |
|
| Back to top |
|
|
Sleeper
l33t
Joined: 12 Nov 2002
Posts: 667
|
| Posted: Tue Dec 21, 2004 8:57 am Post subject: Re: sadly. |
|
|
| maciunio wrote: | | nope. nothing exotic or strange. just iptables, ipv4, shorewall. i have noticed that it happens with the regularity of IP changes from my isp. before that 'error' my ip changed 3-4 times a day, and this stuff happens... 3-4 times a day. the worst thing is that between those 'errors' all works fine! and then... bum, no connection and problems with raising it up. reboot usually helps. |
OK.. that can be a clue ... You definitely should post your problem on our ML (in english, there's no problem ...), in case someone else as an idea ...
https://gna.org/mail/?group=eagleusb |
|
| Back to top |
|
|
maciunio
n00b
Joined: 09 Dec 2004
Posts: 7
Location: Poland
|
| Posted: Tue Dec 21, 2004 3:55 pm Post subject: ok |
|
|
| I have just posted there. We will see what happens... |
|
| Back to top |
|
|
|
French
