Index du Forum

 
 FAQFAQ   RechercherRechercher   Liste des MembresListe des Membres   Groupes d'utilisateursGroupes d'utilisateurs   S'enregistrerS'enregistrer 
 ProfilProfil   Se connecter pour vérifier ses messages privésSe connecter pour vérifier ses messages privés   ConnexionConnexion 

Fonction syslog ou Journal des évènements

Aller à la page Précédente  1, 2, 3  Suivante
 
Poster un nouveau sujet   Répondre au sujet    Accueil du site -> Index du Forum -> Configuration CI Box & Autres
Voir le sujet précédent :: Voir le sujet suivant  
Auteur Message
Clarita
Membre indispensable
Membre indispensable


Inscrit le: 20 Juin 2005
Messages: 3138
Localisation: Auvergne

MessagePosté le: Sam 28 Oct 2006 pm 20:06    Sujet du message: Répondre en citant

Ok Very Happy
je continue
@+

_________________
Club Internet, ND, ADSL2+ <24Mega + VoIP CI-Box: 1104/20955
Ligne: dist 560m, aff 6,94. Grenouille: dl 1578Ko/s, ul 108Ko/s, ping 36ms
XP home SP2 et Vista Premium.
Revenir en haut de page
Voir le profil de l'utilisateur Envoyer un message privé Yahoo Messenger MSN Messenger
fomy
Membre indispensable
Membre indispensable


Inscrit le: 24 Oct 2005
Messages: 1785
Localisation: CLICHY 92

MessagePosté le: Sam 28 Oct 2006 pm 20:35    Sujet du message: Répondre en citant

hum je viens de comprendre qu'on parlait pas de la meme chose Embarassed
_________________
DT - ADSL2+ - DsLam PER92 - Ligne 1748 mètres(4/10 sur 842m, 5/10 sur 906m) - Ci-BOX synchro : 11406 / 832 - TV Thomson
Revenir en haut de page
Voir le profil de l'utilisateur Envoyer un message privé MSN Messenger
Clarita
Membre indispensable
Membre indispensable


Inscrit le: 20 Juin 2005
Messages: 3138
Localisation: Auvergne

MessagePosté le: Sam 28 Oct 2006 pm 20:44    Sujet du message: Répondre en citant

si si on parle bien de la même chose Smile
sauf que des fois le pachyderme est difficile à décodé Wink

_________________
Club Internet, ND, ADSL2+ <24Mega + VoIP CI-Box: 1104/20955
Ligne: dist 560m, aff 6,94. Grenouille: dl 1578Ko/s, ul 108Ko/s, ping 36ms
XP home SP2 et Vista Premium.
Revenir en haut de page
Voir le profil de l'utilisateur Envoyer un message privé Yahoo Messenger MSN Messenger
Dumboton
Membre indispensable
Membre indispensable


Inscrit le: 20 Juin 2005
Messages: 10316
Localisation: 95170

MessagePosté le: Sam 28 Oct 2006 pm 21:02    Sujet du message: Répondre en citant

où il ne comprend pas le problème Cool
_________________

CI c'était des hommes, un service et de la qualité
Revenir en haut de page
Voir le profil de l'utilisateur Envoyer un message privé Envoyer un e-mail
Clarita
Membre indispensable
Membre indispensable


Inscrit le: 20 Juin 2005
Messages: 3138
Localisation: Auvergne

MessagePosté le: Sam 28 Oct 2006 pm 22:35    Sujet du message: Répondre en citant

Voilà pour ce soir à 23H11

Log effacée pour ma sécurité Wink

_________________
Club Internet, ND, ADSL2+ <24Mega + VoIP CI-Box: 1104/20955
Ligne: dist 560m, aff 6,94. Grenouille: dl 1578Ko/s, ul 108Ko/s, ping 36ms
XP home SP2 et Vista Premium.


Dernière édition par Clarita le Sam 28 Oct 2006 pm 22:52; édité 1 fois
Revenir en haut de page
Voir le profil de l'utilisateur Envoyer un message privé Yahoo Messenger MSN Messenger
Dumboton
Membre indispensable
Membre indispensable


Inscrit le: 20 Juin 2005
Messages: 10316
Localisation: 95170

MessagePosté le: Sam 28 Oct 2006 pm 22:50    Sujet du message: Répondre en citant

Il s'agit d'une reconnexion, le log que tu montres est équivalent à un reboot.
Donc pas étonnant le clic-clac.
Attention tu nous exposes ton IP trop souvent (intrusion) et celle de ton dslam (gw).

effaces le log c'est plus sur.

Il y a forcément coupure
entre ppp down et ppp up (receive a valid ip) mais elle est très courte.
_________________

CI c'était des hommes, un service et de la qualité
Revenir en haut de page
Voir le profil de l'utilisateur Envoyer un message privé Envoyer un e-mail
Clarita
Membre indispensable
Membre indispensable


Inscrit le: 20 Juin 2005
Messages: 3138
Localisation: Auvergne

MessagePosté le: Sam 28 Oct 2006 pm 22:55    Sujet du message: Répondre en citant

Ok, mais à part cette micro déconnexion, que je n'ai même pas ressenti,
il ne dit rien, ni d'où cela provient?

_________________
Club Internet, ND, ADSL2+ <24Mega + VoIP CI-Box: 1104/20955
Ligne: dist 560m, aff 6,94. Grenouille: dl 1578Ko/s, ul 108Ko/s, ping 36ms
XP home SP2 et Vista Premium.
Revenir en haut de page
Voir le profil de l'utilisateur Envoyer un message privé Yahoo Messenger MSN Messenger
Quo Vadis
Membre habitué
Membre habitué


Inscrit le: 11 Oct 2005
Messages: 69

MessagePosté le: Sam 28 Oct 2006 pm 23:20    Sujet du message: Répondre en citant

as tu vérifié le débit de synchro dans le modem avant et après ?


typique sur ce modem le reboot pour se resynchroniser.

Je suppose que ça doit lui arriver a un autre moment de la journée, quand le débit de synchro varie encrore une fois.

Les micros pertes de synchro ne se voient pas forcément avec la diode adsl.

Donc, marge de bruit et débit de synchro avant et après serait une bonne info.
Revenir en haut de page
Voir le profil de l'utilisateur Envoyer un message privé
Clarita
Membre indispensable
Membre indispensable


Inscrit le: 20 Juin 2005
Messages: 3138
Localisation: Auvergne

MessagePosté le: Sam 28 Oct 2006 pm 23:50    Sujet du message: Répondre en citant

Oui, j'ai même fait des prises d'écran (à 23h02 et 23h15)
les débits, la synchro, tout est identique!

_________________
Club Internet, ND, ADSL2+ <24Mega + VoIP CI-Box: 1104/20955
Ligne: dist 560m, aff 6,94. Grenouille: dl 1578Ko/s, ul 108Ko/s, ping 36ms
XP home SP2 et Vista Premium.
Revenir en haut de page
Voir le profil de l'utilisateur Envoyer un message privé Yahoo Messenger MSN Messenger
Quo Vadis
Membre habitué
Membre habitué


Inscrit le: 11 Oct 2005
Messages: 69

MessagePosté le: Dim 29 Oct 2006 am 08:15    Sujet du message: Répondre en citant

interessant, si le modem reboot et retrouve les memes valeurs de synchro.

Pour s'assurer que ça n'a rien a voir avec la coupure Ft (ce qui est très improbable), reboot ton modem dans la journée, comme elle se produit toutes les 24 heures la déco devrait changer de moment.

Avant de rebooter verifie aussi les valeurs de synchro pour voir si a ce moment là aussi il retrouve les memes valeurs après.
Revenir en haut de page
Voir le profil de l'utilisateur Envoyer un message privé
Dumboton
Membre indispensable
Membre indispensable


Inscrit le: 20 Juin 2005
Messages: 10316
Localisation: 95170

MessagePosté le: Dim 29 Oct 2006 am 08:22    Sujet du message: Répondre en citant

Je tentes le diable Wink
Jai fait un desynchro puis une resynchro manuellement. Voici mon log

De tête, il y a une légère différence, à savoir que tu n'avais pas adsl link down ni ensuite le renegociation (message ADSL).

Donc à mon avis il s'agit d'un renouvellement toutes les 24 de la connexion PPP.
Hypothèse à confirmer


Desynchro manuelle
<2>kernel: ADSL link down in 29-Oct 8:5:57.88 from 192.168.1.1
<2>pppd[397]: Clear IP addresses. Connection DOWN. in 29-Oct 8:5:59.63 from 192.168.1.1
<2>pppd[397]: Clear IP addresses. PPP connection DOWN. in 29-Oct 8:5:59.63 from 192.168.1.1
Resynchro manuelle
<4>kernel: BcmAdsl_Initialize=0xC00521C8, g_pFnNotifyCallback=0xC00665E4 in 29-Oct 8:11:40.65 from 192.168.1.1
<2>kernel: ADSL G.994 training in 29-Oct 8:11:42.16 from 192.168.1.1
<2>kernel: ADSL G.992 started in 29-Oct 8:11:47.17 from 192.168.1.1
<2>kernel: ADSL G.992 channel analysis in 29-Oct 8:11:52.18 from 192.168.1.1
<2>kernel: ADSL G.992 message exchange in 29-Oct 8:11:56.20 from 192.168.1.1
<2>kernel: ADSL link up, interleaved, us=947, ds=12319 in 29-Oct 8:11:56.35 from 192.168.1.1
<7>syslog: iptables -t nat -A PREROUTING -i br0 -d 192.168.1.1 -p udp --dport 53 -j DNAT --to 128.9.0.107 in 29-Oct 8:11:58.23 from 192.168.1.1
<7>syslog: iptables -D INPUT -p 2 -j ACCEPT 2>/dev/null in 29-Oct 8:11:58.34 from 192.168.1.1
<7>syslog: iptables -D FORWARD -d 224.0.0.0/3 -j ACCEPT 2>/dev/null in 29-Oct 8:11:58.40 from 192.168.1.1
<7>syslog: iptables -t nat -D PREROUTING -d 224.0.0.0/3 -j ACCEPT 2>/dev/null in 29-Oct 8:11:58.53 from 192.168.1.1
<7>syslog: iptables -I INPUT 1 -p 2 -j ACCEPT in 29-Oct 8:11:58.57 from 192.168.1.1
<7>syslog: iptables -I FORWARD 1 -d 224.0.0.0/3 -j ACCEPT in 29-Oct 8:11:58.73 from 192.168.1.1
<7>syslog: iptables -t nat -I PREROUTING 1 -d 224.0.0.0/3 -j ACCEPT in 29-Oct 8:11:58.88 from 192.168.1.1
<5>pppd[397]: PPP: Start to connect ... in 29-Oct 8:11:59.21 from 192.168.1.1
<5>pppd[397]: PPP: Start to connect ... in 29-Oct 8:12:12.86 from 192.168.1.1
<5>pppd[397]: PPP: Start to connect ... in 29-Oct 8:12:26.50 from 192.168.1.1
<2>pppd[397]: PPP LCP UP. in 29-Oct 8:12:28.13 from 192.168.1.1
<2>pppd[397]: Received valid IP address from server. Connection UP. in 29-Oct 8:12:28.29 from 192.168.1.1
<7>syslog: route add default gw xx.xx.xx.xx 2>/dev/null in 29-Oct 8:12:28.69 from 192.168.1.1
<7>syslog: echo > /proc/net/ip_conntrack in 29-Oct 8:12:28.93 from 192.168.1.1
<7>syslog: echo "1000" > /proc/sys/net/ipv4/ip_conntrack_max in 29-Oct 8:12:29.1 from 192.168.1.1
<7>syslog: iptables -t nat -D PREROUTING -i br0 -d 192.168.1.1 -p udp --dport 53 -j DNAT --to 128.9.0.107 2>/dev/null in 29-Oct 8:12:29.13 from 192.168.1.1
<7>syslog: iptables -t nat -D POSTROUTING -o ppp_8_35_1 -s 192.168.1.0/255.255.255.0 -j MASQUERADE 2>/dev/null in 29-Oct 8:12:29.30 from 192.168.1.1
<7>syslog: iptables -t nat -A POSTROUTING -o ppp_8_35_1 -s 192.168.1.0/255.255.255.0 -j MASQUERADE in 29-Oct 8:12:29.34 from 192.168.1.1
<7>syslog: iptables -t nat -D PREROUTING -i br0 -d 192.168.1.1 -p udp --dport 53 -j DNAT --to 194.117.200.11 2>/dev/null in 29-Oct 8:12:29.53 from 192.168.1.1
<7>syslog: iptables -t nat -A PREROUTING -i br0 -d 192.168.1.1 -p udp --dport 53 -j DNAT --to 194.117.200.11 in 29-Oct 8:12:29.65 from 192.168.1.1
<7>syslog: /bin/dnsprobe & in 29-Oct 8:12:29.81 from 192.168.1.1
<5>dnsprobe[5304]: dnsprobe started! in 29-Oct 8:12:30.10 from 192.168.1.1
<7>syslog: echo 1 > /proc/sys/net/ipv4/conf/ppp_8_35_1/rp_filter in 29-Oct 8:12:31.11 from 192.168.1.1
<7>syslog: iptables -A INPUT -p ALL -i ppp_8_35_1 -m state --state ESTABLISHED,RELATED -j ACCEPT in 29-Oct 8:12:31.28 from 192.168.1.1
<7>syslog: iptables -A FORWARD -p ALL -i ppp_8_35_1 -m state --state ESTABLISHED,RELATED -j ACCEPT in 29-Oct 8:12:31.37 from 192.168.1.1
<7>syslog: iptables -A INPUT -p tcp --dport 1863:1864 -i ppp_8_35_1 -j ACCEPT in 29-Oct 8:12:31.48 from 192.168.1.1
<7>syslog: iptables -A INPUT -p tcp --dport 4443 -i ppp_8_35_1 -j ACCEPT in 29-Oct 8:12:31.57 from 192.168.1.1
<7>syslog: iptables -A INPUT -p tcp --dport 5190 -i ppp_8_35_1 -j ACCEPT in 29-Oct 8:12:31.66 from 192.168.1.1
<7>syslog: iptables -A INPUT -p tcp --dport 5566 -i ppp_8_35_1 -j ACCEPT in 29-Oct 8:12:31.82 from 192.168.1.1
<7>syslog: iptables -A INPUT -p tcp --dport 40000:40099 -i ppp_8_35_1 -j ACCEPT in 29-Oct 8:12:31.87 from 192.168.1.1
<7>syslog: iptables -A INPUT -i ppp_8_35_1 -p tcp --syn -m limit --limit 6/h -j LOG --log-level 1 --log-prefix="Intrusion -> " in 29-Oct 8:12:32.3 from 192.168.1.1
<7>syslog: iptables -A FORWARD -i ppp_8_35_1 -p tcp --syn -m limit --limit 6/h -j LOG --log-level 1 --log-prefix="Intrusion -> " in 29-Oct 8:12:32.8 from 192.168.1.1
<7>syslog: iptables -A INPUT -i ppp_8_35_1 -j DROP in 29-Oct 8:12:32.22 from 192.168.1.1
<7>syslog: iptables -A FORWARD -i ppp_8_35_1 -j DROP in 29-Oct 8:12:32.29 from 192.168.1.1
<7>syslog: iptables -I INPUT 1 -p icmp --icmp-type echo-request -i ppp_8_35_1 -j ACCEPT in 29-Oct 8:12:32.49 from 192.168.1.1
<4>kernel: BOS: AppReset() - Signalling root task of reset. in 29-Oct 8:12:36.36 from 192.168.1.1
<4>kernel: in 29-Oct 8:12:36.37 from 192.168.1.1
<4>kernel: in 29-Oct 8:12:36.38 from 192.168.1.1
<4>kernel: BOS: bosAppRootTask() - RESET NOW (reset #3) in 29-Oct 8:12:36.39 from 192.168.1.1
<4>kernel: in 29-Oct 8:12:36.40 from 192.168.1.1
<4>kernel: BOS: Enter TaskResetNotifyAll in 29-Oct 8:12:36.41 from 192.168.1.1
<4>kernel: BOS: TaskResetNotifyAll informed and resumed task aoAP in 29-Oct 8:12:36.42 from 192.168.1.1
<4>kernel: BOS: TaskResetNotifyAll informed task 3341_ASSER in 29-Oct 8:12:36.43 from 192.168.1.1
<4>kernel: BOS: TaskResetNotifyAll informed task VRGEVPR in 29-Oct 8:12:36.44 from 192.168.1.1
<4>kernel: BOS: TaskResetNotifyAll informed task HCAS in 29-Oct 8:12:36.45 from 192.168.1.1
<4>kernel: BOS: TaskResetNotifyAll informed task HTSK in 29-Oct 8:12:36.46 from 192.168.1.1
<4>kernel: BOS: TaskResetNotifyAll informed task PSTN in 29-Oct 8:12:36.47 from 192.168.1.1
<4>kernel: BOS: 6 tasks notified of reset, waiting for acks... in 29-Oct 8:12:36.48 from 192.168.1.1
<4>kernel: in 29-Oct 8:12:36.49 from 192.168.1.1
<4>kernel: BOS: Enter TaskResetAck (task=HTSK) in 29-Oct 8:12:36.54 from 192.168.1.1
<4>kernel: BOS: Enter TaskResetAck (task=HCAS) in 29-Oct 8:12:36.55 from 192.168.1.1
<4>kernel: BOS: Enter TaskResetAck (task=aoAP) in 29-Oct 8:12:36.61 from 192.168.1.1
<4>kernel: BOS: Enter TaskProceedToShutdown 0x805dfac0 (HTSK) in 29-Oct 8:12:36.62 from 192.168.1.1
<4>kernel: BOS: TaskProceedToShutdown() signaling task (HTSK) in 29-Oct 8:12:36.63 from 192.168.1.1
<4>kernel: BOS: Exit TaskProceedToShutdown (HTSK) in 29-Oct 8:12:36.64 from 192.168.1.1
<4>kernel: BOS: Enter TaskWaitForDone - NULL waiting on task 0x805dfac0 (HTSK) in 29-Oct 8:12:36.64 from 192.168.1.1
<4>kernel: BOS: Exit TaskResetAck (task=HTSK) in 29-Oct 8:12:36.65 from 192.168.1.1
<4>kernel: BOS: Enter TaskEnterShutdown (task=HTSK) in 29-Oct 8:12:36.66 from 192.168.1.1
<4>kernel: BOS: Exit TaskEnterShutdown (task=HTSK) in 29-Oct 8:12:36.67 from 192.168.1.1
<4>kernel: BOS: Enter TaskEnterDone (task=HTSK) in 29-Oct 8:12:36.68 from 192.168.1.1
<4>kernel: BOS: Exit TaskEnterDone (task=HTSK) in 29-Oct 8:12:36.68 from 192.168.1.1
<4>kernel: BOS: Enter TaskResetAck (task=3341_ASSER) in 29-Oct 8:12:36.69 from 192.168.1.1
<4>kernel: BOS: Exit TaskWaitForDone - NULL done waiting on task 0x805dfac0 (HTSK) in 29-Oct 8:12:36.70 from 192.168.1.1
<4>kernel: BOS: Enter TaskProceedToShutdown 0x807021a0 (HCAS) in 29-Oct 8:12:36.71 from 192.168.1.1
<4>kernel: BOS: TaskProceedToShutdown() signaling task (HCAS) in 29-Oct 8:12:36.71 from 192.168.1.1
<4>kernel: BOS: Exit TaskProceedToShutdown (HCAS) in 29-Oct 8:12:36.77 from 192.168.1.1
<4>kernel: BOS: Enter TaskWaitForDone - NULL waiting on task 0x807021a0 (HCAS) in 29-Oct 8:12:36.78 from 192.168.1.1
<4>kernel: BOS: Exit TaskResetAck (task=HCAS) in 29-Oct 8:12:36.78 from 192.168.1.1
<4>kernel: BOS: Enter TaskEnterShutdown (task=HCAS) in 29-Oct 8:12:36.79 from 192.168.1.1
<4>kernel: BOS: Exit TaskEnterShutdown (task=HCAS) in 29-Oct 8:12:36.80 from 192.168.1.1
<4>kernel: BOS: Enter TaskEnterDone (task=HCAS) in 29-Oct 8:12:36.81 from 192.168.1.1
<4>kernel: BOS: Exit TaskEnterDone (task=HCAS) in 29-Oct 8:12:36.81 from 192.168.1.1
<4>kernel: BOS: Exit TaskWaitForDone - NULL done waiting on task 0x807021a0 (HCAS) in 29-Oct 8:12:36.82 from 192.168.1.1
<4>kernel: CAS shutdown complete! in 29-Oct 8:12:36.85 from 192.168.1.1
<4>kernel: BOS: Enter TaskProceedToShutdown 0x805df1c0 (PSTN) in 29-Oct 8:12:36.86 from 192.168.1.1
<4>kernel: BOS: TaskProceedToShutdown() signaling task (PSTN) in 29-Oct 8:12:36.87 from 192.168.1.1
<4>kernel: BOS: Exit TaskProceedToShutdown (PSTN) in 29-Oct 8:12:36.88 from 192.168.1.1
<4>kernel: BOS: Enter TaskWaitForDone - NULL waiting on task 0x805df1c0 (PSTN) in 29-Oct 8:12:36.89 from 192.168.1.1
<4>kernel: BOS: Enter TaskResetAck (task=VRGEVPR) in 29-Oct 8:12:37.45 from 192.168.1.1
<4>kernel: BOS: Enter TaskResetAck (task=PSTN) in 29-Oct 8:12:37.88 from 192.168.1.1
<4>kernel: BOS: Exit TaskResetAck (task=PSTN) in 29-Oct 8:12:37.92 from 192.168.1.1
<4>kernel: BOS: Enter TaskEnterShutdown (task=PSTN) in 29-Oct 8:12:37.93 from 192.168.1.1
<4>kernel: BOS: Exit TaskEnterShutdown (task=PSTN) in 29-Oct 8:12:37.93 from 192.168.1.1
<4>kernel: BOS: Enter TaskEnterDone (task=PSTN) in 29-Oct 8:12:37.95 from 192.168.1.1
<4>kernel: BOS: Exit TaskEnterDone (task=PSTN) in 29-Oct 8:12:37.96 from 192.168.1.1
<4>kernel: in 29-Oct 8:12:37.97 from 192.168.1.1
<4>kernel: : All 6 tasks acknowledged reset. in 29-Oct 8:12:37.98 from 192.168.1.1
<4>kernel: BOS: Exit TaskResetNotifyAll in 29-Oct 8:12:37.99 from 192.168.1.1
<4>kernel: BOS: Enter TaskProceedToShutdown 0x80bb2180 (aoAP) in 29-Oct 8:12:38.0 from 192.168.1.1
<4>kernel: BOS: TaskProceedToShutdown() signaling task (aoAP) in 29-Oct 8:12:38.1 from 192.168.1.1
<4>kernel: BOS: Exit TaskProceedToShutdown (aoAP) in 29-Oct 8:12:38.2 from 192.168.1.1
<4>kernel: BOS: Enter TaskWaitForDone - NULL waiting on task 0x80bb2180 (aoAP) in 29-Oct 8:12:38.3 from 192.168.1.1
<4>kernel: BOS: Exit TaskWaitForDone - NULL done waiting on task 0x805df1c0 (PSTN) in 29-Oct 8:12:38.4 from 192.168.1.1
<4>kernel: bosMsgQDestroy: Successfully deleted message queue at address 0x40002 in 29-Oct 8:12:38.4 from 192.168.1.1
<4>kernel: PSTN_CTL shutdown complete! in 29-Oct 8:12:38.21 from 192.168.1.1
<4>kernel: BOS: Enter TaskProceedToShutdown 0x80702620 (VRGEVPR) in 29-Oct 8:12:38.27 from 192.168.1.1
<4>kernel: BOS: TaskProceedToShutdown() signaling task (VRGEVPR) in 29-Oct 8:12:38.28 from 192.168.1.1
<4>kernel: BOS: Exit TaskProceedToShutdown (VRGEVPR) in 29-Oct 8:12:38.29 from 192.168.1.1
<4>kernel: BOS: Enter TaskWaitForDone - NULL waiting on task 0x80702620 (VRGEVPR) in 29-Oct 8:12:38.39 from 192.168.1.1
<4>kernel: BOS: Exit TaskResetAck (task=VRGEVPR) in 29-Oct 8:12:38.40 from 192.168.1.1
<4>kernel: BOS: Enter TaskEnterShutdown (task=VRGEVPR) in 29-Oct 8:12:38.41 from 192.168.1.1
<4>kernel: BOS: Exit TaskEnterShutdown (task=VRGEVPR) in 29-Oct 8:12:38.41 from 192.168.1.1
<4>kernel: BOS: Enter TaskEnterDone (task=VRGEVPR) in 29-Oct 8:12:38.42 from 192.168.1.1
<4>kernel: BOS: Exit TaskEnterDone (task=VRGEVPR) in 29-Oct 8:12:38.43 from 192.168.1.1
<4>kernel: BOS: Exit TaskResetAck (task=aoAP) in 29-Oct 8:12:38.44 from 192.168.1.1
<4>kernel: App task has entered the shutdown state, exiting main... in 29-Oct 8:12:38.45 from 192.168.1.1
<4>kernel: BOS: Enter TaskEnterShutdown (task=aoAP) in 29-Oct 8:12:38.46 from 192.168.1.1
<4>kernel: BOS: Exit TaskEnterShutdown (task=aoAP) in 29-Oct 8:12:38.47 from 192.168.1.1
<4>kernel: BOS: Enter TaskEnterDone (task=aoAP) in 29-Oct 8:12:38.47 from 192.168.1.1
<4>kernel: BOS: Exit TaskEnterDone (task=aoAP) in 29-Oct 8:12:38.48 from 192.168.1.1
<4>kernel: BOS: Exit TaskWaitForDone - NULL done waiting on task 0x80bb2180 (aoAP) in 29-Oct 8:12:38.49 from 192.168.1.1
<4>kernel: in 29-Oct 8:12:38.50 from 192.168.1.1
<4>kernel: BOS: bosAppRootTask() - Reset #3 completed, good night... in 29-Oct 8:12:38.51 from 192.168.1.1
<4>kernel: in 29-Oct 8:12:38.52 from 192.168.1.1
<4>kernel: in 29-Oct 8:12:38.52 from 192.168.1.1
<4>kernel: BOS: Exit TaskWaitForDone - NULL done waiting on task 0x80702620 (VRGEVPR) in 29-Oct 8:12:38.53 from 192.168.1.1
<4>kernel: bosMsgQDestroy: Successfully deleted message queue at address 0x38001 in 29-Oct 8:12:38.54 from 192.168.1.1
<4>kernel: VRGEVPR shutdown complete! in 29-Oct 8:12:38.55 from 192.168.1.1
<4>kernel: BOS: Enter TaskProceedToShutdown 0x80702aa0 (3341_ASSER) in 29-Oct 8:12:38.55 from 192.168.1.1
<4>kernel: BOS: TaskProceedToShutdown() signaling task (3341_ASSER) in 29-Oct 8:12:38.58 from 192.168.1.1
<4>kernel: BOS: Exit TaskProceedToShutdown (3341_ASSER) in 29-Oct 8:12:38.59 from 192.168.1.1
<4>kernel: BOS: Enter TaskWaitForDone - NULL waiting on task 0x80702aa0 (3341_ASSER) in 29-Oct 8:12:38.60 from 192.168.1.1
<4>kernel: BOS: Exit TaskResetAck (task=3341_ASSER) in 29-Oct 8:12:38.61 from 192.168.1.1
<4>kernel: BOS: Enter TaskEnterShutdown (task=3341_ASSER) in 29-Oct 8:12:38.62 from 192.168.1.1
<4>kernel: BOS: Exit TaskEnterShutdown (task=3341_ASSER) in 29-Oct 8:12:38.62 from 192.168.1.1
<4>kernel: BOS: Enter TaskEnterDone (task=3341_ASSER) in 29-Oct 8:12:38.63 from 192.168.1.1
<4>kernel: BOS: Exit TaskEnterDone (task=3341_ASSER) in 29-Oct 8:12:38.64 from 192.168.1.1
<4>kernel: BOS: Exit TaskWaitForDone - NULL done waiting on task 0x80702aa0 (3341_ASSER) in 29-Oct 8:12:38.65 from 192.168.1.1
<4>kernel: VRG endpt shutdown complete! in 29-Oct 8:12:38.66 from 192.168.1.1
<4>kernel: BOS: Enter bosStartApp in 29-Oct 8:12:44.92 from 192.168.1.1
<4>kernel: in 29-Oct 8:12:44.94 from 192.168.1.1
<4>kernel: in 29-Oct 8:12:44.95 from 192.168.1.1
<4>kernel: BOS: bosAppRootTask() - Is it morning already? Spawning app task (epoch #3)... in 29-Oct 8:12:44.96 from 192.168.1.1
<4>kernel: in 29-Oct 8:12:44.97 from 192.168.1.1
<4>kernel: BOS: Enter TaskCreate aoAP in 29-Oct 8:12:44.98 from 192.168.1.1
<4>kernel: BOS: TaskCreate - taskRessurrect aoAP in 29-Oct 8:12:44.99 from 192.168.1.1
<4>kernel: BOS: AppResetDetectionEnable() - Enabled reset detection. in 29-Oct 8:12:45.0 from 192.168.1.1
<4>kernel: bcmOsTaskCreate: in 29-Oct 8:12:45.97 from 192.168.1.1
<4>kernel: TASK NAME = aoRT in 29-Oct 8:12:45.98 from 192.168.1.1
<4>kernel: TASK_PRIORITY = 1 in 29-Oct 8:12:45.99 from 192.168.1.1
<4>kernel: BOS: Exit bosStartApp in 29-Oct 8:12:46.0 from 192.168.1.1
<4>kernel: Reseting the 3341 in 29-Oct 8:12:46.1 from 192.168.1.1
<4>kernel: voipResetGpio = 6 in 29-Oct 8:12:46.2 from 192.168.1.1
<4>kernel: PASS: mmr in 29-Oct 8:12:46.2 from 192.168.1.1
<4>kernel: PASS: chipCtl in 29-Oct 8:12:46.3 from 192.168.1.1
<4>kernel: PASS: mspi in 29-Oct 8:12:46.4 from 192.168.1.1
<4>kernel: PASS: scratchSram in 29-Oct 8:12:46.5 from 192.168.1.1
<4>kernel: PASS: apmregs in 29-Oct 8:12:46.6 from 192.168.1.1
<4>kernel: PASS: apm0 in 29-Oct 8:12:46.7 from 192.168.1.1
<4>kernel: PASS: apm1 in 29-Oct 8:12:47.30 from 192.168.1.1
<4>kernel: PASS: hvg in 29-Oct 8:12:47.31 from 192.168.1.1
<4>kernel: PASS: slic in 29-Oct 8:12:47.32 from 192.168.1.1
<4>kernel: PASS: vpm in 29-Oct 8:12:47.33 from 192.168.1.1
<4>kernel: PASS: mbox in 29-Oct 8:12:47.34 from 192.168.1.1
<4>kernel: 3341 diagnostics passed! in 29-Oct 8:12:47.35 from 192.168.1.1
<4>kernel: Reseting the 3341 in 29-Oct 8:12:47.36 from 192.168.1.1
<4>kernel: voipResetGpio = 6 in 29-Oct 8:12:47.37 from 192.168.1.1
<4>kernel: Initializing 3341 drivers in 29-Oct 8:12:47.38 from 192.168.1.1
<4>kernel: -------------- TDM DMA setup strt -------------- in 29-Oct 8:12:47.39 from 192.168.1.1
<4>kernel: SAMPLESIZE = 8 in 29-Oct 8:12:47.40 from 192.168.1.1
<4>kernel: DESCRIPTORP = 0xb7fe6300 INGRESSP = 0xb7fe6310 EGRESSP = 0xb7fe6330 in 29-Oct 8:12:47.41 from 192.168.1.1
<4>kernel: Initializing Memory: 8 (16-bit locations) in 29-Oct 8:12:47.42 from 192.168.1.1
<4>kernel: Priming TX FIFO.... in 29-Oct 8:12:47.43 from 192.168.1.1
<4>kernel: Completed TDM3341 init!!!! in 29-Oct 8:12:47.44 from 192.168.1.1
<4>kernel: MSPI driver init SUCCESSFUL in 29-Oct 8:12:47.45 from 192.168.1.1
<4>kernel: MSPI driver registers update SUCCESSFUL in 29-Oct 8:12:47.46 from 192.168.1.1
<4>kernel: BOARDHAL Enabling relays in 29-Oct 8:12:47.66 from 192.168.1.1
<4>kernel: Loading 3341 Zsp with Hausware app. in 29-Oct 8:12:47.67 from 192.168.1.1
<4>kernel: BOS: Enter TaskCreate 3341_ASSERT_IST in 29-Oct 8:12:47.68 from 192.168.1.1
<4>kernel: BOS: TaskCreate - taskRessurrect 3341_ASSERT_IST in 29-Oct 8:12:47.69 from 192.168.1.1
<4>kernel: DSP Handshake. Hausware ZSP app initialized properly. in 29-Oct 8:12:47.69 from 192.168.1.1
<4>kernel: bosMsgQCreate: Created message queue VRGEVQ at address 0x50001 in 29-Oct 8:12:47.70 from 192.168.1.1
<4>kernel: BOS: Enter TaskCreate VRGEVPR in 29-Oct 8:12:47.71 from 192.168.1.1
<4>kernel: BOS: TaskCreate - taskRessurrect VRGEVPR in 29-Oct 8:12:47.72 from 192.168.1.1
<4>kernel: BOS: Enter TaskCreate HCAS in 29-Oct 8:12:47.72 from 192.168.1.1
<4>kernel: BOS: TaskCreate - taskRessurrect HCAS in 29-Oct 8:12:47.73 from 192.168.1.1
<4>kernel: ENDPT: Creating hausware task in 29-Oct 8:12:47.74 from 192.168.1.1
<4>kernel: BOS: Enter TaskCreate HTSK in 29-Oct 8:12:47.75 from 192.168.1.1
<4>kernel: BOS: TaskCreate - taskRessurrect HTSK in 29-Oct 8:12:47.76 from 192.168.1.1
<4>kernel: DAA DBG: MSPI Hdl = 0x500 in 29-Oct 8:12:47.76 from 192.168.1.1
<4>kernel: DAA DBG: GPIO Hdl = 0xb in 29-Oct 8:12:47.77 from 192.168.1.1
<4>kernel: DAA DBG: DAA read failed!!! in 29-Oct 8:12:48.14 from 192.168.1.1
<4>kernel: DAA Device Init completed in 29-Oct 8:12:48.15 from 192.168.1.1
<4>kernel: DAA init successful in 29-Oct 8:12:48.16 from 192.168.1.1
<4>kernel: bosMsgQCreate: Created message queue PSTN_CTL_EVQ at address 0x58002 in 29-Oct 8:12:48.17 from 192.168.1.1
<4>kernel: BOS: Enter TaskCreate PSTN in 29-Oct 8:12:48.18 from 192.168.1.1
<4>kernel: BOS: TaskCreate - taskRessurrect PSTN in 29-Oct 8:12:48.19 from 192.168.1.1
<4>kernel: pstnCtlInit successful in 29-Oct 8:12:48.20 from 192.168.1.1
<4>kernel: vrgendptCreate: capabilities.endptType = 0 in 29-Oct 8:12:48.21 from 192.168.1.1
<4>kernel: ENDPT: 'HAPI_RM_OPEN_VHD_EVT' (0x80c1), hdl:0x30, op1:0x50, op2:0x1 in 29-Oct 8:12:48.22 from 192.168.1.1
<4>kernel: in 29-Oct 8:12:48.23 from 192.168.1.1
<4>kernel: ENDPT: hdspVhdOpen Primary Connection VHD success. VHD (0x50) of type: 0x0 in 29-Oct 8:12:48.24 from 192.168.1.1
<4>kernel: ENDPT: 'HAPI_RM_OPEN_VHD_EVT' (0x80c1), hdl:0x30, op1:0x51, op2:0x1 in 29-Oct 8:12:48.25 from 192.168.1.1
<4>kernel: in 29-Oct 8:12:48.31 from 192.168.1.1
<4>kernel: ENDPT: hdspVhdOpen Endpt VHD success. VHD (0x51) of type: 0x2 in 29-Oct 8:12:48.31 from 192.168.1.1
<4>kernel: ENDPT: TX Gain set to 1000 in 29-Oct 8:12:48.32 from 192.168.1.1
<4>kernel: ENDPT: RX Gain set to 1000 in 29-Oct 8:12:48.34 from 192.168.1.1
<4>kernel: ENDPT: 'HAPI_ECAN_STATE_EVT' (0x3ac0), hdl:0x0, op1:0x7, op2:0x0 in 29-Oct 8:12:48.36 from 192.168.1.1
<4>kernel: boardHalCasGetDriver: chan = 0 in 29-Oct 8:12:48.37 from 192.168.1.1
<4>kernel: Default value for provItemId '41' did not exist in 29-Oct 8:12:48.38 from 192.168.1.1
<4>kernel: ENDPT: Initialization completed successfully for endpt 0 in 29-Oct 8:12:48.41 from 192.168.1.1
<4>kernel: in 29-Oct 8:12:48.41 from 192.168.1.1
<4>kernel: vrgendptCreate: capabilities.endptType = 0 in 29-Oct 8:12:48.42 from 192.168.1.1
<4>kernel: ENDPT: 'HAPI_RM_OPEN_VHD_EVT' (0x80c1), hdl:0x30, op1:0x52, op2:0x1 in 29-Oct 8:12:48.44 from 192.168.1.1
<4>kernel: in 29-Oct 8:12:48.46 from 192.168.1.1
<4>kernel: ENDPT: hdspVhdOpen Primary Connection VHD success. VHD (0x52) of type: 0x0 in 29-Oct 8:12:48.47 from 192.168.1.1
<4>kernel: ENDPT: 'HAPI_RM_OPEN_VHD_EVT' (0x80c1), hdl:0x30, op1:0x53, op2:0x1 in 29-Oct 8:12:48.52 from 192.168.1.1
<4>kernel: in 29-Oct 8:12:48.58 from 192.168.1.1
<4>kernel: ENDPT: hdspVhdOpen Endpt VHD success. VHD (0x53) of type: 0x2 in 29-Oct 8:12:48.58 from 192.168.1.1
<4>kernel: ENDPT: TX Gain set to 1000 in 29-Oct 8:12:48.59 from 192.168.1.1
<4>kernel: ENDPT: RX Gain set to 1000 in 29-Oct 8:12:48.61 from 192.168.1.1
<4>kernel: ENDPT: 'HAPI_ECAN_STATE_EVT' (0x3ac0), hdl:0x1, op1:0x7, op2:0x0 in 29-Oct 8:12:48.62 from 192.168.1.1
<4>kernel: boardHalCasGetDriver: chan = 1 in 29-Oct 8:12:48.64 from 192.168.1.1
<4>kernel: Default value for provItemId '41' did not exist in 29-Oct 8:12:48.65 from 192.168.1.1
<4>kernel: ENDPT: Initialization completed successfully for endpt 1 in 29-Oct 8:12:48.68 from 192.168.1.1
<4>kernel: in 29-Oct 8:12:48.68 from 192.168.1.1
<4>kernel: vrgendptCreate: capabilities.endptType = 1 in 29-Oct 8:12:48.69 from 192.168.1.1
<4>kernel: ENDPT: 'HAPI_RM_OPEN_VHD_EVT' (0x80c1), hdl:0x30, op1:0x54, op2:0x1 in 29-Oct 8:12:48.71 from 192.168.1.1
<4>kernel: in 29-Oct 8:12:48.79 from 192.168.1.1
<4>kernel: ENDPT: hdspVhdOpen PSTN VHD success. VHD (0x54) of type: 0x6 in 29-Oct 8:12:48.80 from 192.168.1.1
<4>kernel: ENDPT: TX Gain set to 1000 in 29-Oct 8:12:48.80 from 192.168.1.1
<4>kernel: ENDPT: RX Gain set to 1000 in 29-Oct 8:12:48.82 from 192.168.1.1
<4>kernel: ENDPT: 'HAPI_ECAN_STATE_EVT' (0x3ac0), hdl:0x2, op1:0x7, op2:0x0 in 29-Oct 8:12:48.84 from 192.168.1.1
<4>kernel: kernel: error during endptInit in 29-Oct 8:12:48.87 from 192.168.1.1
<7>syslog: kill -SIGTERM 2640 in 29-Oct 8:12:52.88 from 192.168.1.1
<5>igmp[2640]: setsockopt- MRT_ADD_VIF in 29-Oct 8:12:52.96 from 192.168.1.1
<7>syslog: /bin/igmp qi=30 ppp_8_35_1 nas_8_36 & in 29-Oct 8:12:54.2 from 192.168.1.1
<5>igmp[5416]: igmp started! in 29-Oct 8:12:54.8 from 192.168.1.1
<5>igmp[5416]: interface xx.xx.xx.xx, UPSTREAM ver=0x16 name=ppp_8_35_1 index=17 in 29-Oct 8:13:0.9 from 192.168.1.1
<5>igmp[5416]: interface 192.168.1.1, DOWNSTREAM ver=0x16 name=br0 index=9 in 29-Oct 8:13:0.10 from 192.168.1.1

_________________

CI c'était des hommes, un service et de la qualité


Dernière édition par Dumboton le Mar 31 Oct 2006 pm 14:29; édité 1 fois
Revenir en haut de page
Voir le profil de l'utilisateur Envoyer un message privé Envoyer un e-mail
Clarita
Membre indispensable
Membre indispensable


Inscrit le: 20 Juin 2005
Messages: 3138
Localisation: Auvergne

MessagePosté le: Dim 29 Oct 2006 am 09:26    Sujet du message: Répondre en citant

Hello,
Je remets la partie du log qui correspond à "ma déconnexion" d'hier soir,
en espérant ne pas commettre d'impair,
comme ça tu peux mieux comparer.

Mais pour quoi aurais-je un renouvellement toutes les 24 de la connexion PPP?
C'est bizarre car je n'ai rien changé dans le modem.



<7> syslog: wlctl ver > /var/wlver in 28-Oct 23:9:30.70 from 192.168.1.1
<7> syslog: wlctl ver > /var/wlver in 28-Oct 23:9:53.14 from 192.168.1.1
<7> syslog: wlctl ver > /var/wlver in 28-Oct 23:10:15.54 from 192.168.1.1
<7> syslog: wlctl ver > /var/wlver in 28-Oct 23:10:37.93 from 192.168.1.1
<7> syslog: wlctl ver > /var/wlver in 28-Oct 23:11:0.32 from 192.168.1.1
<2> pppd[519]: Clear IP addresses. PPP connection DOWN. in 28-Oct 23:11:12.29 from 192.168.1.1
<5> pppd[519]: PPP: Start to connect ... in 28-Oct 23:11:18.31 from 192.168.1.1
<7> syslog: wlctl ver > /var/wlver in 28-Oct 23:11:22.81 from 192.168.1.1
<2> pppd[519]: PPP LCP UP. in 28-Oct 23:11:22.98 from 192.168.1.1
<2> pppd[519]: PPP LCP UP. in 28-Oct 23:11:23.57 from 192.168.1.1
<2> pppd[519]: Received valid IP address from server. Connection UP. in 28-Oct 23:11:23.79 from 192.168.1.1
<7> syslog: route add default gw 195.36.128.1 2>/dev/null in 28-Oct 23:11:24.1 from 192.168.1.1
<7> syslog: iptables -t nat -D POSTROUTING -o ppp_8_35_1 -s 192.168.1.0/255.255.255.0 -j MASQUERADE 2>/dev/null in 28-Oct 23:11:24.6 from 192.168.1.1
<7> syslog: iptables -t nat -A POSTROUTING -o ppp_8_35_1 -s 192.168.1.0/255.255.255.0 -j MASQUERADE in 28-Oct 23:11:24.10 from 192.168.1.1
<7> syslog: echo 1 > /proc/sys/net/ipv4/conf/ppp_8_35_1/rp_filter in 28-Oct 23:11:24.20 from 192.168.1.1
<7> syslog: iptables -A INPUT -p ALL -i ppp_8_35_1 -m state --state ESTABLISHED,RELATED -j ACCEPT in 28-Oct 23:11:24.25 from 192.168.1.1
<7> syslog: iptables -A FORWARD -p ALL -i ppp_8_35_1 -m state --state ESTABLISHED,RELATED -j ACCEPT in 28-Oct 23:11:24.29 from 192.168.1.1
<7> syslog: iptables -A INPUT -p tcp --dport 1863:1864 -i ppp_8_35_1 -j ACCEPT in 28-Oct 23:11:24.32 from 192.168.1.1
<7> syslog: iptables -A INPUT -p tcp --dport 4443 -i ppp_8_35_1 -j ACCEPT in 28-Oct 23:11:24.37 from 192.168.1.1
<7> syslog: iptables -A INPUT -p tcp --dport 5190 -i ppp_8_35_1 -j ACCEPT in 28-Oct 23:11:24.42 from 192.168.1.1
<7> syslog: iptables -A INPUT -p tcp --dport 5566 -i ppp_8_35_1 -j ACCEPT in 28-Oct 23:11:24.46 from 192.168.1.1
<7> syslog: iptables -A INPUT -p tcp --dport 40000:40099 -i ppp_8_35_1 -j ACCEPT in 28-Oct 23:11:24.53 from 192.168.1.1
<7> syslog: iptables -A INPUT -i ppp_8_35_1 -p tcp --syn -m limit --limit 6/h -j LOG --log-level 1 --log-prefix="Intrusion -> " in 28-Oct 23:11:24.56 from 192.168.1.1
<7> syslog: iptables -A FORWARD -i ppp_8_35_1 -p tcp --syn -m limit --limit 6/h -j LOG --log-level 1 --log-prefix="Intrusion -> " in 28-Oct 23:11:24.60 from 192.168.1.1
<7> syslog: iptables -A INPUT -i ppp_8_35_1 -j DROP in 28-Oct 23:11:24.65 from 192.168.1.1
<7> syslog: iptables -A FORWARD -i ppp_8_35_1 -j DROP in 28-Oct 23:11:24.70 from 192.168.1.1
<4> kernel: BOS: AppReset() - Signalling root task of reset. in 28-Oct 23:11:26.7 from 192.168.1.1
<4> kernel: in 28-Oct 23:11:26.7 from 192.168.1.1
<4> kernel: in 28-Oct 23:11:26.7 from 192.168.1.1
<4> kernel: BOS: bosAppRootTask() - RESET NOW (reset #25) in 28-Oct 23:11:26.7 from 192.168.1.1
<4> kernel: in 28-Oct 23:11:26.7 from 192.168.1.1
<4> kernel: BOS: Enter TaskResetNotifyAll in 28-Oct 23:11:26.7 from 192.168.1.1
<4> kernel: BOS: TaskResetNotifyAll informed and resumed task aoAP in 28-Oct 23:11:26.9 from 192.168.1.1
<4> kernel: BOS: TaskResetNotifyAll informed task 3341_ASSER in 28-Oct 23:11:26.9 from 192.168.1.1
<4> kernel: BOS: TaskResetNotifyAll informed task VRGEVPR in 28-Oct 23:11:26.9 from 192.168.1.1
<4> kernel: BOS: TaskResetNotifyAll informed task HCAS in 28-Oct 23:11:26.9 from 192.168.1.1
<4> kernel: BOS: TaskResetNotifyAll informed task HTSK in 28-Oct 23:11:26.9 from 192.168.1.1
<4> kernel: BOS: TaskResetNotifyAll informed task PSTN in 28-Oct 23:11:26.9 from 192.168.1.1
<4> kernel: BOS: 6 tasks notified of reset, waiting for acks... in 28-Oct 23:11:26.9 from 192.168.1.1
<4> kernel: in 28-Oct 23:11:26.9 from 192.168.1.1
<4> kernel: BOS: Enter TaskResetAck (task=HTSK) in 28-Oct 23:11:26.9 from 192.168.1.1
<4> kernel: BOS: Enter TaskResetAck (task=HCAS) in 28-Oct 23:11:26.9 from 192.168.1.1
<4> kernel: BOS: Enter TaskResetAck (task=aoAP) in 28-Oct 23:11:26.9 from 192.168.1.1
<4> kernel: BOS: Enter TaskProceedToShutdown 0x80edb1a0 (HTSK) in 28-Oct 23:11:26.14 from 192.168.1.1
<4> kernel: BOS: TaskProceedToShutdown() signaling task (HTSK) in 28-Oct 23:11:26.14 from 192.168.1.1
<4> kernel: BOS: Exit TaskProceedToShutdown (HTSK) in 28-Oct 23:11:26.14 from 192.168.1.1
<4> kernel: BOS: Enter TaskWaitForDone - NULL waiting on task 0x80edb1a0 (HTSK) in 28-Oct 23:11:26.14 from 192.168.1.1
<4> kernel: BOS: Exit TaskResetAck (task=HTSK) in 28-Oct 23:11:26.14 from 192.168.1.1
<4> kernel: BOS: Enter TaskEnterShutdown (task=HTSK) in 28-Oct 23:11:26.14 from 192.168.1.1
<4> kernel: BOS: Exit TaskEnterShutdown (task=HTSK) in 28-Oct 23:11:26.15 from 192.168.1.1
<4> kernel: BOS: Enter TaskEnterDone (task=HTSK) in 28-Oct 23:11:26.15 from 192.168.1.1
<4> kernel: BOS: Exit TaskEnterDone (task=HTSK) in 28-Oct 23:11:26.15 from 192.168.1.1
<4> kernel: BOS: Exit TaskWaitForDone - NULL done waiting on task 0x80edb1a0 (HTSK) in 28-Oct 23:11:26.26 from 192.168.1.1
<4> kernel: BOS: Enter TaskProceedToShutdown 0x80edb620 (HCAS) in 28-Oct 23:11:26.26 from 192.168.1.1
<4> kernel: BOS: TaskProceedToShutdown() signaling task (HCAS) in 28-Oct 23:11:26.26 from 192.168.1.1
<4> kernel: BOS: Exit TaskProceedToShutdown (HCAS) in 28-Oct 23:11:26.28 from 192.168.1.1
<4> kernel: BOS: Enter TaskWaitForDone - NULL waiting on task 0x80edb620 (HCAS) in 28-Oct 23:11:26.28 from 192.168.1.1
<4> kernel: BOS: Exit TaskResetAck (task=HCAS) in 28-Oct 23:11:26.28 from 192.168.1.1
<4> kernel: BOS: Enter TaskEnterShutdown (task=HCAS) in 28-Oct 23:11:26.28 from 192.168.1.1
<4> kernel: BOS: Exit TaskEnterShutdown (task=HCAS) in 28-Oct 23:11:26.28 from 192.168.1.1
<4> kernel: BOS: Enter TaskEnterDone (task=HCAS) in 28-Oct 23:11:26.28 from 192.168.1.1
<4> kernel: BOS: Exit TaskEnterDone (task=HCAS) in 28-Oct 23:11:26.28 from 192.168.1.1
<4> kernel: BOS: Exit TaskWaitForDone - NULL done waiting on task 0x80edb620 (HCAS) in 28-Oct 23:11:26.37 from 192.168.1.1
<4> kernel: CAS shutdown complete! in 28-Oct 23:11:26.37 from 192.168.1.1
<4> kernel: BOS: Enter TaskProceedToShutdown 0x80724ac0 (PSTN) in 28-Oct 23:11:26.37 from 192.168.1.1
<4> kernel: BOS: TaskProceedToShutdown() signaling task (PSTN) in 28-Oct 23:11:26.37 from 192.168.1.1
<4> kernel: BOS: Exit TaskProceedToShutdown (PSTN) in 28-Oct 23:11:26.39 from 192.168.1.1
<4> kernel: BOS: Enter TaskWaitForDone - NULL waiting on task 0x80724ac0 (PSTN) in 28-Oct 23:11:26.39 from 192.168.1.1
<4> kernel: BOS: Enter TaskResetAck (task=PSTN) in 28-Oct 23:11:26.81 from 192.168.1.1
<4> kernel: BOS: Exit TaskResetAck (task=PSTN) in 28-Oct 23:11:26.81 from 192.168.1.1
<4> kernel: BOS: Enter TaskEnterShutdown (task=PSTN) in 28-Oct 23:11:26.81 from 192.168.1.1
<4> kernel: BOS: Exit TaskEnterShutdown (task=PSTN) in 28-Oct 23:11:26.81 from 192.168.1.1
<4> kernel: BOS: Enter TaskEnterDone (task=PSTN) in 28-Oct 23:11:26.81 from 192.168.1.1
<4> kernel: BOS: Exit TaskEnterDone (task=PSTN) in 28-Oct 23:11:26.81 from 192.168.1.1
<4> kernel: BOS: Exit TaskWaitForDone - NULL done waiting on task 0x80724ac0 (PSTN) in 28-Oct 23:11:26.92 from 192.168.1.1
<4> kernel: bosMsgQDestroy: Successfully deleted message queue at address 0x250002 in 28-Oct 23:11:26.92 from 192.168.1.1
<4> kernel: PSTN_CTL shutdown complete! in 28-Oct 23:11:26.92 from 192.168.1.1
<4> kernel: BOS: Enter TaskProceedToShutdown 0x80edbaa0 (VRGEVPR) in 28-Oct 23:11:26.92 from 192.168.1.1
<4> kernel: BOS: TaskProceedToShutdown() signaling task (VRGEVPR) in 28-Oct 23:11:26.92 from 192.168.1.1
<4> kernel: BOS: Exit TaskProceedToShutdown (VRGEVPR) in 28-Oct 23:11:26.92 from 192.168.1.1
<4> kernel: BOS: Enter TaskWaitForDone - NULL waiting on task 0x80edbaa0 (VRGEVPR) in 28-Oct 23:11:26.92 from 192.168.1.1
<4> kernel: BOS: Enter TaskResetAck (task=VRGEVPR) in 28-Oct 23:11:27.10 from 192.168.1.1
<4> kernel: BOS: Exit TaskResetAck (task=VRGEVPR) in 28-Oct 23:11:27.10 from 192.168.1.1
<4> kernel: BOS: Enter TaskEnterShutdown (task=VRGEVPR) in 28-Oct 23:11:27.10 from 192.168.1.1
<4> kernel: BOS: Exit TaskEnterShutdown (task=VRGEVPR) in 28-Oct 23:11:27.10 from 192.168.1.1
<4> kernel: BOS: Enter TaskEnterDone (task=VRGEVPR) in 28-Oct 23:11:27.10 from 192.168.1.1
<4> kernel: BOS: Exit TaskEnterDone (task=VRGEVPR) in 28-Oct 23:11:27.10 from 192.168.1.1
<4> kernel: BOS: Exit TaskWaitForDone - NULL done waiting on task 0x80edbaa0 (VRGEVPR) in 28-Oct 23:11:27.15 from 192.168.1.1
<4> kernel: bosMsgQDestroy: Successfully deleted message queue at address 0x248001 in 28-Oct 23:11:27.15 from 192.168.1.1
<4> kernel: VRGEVPR shutdown complete! in 28-Oct 23:11:27.15 from 192.168.1.1
<4> kernel: BOS: Enter TaskProceedToShutdown 0x80b59180 (3341_ASSER) in 28-Oct 23:11:27.15 from 192.168.1.1
<4> kernel: BOS: TaskProceedToShutdown() signaling task (3341_ASSER) in 28-Oct 23:11:27.15 from 192.168.1.1
<4> kernel: BOS: Exit TaskProceedToShutdown (3341_ASSER) in 28-Oct 23:11:27.15 from 192.168.1.1
<4> kernel: BOS: Enter TaskWaitForDone - NULL waiting on task 0x80b59180 (3341_ASSER) in 28-Oct 23:11:27.15 from 192.168.1.1
<4> kernel: BOS: Enter TaskResetAck (task=3341_ASSER) in 28-Oct 23:11:27.42 from 192.168.1.1
<4> kernel: BOS: Exit TaskResetAck (task=3341_ASSER) in 28-Oct 23:11:27.42 from 192.168.1.1
<4> kernel: BOS: Enter TaskEnterShutdown (task=3341_ASSER) in 28-Oct 23:11:27.42 from 192.168.1.1
<4> kernel: BOS: Exit TaskEnterShutdown (task=3341_ASSER) in 28-Oct 23:11:27.42 from 192.168.1.1
<4> kernel: BOS: Enter TaskEnterDone (task=3341_ASSER) in 28-Oct 23:11:27.42 from 192.168.1.1
<4> kernel: BOS: Exit TaskEnterDone (task=3341_ASSER) in 28-Oct 23:11:27.42 from 192.168.1.1
<4> kernel: in 28-Oct 23:11:27.42 from 192.168.1.1
<4> kernel: : All 6 tasks acknowledged reset. in 28-Oct 23:11:27.42 from 192.168.1.1
<4> kernel: BOS: Exit TaskResetNotifyAll in 28-Oct 23:11:27.42 from 192.168.1.1
<4> kernel: BOS: Enter TaskProceedToShutdown 0x80b59600 (aoAP) in 28-Oct 23:11:27.42 from 192.168.1.1
<4> kernel: BOS: TaskProceedToShutdown() signaling task (aoAP) in 28-Oct 23:11:27.42 from 192.168.1.1
<4> kernel: BOS: Exit TaskProceedToShutdown (aoAP) in 28-Oct 23:11:27.42 from 192.168.1.1
<4> kernel: BOS: Enter TaskWaitForDone - NULL waiting on task 0x80b59600 (aoAP) in 28-Oct 23:11:27.42 from 192.168.1.1
<4> kernel: BOS: Exit TaskResetAck (task=aoAP) in 28-Oct 23:11:27.46 from 192.168.1.1
<4> kernel: App task has entered the shutdown state, exiting main... in 28-Oct 23:11:27.46 from 192.168.1.1
<4> kernel: BOS: Enter TaskEnterShutdown (task=aoAP) in 28-Oct 23:11:27.46 from 192.168.1.1
<4> kernel: BOS: Exit TaskEnterShutdown (task=aoAP) in 28-Oct 23:11:27.46 from 192.168.1.1
<4> kernel: BOS: Enter TaskEnterDone (task=aoAP) in 28-Oct 23:11:27.46 from 192.168.1.1
<4> kernel: BOS: Exit TaskEnterDone (task=aoAP) in 28-Oct 23:11:27.46 from 192.168.1.1
<4> kernel: BOS: Exit TaskWaitForDone - NULL done waiting on task 0x80b59180 (3341_ASSER) in 28-Oct 23:11:27.46 from 192.168.1.1
<4> kernel: BOS: Exit TaskWaitForDone - NULL done waiting on task 0x80b59600 (aoAP) in 28-Oct 23:11:27.53 from 192.168.1.1
<4> kernel: in 28-Oct 23:11:27.53 from 192.168.1.1
<4> kernel: BOS: bosAppRootTask() - Reset #25 completed, good night... in 28-Oct 23:11:27.53 from 192.168.1.1
<4> kernel: in 28-Oct 23:11:27.53 from 192.168.1.1
<4> kernel: in 28-Oct 23:11:27.53 from 192.168.1.1
<4> kernel: VRG endpt shutdown complete! in 28-Oct 23:11:27.70 from 192.168.1.1
<4> kernel: BOS: Enter bosStartApp in 28-Oct 23:11:34.25 from 192.168.1.1
<4> kernel: in 28-Oct 23:11:34.28 from 192.168.1.1
<4> kernel: in 28-Oct 23:11:34.28 from 192.168.1.1
<4> kernel: BOS: bosAppRootTask() - Is it morning already? Spawning app task (epoch #25)... in 28-Oct 23:11:34.28 from 192.168.1.1
<4> kernel: in 28-Oct 23:11:34.28 from 192.168.1.1
<4> kernel: BOS: Enter TaskCreate aoAP in 28-Oct 23:11:34.28 from 192.168.1.1
<4> kernel: BOS: TaskCreate - taskRessurrect aoAP in 28-Oct 23:11:34.28 from 192.168.1.1
<4> kernel: BOS: AppResetDetectionEnable() - Enabled reset detection. in 28-Oct 23:11:34.28 from 192.168.1.1
<4> kernel: bcmOsTaskCreate: in 28-Oct 23:11:35.35 from 192.168.1.1
<4> kernel: TASK NAME = aoRT in 28-Oct 23:11:35.37 from 192.168.1.1
<4> kernel: TASK_PRIORITY = 1 in 28-Oct 23:11:35.37 from 192.168.1.1
<4> kernel: ERROR: bosEventRegisterTask() - No free entries in TCB list in 28-Oct 23:11:35.37 from 192.168.1.1
<4> kernel: BOS: Exit bosStartApp in 28-Oct 23:11:35.37 from 192.168.1.1
<4> kernel: Reseting the 3341 in 28-Oct 23:11:35.37 from 192.168.1.1
<4> kernel: voipResetGpio = 6 in 28-Oct 23:11:35.37 from 192.168.1.1
<4> kernel: PASS: mmr in 28-Oct 23:11:35.37 from 192.168.1.1
<4> kernel: PASS: chipCtl in 28-Oct 23:11:35.37 from 192.168.1.1
<4> kernel: PASS: mspi in 28-Oct 23:11:35.37 from 192.168.1.1
<4> kernel: PASS: scratchSram in 28-Oct 23:11:35.37 from 192.168.1.1
<4> kernel: PASS: apmregs in 28-Oct 23:11:35.37 from 192.168.1.1
<4> kernel: PASS: apm0 in 28-Oct 23:11:35.39 from 192.168.1.1
<4> kernel: PASS: apm1 in 28-Oct 23:11:36.76 from 192.168.1.1
<4> kernel: PASS: hvg in 28-Oct 23:11:36.76 from 192.168.1.1
<4> kernel: PASS: slic in 28-Oct 23:11:36.76 from 192.168.1.1
<4> kernel: PASS: vpm in 28-Oct 23:11:36.76 from 192.168.1.1
<4> kernel: PASS: mbox in 28-Oct 23:11:36.76 from 192.168.1.1
<4> kernel: 3341 diagnostics passed! in 28-Oct 23:11:36.76 from 192.168.1.1
<4> kernel: Reseting the 3341 in 28-Oct 23:11:36.76 from 192.168.1.1
<4> kernel: voipResetGpio = 6 in 28-Oct 23:11:36.76 from 192.168.1.1
<4> kernel: Initializing 3341 drivers in 28-Oct 23:11:36.76 from 192.168.1.1
<4> kernel: -------------- TDM DMA setup strt -------------- in 28-Oct 23:11:36.82 from 192.168.1.1
<4> kernel: SAMPLESIZE = 8 in 28-Oct 23:11:36.82 from 192.168.1.1
<4> kernel: DESCRIPTORP = 0xb7fe6300 INGRESSP = 0xb7fe6310 EGRESSP = 0xb7fe6330 in 28-Oct 23:11:36.82 from 192.168.1.1
<4> kernel: Initializing Memory: 8 (16-bit locations) in 28-Oct 23:11:36.82 from 192.168.1.1
<4> kernel: Priming TX FIFO.... in 28-Oct 23:11:36.82 from 192.168.1.1
<4> kernel: Completed TDM3341 init!!!! in 28-Oct 23:11:36.82 from 192.168.1.1
<4> kernel: MSPI driver init SUCCESSFUL in 28-Oct 23:11:36.82 from 192.168.1.1
<4> kernel: MSPI driver registers update SUCCESSFUL in 28-Oct 23:11:36.82 from 192.168.1.1
<4> kernel: BOARDHAL Enabling relays in 28-Oct 23:11:37.14 from 192.168.1.1
<4> kernel: Loading 3341 Zsp with Hausware app. in 28-Oct 23:11:37.14 from 192.168.1.1
<4> kernel: BOS: Enter TaskCreate 3341_ASSERT_IST in 28-Oct 23:11:37.14 from 192.168.1.1
<4> kernel: BOS: TaskCreate - taskRessurrect 3341_ASSERT_IST in 28-Oct 23:11:37.14 from 192.168.1.1
<4> kernel: DSP Handshake. Hausware ZSP app initialized properly. in 28-Oct 23:11:37.14 from 192.168.1.1
<4> kernel: bosMsgQCreate: Created message queue VRGEVQ at address 0x260001 in 28-Oct 23:11:37.14 from 192.168.1.1
<4> kernel: BOS: Enter TaskCreate VRGEVPR in 28-Oct 23:11:37.14 from 192.168.1.1
<4> kernel: BOS: TaskCreate - taskRessurrect VRGEVPR in 28-Oct 23:11:37.14 from 192.168.1.1
<4> kernel: BOS: Enter TaskCreate HCAS in 28-Oct 23:11:37.14 from 192.168.1.1
<4> kernel: BOS: TaskCreate - taskRessurrect HCAS in 28-Oct 23:11:37.14 from 192.168.1.1
<4> kernel: ENDPT: Creating hausware task in 28-Oct 23:11:37.14 from 192.168.1.1
<4> kernel: BOS: Enter TaskCreate HTSK in 28-Oct 23:11:37.15 from 192.168.1.1
<4> kernel: BOS: TaskCreate - taskRessurrect HTSK in 28-Oct 23:11:37.15 from 192.168.1.1
<4> kernel: DAA DBG: MSPI Hdl = 0x500 in 28-Oct 23:11:37.15 from 192.168.1.1
<4> kernel: DAA DBG: GPIO Hdl = 0xb in 28-Oct 23:11:37.15 from 192.168.1.1
<4> kernel: DAA DBG: DAA read failed!!! in 28-Oct 23:11:37.60 from 192.168.1.1
<4> kernel: DAA Device Init completed in 28-Oct 23:11:37.60 from 192.168.1.1
<4> kernel: DAA init successful in 28-Oct 23:11:37.60 from 192.168.1.1
<4> kernel: bosMsgQCreate: Created message queue PSTN_CTL_EVQ at address 0x268002 in 28-Oct 23:11:37.60 from 192.168.1.1
<4> kernel: BOS: Enter TaskCreate PSTN in 28-Oct 23:11:37.60 from 192.168.1.1
<4> kernel: BOS: TaskCreate - taskRessurrect PSTN in 28-Oct 23:11:37.60 from 192.168.1.1
<4> kernel: pstnCtlInit successful in 28-Oct 23:11:37.60 from 192.168.1.1
<4> kernel: vrgendptCreate: capabilities.endptType = 0 in 28-Oct 23:11:37.60 from 192.168.1.1
<4> kernel: ENDPT: 'HAPI_RM_OPEN_VHD_EVT' (0x80c1), hdl:0x30, op1:0x50, op2:0x1 in 28-Oct 23:11:37.65 from 192.168.1.1
<4> kernel: in 28-Oct 23:11:37.67 from 192.168.1.1
<4> kernel: ENDPT: hdspVhdOpen Primary Connection VHD success. VHD (0x50) of type: 0x0 in 28-Oct 23:11:37.67 from 192.168.1.1
<4> kernel: ENDPT: 'HAPI_RM_OPEN_VHD_EVT' (0x80c1), hdl:0x30, op1:0x51, op2:0x1 in 28-Oct 23:11:37.75 from 192.168.1.1
<4> kernel: in 28-Oct 23:11:37.79 from 192.168.1.1
<4> kernel: ENDPT: hdspVhdOpen Endpt VHD success. VHD (0x51) of type: 0x2 in 28-Oct 23:11:37.79 from 192.168.1.1
<4> kernel: ENDPT: TX Gain set to 1000 in 28-Oct 23:11:37.81 from 192.168.1.1
<4> kernel: ENDPT: RX Gain set to 1000 in 28-Oct 23:11:37.84 from 192.168.1.1
<4> kernel: ENDPT: 'HAPI_ECAN_STATE_EVT' (0x3ac0), hdl:0x0, op1:0x7, op2:0x0 in 28-Oct 23:11:37.84 from 192.168.1.1
<4> kernel: boardHalCasGetDriver: chan = 0 in 28-Oct 23:11:37.87 from 192.168.1.1
<4> kernel: Default value for provItemId '41' did not exist in 28-Oct 23:11:37.87 from 192.168.1.1
<4> kernel: ENDPT: Initialization completed successfully for endpt 0 in 28-Oct 23:11:37.90 from 192.168.1.1
<4> kernel: in 28-Oct 23:11:37.90 from 192.168.1.1
<4> kernel: vrgendptCreate: capabilities.endptType = 0 in 28-Oct 23:11:37.90 from 192.168.1.1
<4> kernel: ENDPT: 'HAPI_RM_OPEN_VHD_EVT' (0x80c1), hdl:0x30, op1:0x52, op2:0x1 in 28-Oct 23:11:37.95 from 192.168.1.1
<4> kernel: in 28-Oct 23:11:37.96 from 192.168.1.1
<4> kernel: ENDPT: hdspVhdOpen Primary Connection VHD success. VHD (0x52) of type: 0x0 in 28-Oct 23:11:37.96 from 192.168.1.1
<4> kernel: ENDPT: 'HAPI_RM_OPEN_VHD_EVT' (0x80c1), hdl:0x30, op1:0x53, op2:0x1 in 28-Oct 23:11:38.3 from 192.168.1.1
<4> kernel: in 28-Oct 23:11:38.9 from 192.168.1.1
<4> kernel: ENDPT: hdspVhdOpen Endpt VHD success. VHD (0x53) of type: 0x2 in 28-Oct 23:11:38.9 from 192.168.1.1
<4> kernel: ENDPT: TX Gain set to 1000 in 28-Oct 23:11:38.10 from 192.168.1.1
<4> kernel: ENDPT: RX Gain set to 1000 in 28-Oct 23:11:38.12 from 192.168.1.1
<4> kernel: ENDPT: 'HAPI_ECAN_STATE_EVT' (0x3ac0), hdl:0x1, op1:0x7, op2:0x0 in 28-Oct 23:11:38.14 from 192.168.1.1
<4> kernel: boardHalCasGetDriver: chan = 1 in 28-Oct 23:11:38.15 from 192.168.1.1
<4> kernel: Default value for provItemId '41' did not exist in 28-Oct 23:11:38.15 from 192.168.1.1
<4> kernel: ENDPT: Initialization completed successfully for endpt 1 in 28-Oct 23:11:38.18 from 192.168.1.1
<4> kernel: in 28-Oct 23:11:38.18 from 192.168.1.1
<4> kernel: vrgendptCreate: capabilities.endptType = 1 in 28-Oct 23:11:38.18 from 192.168.1.1
<4> kernel: ENDPT: 'HAPI_RM_OPEN_VHD_EVT' (0x80c1), hdl:0x30, op1:0x54, op2:0x1 in 28-Oct 23:11:38.21 from 192.168.1.1
<4> kernel: in 28-Oct 23:11:38.31 from 192.168.1.1
<4> kernel: ENDPT: hdspVhdOpen PSTN VHD success. VHD (0x54) of type: 0x6 in 28-Oct 23:11:38.31 from 192.168.1.1
<4> kernel: ENDPT: TX Gain set to 1000 in 28-Oct 23:11:38.32 from 192.168.1.1
<4> kernel: ENDPT: RX Gain set to 1000 in 28-Oct 23:11:38.34 from 192.168.1.1
<4> kernel: ENDPT: 'HAPI_ECAN_STATE_EVT' (0x3ac0), hdl:0x2, op1:0x7, op2:0x0 in 28-Oct 23:11:38.35 from 192.168.1.1
<4> kernel: kernel: error during endptInit in 28-Oct 23:11:38.39 from 192.168.1.1
<7> syslog: kill -SIGTERM 5048 in 28-Oct 23:11:40.14 from 192.168.1.1
<7> syslog: /bin/igmp qi=30 ppp_8_35_1 & in 28-Oct 23:11:41.25 from 192.168.1.1
<5> igmp[5966]: igmp started! in 28-Oct 23:11:41.28 from 192.168.1.1
<7> syslog: wlctl ver > /var/wlver in 28-Oct 23:11:45.20 from 192.168.1.1
<5> igmp[5966]: interface 192.168.1.1, DOWNSTREAM ver=0x16 name=br0 index=9 in 28-Oct 23:11:47.28 from 192.168.1.1
<7> syslog: wlctl ver > /var/wlver in 28-Oct 23:12:17.70 from 192.168.1.1
<7> syslog: wlctl ver > /var/wlver in 28-Oct 23:12:30.3 from 192.168.1.1
<7> syslog: wlctl ver > /var/wlver in 28-Oct 23:12:51.43 from 192.168.1.1
<7> syslog: wlctl ver > /var/wlver in 28-Oct 23:13:37.10 from 192.168.1.1
<7> syslog: wlctl ver > /var/wlver in 28-Oct 23:13:37.10 from 192.168.1.1
<7> syslog: wlctl ver > /var/wlver in 28-Oct 23:13:57.78 from 192.168.1.1
<7> syslog: wlctl ver > /var/wlver in 28-Oct 23:14:20.34 from 192.168.1.1
<7> syslog: wlctl ver > /var/wlver in 28-Oct 23:14:42.71 from 192.168.1.1
<7> syslog: wlctl ver > /var/wlver in 28-Oct 23:15:5.9 from 192.168.1.1
<7> syslog: wlctl ver > /var/wlver in 28-Oct 23:15:27.48 from 192.168.1.1
<7> syslog: wlctl ver > /var/wlver in 28-Oct 23:15:49.98 from 192.168.1.1
_________________
Club Internet, ND, ADSL2+ <24Mega + VoIP CI-Box: 1104/20955
Ligne: dist 560m, aff 6,94. Grenouille: dl 1578Ko/s, ul 108Ko/s, ping 36ms
XP home SP2 et Vista Premium.
Revenir en haut de page
Voir le profil de l'utilisateur Envoyer un message privé Yahoo Messenger MSN Messenger
Dumboton
Membre indispensable
Membre indispensable


Inscrit le: 20 Juin 2005
Messages: 10316
Localisation: 95170

MessagePosté le: Dim 29 Oct 2006 am 10:06    Sujet du message: Répondre en citant

Oui tu passes bien d'un PPP down à un PPP UP sans renégociation de la synchro ADSL

2> pppd[519]: Clear IP addresses. PPP connection DOWN. in 28-Oct 23:11:12.29 from 192.168.1.1
<5> pppd[519]: PPP: Start to connect ... in 28-Oct 23:11:18.31 from 192.168.1.1
...
<2> pppd[519]: PPP LCP UP. in 28-Oct 23:11:22.98 from 192.168.1.1
<2> pppd[519]: PPP LCP UP. in 28-Oct 23:11:23.57 from 192.168.1.1
<2> pppd[519]: Received valid IP address from server. Connection UP. in 28-Oct 23:11:23.79 from 192.168.1.1

Peut-être une procédure standard de renouvellement de la connexion chez FT avec pour la VOIP une réattribution automatique de la même IP.

Ce serait un peu normal et plus simple (pur FT ou CI) que tous les abonnés ND aient le même protocole (resynchro toutes les 24h), le traitement ensuite dépendant que de son statut.
_________________

CI c'était des hommes, un service et de la qualité
Revenir en haut de page
Voir le profil de l'utilisateur Envoyer un message privé Envoyer un e-mail
Dumboton
Membre indispensable
Membre indispensable


Inscrit le: 20 Juin 2005
Messages: 10316
Localisation: 95170

MessagePosté le: Dim 29 Oct 2006 am 10:07    Sujet du message: Répondre en citant

Oui tu passes bien d'un PPP down à un PPP UP sans renégociation de la synchro ADSL

2> pppd[519]: Clear IP addresses. PPP connection DOWN. in 28-Oct 23:11:12.29 from 192.168.1.1
<5> pppd[519]: PPP: Start to connect ... in 28-Oct 23:11:18.31 from 192.168.1.1
...
<2> pppd[519]: PPP LCP UP. in 28-Oct 23:11:22.98 from 192.168.1.1
<2> pppd[519]: PPP LCP UP. in 28-Oct 23:11:23.57 from 192.168.1.1
<2> pppd[519]: Received valid IP address from server. Connection UP. in 28-Oct 23:11:23.79 from 192.168.1.1

Peut-être une procédure standard de renouvellement de la connexion chez FT avec pour la VOIP une réattribution automatique de la même IP.

Ce serait un peu normal et plus simple (pur FT ou CI) que tous les abonnés ND aient le même protocole (resynchro toutes les 24h), le traitement ensuite dépendant que de son statut. (Ip nouvelle ou identique)
_________________

CI c'était des hommes, un service et de la qualité
Revenir en haut de page
Voir le profil de l'utilisateur Envoyer un message privé Envoyer un e-mail
NIKON_33
Membre régulier
Membre régulier


Inscrit le: 30 Sep 2006
Messages: 153
Localisation: Bègles

MessagePosté le: Lun 30 Oct 2006 pm 18:38    Sujet du message: Re: Syslog ou Journal des évènements Macintosh Mac 7/8/9 Répondre en citant

Dumboton a écrit:
Pour avoir un log continu des évènements, je vous propose :
1°) Sur le PC
Installer un syslog, j'ai utilisé du temps de ce post, mais je conseille vivement le lien en 4°) que j'ai depuis adopté
Kiwi syslogd (freeware)
http://www.kiwisyslog.com/software_downloads.htm



Et pour les utilisateurs Macintosh
Et pour les vieux utilisateurs de Macintosh (de Mac Os 7 à Mac Os 9)
..pas Mac Os X

je viens de trouver DEUX logiciels pouvant faire le suivi des Syslog
..qui fonctionnent chez moi en Mac Os 8.6

Arrow MacNetLogger v0.96b9 (Mac NetLogger FAT v0.96b9)
et
Arrow syslogd218.smi.sit.hqx US$= 20 brian@classicalguitar.net Client/Server

je les indique des fois qu'un macintoshien en ai besoin..je préfère Mac NetLogger FAT v0.96b9 simple efficace UDP 514
Shocked Shocked
_________________
Mac 8.6 & 10.5.6 BEG33 1944m -29 dB NeufBox DT NB4 Ethernet
le 28/3/2009
ADSL2+ LRUp 857 LRDw 5626 SNRMUp 12.7 SNRMDw 7.6 AttUp 24.1 AttDw 43.0
>>> DWL 570 Ko/sec UPLD>>> 85 Ko/sec
Revenir en haut de page
Voir le profil de l'utilisateur Envoyer un message privé
Montrer les messages depuis:   
Poster un nouveau sujet   Répondre au sujet     Index du Forum -> Configuration CI Box & Autres Toutes les heures sont au format Heure D'hiver
Aller à la page Précédente  1, 2, 3  Suivante
Page 2 sur 3

 
Sauter vers:  
Vous ne pouvez pas poster de nouveaux sujets dans ce forum
Vous ne pouvez pas répondre aux sujets dans ce forum
Vous ne pouvez pas éditer vos messages dans ce forum
Vous ne pouvez pas supprimer vos messages dans ce forum
Vous ne pouvez pas voter dans les sondages de ce forum


Powered by phpBB © 2001, 2005 phpBB Group
Traduction par : phpBB-fr.com
© ClubNews.fr