Querido Hélio muito obrigado pela resposta! observando a leitura do arquivo que vc me orientou primeiramente aparece isso:
pr 20 13:42:01 router kernel: [222653.554393] UDP: bad checksum. From 186.214.57.238:33622 to 187.14.17.118:61642 ulen 1446 Apr 20 13:42:44 router kernel: [222696.003130] UDP: bad checksum. From 186.214.57.238:33622 to 187.14.17.118:61642 ulen 1446 Apr 20 13:42:52 router kernel: [222704.699810] UDP: bad checksum. From 186.214.57.238:33622 to 187.14.17.118:61642 ulen 1446 Apr 20 13:42:52 router kernel: [222704.763835] UDP: bad checksum. From 186.214.57.238:33622 to 187.14.17.118:61642 ulen 1446 Apr 20 13:43:24 router kernel: [222736.678546] UDP: bad checksum. From 186.214.57.238:33622 to 187.14.17.118:61642 ulen 1446 Apr 20 13:43:27 router kernel: [222739.618334] UDP: bad checksum. From 186.214.57.238:33622 to 187.14.17.118:61642 ulen 1446 Apr 20 13:43:37 router kernel: [222749.741859] UDP: bad checksum. From 186.214.57.238:33622 to 187.14.17.118:61642 ulen 1446 Apr 20 13:48:20 router kernel: [223032.507520] UDP: bad checksum. From 186.214.57.238:33622 to 187.14.17.118:61642 ulen 1446 depois aparece isso: Apr 20 22:40:32 router kernel: [254964.820002] ------------[ cut here ]------------ Apr 20 22:40:32 router kernel: [254964.820002] WARNING: at net/sched/sch_generic.c:222 dev_watchdog+0xa6/0xfb() Apr 20 22:40:32 router kernel: [254964.820002] Modules linked in: wlan_wep bridge wlan_scan_ap ipt_REDIRECT ipt_MASQUERADE iptable_nat nf_nat nf_conntrack_ipv4 nf_conntrack iptable_filter xt_TCPMSS xt_tcpmss xt_tcpudp iptable_mangle ip_tables x_tables pppoe pppox ppp_generic slhc ipv6 loop wlan_scan_sta ath_rate_sample ath_pci wlan ath_hal(P) parport_pc parport snd_pcsp k8temp shpchp pci_hotplug snd_intel8x0 snd_ac97_codec ac97_bus snd_pcm snd_timer snd soundcore snd_page_alloc button i2c_nforce2 i2c_core evdev ext3 jbd mbcache ide_cd_mod cdrom ide_disk ata_generic sata_nv libata scsi_mod dock 3c59x mii ide_pci_generic amd74xx ide_core forcedeth ehci_hcd ohci_hcd thermal processor fan thermal_sys [last unloaded: scsi_wait_scan] Apr 20 22:40:32 router kernel: [254964.820002] Pid: 0, comm: swapper Tainted: P 2.6.26-2-amd64 #1 Apr 20 22:40:32 router kernel: [254964.820002] Apr 20 22:40:32 router kernel: [254964.820002] Call Trace: Apr 20 22:40:32 router kernel: [254964.820002] <IRQ> [<ffffffff80234958>] warn_on_slowpath+0x51/0x7a Apr 20 22:40:32 router kernel: [254964.820002] [<ffffffffa01f870f>] :ath_hal:zz00057cd9+0x150/0x15f Apr 20 22:40:32 router kernel: [254964.820002] [<ffffffffa01e3e33>] :ath_hal:ath_hal_process_noisefloor+0x14d/0x2fa1 Apr 20 22:40:32 router kernel: [254964.820002] [<ffffffffa01e3c91>] :ath_hal:zz00007c1a+0x1d/0x72 Apr 20 22:40:32 router kernel: [254964.820002] [<ffffffffa02953d3>] :ath_pci:ath_set_ack_bitrate+0x226/0x233 Apr 20 22:40:32 router kernel: [254964.820002] [<ffffffffa0276b13>] :ath_pci:ath_reset+0x2c8/0x314 Apr 20 22:40:32 router kernel: [254964.820002] [<ffffffff803ccc32>] dev_watchdog+0x0/0xfb Apr 20 22:40:32 router kernel: [254964.820002] [<ffffffff803cccd8>] dev_watchdog+0xa6/0xfb Apr 20 22:40:32 router kernel: [254964.820002] [<ffffffff803ccc32>] dev_watchdog+0x0/0xfb Apr 20 22:40:32 router kernel: [254964.820002] [<ffffffff8023ca01>] run_timer_softirq+0x16a/0x1e2 Apr 20 22:40:32 router kernel: [254964.820002] [<ffffffff802393cd>] __do_softirq+0x5c/0xd1 Apr 20 22:40:32 router kernel: [254964.820002] [<ffffffff8020d2dc>] call_softirq+0x1c/0x28 Apr 20 22:40:32 router kernel: [254964.820002] [<ffffffff8020f3e8>] do_softirq+0x3c/0x81 Apr 20 22:40:32 router kernel: [254964.820002] [<ffffffff8023932b>] irq_exit+0x3f/0x85 Apr 20 22:40:32 router kernel: [254964.820002] [<ffffffff8021aaab>] smp_apic_timer_interrupt+0x8c/0xa4 Apr 20 22:40:32 router kernel: [254964.820002] [<ffffffff8020b0ae>] default_idle+0x0/0x46 Apr 20 22:40:32 router kernel: [254964.820002] [<ffffffff8020cd02>] apic_timer_interrupt+0x72/0x80 Apr 20 22:40:32 router kernel: [254964.820002] <EOI> [<ffffffff8021a857>] lapic_next_event+0x0/0x13 Apr 20 22:40:32 router kernel: [254964.820002] [<ffffffff8021eb64>] native_safe_halt+0x2/0x3 Apr 20 22:40:32 router kernel: [254964.820002] [<ffffffff8020b0d8>] default_idle+0x2a/0x46 e em seguida fica tudo assim: Apr 20 22:40:32 router kernel: [254964.820002] ---[ end trace 6ab9d78664740dd3 ]--- Apr 20 22:40:42 router kernel: [254974.816007] NETDEV WATCHDOG: wifi0: transmit timed out Apr 20 22:40:52 router kernel: [254984.816008] NETDEV WATCHDOG: wifi0: transmit timed out Apr 20 22:41:02 router kernel: [254994.816007] NETDEV WATCHDOG: wifi0: transmit timed out Apr 20 22:41:17 router kernel: [255009.816007] NETDEV WATCHDOG: wifi0: transmit timed out Apr 20 22:41:27 router kernel: [255019.816007] NETDEV WATCHDOG: wifi0: transmit timed out Apr 20 22:41:37 router kernel: [255029.816007] NETDEV WATCHDOG: wifi0: transmit timed out Apr 20 22:41:47 router kernel: [255039.816007] NETDEV WATCHDOG: wifi0: transmit timed out Apr 20 22:41:57 router kernel: [255049.816008] NETDEV WATCHDOG: wifi0: transmit timed out Apr 20 22:42:07 router kernel: [255059.816007] NETDEV WATCHDOG: wifi0: transmit timed out Apr 20 22:42:17 router kernel: [255069.816006] NETDEV WATCHDOG: wifi0: transmit timed out Apr 20 22:42:27 router kernel: [255079.816009] NETDEV WATCHDOG: wifi0: transmit timed out Apr 20 22:42:37 router kernel: [255089.816007] NETDEV WATCHDOG: wifi0: transmit timed out Isso é o que aparece no kern.log. O que eu poderia fazer de posse nestas informações. Abraços, Moksha Em 21 de abril de 2011 20:34, Helio Loureiro <[email protected]>escreveu: > > >> Para dar fim ao meu calvário e lembrando dos posts anteriores que coloquei >> aqui de como transformar meu Debian em AP, resolvi retroceder um pouco e >> instalar o Debian 5 visto que ele ainda mantém os pacotes MADWIFI. Pois bem >> consegui restabelecer este meu AP como antes quando era o 4.0 Etch, mas, >> está acontecendo uma coisa muito chata, a minha rede sem fio não fica no ar >> por muito tempo, eu cenecto por alguns minutos e de repente ela sai e não >> reconhece mais as estações nela antes conectadas daí tenho que re-startar o >> scrip e aí sim a rede volta ao normal e garanto que neste script não tem >> nada de diferente que já existia antes quando eu já usava ele e a rede >> ficava uptime direto. Será que é pq eu agora estou usando o Debian 64 bits e >> o anterior era 32 bits? Não tenho idéia do que possa estar acontecendo, >> agradeço desde já alguma ajuda. Abraços, >> >> > Vc precisa enviar a saída do dmesg ou /var/log/kern.log do momento em que o > AP para de funcionar. > > Tá com cara de bug de kernel com firmware que vc tá usando. Pq não tenta > pegar o kernel 2.6.38? Pelo changelog, parece que tem várias atualizações > para chips atheros. > > []´s > Helio Loureiro > http://helio.loureiro.eng.br > http://hloureiro.multiply.com > http://twitter.com/helioloureiro > >
