Jul/07/2006 07:00:17 Drop TCP packet from WAN 200.122.107.174:52435 81.196.143.36:2086 Rule: Default deny Jul/07/2006 07:00:10 Drop TCP packet from WAN 200.122.107.174:52435 81.196.143.36:2086 Rule: Default deny Jul/07/2006 07:00:07 Drop TCP packet from WAN 200.122.107.174:52435 81.196.143.36:2086 Rule: Default deny Jul/07/2006 06:59:43 Drop UDP packet from WAN 200.122.107.174:2086 81.196.143.36:2086 Rule: Default deny Jul/07/2006 06:59:39 Drop TCP packet from WAN 200.122.107.174:52383 81.196.143.36:2086 Rule: Default deny Jul/07/2006 06:59:20 Drop UDP packet from WAN 200.122.107.174:2086 81.196.143.36:2086 Rule: Default deny Jul/07/2006 06:59:14 Drop TCP packet from WAN 200.122.107.174:52383 81.196.143.36:2086 Rule: Default deny Jul/07/2006 06:58:54 Drop TCP packet from WAN 200.122.107.174:52383 81.196.143.36:2086 Rule: Default deny Jul/07/2006 06:58:51 Drop TCP packet from WAN 200.122.107.174:52383 81.196.143.36:2086 Rule: Default deny Jul/07/2006 06:58:47 Drop TCP packet from WAN 200.122.107.174:52355 81.196.143.36:2086 Rule: Default deny Jul/07/2006 07:01:37 Drop TCP packet from WAN 209.202.230.115:80 81.196.143.36:27283 Rule: Default deny Jul/07/2006 07:01:31 Drop TCP packet from WAN 200.122.107.174:42549 81.196.143.36:2086 Rule: Default deny Jul/07/2006 07:01:30 Drop TCP packet from WAN 209.202.230.115:80 81.196.143.36:27283 Rule: Default deny Jul/07/2006 07:01:26 Drop TCP packet from WAN 200.122.107.174:42549 81.196.143.36:2086 Rule: Default deny Jul/07/2006 07:01:23 Drop TCP packet from WAN 200.122.107.174:42549 81.196.143.36:2086 Rule: Default deny Jul/07/2006 07:01:06 Drop TCP packet from WAN 200.122.107.174:42508 81.196.143.36:2086 Rule: Default deny Jul/07/2006 07:00:59 Drop TCP packet from WAN 200.122.107.174:42508 81.196.143.36:2086 Rule: Default deny Jul/07/2006 07:00:56 Drop TCP packet from WAN 200.122.107.174:42508 81.196.143.36:2086 Rule: Default deny Jul/07/2006 07:00:51 Drop TCP packet from WAN 200.122.107.174:52489 81.196.143.36:2086 Rule: Default deny Jul/07/2006 07:00:50 Drop TCP packet from WAN 200.122.107.174:52435 81.196.143.36:2086 Rule: Default deny Jul/07/2006 07:00:56 Drop TCP packet from WAN 200.122.107.174:42508 81.196.143.36:2086 Rule: Default deny Jul/07/2006 07:00:51 Drop TCP packet from WAN 200.122.107.174:52489 81.196.143.36:2086 Rule: Default deny Jul/07/2006 07:00:50 Drop TCP packet from WAN 200.122.107.174:52435 81.196.143.36:2086 Rule: Default deny Jul/07/2006 07:00:39 Drop TCP packet from WAN 200.122.107.174:52489 81.196.143.36:2086 Rule: Default deny Jul/07/2006 07:00:34 Drop TCP packet from WAN 200.122.107.174:52489 81.196.143.36:2086 Rule: Default deny Jul/07/2006 07:00:32 Drop TCP packet from WAN 200.122.107.174:52489 81.196.143.36:2086 Rule: Default deny Jul/07/2006 07:00:29 Drop UDP packet from WAN 204.16.208.117:54289 81.196.143.36:1027 Rule: Default deny Jul/07/2006 07:00:29 Drop UDP packet from WAN 204.16.208.117:54289 81.196.143.36:1026 Rule: Default deny Jul/07/2006 07:00:29 Drop UDP packet from WAN 204.16.208.117:54289 81.196.143.36:1027 Rule: Default deny Jul/07/2006 07:00:29 Drop UDP packet from WAN 204.16.208.117:54289 81.196.143.36:1026 Rule: Default deny Jul/07/2006 07:00:29 Drop UDP packet from WAN 204.16.208.117:54289 81.196.143.36:1027 Rule: Default deny Jul/07/2006 07:00:29 Drop UDP packet from WAN 204.16.208.117:54289 81.196.143.36:1026 Rule: Default deny Jul/07/2006 07:00:27 Drop TCP packet from WAN 200.122.107.174:52435 81.196.143.36:2086 Rule: Default deny Jul/07/2006 07:00:17 Drop TCP packet from WAN 200.122.107.174:52435 81.196.143.36:2086 Rule: Default deny Jul/07/2006 07:00:10 Drop TCP packet from WAN 200.122.107.174:52435 81.196.143.36:2086 Rule: Default deny Jul/07/2006 07:00:07 Drop TCP packet from WAN 200.122.107.174:52435 81.196.143.36:2086 Rule: Default deny Jul/07/2006 06:59:43 Drop UDP packet from WAN 200.122.107.174:2086 81.196.143.36:2086 Rule: Default deny Jul/07/2006 06:59:39 Drop TCP packet from WAN 200.122.107.174:52383 81.196.143.36:2086 Rule: Default deny Jul/07/2006 06:59:20 Drop UDP packet from WAN 200.122.107.174:2086 81.196.143.36:2086 Rule: Default deny Jul/07/2006 06:59:14 Drop TCP packet from WAN 200.122.107.174:52383 81.196.143.36:2086 Rule: Default deny Jul/07/2006 06:59:20 Drop UDP packet from WAN 200.122.107.174:2086 81.196.143.36:2086 Rule: Default deny Jul/07/2006 06:59:14 Drop TCP packet from WAN 200.122.107.174:52383 81.196.143.36:2086 Rule: Default deny Jul/07/2006 06:58:54 Drop TCP packet from WAN 200.122.107.174:52383 81.196.143.36:2086 Rule: Default deny Jul/07/2006 06:58:51 Drop TCP packet from WAN 200.122.107.174:52383 81.196.143.36:2086 Rule: Default deny Jul/07/2006 06:58:47 Drop TCP packet from WAN 200.122.107.174:52355 81.196.143.36:2086 Rule: Default deny Jul/07/2006 06:58:29 Drop UDP packet from WAN 200.122.107.174:2086 81.196.143.36:2086 Rule: Default deny Jul/07/2006 06:58:24 Drop TCP packet from WAN 200.122.107.174:52355 81.196.143.36:2086 Rule: Default deny Jul/07/2006 06:58:24 Drop TCP packet from WAN 200.122.107.174:52343 81.196.143.36:2086 Rule: Default deny Jul/07/2006 06:58:12 Drop TCP packet from WAN 200.122.107.174:52355 81.196.143.36:2086 Rule: Default deny Jul/07/2006 06:58:05 Drop TCP packet from WAN 200.122.107.174:52355 81.196.143.36:2086 Rule: Default deny
És ez csak 5 oldal volt a 20 oldalas log-ból, mely televan ehez hasonlókkal...
- mbaron blogja
- A hozzászóláshoz be kell jelentkezni
- 1397 megtekintés
Hozzászólások
Tavaly en is hasznaltam SOHO routert, az akkori tapasztalataim azok, hogy rengeteg forgalom jon a helyi (ertsd eMTA es CMTS/CMS (?) kozott) halozatrol. Nalam a jellemzo a "from UDP 137,139" volt, ha jol emlekszem. Magyarul egy csomo Windows lokte ki magarol a dolgokat.
Az termeszetes, hogy a router WAN portjan joval nagyobb a forgalom, es akkor is villog a led, ha ki van kapcsolva a szamitogeped.
Es eszembe jutott egy dolog, amit mar regen meg akarok kerdezni.
Az ISP nyujt nehany DHCP szervert. Ez oszt DNS-t, gateway-t.
Ha egy rosszindulatu felhasznalo beallit egy DHCP szervert ebben a kabel modem-es halozatban, ami ugyancsak oszt DNS-t is, es pl a www.csulok.hu-ra egy akarmilyen IP-t tesz, ahol a tartalom/kinezet ugyanaz csak eppen az oldal rosszindulatu, en ezt nem veszem eszre, csak ha megnezem, hogy a www.csulok.hu-ra milyen IP-t kapok es tudom, hogy eredetileg milyen IP-je kellene, hogy legyen.
Ezt minden tovabbi nelkul megteheti, technikai akadalya nincsen?
Tehat felepithetek-e vele egy teljes DHCP kapcsolatot, ahol netet, DNS-t kapok, es o beallit nekem egy mukodo gateway-t?
- A hozzászóláshoz be kell jelentkezni
Ne mondd mar, hogy ez olyan nehez...
man nslookup
Name: 200-122-107-174.cab.prima.net.ar
Address: 200.122.107.174
can't find 204.16.208.117:Non-existent host/domain
Name: wiredfe20.bos.lycos.com
Address: 209.202.230.115
- A hozzászóláshoz be kell jelentkezni
Ha ez vigasztal, nalam ugyanez van, ugyanezzel a routerrel. Rengetegszer elofordul, hogy valamilyen tavoli, ismeretlen (talan win-es) geprol valami fereg csatlakozni probal a router valamelyik portjara. Pont ezert is jo egy ilyen router, mert kiszuri az ilyen "szemetet". (Halozati cimforditast hasznal, ezert csak a router mogul lehet kifele kapcsolatot kiepiteni, kivulrol befele nem, tehat az ilyesmi fergek fonnakadnak a routeren. Ennek logjat latod 20 oldalon keresztul. Ez a tipus ennyit jegyez meg egyszerre a logbol.)
Az is termeszetes, hogy a WAN LED allandoan villog, mert folyamatosan kommunikalnak egymassal a modemmel, szerintem.
- A hozzászóláshoz be kell jelentkezni