Nettet på mamma sin maskin blir sirup når jeg laster ned med uTorrent?

RamGuy · 17. november 2008

Okay, jeg trenger litt hjelp med hjemmenettverket vårt!

Har forsøkt å sette opp vår D-Link DIR-655 Rev3 slik at Mamma og Jan (stefar) skal ha absolutt høyest prioritet på nettverket?

Slik at om jeg laster ned med uTorrent osv.. Hva det enn måtte være så skal de ha en optimal nettopplevelse, UANSETT HVA!

Så om jeg laster ned en film fra thepiratebay.org på full guffe og nettet da i teorien strupes fullstendig så skal mamma og jan i det de kobler seg på automatisk prioriteres å få den trafikken de trenger automatisk!

Har forsøkt å få til nettopp dette over lengre tid men det ser ikke ut til å ville fungere i det hele tatt?

Hva som skjer er jeg neimen meg ikke sikker på..

For det første så har jeg satt opp en tidsplan på uTorrent, og de tidene på døgnet hvor folk faktisk er oppe på nettet her så er uTorrent cappet til 250kbps ned og 8kbps opp, og når nettlinja vår er en 5000 / 500 linje fra Telenor så burde jo ikke uTorrent kunne gjøre nettet helt sirup i utgangspunktet?

Samtidig som det så er alle mine porter åpne, brannmur deaktivert og mamma og jan har en prio på 1 på DIR-655 sin QoS på alt de måtte finne på å gjøre på nettet?

Til tross for dette så påstår mamma at i kveld så ble hele nettet sirup?

Hun påstår faktisk at ting fungerer bedre med vår gamle Linksys WRT54Gv5 (ja, det som kjøre VMWorks og har lite RAM!) hvordan er det mulig?

Og det som er veldig rart er at jeg selv ikke opplever noen problemer på verken min bærbare eller stasjonære maskin?

Jeg har ikke noen prioritet i QoS til DIR-655, og mens jeg laste ned med uTorrent så opplever ikke jeg noen større problemer? Latencyen i WoW går litt opp men ikke så alt for voldsomt, jeg åpner nettsider uten større problemer, kan faktisk laste ned fra nettet uten at det går skremmende tregt? Mens mamma på sin PC påstår at alt er fullstendig sirup?

Hva kan årsaken til dette være? Hva gjør jeg feil?

17. november 2008

har du prøvd å kjøre hastighetstest på de forskjellige pc'ene når du laster ned og ikke da, for å se at det faktisk går tregere nå du laster ned? er ingen ekspert så kan nok ikke hjelpe deg, men du kan nå begynne med å sjekke at det mora di sier faktisk stemmer? kanskje hun ikke liker nedlastingen og dette er hennes måte for å få deg til å "slutte" med det? (ulovlig nedlasting og piratkopiering er forøvrig fy fy å diskutere på forumet)

men nå er det vel ikke den faktiske hastigheten opp/ned som kveler hastighet når det gjelder torrents, men antall tilkoblinger. dette kan begrenses i de fleste klienter. dersom du laster ned en torrent (merk: torrent er i seg selv ikke ulovlig), og er koblet til en drøss med seeds/leechers, så vil dette kvele antall tilgjengelige tilkoblinger for annen trafikk.

dette ble noe knotete forklart, men jeg er meget trøtt (og tar jeg feil, så må noen andre bare rette på meg)

aksjonist · 18. november 2008

En mulighet er å bytte router til en Linksys WRT54GL;

http://www.squidoo.com/bandwidth-management

http://lifehacker.com/344765/turn-your-60-...ter-with-tomato

http://www.datakjeden.no/PartDetail.aspx?q...bc:36180%3br:pg

Har den selv og synes den er meget bra.

RamGuy · 19. november 2008

Fikk oppleve dette fenomenet på min onkel og mamma sin maskin idag..

De er koblet til routeren, men av en eller annen merkelig grunn så får de så vidt åpnet en nettside de første 5minuttene? Så ser det hele ut til å bedre seg etterhvert?

Virker som dette fenomenet kun eksisterer med det trådløse, for jeg opplever aldri noe slikt via kabel og det er ikke selve nettet som er tregt ettersom det overhode ikke finnes problemer hos meg, er akkurat som det trådløse "lagger" noe voldsomt i starten?

Lars Dongeri Oppholdsnes · 20. november 2008

Du kan prøve å redusere antall tilkoblinger i torrentprogrammet. Prøv å sett det til 150 tilkoblinger totalt (globalt).

Har du kryptert det trådløse nettet? Det bør være kryptert med WPA slik at ingen kan misbruke det.

Når det gjelder trådløst så kan det være støy som forårsaker tregt nett. Prøv å bytt kanal i router (velg en i motsatt ende av skalaen).

En annen ting du kan prøve er å gå inn på ADVANCED og slå av Wifi Protected Network i router for å se om det hjelper.

Endret 20. november 2008 av la7dfa.com

RamGuy · 23. november 2008

Har for øyeblikket redusert connections til fattige 70..

Nettverket kjører WPA2 only med AES kryptering? Kjører i g / n modus med extra wireless security deaktivert.

Har forsøkt med auto valg av kanal, samtidig forsøkt manuelt fra den ene enden av skalaen og over til den andre men ser ikke ut til å være store forskjellen uansett hva jeg velger, er bare 2x andre trådløse nettverk i nærheten uansett

Wifi Protected Network er deaktivert, sammen med wish og litt sånt som jeg ikke så behovet for å har hørt skal ha mer negativ innvirkning enn positiv. Kjører nå også firmware 1.11EU da jeg føler den ser ut til å fungere hakket bedre enn 1.21, men dog ikke godt nok?

Det er helt klart noe merkelig med det trådløse her..

Sitter på en Lenovo ThinkPad SL-300 og har 150mpbs og ting fungerer helt fint, så starter jeg litt torrent nedlasting uten at det har spesielt negativt inpack på selve ytelse på nettverket, men min trådløse tilkobling forsvinner plutselig av seg selv?

Det er ikke routeren som har restartet seg for jeg mister ikke kontaktet på min stasjonære (kabel)?

Men det trådløse bare forsvinner, og det selv om nettverket tilsynelatende 2sekunder etterpå fremdeles er tilgengjelig?

Dette fenomenet ser ikke ut til å skje hvis jeg ikke mindre kjører uTorrent på min stasjonære?

RamGuy · 23. november 2008

Nå datt nettet nettopp ut på min stasjonære, uten noen synlig grunn?

Ikke noe spesielt be utført på nettet (annet enn litt World of Warcraft), null torrent, kun min maskin som er tilkoblet via kabel så eneste som sto på var FireFox og World of Warcraft fra kun min maskin som har alle porter åpnet?

Tok en rask kopi av det siste som sto i loggen om noen kan tyde noe ut av den:

[iNFO] Sat Nov 22 04:52:50 2008 Blocked incoming TCP packet from 85.12.17.139:80 to 192.168.0.3:1421 as FIN:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:52:39 2008 Blocked incoming TCP packet from 85.12.17.139:80 to 192.168.0.3:1419 as FIN:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:52:25 2008 Blocked incoming TCP packet from 85.12.17.139:80 to 192.168.0.3:1422 as FIN:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:52:16 2008 Blocked incoming TCP packet from 85.12.17.139:80 to 192.168.0.3:1420 as FIN:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:52:15 2008 Blocked incoming TCP packet from 85.12.17.139:80 to 192.168.0.3:1423 as FIN:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:52:06 2008 Blocked incoming TCP packet from 85.12.17.139:80 to 192.168.0.3:1424 as FIN:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:51:46 2008 Blocked incoming TCP packet from 85.12.17.139:80 to 192.168.0.3:1421 as FIN:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:51:35 2008 Blocked incoming TCP packet from 85.12.17.139:80 to 192.168.0.3:1419 as FIN:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:51:21 2008 Blocked incoming TCP packet from 85.12.17.139:80 to 192.168.0.3:1422 as FIN:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:51:12 2008 Blocked incoming TCP packet from 85.12.17.139:80 to 192.168.0.3:1420 as FIN:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:51:11 2008 Blocked incoming TCP packet from 85.12.17.139:80 to 192.168.0.3:1423 as FIN:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:51:02 2008 Blocked incoming TCP packet from 85.12.17.139:80 to 192.168.0.3:1424 as FIN:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:50:42 2008 Blocked incoming TCP packet from 85.12.17.139:80 to 192.168.0.3:1421 as FIN:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:50:38 2008 Wireless system with MAC address 002191EA9535 disconnected for reason: AP maybe crash...

[iNFO] Sat Nov 22 04:50:31 2008 Blocked incoming TCP packet from 85.12.17.139:80 to 192.168.0.3:1419 as FIN:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:50:23 2008 Blocked incoming TCP packet from 85.12.17.139:80 to 192.168.0.3:1422 as FIN:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:50:19 2008 Blocked incoming TCP packet from 85.12.17.139:80 to 192.168.0.3:1420 as FIN:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:50:18 2008 Blocked incoming TCP packet from 85.12.17.139:80 to 192.168.0.3:1423 as FIN:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:50:17 2008 Blocked incoming TCP packet from 80.239.181.75:3724 to 192.168.0.3:3656 as PSH:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:50:17 2008 Blocked incoming TCP packet from 80.239.181.75:3724 to 192.168.0.3:3661 as PSH:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:50:14 2008 Blocked incoming TCP packet from 85.12.17.139:80 to 192.168.0.3:1424 as FIN:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:50:04 2008 Wireless system with MAC address 002191EA9535 disconnected for reason: AP maybe crash...

[iNFO] Sat Nov 22 04:50:04 2008 Blocked incoming TCP packet from 85.12.17.139:80 to 192.168.0.3:1421 as FIN:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:49:59 2008 Blocked incoming TCP packet from 85.12.17.139:80 to 192.168.0.3:1419 as FIN:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:49:57 2008 Log viewed by IP address 192.168.1.149

[iNFO] Sat Nov 22 04:49:54 2008 Blocked incoming TCP packet from 85.12.17.139:80 to 192.168.0.3:1422 as FIN:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:49:54 2008 Allowed configuration authentication by IP address 192.168.1.149

[iNFO] Sat Nov 22 04:49:52 2008 Blocked incoming TCP packet from 85.12.17.139:80 to 192.168.0.3:1420 as FIN:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:49:51 2008 Blocked incoming TCP packet from 85.12.17.139:80 to 192.168.0.3:1423 as FIN:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:49:50 2008 Blocked incoming TCP packet from 85.12.17.139:80 to 192.168.0.3:1424 as FIN:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:49:45 2008 Blocked incoming TCP packet from 85.12.17.139:80 to 192.168.0.3:1421 as FIN:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:49:44 2008 Blocked incoming TCP packet from 80.239.181.75:3724 to 192.168.0.3:3656 as PSH:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:49:44 2008 Blocked incoming TCP packet from 80.239.181.75:3724 to 192.168.0.3:3661 as PSH:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:49:40 2008 Blocked incoming TCP packet from 85.12.17.139:80 to 192.168.0.3:1422 as FIN:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:49:39 2008 Blocked incoming TCP packet from 85.12.17.139:80 to 192.168.0.3:1420 as FIN:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:49:38 2008 Blocked incoming TCP packet from 85.12.17.139:80 to 192.168.0.3:1423 as FIN:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:49:38 2008 Blocked incoming TCP packet from 85.12.17.139:80 to 192.168.0.3:1424 as FIN:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:49:35 2008 Blocked incoming TCP packet from 85.12.17.139:80 to 192.168.0.3:1421 as FIN:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:49:34 2008 Blocked incoming TCP packet from 85.12.17.139:80 to 192.168.0.3:1419 as FIN:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:49:32 2008 Blocked incoming TCP packet from 85.12.17.139:80 to 192.168.0.3:1422 as FIN:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:49:32 2008 Blocked incoming TCP packet from 85.12.17.139:80 to 192.168.0.3:1420 as FIN:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:49:31 2008 Blocked incoming TCP packet from 85.12.17.139:80 to 192.168.0.3:1424 as FIN:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:49:31 2008 Blocked incoming TCP packet from 85.12.17.139:80 to 192.168.0.3:1423 as FIN:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:49:31 2008 Blocked outgoing TCP packet from 192.168.1.149:3656 to 80.239.181.75:3724 as PSH:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:49:30 2008 Blocked incoming TCP packet from 85.12.17.139:80 to 192.168.0.3:1421 as FIN:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:49:30 2008 Blocked incoming TCP packet from 85.12.17.139:80 to 192.168.0.3:1419 as FIN:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:49:28 2008 Blocked incoming TCP packet from 80.239.181.75:3724 to 192.168.0.3:3656 as PSH:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:49:28 2008 Blocked incoming TCP packet from 80.239.181.75:3724 to 192.168.0.3:3661 as PSH:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:49:27 2008 Blocked incoming TCP packet from 85.12.17.139:80 to 192.168.0.3:1422 as FIN:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:49:27 2008 Blocked incoming TCP packet from 85.12.17.139:80 to 192.168.0.3:1420 as FIN:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:49:26 2008 Blocked incoming TCP packet from 85.12.17.139:80 to 192.168.0.3:1421 as FIN:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:49:26 2008 Blocked incoming TCP packet from 85.12.17.139:80 to 192.168.0.3:1423 as FIN:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:49:26 2008 Blocked incoming TCP packet from 85.12.17.139:80 to 192.168.0.3:1419 as FIN:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:49:25 2008 Blocked incoming TCP packet from 85.12.17.139:80 to 192.168.0.3:1422 as FIN:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:49:25 2008 Blocked incoming TCP packet from 85.12.17.139:80 to 192.168.0.3:1420 as FIN:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:49:24 2008 Starting DHCP server

[iNFO] Sat Nov 22 04:49:24 2008 Blocked incoming TCP packet from 85.12.17.139:80 to 192.168.0.3:1424 as FIN:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:49:24 2008 Blocked incoming TCP packet from 85.12.17.139:80 to 192.168.0.3:1421 as FIN:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:49:24 2008 Blocked incoming TCP packet from 85.12.17.139:80 to 192.168.0.3:1419 as FIN:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:49:23 2008 Blocked incoming TCP packet from 85.12.17.139:80 to 192.168.0.3:1423 as FIN:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:49:23 2008 Blocked incoming TCP packet from 85.12.17.139:80 to 192.168.0.3:1422 as FIN:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:49:23 2008 Blocked incoming TCP packet from 85.12.17.139:80 to 192.168.0.3:1420 as FIN:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:49:23 2008 Blocked incoming TCP packet from 85.12.17.139:80 to 192.168.0.3:1424 as FIN:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:49:23 2008 Blocked incoming TCP packet from 85.12.17.139:80 to 192.168.0.3:1421 as FIN:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:49:23 2008 Blocked incoming TCP packet from 85.12.17.139:80 to 192.168.0.3:1419 as FIN:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:49:22 2008 Blocked incoming TCP packet from 85.12.17.139:80 to 192.168.0.3:1420 as FIN:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:49:22 2008 Blocked incoming TCP packet from 85.12.17.139:80 to 192.168.0.3:1422 as FIN:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:49:22 2008 Blocked incoming TCP packet from 85.12.17.139:80 to 192.168.0.3:1424 as FIN:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:49:22 2008 Blocked incoming TCP packet from 85.12.17.139:80 to 192.168.0.3:1419 as FIN:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:49:22 2008 Blocked incoming TCP packet from 85.12.17.139:80 to 192.168.0.3:1421 as FIN:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:49:22 2008 Blocked incoming TCP packet from 85.12.17.139:80 to 192.168.0.3:1423 as FIN:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:49:22 2008 Blocked incoming TCP packet from 85.12.17.139:80 to 192.168.0.3:1420 as FIN:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:49:22 2008 Blocked incoming TCP packet from 85.12.17.139:80 to 192.168.0.3:1422 as FIN:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:49:22 2008 Blocked outgoing TCP packet from 192.168.1.149:1440 to 66.135.59.229:80 as FIN:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:49:22 2008 Blocked incoming TCP packet from 85.12.17.139:80 to 192.168.0.3:1419 as FIN:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:49:22 2008 Blocked incoming TCP packet from 85.12.17.139:80 to 192.168.0.3:1421 as FIN:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:49:21 2008 Blocked incoming TCP packet from 85.12.17.139:80 to 192.168.0.3:1423 as FIN:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:49:20 2008 Blocked outgoing TCP packet from 192.168.1.149:3661 to 80.239.181.75:3724 as PSH:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:49:20 2008 Blocked incoming TCP packet from 80.239.181.75:3724 to 192.168.0.3:3656 as PSH:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:49:19 2008 Blocked incoming TCP packet from 80.239.181.75:3724 to 192.168.0.3:3661 as PSH:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:49:18 2008 Latest firmware version 1.20 is available

[iNFO] Sat Nov 22 04:49:18 2008 Starting WAN Services

[iNFO] Sat Nov 22 04:49:18 2008 Estimating speed of WAN interface

[iNFO] Sat Nov 22 04:49:18 2008 WAN interface is up. Connection to Internet established with IP Address 192.168.0.3 and default gateway 192.168.0.1

[iNFO] Sat Nov 22 04:49:18 2008 Bringing up WAN using Static IP Address

[iNFO] Sat Nov 22 04:49:18 2008 WAN interface cable has been connected

[iNFO] Sat Nov 22 04:49:17 2008 LAN interface is up

[iNFO] Sat Nov 22 04:49:17 2008 LAN Ethernet Carrier Detected

[iNFO] Sat Nov 22 04:49:16 2008 Device initialized

[WARN] Sat Nov 22 04:49:16 2008 gw_wireless_schedule init

[iNFO] Sat Nov 22 04:49:16 2008 Wireless Link is up

[iNFO] Sat Nov 22 04:49:15 2008 No Internet access policy is in effect. Unrestricted Internet access allowed to everyone

[iNFO] Thu Jan 01 01:00:00 1970 Loaded configuration from non-volatile memory

RamGuy · 23. november 2008

Og der forsvant nett-tilgangen i samme sekund som jeg åpnet FireFox?

Har på følelsen at det er et eller annet som gjør at min DIR-655 av en eller annen merkelig grunn bestemt blokker WAN eller et eller annet når noe spesifikt skjer, og dette ønsker jeg selvsagt å få satt en stopper for!

Sinnssykt irriterende at nettet detter ut når du kun gjør helt elementære ting?

Når jeg drev å lastet ned drivere til min Lenovo ThinkPad SL-300 og litt sånt i går så viste nettet en tendens til å dette ut under nedlasting via FireFox? Dønn stabilt når jeg kun kjører World of Warcraft og ingenting annet (om vi ser bort i fra at min bærbare mistet forbindelse med det trådløse støtt og stadig) men når jeg nå altså bare åpnet FireFox mens World of Warcraft kjørt så datt nettet ut sekundet FireFox åpnet seg? En sammenheng?

Nettet ser ikke ut til å dette ut om jeg kjører uTorrent heller, problemene ser faktisk ut til å ha noen forbindelser knyttet opp mot FireFox? Nedlastinger via FireFox ser tidvis ut til å få nettet til å dette ut? Og nå siste bare datt det ut av å åpne FireFox?

Hadde liggende tendenser med min DGL-4500 en periode før flash minnet på den ble defekt, grusomt irriterende!

Og jeg vil svært gjerne finne ut hva som skjer og hvorfor det skjer!

Ny log:

Klikk for å se/fjerne spoilerteksten nedenfor

[iNFO] Sat Nov 22 04:57:43 2008 Wireless system with MAC address 002191EA9535 disconnected for reason: AP maybe crash...

[iNFO] Sat Nov 22 04:54:45 2008 Above message repeated 3 times

[iNFO] Sat Nov 22 04:54:13 2008 Blocked outgoing TCP packet from 192.168.1.149:1551 to 74.125.77.102:80 as FIN:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:54:09 2008 Wireless system with MAC address 002191EA9535 disconnected for reason: AP maybe crash...

[iNFO] Sat Nov 22 04:53:22 2008 Above message repeated 2 times

[iNFO] Sat Nov 22 04:52:43 2008 Blocked outgoing TCP packet from 192.168.1.149:1541 to 194.24.252.216:80 as PSH:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:52:43 2008 Blocked outgoing TCP packet from 192.168.1.149:1546 to 194.24.252.216:80 as PSH:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:52:43 2008 Blocked outgoing TCP packet from 192.168.1.149:1545 to 194.24.252.216:80 as PSH:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:52:43 2008 Blocked outgoing TCP packet from 192.168.1.149:1544 to 194.24.252.216:80 as PSH:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:52:43 2008 Blocked outgoing TCP packet from 192.168.1.149:1543 to 194.24.252.216:80 as PSH:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:52:43 2008 Blocked outgoing TCP packet from 192.168.1.149:1542 to 194.24.252.216:80 as PSH:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:52:42 2008 Wireless system with MAC address 002191EA9535 disconnected for reason: AP maybe crash...

[iNFO] Sat Nov 22 04:52:00 2008 Above message repeated 1 times

[iNFO] Sat Nov 22 04:51:57 2008 Log viewed by IP address 192.168.1.149

[iNFO] Sat Nov 22 04:51:53 2008 Allowed configuration authentication by IP address 192.168.1.149

[iNFO] Sat Nov 22 04:51:10 2008 Blocked incoming TCP packet from 194.24.252.223:80 to 192.168.0.3:1534 as FIN:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:50:49 2008 Blocked incoming TCP packet from 74.125.100.35:80 to 192.168.0.3:1552 as FIN:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:50:48 2008 Wireless system with MAC address 002191EA9535 disconnected for reason: AP maybe crash...

[iNFO] Sat Nov 22 04:50:28 2008 Blocked incoming TCP packet from 194.24.252.216:80 to 192.168.0.3:1541 as FIN:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:50:27 2008 Blocked incoming TCP packet from 194.24.252.216:80 to 192.168.0.3:1542 as FIN:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:50:25 2008 Blocked incoming TCP packet from 194.24.252.216:80 to 192.168.0.3:1543 as FIN:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:50:24 2008 Blocked incoming TCP packet from 194.24.252.216:80 to 192.168.0.3:1546 as FIN:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:50:22 2008 Blocked incoming TCP packet from 194.24.252.216:80 to 192.168.0.3:1545 as FIN:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:50:22 2008 Blocked incoming TCP packet from 194.24.252.216:80 to 192.168.0.3:1544 as FIN:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:50:17 2008 Blocked incoming TCP packet from 80.239.181.75:3724 to 192.168.0.3:1518 as PSH:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:50:16 2008 Blocked incoming TCP packet from 80.239.181.75:3724 to 192.168.0.3:1468 as PSH:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:50:13 2008 Blocked incoming TCP packet from 74.125.100.35:80 to 192.168.0.3:1552 as FIN:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:50:11 2008 Blocked incoming TCP packet from 194.24.252.223:80 to 192.168.0.3:1534 as FIN:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:50:09 2008 Wireless system with MAC address 002191EA9535 disconnected for reason: AP maybe crash...

[iNFO] Sat Nov 22 04:50:09 2008 Blocked outgoing TCP packet from 192.168.1.149:1552 to 74.125.100.35:80 as PSH:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:49:55 2008 Blocked incoming TCP packet from 74.125.100.35:80 to 192.168.0.3:1552 as FIN:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:49:55 2008 Blocked incoming TCP packet from 194.24.252.216:80 to 192.168.0.3:1541 as FIN:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:49:54 2008 Blocked incoming TCP packet from 194.24.252.216:80 to 192.168.0.3:1542 as FIN:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:49:53 2008 Blocked incoming TCP packet from 194.24.252.216:80 to 192.168.0.3:1543 as FIN:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:49:53 2008 Blocked incoming TCP packet from 194.24.252.216:80 to 192.168.0.3:1546 as FIN:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:49:52 2008 Blocked incoming TCP packet from 194.24.252.216:80 to 192.168.0.3:1545 as FIN:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:49:52 2008 Blocked incoming TCP packet from 194.24.252.216:80 to 192.168.0.3:1544 as FIN:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:49:46 2008 Blocked incoming TCP packet from 74.125.100.35:80 to 192.168.0.3:1552 as FIN:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:49:44 2008 Blocked incoming TCP packet from 80.239.181.75:3724 to 192.168.0.3:1518 as PSH:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:49:43 2008 Blocked incoming TCP packet from 80.239.181.75:3724 to 192.168.0.3:1468 as PSH:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:49:42 2008 Blocked incoming TCP packet from 194.24.252.223:80 to 192.168.0.3:1534 as FIN:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:49:42 2008 Blocked incoming TCP packet from 74.125.100.35:80 to 192.168.0.3:1552 as FIN:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:49:38 2008 Above message repeated 2 times

[iNFO] Sat Nov 22 04:49:38 2008 Blocked incoming TCP packet from 194.24.252.216:80 to 192.168.0.3:1541 as FIN:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:49:38 2008 Blocked incoming TCP packet from 74.125.100.35:80 to 192.168.0.3:1552 as FIN:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:49:38 2008 Blocked incoming TCP packet from 194.24.252.216:80 to 192.168.0.3:1542 as FIN:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:49:37 2008 Blocked incoming TCP packet from 74.125.100.35:80 to 192.168.0.3:1552 as FIN:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:49:37 2008 Blocked incoming TCP packet from 194.24.252.216:80 to 192.168.0.3:1543 as FIN:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:49:37 2008 Blocked incoming TCP packet from 194.24.252.216:80 to 192.168.0.3:1546 as FIN:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:49:36 2008 Blocked incoming TCP packet from 194.24.252.216:80 to 192.168.0.3:1545 as FIN:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:49:36 2008 Blocked incoming TCP packet from 194.24.252.216:80 to 192.168.0.3:1544 as FIN:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:49:33 2008 Blocked incoming TCP packet from 74.125.77.102:80 to 192.168.0.3:1551 as FIN:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:49:30 2008 Blocked incoming TCP packet from 194.24.252.216:80 to 192.168.0.3:1541 as FIN:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:49:30 2008 Blocked incoming TCP packet from 194.24.252.216:80 to 192.168.0.3:1542 as FIN:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:49:29 2008 Blocked incoming TCP packet from 194.24.252.216:80 to 192.168.0.3:1543 as FIN:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:49:29 2008 Blocked incoming TCP packet from 194.24.252.216:80 to 192.168.0.3:1546 as FIN:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:49:29 2008 Blocked incoming TCP packet from 194.24.252.216:80 to 192.168.0.3:1545 as FIN:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:49:29 2008 Blocked incoming TCP packet from 194.24.252.216:80 to 192.168.0.3:1544 as FIN:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:49:28 2008 Blocked incoming TCP packet from 80.239.181.75:3724 to 192.168.0.3:1518 as PSH:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:49:27 2008 Blocked incoming TCP packet from 80.239.181.75:3724 to 192.168.0.3:1468 as PSH:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:49:27 2008 Blocked incoming TCP packet from 194.24.252.223:80 to 192.168.0.3:1534 as FIN:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:49:27 2008 Blocked outgoing TCP packet from 192.168.1.149:1534 to 194.24.252.223:80 as FIN:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:49:26 2008 Blocked outgoing TCP packet from 192.168.1.149:1468 to 80.239.181.75:3724 as PSH:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:49:25 2008 Blocked incoming TCP packet from 194.24.252.216:80 to 192.168.0.3:1541 as FIN:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:49:25 2008 Blocked incoming TCP packet from 194.24.252.216:80 to 192.168.0.3:1542 as FIN:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:49:25 2008 Blocked incoming TCP packet from 194.24.252.216:80 to 192.168.0.3:1543 as FIN:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:49:25 2008 Blocked incoming TCP packet from 194.24.252.216:80 to 192.168.0.3:1546 as FIN:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:49:25 2008 Blocked incoming TCP packet from 194.24.252.216:80 to 192.168.0.3:1545 as FIN:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:49:25 2008 Blocked incoming TCP packet from 194.24.252.216:80 to 192.168.0.3:1544 as FIN:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:49:24 2008 Starting DHCP server

[iNFO] Sat Nov 22 04:49:24 2008 Blocked incoming TCP packet from 74.125.77.102:80 to 192.168.0.3:1551 as FIN:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:49:23 2008 Blocked incoming TCP packet from 194.24.252.216:80 to 192.168.0.3:1541 as FIN:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:49:23 2008 Blocked incoming TCP packet from 194.24.252.216:80 to 192.168.0.3:1542 as FIN:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:49:23 2008 Blocked incoming TCP packet from 194.24.252.216:80 to 192.168.0.3:1543 as FIN:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:49:23 2008 Blocked incoming TCP packet from 194.24.252.216:80 to 192.168.0.3:1546 as FIN:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:49:23 2008 Blocked incoming TCP packet from 194.24.252.216:80 to 192.168.0.3:1545 as FIN:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:49:23 2008 Blocked incoming TCP packet from 194.24.252.216:80 to 192.168.0.3:1544 as FIN:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:49:22 2008 Blocked incoming TCP packet from 194.24.252.216:80 to 192.168.0.3:1541 as FIN:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:49:22 2008 Blocked incoming TCP packet from 194.24.252.216:80 to 192.168.0.3:1542 as FIN:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:49:22 2008 Blocked incoming TCP packet from 194.24.252.216:80 to 192.168.0.3:1543 as FIN:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:49:22 2008 Blocked incoming TCP packet from 194.24.252.216:80 to 192.168.0.3:1546 as FIN:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:49:22 2008 Blocked incoming TCP packet from 194.24.252.216:80 to 192.168.0.3:1545 as FIN:ACK received but there is no active connection

[iNFO] Sat Nov 22 04:49:22 2008 Blocked incoming TCP packet from 194.24.252.216:80 to 192.168.0.3:1544 as FIN:ACK received but there is no active connection