Lemrid

salam voilà une bonne sOlution http://www.torproject.org/vidalia/index.html.en

re, exact Une fin de session programmée à des heures précises ( en rouge sur les logs )

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

salam bonne initiative pour compléter le sujet : http://www.forumdz.com/showthread.php?t=15039&highlight=prtg http://www.forumdz.com/showthread.php?t=14895&highlight=prtg

re, problème résolu ce matin ceci concernait le réseau ATM

salam depuis 18:33 deconnexion eazy 08/01/2003 00:41:42 sending ACK to 192.168.1.2 08/01/2003 00:41:42 PPPoE send PADI 08/01/2003 00:41:31 PPPoE send PADI 08/01/2003 00:41:18 PPPoE send PADI 08/01/2003 00:41:05 PPPoE send PADI 08/01/2003 00:40:52 PPPoE send PADI 08/01/2003 00:40:42 PPPoE send PADI 08/01/2003 00:40:29 PPPoE send PADI 08/01/2003 00:40:16 PPPoE send PADI 08/01/2003 00:40:03 PPPoE send PADI 08/01/2003 00:39:52 PPPoE send PADI 08/01/2003 00:39:39 PPPoE send PADI 08/01/2003 00:39:26 PPPoE send PADI 08/01/2003 00:39:13 PPPoE send PADI 08/01/2003 00:39:03 PPPoE send PADI 08/01/2003 00:38:50 PPPoE send PADI 08/01/2003 00:38:37 PPPoE send PADI 08/01/2003 00:38:24 PPPoE send PADI 08/01/2003 00:38:24 Dial On Demand(PPPoE1) 08/01/2003 00:38:14 PPPoE send PADI 08/01/2003 00:38:01 PPPoE send PADI 08/01/2003 00:37:48 PPPoE send PADI 08/01/2003 00:37:35 PPPoE send PADI 08/01/2003 00:37:24 PPPoE send PADI 08/01/2003 00:37:11 PPPoE send PADI 08/01/2003 00:36:58 PPPoE send PADI 08/01/2003 00:36:45 PPPoE send PADI 08/01/2003 00:36:35 PPPoE send PADI 08/01/2003 00:36:22 PPPoE send PADI 08/01/2003 00:36:09 PPPoE send PADI 08/01/2003 00:35:56 PPPoE send PADI 08/01/2003 00:35:45 PPPoE send PADI 08/01/2003 00:35:32 PPPoE send PADI 08/01/2003 00:35:19 PPPoE send PADI 08/01/2003 00:35:06 PPPoE send PADI 08/01/2003 00:34:56 PPPoE send PADI 08/01/2003 00:34:43 PPPoE send PADI 08/01/2003 00:34:30 PPPoE send PADI 08/01/2003 00:34:17 PPPoE send PADI 08/01/2003 00:34:06 PPPoE send PADI 08/01/2003 00:33:53 PPPoE send PADI 08/01/2003 00:33:40 PPPoE send PADI 08/01/2003 00:33:27 PPPoE send PADI 08/01/2003 00:33:17 PPPoE send PADI 08/01/2003 00:33:04 PPPoE send PADI 08/01/2003 00:32:51 PPPoE send PADI 08/01/2003 00:32:38 PPPoE send PADI 08/01/2003 00:32:27 PPPoE send PADI 08/01/2003 00:32:14 PPPoE send PADI 08/01/2003 00:32:01 PPPoE send PADI 08/01/2003 00:31:48 PPPoE send PADI 08/01/2003 00:31:38 PPPoE send PADI 08/01/2003 00:31:25 PPPoE send PADI 08/01/2003 00:31:12 PPPoE send PADI 08/01/2003 00:30:59 PPPoE send PADI 08/01/2003 00:30:48 PPPoE send PADI 08/01/2003 00:30:35 PPPoE send PADI 08/01/2003 00:30:22 PPPoE send PADI 08/01/2003 00:30:09 PPPoE send PADI 08/01/2003 00:29:59 PPPoE send PADI 08/01/2003 00:29:46 PPPoE send PADI 08/01/2003 00:29:33 PPPoE send PADI 08/01/2003 00:29:20 PPPoE send PADI 08/01/2003 00:29:09 PPPoE send PADI 08/01/2003 00:28:56 PPPoE send PADI 08/01/2003 00:28:43 PPPoE send PADI 08/01/2003 00:28:30 PPPoE send PADI 08/01/2003 00:28:20 PPPoE send PADI 08/01/2003 00:28:07 PPPoE send PADI 08/01/2003 00:27:54 PPPoE send PADI 08/01/2003 00:27:41 PPPoE send PADI 08/01/2003 00:27:30 PPPoE send PADI 08/01/2003 00:27:17 PPPoE send PADI 08/01/2003 00:27:04 PPPoE send PADI 08/01/2003 00:26:51 PPPoE send PADI 08/01/2003 00:26:41 PPPoE send PADI 08/01/2003 00:26:28 PPPoE send PADI 08/01/2003 00:26:15 PPPoE send PADI 08/01/2003 00:26:02 PPPoE send PADI 08/01/2003 00:25:51 PPPoE send PADI 08/01/2003 00:25:38 PPPoE send PADI 08/01/2003 00:25:25 PPPoE send PADI 08/01/2003 00:25:12 PPPoE send PADI 08/01/2003 00:25:02 PPPoE send PADI 08/01/2003 00:24:49 PPPoE send PADI 08/01/2003 00:24:36 PPPoE send PADI 08/01/2003 00:24:23 PPPoE send PADI 08/01/2003 00:24:12 PPPoE send PADI 08/01/2003 00:23:59 PPPoE send PADI 08/01/2003 00:23:46 PPPoE send PADI 08/01/2003 00:23:33 PPPoE send PADI 08/01/2003 00:23:23 PPPoE send PADI 08/01/2003 00:23:10 PPPoE send PADI 08/01/2003 00:22:57 PPPoE send PADI 08/01/2003 00:22:44 PPPoE send PADI 08/01/2003 00:22:33 PPPoE send PADI 08/01/2003 00:22:20 PPPoE send PADI 08/01/2003 00:22:07 PPPoE send PADI 08/01/2003 00:21:54 PPPoE send PADI 08/01/2003 00:21:44 PPPoE send PADI 08/01/2003 00:21:31 PPPoE send PADI 08/01/2003 00:21:18 PPPoE send PADI 08/01/2003 00:21:05 PPPoE send PADI 08/01/2003 00:20:54 PPPoE send PADI 08/01/2003 00:20:41 PPPoE send PADI 08/01/2003 00:20:28 PPPoE send PADI 08/01/2003 00:20:15 PPPoE send PADI 08/01/2003 00:20:05 PPPoE send PADI 08/01/2003 00:19:52 PPPoE send PADI 08/01/2003 00:19:39 PPPoE send PADI 08/01/2003 00:19:26 PPPoE send PADI 08/01/2003 00:19:15 PPPoE send PADI 08/01/2003 00:19:02 PPPoE send PADI 08/01/2003 00:18:49 PPPoE send PADI 08/01/2003 00:18:36 PPPoE send PADI 08/01/2003 00:18:26 PPPoE send PADI 08/01/2003 00:18:13 PPPoE send PADI 08/01/2003 00:18:00 PPPoE send PADI 08/01/2003 00:17:47 PPPoE send PADI 08/01/2003 00:17:36 PPPoE send PADI 08/01/2003 00:17:23 PPPoE send PADI 08/01/2003 00:17:10 PPPoE send PADI 08/01/2003 00:16:57 PPPoE send PADI 08/01/2003 00:16:47 PPPoE send PADI 08/01/2003 00:16:34 PPPoE send PADI 08/01/2003 00:16:21 PPPoE send PADI 08/01/2003 00:16:08 PPPoE send PADI 08/01/2003 00:15:57 PPPoE send PADI 08/01/2003 00:15:44 PPPoE send PADI 08/01/2003 00:15:31 PPPoE send PADI 08/01/2003 00:15:18 PPPoE send PADI 08/01/2003 00:15:08 PPPoE send PADI 08/01/2003 00:14:55 PPPoE send PADI 08/01/2003 00:14:42 PPPoE send PADI 08/01/2003 00:14:29 PPPoE send PADI 08/01/2003 00:14:18 PPPoE send PADI 08/01/2003 00:14:05 PPPoE send PADI 08/01/2003 00:13:52 PPPoE send PADI 08/01/2003 00:13:39 PPPoE send PADI 08/01/2003 00:13:29 PPPoE send PADI 08/01/2003 00:13:16 PPPoE send PADI 08/01/2003 00:13:03 PPPoE send PADI 08/01/2003 00:12:50 PPPoE send PADI 08/01/2003 00:12:39 PPPoE send PADI 08/01/2003 00:12:26 PPPoE send PADI 08/01/2003 00:12:13 PPPoE send PADI 08/01/2003 00:12:00 PPPoE send PADI 08/01/2003 00:11:50 PPPoE send PADI 08/01/2003 00:11:37 PPPoE send PADI 08/01/2003 00:11:24 PPPoE send PADI 08/01/2003 00:11:11 PPPoE send PADI 08/01/2003 00:11:00 PPPoE send PADI 08/01/2003 00:10:47 PPPoE send PADI 08/01/2003 00:10:34 PPPoE send PADI 08/01/2003 00:10:21 PPPoE send PADI 08/01/2003 00:10:21 sending ACK to 192.168.1.3 08/01/2003 00:10:21 sending OFFER to 192.168.1.3 08/01/2003 00:10:11 PPPoE send PADI 08/01/2003 00:09:58 PPPoE send PADI 08/01/2003 00:09:47 sending ACK to 192.168.1.2 pour info : http://en.wikipedia.org/wiki/Point-to-Point_Protocol_over_Ethernet#PADI PS : je me demande qui s'amuse à JOUER un jour férié edit : j'ai trouvé cette démarche très instructive http://www.justneuf.com/print.html&client=wordr&f=59&t=68532

http://www.forumdz.com/showpost.php?p=129428&postcount=1

re, AT n'y est pour rien. les responsable de ceci sont : - La firme sagem qui n'a pas protégé son firmware - le user qui ne prend pas les mesures élémentaires de sécurité ( changement de mot de passe admin, activation du firewall ... )

re, remember the time http://www.forumdz.com/showthread.php?t=7826&highlight=antenne+wifi http://www.forumdz.com/showpost.php?p=46915&postcount=5

re, antennes hot spots pas de soucis : 1 - antennes commerciales : dispo en commerce ( dlink ... ) 2 - faites joujou avec le ricoré http://www.nantes-wireless.org/actu/article.php3?id_article=10 http://adsltele.free.fr/antenne-ricore.php ps : SHDSL : http://fr.wikipedia.org/wiki/SHDSL

@Havoc justement pfsense intègre un portail captif en plus si ajout d'abonnées possibilité d'adjoindre une nouvelle connexion dynamiquement et sans toucher au système

salam - une 2,3 Mbps SHDSL http://www.djaweb.dz/?page=offres - +ieurs hotspots wifi pour couvrir la zone desservie - une gestion des access via ipcop ou pfsense edit : 42000 da / 500 = 84 DA par personne par mois

http://www.lightreading.com/document.asp?doc_id=181792

salam nouvelle platforme : et cerise du gâteau http://www.linkedin.com/in/allaouaboughrira

lu, spécialisation auto et s'y mettre à fond : marques, tunning, maintenance, astuces, accessoires, GPS ... je pense que la diversification des thèmes est une mauvaise idée PS : ah j'ai oublié tout ce qui est lié à l'auto : trafic routier, infra ( routes, autoroutes, parkings), pompes essences, gestion rationnelle du carburant etc.... voilà ton site bien remplis là

re, une analyse du fonctionnement du psybot http://users.adam.com.au/bogaurd/PSYB0T.pdf

salam le problème est apparu il y a quelques jours, et exactement après que la promo de djaweb relative au changement de modems a commencé. plusieurs utilisateurs ont commencé à se plaindre des symptômes suivants : - Baisse de débit. - Absence de connexion ( blocage du port 80 ) la procédure adopté par les techniciens de djaweb a été de réinitialiser les modems, et par magie la connexion redevenait impeccable. mais d'autres users se sont replaint des mêmes symptômes après un certain temps d'utilisation. hier, j'ai commencé a avoir le même problème avec mes connexions ( dlink 2640 & sagem 1500WG ) jusqu'au moment où un ami m'appelle pour me dire qu'en changeant de router ( un sagem 2640 par un mt880 ) la connexion était redevenue parfaite. je décide de faire la même chose ce matin. et hop tout roule. en premier lieu j'ai suspecté un défaut de config ( MTU, encapsulation, ... ) après plusieurs essai le problème persiste. je décide de faire un factory reset du router sagem. là par magie tout rentre dans l'ordre. alors je là je me souvient de cet article ici et je suspecte que les routers sont infecté par le worm PSYBOT voir ici

bah m^me la résolution dns ne passe pas, mais par contre si tu fais un tracert vers IP ca donne ceci : C:\Users\lemrid>tracert forumdz.com Impossible de résoudre le nom du système cible forumdz.com. C:\Users\lemrid>tracert 91.121.24.26 Détermination de l'itinéraire vers 91.121.24.26 avec un maximum de 30 sauts. 1 6 ms 6 ms 6 ms . [192.168.1.1] 2 43 ms 42 ms 43 ms 41.200.240.1 3 43 ms 43 ms 42 ms 10.10.8.2 4 * * * Délai d'attente de la demande dépassé. 5 * * * Délai d'attente de la demande dépassé. 6 * * * Délai d'attente de la demande dépassé. 7 109 ms 109 ms 111 ms 193.251.169.178 8 157 ms 153 ms 155 ms 195.22.197.93 9 178 ms 174 ms 173 ms 89.221.34.153 10 184 ms 175 ms 178 ms 195.219.180.93 11 191 ms 197 ms 195 ms 195.219.150.13 12 575 ms 588 ms 603 ms 94.23.122.82 13 * * * Délai d'attente de la demande dépassé. 14 * 135 ms 131 ms 213.251.191.165 15 136 ms 135 ms 134 ms 91.121.24.26 Itinéraire déterminé.

re, le problème est réapparu depuis 3 à 4 jours et toujours aucune solution

salam erreur plateforme NGN triplay http://wwwen.zte.com.cn/en/products/wirelines/bearer_network/ng_sdh_mstp/200908/t20090826_175091.html http://wwwen.zte.com.cn/en/products/wirelines/bearer_network/ng_sdh_mstp/200908/t20090826_175092.html

salam check MP

lu, thkx pour les précisions 1 - Concernant le cache, et sachant à peu près ce que la grande majorité des internautes DZ consultent, il est rare de solliciter un site qui ne soit pas déjà indexé ds la base du dns quoique celà est bénéfique puisqu'il enrichira le cache du resolver. 2 - 512 octets x nbr de requetes x nbr d'abonnées : cela engendre un assez hugh trafic que je préfère utiliser pour d'autres purpose. 3 - concernant l'"écoute" détendez vous puisque vous serez loggé dans tout les cas ( opendns ou djaweb )

salam j'aurais souhaité que les servers soient plutôt hébergés au bled

re, je m'explique : utiliser les server dns de djaweb permettent d'interroger localement le server DNS, en d'autre termes au lieu d'aller chercher les IP correspondants au URL aux US ou FR il va les obtenir d'une machine locale. cette méthode permet : - d'optimiser les temps de réponses du resolver - d'éviter les timeout et basculment des servers DNS - de réduire le trafic, du aux requêtes dns, transitant par le backbone PS : si tlm bascule vers les servers djaweb, la différence se sentira voilà une description du processus d'interrogation de résolution des nom

re, change les au niveau du router