Jump to content

Délestage programmé chez Anis ????


Recommended Posts

Salam

 

Jan  1 12:00:14> AP Acquiring Lock
Jan  1 12:00:16> NTP Polling Timer for DHCP Started succesfully.
Jan  1 12:00:16> DSL Polling Timer Started succesfully.
Jan  1 12:00:17> Firewall NAT service started
Jan  1 12:00:17> AP REPORT LOCK ACQUIRED
Jan  1 12:00:17> wlan_handle_load_event - Acquired Lock
Jan  1 12:00:18> MAC address is : 00:21:91:2c:29:26
Jan  1 12:00:22>  starting on port 80
Jan  1 12:00:23> Initializing the WAN Bridge.
Jan  1 12:00:23> Please set the MAC Address for the WAN Bridge.
Jan  1 12:00:23> Set the Environment variable 'wan_br_mac'. 
Jan  1 12:00:23> xx.xx.xx.xx.xx.xx
Jan  1 12:00:23> Mounted root (squashfs filesystem) readonly.
Jan  1 12:00:23> Mounted devfs on /dev
Jan  1 12:00:23> 64k freed
Jan  1 12:00:23> Algorithmics/MIPS FPU Emulator v1.5
Jan  1 12:00:23> registered device TI Avalanche SAR
Jan  1 12:00:23> Ohio250(7200/7100A2) detected
Jan  1 12:00:23> DSP binary filesize = 356930 bytes
Jan  1 12:00:23> Setting mode to 0xffff
Jan  1 12:00:23> version:[6.00.01.00]
Jan  1 12:00:23> Enable_igmp_snooping_register!!!
Jan  1 12:00:23> Setting mode to 0xffff
Jan  1 12:00:23> Default Asymmetric MTU for nas0 1500
Jan  1 12:00:23> Registering protocol inspector: 0x94178678 for VCC:0x9400da00
Jan  1 12:00:23> Default Asymmetric MTU for br0 1500
Jan  1 12:00:23> Bridge Created: br0
Jan  1 12:00:23> Bridge Created: br1
Jan  1 12:00:24> WPA Authenticator Started
Jan  1 12:00:24> Bridge Interface Added: eth0
Jan  1 12:00:25> 2 
Jan  1 12:00:25> Default Asymmetric MTU for br1 1500
Jan  1 12:00:25> 2 
Jan  1 12:00:26> DSL Carrier is down
Jan  1 12:00:27> Default Asymmetric MTU for wlan0 1500
Jan  1 12:00:27> Default Asymmetric MTU for wdsup0 1500
Jan  1 12:00:27> Default Asymmetric MTU for wdsdw0 1500
Jan  1 12:00:27> Default Asymmetric MTU for wdsdw1 1500
Jan  1 12:00:27> Default Asymmetric MTU for wdsdw2 1500
Jan  1 12:00:27> Default Asymmetric MTU for wdsdw3 1500
Jan  1 12:00:28> AP Driver configuration successful
Jan  1 12:00:31> AP IS UP
Jan  1 12:00:31> MemAddr=0xa4000000, RegAddr=0xa4080000
Jan  1 12:00:31> whal_hwCtrl_ProcessEepromBREntry: Reg = 0x58f0 Data 0x8
Jan  1 12:00:31> whal_hwCtrl_ProcessEepromBREntry: Reg = 0x58d4 Data 0x10
Jan  1 12:00:31> whal_hwCtrl_ProcessEepromBREntry: Reg = 0x58b0 Data 0x4
Jan  1 12:00:31> whal_hwCtrl_ProcessEepromBR : CurrEepromBufPtr = 0xc
Jan  1 12:00:31> whal_hwCtrl_GetNvsDataSize: eepromImage.len = 0x1d9 288: Get NVS file information: NvsDataLen = 0x134 tblsOffset 0xa9
Jan  1 12:00:31> whal_acxProcInitiate: Cpu halt -} download code
Jan  1 12:00:31> whal_acxProcLoadFwImage: 0xa4000000, 0x0
Jan  1 12:00:31> whal_acxProcLoadFwImage() -- Loading FW image
Jan  1 12:00:31> Compiled for DCR radio
Jan  1 12:00:31> whal_acxProcLoadFwImage: 1, pBuf=0xc00b0d10, len=0x14b50. Extra pBuf=0x0, len=0x0
Jan  1 12:00:31> AP Releasing Lock
Jan  1 12:00:31> whal_acxProcLoadFwImage: 2, pBuf=0xc00b0d10, len=0x14b50. Extra pBuf=0x0, len=0x0
Jan  1 12:00:31> whal_acxProcLoadFwImage: 3, pBuf=0xc00b0d10, len=0x14b50, DataLen=0x14b48
Jan  1 12:00:31> whal_acxProcLoadFwImage: 4, pBuf=0xc00b0d10, len=0x14b50
Jan  1 12:00:31> whal_acxProcLoadFwImage: Checksum, calc=0x6dc2a3, file=0x6dc2a3
Jan  1 12:00:31> wdrv_txInit: AC = 3 size = 192
Jan  1 12:00:31> Tx is up
Jan  1 12:00:31> MemMngr is up
Jan  1 12:00:31> main state machine is up
Jan  1 12:00:31> QoS module is up is up
Jan  1 12:00:31> WDRV_MAINSM: WLAN Driver initialized successfully
Jan  1 12:00:31> 
Jan  1 12:00:31> WDRV_4X: 4x Disabled
Jan  1 12:00:31> WDRV_4X: Concatenation Disabled
Jan  1 12:00:31> WDRV_4X: Ack Emulation Disabled
Jan  1 12:00:31> whal_apiStartBss: Enable Tx, Rx and Start the Bss
Jan  1 12:00:31> ----------------------------------------------------------------
Jan  1 12:00:31> ----------------------------------------------------------------
Jan  1 12:00:31>   START BSS, SSID=DLINK_WIRELESS, BSSID=00-21-91-2C-29-26
Jan  1 12:00:31> ----------------------------------------------------------------
Jan  1 12:00:31> ----------------------------------------------------------------
Jan  1 12:00:31>  AP Power Level = 1
Jan  1 12:00:31>  Regulatory Domain = ETSI
Jan  1 12:00:31>           Net[0] : Channel=6
Jan  1 12:00:31> ----------------------------------------------------------------
Jan  1 12:00:31> FW Watchdog is Enabled
Jan  1 12:00:32> Bridge Interface Added: wlan0
Jan  1 12:00:42> DSL in Sync
Jan  1 12:00:46> DSL Carrier is up
Jan  1 12:00:46> sar read trained mode (5)(ADSL_2plus)
Jan  1 12:00:47> pingStat 2, oamHdr 230 result 0
Jan  1 12:00:47> pingStat 2, oamHdr 200 result 0
Jan  1 12:00:47> pingStat 2, oamHdr 280 result 0
Jan  1 12:00:47> pingStat 2, oamHdr 240 result 0
Jan  1 12:00:47> pingStat 2, oamHdr 260 result 0
Jan  1 12:00:47> pingStat 2, oamHdr 600 result 0
Jan  1 12:00:47> pingStat 2, oamHdr 230 result 0
Jan  1 12:00:47> pingStat 2, oamHdr 800230 result 0
Jan  1 12:00:47> pingStat 2, oamHdr 2B0 result 0
Jan  1 12:00:47> pingStat 2, oamHdr 330 result 0
Jan  1 12:00:47> pingStat 2, oamHdr 3B0 result 0
Jan  1 12:00:47> pingStat 2, oamHdr 8002B0 result 0
Jan  1 12:00:47> pingStat 2, oamHdr 800330 result 0
Jan  1 12:00:47> pingStat 2, oamHdr 8003B0 result 0
Jan  1 12:00:47> get 0xF at Addr 0xA30085B0
Jan  1 12:00:48> pppd 2.4.3 started by root, uid 0
Jan  1 12:00:48> Connect: ppp0 {--} nas0
Jan  1 12:00:48> peer from calling number 00:30:88:01:5D:EB authorized
Jan  1 12:00:49> ppp0
Jan  1 12:00:49> WAN IP address 41.200.241.45
Jan  1 12:00:49> WAN gateway 41.200.240.1
Jan  1 12:00:49> PPPoE Connect with IP Address 41.200.241.45 
Jan  1 12:00:49> PPPoE Connection Successfully Established 
Jan  1 12:00:49> PPPoE Connect with Gateway IP Address: 41.200.240.1 
Nov  3 10:52:28> bad diff in charge, cl=880001 diff=172032 now=114688 then=4294909952 j=524302
Nov  3 12:19:51> bad diff in charge, cl=880001 diff=73728 now=0 then=4294893568 j=1048576
Nov  3 13:47:14> bad diff in charge, cl=880001 diff=172032 now=114688 then=4294909952 j=1572878
Nov  3 15:14:37> bad diff in charge, cl=880001 diff=16384 now=0 then=4294950912 j=2097152
Nov  3 16:05:08> DSL out of sync
Nov  3 16:05:09> DSL in Sync
Nov  3 16:41:59> bad diff in charge, cl=880001 diff=139264 now=8192 then=4294836224 j=2621441
Nov  3 18:09:22> bad diff in charge, cl=880001 diff=90112 now=32768 then=4294909952 j=3145732
Nov  3 19:36:45> bad diff in charge, cl=880001 diff=172032 now=40960 then=4294836224 j=3670021
Nov  3 21:04:08> bad diff in charge, cl=880001 diff=253952 now=24576 then=4294737920 j=4194307
[color="Red"]Nov  3 21:25:54> ppp0[/color]
Nov  3 21:25:57> Connection terminated.
Nov  3 21:25:57> Connect: ppp0 {--} nas0
Nov  3 21:25:57> Modem hangup
Nov  3 21:25:57> Terminated: Modem Hang-Up
Nov  3 21:25:59> pppd 2.4.3 started by root, uid 0
Nov  3 21:26:34> Timeout waiting for PADS packets
Nov  3 21:26:34> Unable to complete PPPoE Discovery
Nov  3 21:26:34> PPPD Successfully Launched
Nov  3 21:26:38> pppd 2.4.3 started by root, uid 0
Nov  3 21:26:38> Connect: ppp0 {--} nas0
Nov  3 21:26:42> peer from calling number 00:30:88:01:5D:EB authorized
[color="Red"]Nov  3 21:26:42> ppp0[/color]
Nov  3 21:26:42> WAN IP address 41.200.242.157
Nov  3 21:26:42> PPPoE Connect with IP Address 41.200.242.157 
Nov  3 21:26:42> PPPoE Connection Successfully Established 
Nov  3 21:26:42> PPPoE Connect with Gateway IP Address: 41.200.240.1 
Nov  3 21:26:42> WAN gateway 41.200.240.1
Nov  3 22:31:31> bad diff in charge, cl=880001 diff=24576 now=16384 then=4294959104 j=4718594
Nov  3 23:58:54> bad diff in charge, cl=880001 diff=139264 now=81920 then=4294909952 j=5242890
Nov  4 01:26:17> bad diff in charge, cl=880001 diff=81920 now=40960 then=4294926336 j=5767173
Nov  4 02:53:40> bad diff in charge, cl=880001 diff=40960 now=24576 then=4294950912 j=6291459
Nov  4 04:21:03> bad diff in charge, cl=880001 diff=73728 now=40960 then=4294934528 j=6815749
Nov  4 05:48:26> bad diff in charge, cl=880001 diff=638976 now=163840 then=4294492160 j=7340052
Nov  4 07:15:48> bad diff in charge, cl=880001 diff=155648 now=114688 then=4294926336 j=7864334
Nov  4 08:43:11> bad diff in charge, cl=880001 diff=16384 now=8192 then=4294959104 j=8388609
[color="DarkRed"]Nov  4 09:26:41> ppp0[/color]
Nov  4 09:26:44> Connection terminated.
Nov  4 09:26:45> Connect: ppp0 {--} nas0
Nov  4 09:26:45> Modem hangup
Nov  4 09:26:45> Terminated: Modem Hang-Up
Nov  4 09:26:49> pppd 2.4.3 started by root, uid 0
Nov  4 09:27:24> Timeout waiting for PADS packets
Nov  4 09:27:24> Unable to complete PPPoE Discovery
Nov  4 09:27:24> PPPD Successfully Launched
Nov  4 09:27:24> pppd 2.4.3 started by root, uid 0
Nov  4 09:27:25> Connect: ppp0 {--} nas0
Nov  4 09:27:25> peer from calling number 00:30:88:01:5D:EB authorized
[color="DarkRed"]Nov  4 09:27:25> ppp0[/color]
Nov  4 09:27:25> WAN IP address 41.200.243.143
Nov  4 09:27:25> PPPoE Connect with IP Address 41.200.243.143 
Nov  4 09:27:25> PPPoE Connection Successfully Established 
Nov  4 09:27:25> PPPoE Connect with Gateway IP Address: 41.200.240.1 
Nov  4 09:27:25> WAN gateway 41.200.240.1
Nov  4 10:10:36> bad diff in charge, cl=880001 diff=73728 now=57344 then=4294950912 j=8912903
Nov  4 11:37:59> bad diff in charge, cl=880001 diff=212992 now=98304 then=4294852608 j=9437196
Nov  4 13:05:22> bad diff in charge, cl=880001 diff=8192 now=0 then=4294959104 j=9961472
Nov  4 13:58:14> mindelay=500, report it please !
Nov  4 14:32:45> bad diff in charge, cl=880001 diff=172032 now=65536 then=4294860800 j=10485768
Nov  4 16:00:08> bad diff in charge, cl=880001 diff=24576 now=16384 then=4294959104 j=11010050
Nov  4 17:27:31> bad diff in charge, cl=880001 diff=16384 now=8192 then=4294959104 j=11534337
Nov  4 18:54:54> bad diff in charge, cl=880001 diff=8192 now=0 then=4294959104 j=12058624
Nov  4 20:18:08> mindelay=500, report it please !
Nov  4 20:22:17> bad diff in charge, cl=880001 diff=180224 now=24576 then=4294811648 j=12582915
[color="Red"]Nov  4 21:27:27> ppp0[/color]
Nov  4 21:27:30> Connection terminated.
Nov  4 21:27:31> Connect: ppp0 {--} nas0
Nov  4 21:27:31> Modem hangup
Nov  4 21:27:31> Terminated: Modem Hang-Up
Nov  4 21:27:34> pppd 2.4.3 started by root, uid 0
Nov  4 21:28:09> Timeout waiting for PADS packets
Nov  4 21:28:09> Unable to complete PPPoE Discovery
Nov  4 21:28:09> PPPD Successfully Launched
Nov  4 21:28:14> pppd 2.4.3 started by root, uid 0
Nov  4 21:28:14> Connect: ppp0 {--} nas0
Nov  4 21:28:14> peer from calling number 00:30:88:01:5D:EB authorized
[color="DarkRed"]Nov  4 21:28:14> ppp0[/color]
Nov  4 21:28:14> WAN IP address 41.200.240.157
Nov  4 21:28:14> PPPoE Connect with IP Address 41.200.240.157 
Nov  4 21:28:14> PPPoE Connection Successfully Established 
Nov  4 21:28:14> PPPoE Connect with Gateway IP Address: 41.200.240.1 
Nov  4 21:28:14> WAN gateway 41.200.240.1
Nov  4 21:49:39> bad diff in charge, cl=880001 diff=106496 now=16384 then=4294877184 j=13107202
Nov  4 23:17:02> bad diff in charge, cl=880001 diff=147456 now=24576 then=4294844416 j=13631491
Nov  5 00:44:25> bad diff in charge, cl=880001 diff=49152 now=8192 then=4294926336 j=14155777
Nov  5 02:11:48> bad diff in charge, cl=880001 diff=65536 now=24576 then=4294926336 j=14680067
Nov  5 03:39:11> bad diff in charge, cl=880001 diff=90112 now=81920 then=4294959104 j=15204362
Nov  5 05:06:34> bad diff in charge, cl=880001 diff=172032 now=57344 then=4294852608 j=15728647
Nov  5 06:33:57> bad diff in charge, cl=880001 diff=98304 now=0 then=4294868992 j=16252928
Nov  5 08:01:20> bad diff in charge, cl=880001 diff=434176 now=245760 then=4294778880 j=16777246
[color="Red"]Nov  5 09:28:14> ppp0[/color]
Nov  5 09:28:17> Connection terminated.
Nov  5 09:28:18> Connect: ppp0 {--} nas0
Nov  5 09:28:18> Modem hangup
Nov  5 09:28:18> Terminated: Modem Hang-Up
Nov  5 09:28:19> pppd 2.4.3 started by root, uid 0
Nov  5 09:28:54> Timeout waiting for PADS packets
Nov  5 09:28:54> Unable to complete PPPoE Discovery
Nov  5 09:28:54> PPPD Successfully Launched
Nov  5 09:28:59> pppd 2.4.3 started by root, uid 0
Nov  5 09:28:59> bad diff in charge, cl=880001 diff=20561920 now=13352960 then=4287758336 j=17303134
Nov  5 09:28:59> Connect: ppp0 {--} nas0
Nov  5 09:28:59> peer from calling number 00:30:88:01:5D:EB authorized
[color="Red"]Nov  5 09:28:59> ppp0[/color]
Nov  5 09:28:59> WAN IP address 41.200.241.32
Nov  5 09:28:59> PPPoE Connect with IP Address 41.200.241.32 
Nov  5 09:28:59> PPPoE Connection Successfully Established 
Nov  5 09:28:59> PPPoE Connect with Gateway IP Address: 41.200.240.1 
Nov  5 09:28:59> WAN gateway 41.200.240.1

Link to post
Share on other sites

Bonjour,

 

Oui c'est vrai j'ai eu ce problème il y a quelques jours et ce pendant deux jours mais pas de suite ( c'est à dire le 1° jour de 12 h ~ à 20 h 10 précis - le 2° jour tout s'est passé normalement, pas de coupure, le 3° jour comme le 1° jour = 12 h ~ à 20 h 10 piles), donc ça se voit que c'est programmé, mais depuis tout se passe normalement hormis que pour se connecter, il me faut réessayer des dizaines de fois, surtout le soir.

Link to post
Share on other sites

bon pour commencer ce que je dis n'engage que ma personne et elle seule.

Depuis le début de mes vacance d"été j'ai commencé à me lever tôt le matin donc par conséquent j'ai réalisé que ma connexions réinitialise chaque jour à une heure précise (18h55/19H00) et ça correspond a 12 heures de connexion pour faire simple je me lève a 06H50 et j'allume mon pc à 06H55 / 07H00 et la j'apprends que chez anis ya un délestage à chaque 12 heures et comme je l'ai mentionné auparavant cela n'engage que ma personne et je constate ce phénomène depuis qui dirait le moi de juillet

croyez moi les gars c'est pas du baratin

j'ai même demandé à des amis qui ont anis et pour seule réponse j'ai reçu que ya tellement de déconnexion que c'est pas évident de vérifier.

 

le délestage n'arrive pas à des heures précises mais après un laps de temps de connexion; pour mon cas 12 heures. (jyu-ni /douze / twelve / ...)

Edited by assasmourad
Link to post
Share on other sites

Pourquoi parler de délestage alors que ce n'est qu'une déconnexion suive toute de suite de reconnexion et que sa se fait à intervale de 12H ? certe le log prouve la programmation de la déconnexion à des heures précises mais c'est plutôt une réinitialisation de la connexion !

Link to post
Share on other sites

Salam,

 

Ok je vois, merci pour les eclairecissements. Ceci dit, je ne pense pas qu'on puisse appeler ce phenomen ainsi. Le delestage devrait concerner tous ou du moins une partie des abonnées au meme temps. Hors ce n'est pas le cas chaque client à une sorte de bail de N heures.

 

Je ne connais pas l'interet de reinitialiser la connexion periodiquement mais je pense que cette pratiaue permet qu FAI de :

  • Empecher les clients d'avoir un IP fixe
  • Deconnecter l'abonnée si son aboonnement arrive à terme et que sa session reste active.
  • ... d'autres suggestions ?

Link to post
Share on other sites
Salam,

 

[*]... d'autres suggestions ?

 

Interrompre les téléchargements volumineux direct et surtout le P2P ? c'est ce que j'ai constaté avec utorrent en tout cas, si y'as eu une déconnexion, lors de la reconnexion les téléchargements ne reprennent pas, c'est la seule nuisance que j'ai trouvé à cette procédure mais j'en doute que c'est la principale raison !

Edited by Forumdézien
Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.



  • Posts

    • salut mon Dlink est bien placé , en hauteur, force de signal extra mais à certains moment j'ai le wifi qui décroche tout seul depuis mon iphone malgré une force de signal trés bonne, je perds la connection et l'icone wifi disparait !! des réglages particuliers à faire sur mon nouveau Dlink 124 ? j'ai utilisé le logiciel inSSIDer mais j'ai pas compris grand chose à part qu'il fallait mettre le canal 11  sur mon Dlink c'est réglé channel number sur auto et current channel 1 autres réglages channel width est sur 20/40 Mhz le logiciel me conseil de mettre sur 40 seulement des suggestions ? 
    • C'est très claqué sur MyDzStore quand même, https://mydzstore.com/ mais bon, c'est à l'image du pays  
    • salut 80cm suffit pour astra. et  nilesat au nord de l'Algerie mais ca dépend aussi de la qualité de la tête LNB . Tu comprendras tout sur cette page        
    • j'ai activé l'adsl mercredi samedi 16:55 raccordé. je viens de remarqué le message et les appelle en absence d'AT
    • merci pour la réponse...mais c'est pas ce que je demandais... 80cm suffit pour astra...ou eutelsat ou nilesat oui.... MAIS moi je veux savoir si une LNB monobloc-icone (c'est pas la meme chose qu'une tete simple a 4 sortie) captera sur une parabole de 80.... helas tu n'as pas fais de tests...et la plupart des vendeurs ne savent pas...
×
×
  • Create New...