Problem z Dir-615

mithi · 12 Sierpnia 2012

Witam,

Posiadam internet w Multimedii i router Dir-615 , modem od multimedi Motorolla SB4200.

Problem jest taki ,że od jakiegoś czasu zaczęły pojawiać się disconecty. Najczęściej zdarzają się podczas długich sesji bądź gdy w sieci aktualnie pracuje dużo komputerów. 2 komputery są podłączone przez kabel, reszta urządzeń (laptop, telefony i tablet przez wifi) . Router ustawiony jest na DHCP, mac skopiowany z jednego z komputerów które są na kablu. Wifi na WPA , wszystkie inne ustawienia są domyślne jak ma router.

Po takich dc internet czasem wraca sam po paru lub parunastu sekundach, czasem trzeba restartować router/modem.

Próbowałem http://dir615routerproblem.sc42.info/D-Link_DIR-615_disconnect.html, niestety przy tych ustawieniach net muli tak, że nie nadaje się do użycia.

Według obsługi multimedii modem działa poprawnie , natomiast router już wymienili mi od ręki na nowy(taki sam model) ,ale problem dalej jest.

ruffio · 14 Sierpnia 2012

Napisz co masz w logach routera.

Czy technik przed montażem mierzył tłumienność linii?

mithi · 14 Sierpnia 2012

Sieć była montowana parę lat temu ... i wszystko dobrze działało, a ostatnio zaczęły się te DC.

Tak wyglądają logi:

Jan 1 00:00:04 [ATTACK]: SYN Flood from 213.248.127.130

Jan 1 00:00:01 [sYSTEM]: LOG, Start Notice option.

Jan 1 00:00:01 [sYSTEM]: LOG, Start Attacks option.

Jan 1 00:00:01 [sYSTEM]: LOG, Start System Activity option.

Jan 1 00:00:01 [NOTICE]: Start Log Message Service!

Jan 1 00:00:01 [DROP]: Start Log Message Service!

Jan 1 00:00:01 [ATTACK]: Start Log Message Service!

Jan 1 00:00:01 [DEBUG]: Start Log Message Service!

Jan 1 00:00:01 [sYSTEM]: Start Log Message Service!

Jan 3 00:11:19 [ATTACK]: SYN Flood from 213.248.127.130

Jan 3 00:00:56 [sYSTEM]: DHCP Server, Sending OFFER of 192.168.0.105

Jan 3 00:00:53 [sYSTEM]: DHCP Server, Sending ACK of 192.168.0.105

Jan 3 00:00:52 [sYSTEM]: DHCP Server, Sending ACK of 192.168.0.105

Jan 3 00:00:33 [sYSTEM]: SCHEDULE, Wireless Radio On

Jan 3 00:00:33 [sYSTEM]: SCHEDULE, Schedule Stopping

Jan 3 00:00:33 [sYSTEM]: WLAN[2.4G],AutoChannel change to 1

Jan 3 00:00:28 [sYSTEM]: WLAN[2.4G],Available Channel: [CH.1 ~ CH.11]

Jan 2 22:19:31 [sYSTEM]: DHCP Server, Sending ACK of 192.168.0.100

Jan 2 20:49:20 [sYSTEM]: DHCP Server, Sending ACK of 192.168.0.100

Jan 2 18:46:23 [sYSTEM]: DHCP Server, Sending ACK of 192.168.0.100

Jan 2 17:15:38 [sYSTEM]: DHCP Server, Sending ACK of 192.168.0.102

Jan 2 13:51:17 [sYSTEM]: DHCP Server, Sending ACK of 192.168.0.105

Jan 2 13:51:15 [sYSTEM]: DHCP Server, Sending ACK of 192.168.0.105

Jan 2 13:01:24 [sYSTEM]: DHCP Server, Sending OFFER of 192.168.0.105

Jan 2 13:01:15 [sYSTEM]: DHCP Server, Sending OFFER of 192.168.0.105

Jan 2 13:01:11 [sYSTEM]: DHCP Server, Sending OFFER of 192.168.0.105

Jan 2 13:01:09 [sYSTEM]: DHCP Server, Sending ACK of 192.168.0.105

Jan 2 13:01:07 [sYSTEM]: DHCP Server, Sending ACK of 192.168.0.105

Jan 2 13:00:49 [sYSTEM]: DHCP Server, Sending OFFER of 192.168.0.105

Jan 2 13:00:40 [sYSTEM]: DHCP Server, Sending OFFER of 192.168.0.105

Jan 2 13:00:36 [sYSTEM]: DHCP Server, Sending OFFER of 192.168.0.105

Jan 2 13:00:33 [sYSTEM]: DHCP Server, Sending ACK of 192.168.0.105

Jan 2 13:00:32 [sYSTEM]: DHCP Server, Sending ACK of 192.168.0.105

Jan 2 12:11:42 [sYSTEM]: DHCP Server, Sending OFFER of 192.168.0.105

Jan 2 12:11:38 [sYSTEM]: DHCP Server, Sending ACK of 192.168.0.103

Jan 2 12:00:51 [sYSTEM]: DHCP Server, Sending OFFER of 192.168.0.105

Jan 2 12:00:49 [sYSTEM]: DHCP Server, Sending ACK of 192.168.0.105

Jan 2 12:00:47 [sYSTEM]: DHCP Server, Sending ACK of 192.168.0.105

Jan 2 12:00:28 [sYSTEM]: SCHEDULE, Wireless Radio On

Jan 2 12:00:28 [sYSTEM]: SCHEDULE, Schedule Stopping

Jan 2 12:00:28 [sYSTEM]: WLAN[2.4G],AutoChannel change to 3

Jan 2 12:00:23 [sYSTEM]: WLAN[2.4G],Available Channel: [CH.1 ~ CH.11]

Jan 2 10:09:45 [sYSTEM]: DHCP Server, Sending ACK of 192.168.0.103

Jan 2 10:09:44 [sYSTEM]: DHCP Server, Sending OFFER of 192.168.0.103

Jan 2 07:26:19 [ATTACK]: SYN Flood from 199.9.252.172

Jan 2 07:14:38 [ATTACK]: SYN Flood from 23.64.142.224

Jan 2 06:27:42 [sYSTEM]: DHCP Server, Sending ACK of 192.168.0.103

Jan 2 06:11:55 [sYSTEM]: DHCP Server, Sending ACK of 192.168.0.103

Jan 2 05:38:48 [ATTACK]: SYN Flood from 199.9.252.170

Jan 2 04:06:07 [ATTACK]: SYN Flood from 66.220.153.71

Jan 2 04:05:56 [ATTACK]: SYN Flood from 80.239.216.129

Jan 2 04:05:50 [ATTACK]: SYN Flood from 80.239.216.131

Jan 2 04:05:44 [ATTACK]: SYN Flood from 80.239.216.104

Jan 2 04:05:35 [ATTACK]: SYN Flood from 2.22.52.88

Jan 2 04:05:28 [ATTACK]: SYN Flood from 2.22.52.88

Jan 2 04:04:05 [ATTACK]: SYN Flood from 69.171.242.75

Jan 2 03:57:44 [sYSTEM]: DHCP Server, Sending ACK of 192.168.0.103

Jan 2 03:56:44 [sYSTEM]: DHCP Server, Sending ACK of 192.168.0.103

Jan 2 03:50:20 [ATTACK]: SYN Flood from 69.171.227.66

Jan 2 03:49:50 [ATTACK]: SYN Flood from 69.171.227.66

Jan 2 03:28:05 [sYSTEM]: DHCP Server, Sending ACK of 192.168.0.100

Jan 2 02:23:00 [sYSTEM]: DHCP Server, Sending ACK of 192.168.0.103

Jan 2 02:15:29 [sYSTEM]: DHCP Server, Sending ACK of 192.168.0.102

Jan 2 02:15:29 [sYSTEM]: DHCP Server, Sending OFFER of 192.168.0.102

Jan 2 01:41:47 [ATTACK]: SYN Flood from 91.210.156.194

Jan 2 00:31:42 [sYSTEM]: DHCP Server, Sending ACK of 192.168.0.103

Jan 2 00:31:40 [sYSTEM]: DHCP Server, Sending ACK of 192.168.0.103

Jan 2 00:30:38 [sYSTEM]: DHCP Server, Sending ACK of 192.168.0.103

Jan 2 00:29:41 [sYSTEM]: DHCP Server, Sending ACK of 192.168.0.103

Jan 2 00:28:44 [sYSTEM]: DHCP Server, Sending ACK of 192.168.0.103

Jan 2 00:27:46 [sYSTEM]: DHCP Server, Sending ACK of 192.168.0.103

Jan 2 00:27:40 [sYSTEM]: DHCP Server, Sending ACK of 192.168.0.105

Jan 2 00:27:38 [sYSTEM]: DHCP Server, Sending ACK of 192.168.0.105

Jan 2 00:26:48 [sYSTEM]: DHCP Server, Sending ACK of 192.168.0.103

Jan 2 00:24:53 [sYSTEM]: DHCP Server, Sending ACK of 192.168.0.103

Jan 2 00:23:56 [sYSTEM]: DHCP Server, Sending ACK of 192.168.0.103

Jan 2 00:23:36 [sYSTEM]: DHCP Server, Sending ACK of 192.168.0.105

Jan 2 00:23:00 [sYSTEM]: DHCP Server, Sending ACK of 192.168.0.103

Jan 2 00:22:03 [sYSTEM]: DHCP Server, Sending ACK of 192.168.0.103

Jan 2 00:21:05 [sYSTEM]: DHCP Server, Sending ACK of 192.168.0.103

Jan 2 00:20:09 [sYSTEM]: DHCP Server, Sending ACK of 192.168.0.103

Jan 2 00:19:16 [sYSTEM]: DHCP Server, Sending ACK of 192.168.0.103

Jan 2 00:17:40 [sYSTEM]: DHCP Server, Sending ACK of 192.168.0.103

Jan 2 00:05:36 [ATTACK]: SYN Flood from 91.210.156.194

Jan 2 00:05:31 [ATTACK]: SYN Flood from 91.210.156.194

Jan 2 00:04:29 [sYSTEM]: DHCP Server, Sending OFFER of 192.168.0.105

Jan 2 00:00:44 [sYSTEM]: DHCP Server, Sending ACK of 192.168.0.105

Jan 2 00:00:42 [sYSTEM]: DHCP Server, Sending ACK of 192.168.0.105

Jan 2 00:00:23 [sYSTEM]: SCHEDULE, Wireless Radio On

Jan 2 00:00:23 [sYSTEM]: SCHEDULE, Schedule Stopping

Jan 2 00:00:23 [sYSTEM]: WLAN[2.4G],AutoChannel change to 4

Jan 2 00:00:17 [sYSTEM]: WLAN[2.4G],Available Channel: [CH.1 ~ CH.11]

Jan 1 23:44:06 [ATTACK]: SYN Flood from 91.210.156.194

Jan 1 23:43:51 [ATTACK]: SYN Flood from 91.210.156.194

Jan 1 20:07:21 [sYSTEM]: DHCP Server, Sending ACK of 192.168.0.100

Jan 1 19:28:37 [sYSTEM]: DHCP Server, Sending ACK of 192.168.0.100

Jan 1 18:27:40 [sYSTEM]: DHCP Server, Sending ACK of 192.168.0.100

Jan 1 15:03:19 [ATTACK]: SYN Flood from 173.194.70.188

Jan 1 14:10:32 [sYSTEM]: DHCP Server, Sending ACK of 192.168.0.105

Jan 1 13:40:15 [sYSTEM]: DHCP Server, Sending ACK of 192.168.0.101

Jan 1 13:26:57 [sYSTEM]: DHCP Server, Sending ACK of 192.168.0.101

Jan 1 13:12:29 [sYSTEM]: DHCP Server, Sending ACK of 192.168.0.103

Jan 1 13:12:28 [sYSTEM]: DHCP Server, Sending OFFER of 192.168.0.103

Jan 1 13:12:26 [sYSTEM]: DHCP Server, Sending OFFER of 192.168.0.103

Jan 1 12:00:17 [sYSTEM]: SCHEDULE, Wireless Radio On

Jan 1 12:00:17 [sYSTEM]: SCHEDULE, Schedule Stopping

Jan 1 12:00:17 [sYSTEM]: WLAN[2.4G],AutoChannel change to 6

Jan 1 12:00:12 [sYSTEM]: WLAN[2.4G],Available Channel: [CH.1 ~ CH.11]

Jan 1 06:30:39 [sYSTEM]: DHCP Server, Sending ACK of 192.168.0.103

Jan 1 06:19:36 [ATTACK]: SYN Flood from 199.9.252.172

Jan 1 06:10:11 [ATTACK]: SYN Flood from 199.9.252.170

Jan 1 05:21:16 [sYSTEM]: DHCP Server, Sending ACK of 192.168.0.103

Jan 1 05:09:42 [sYSTEM]: DHCP Server, Sending ACK of 192.168.0.103

Jan 1 05:02:19 [sYSTEM]: DHCP Server, Sending ACK of 192.168.0.103

Jan 1 04:47:57 [sYSTEM]: DHCP Server, Sending ACK of 192.168.0.103

Jan 1 04:39:27 [sYSTEM]: DHCP Server, Sending ACK of 192.168.0.103

Jan 1 04:29:40 [ATTACK]: SYN Flood from 213.155.152.203

Jan 1 04:21:30 [sYSTEM]: DHCP Server, Sending ACK of 192.168.0.103

Jan 1 04:21:29 [sYSTEM]: DHCP Server, Sending OFFER of 192.168.0.103

Jan 1 04:19:41 [sYSTEM]: DHCP Server, Sending ACK of 192.168.0.105

Jan 1 04:03:11 [sYSTEM]: DHCP Server, Sending ACK of 192.168.0.103

Jan 1 04:03:09 [sYSTEM]: DHCP Server, Sending ACK of 192.168.0.103

Jan 1 03:59:15 [sYSTEM]: DHCP Server, Sending ACK of 192.168.0.103

Jan 1 03:59:14 [sYSTEM]: DHCP Server, Sending OFFER of 192.168.0.103

Jan 1 03:32:05 [sYSTEM]: DHCP Server, Sending ACK of 192.168.0.100

Jan 1 03:17:50 [sYSTEM]: DHCP Server, Sending ACK of 192.168.0.103

Jan 1 03:17:42 [sYSTEM]: DHCP Server, Sending ACK of 192.168.0.103

Jan 1 03:17:38 [sYSTEM]: DHCP Server, Sending ACK of 192.168.0.103

Jan 1 03:15:49 [sYSTEM]: DHCP Server, Sending ACK of 192.168.0.103

Jan 1 03:15:45 [sYSTEM]: DHCP Server, Sending OFFER of 192.168.0.103

Jan 1 03:15:29 [sYSTEM]: DHCP Server, Sending ACK of 192.168.0.103

Jan 1 03:06:44 [sYSTEM]: DHCP Server, Sending ACK of 192.168.0.103

Jan 1 02:28:37 [sYSTEM]: DHCP Server, Sending ACK of 192.168.0.103

Jan 1 02:14:52 [sYSTEM]: DHCP Server, Sending ACK of 192.168.0.103

Jan 1 02:07:01 [sYSTEM]: DHCP Server, Sending ACK of 192.168.0.103

Jan 1 00:28:58 [sYSTEM]: DHCP Server, Sending ACK of 192.168.0.105

Jan 1 00:28:27 [sYSTEM]: DHCP Server, Sending OFFER of 192.168.0.105

Jan 1 00:18:11 [sYSTEM]: DHCP Server, Sending ACK of 192.168.0.105

Jan 1 00:18:08 [sYSTEM]: DHCP Server, Sending ACK of 192.168.0.105

Jan 1 00:15:25 [sYSTEM]: DHCP Server, Sending ACK of 192.168.0.103

Jan 1 00:03:29 [ATTACK]: SYN Flood from 176.221.96.59

Jan 1 00:03:02 [ATTACK]: SYN Flood from 209.85.148.132

Jan 1 00:03:02 [ATTACK]: SYN Flood from 209.85.148.100

Jan 1 00:03:01 [ATTACK]: SYN Flood from 209.85.148.132

Jan 1 00:03:01 [ATTACK]: SYN Flood from 209.85.148.100

Jan 1 00:03:01 [ATTACK]: SYN Flood from 46.28.247.108

Jan 1 00:02:49 [ATTACK]: SYN Flood from 209.85.148.120

Jan 1 00:02:48 [ATTACK]: SYN Flood from 74.125.232.248

Jan 1 00:00:31 [ATTACK]: SYN Flood from 173.231.136.216

Jan 1 00:00:30 [sYSTEM]: UPnP, Start

Jan 1 00:00:27 [sYSTEM]: UPnP, Stopping

Jan 1 00:00:26 [sYSTEM]: DNS, start DNS Proxy

Jan 1 00:00:24 [sYSTEM]: NET, start Firewall

Jan 1 00:00:24 [sYSTEM]: NET, start NAT

Jan 1 00:00:24 [sYSTEM]: NET, stop Firewall

Jan 1 00:00:24 [sYSTEM]: NET, stop NAT

Jan 1 00:00:24 [sYSTEM]: WAN, WAN1 IP changed, restart services

Jan 1 00:00:24 [sYSTEM]: WAN, WAN1 New IP = 89.229.170.120

Jan 1 00:00:12 [sYSTEM]: SCHEDULE, Wireless Radio On

Jan 1 00:00:12 [sYSTEM]: SCHEDULE, Schedule Stopping

Jan 1 00:00:12 [sYSTEM]: WLAN[2.4G],AutoChannel change to 1

Jan 1 00:00:11 [sYSTEM]: DHCP Server, Sending ACK of 192.168.0.100

Jan 1 00:00:07 [sYSTEM]: WLAN[2.4G],Available Channel: [CH.1 ~ CH.11]

Jan 1 00:00:06 [sYSTEM]: DHCP Server, Sending ACK of 192.168.0.102

Jan 1 00:00:05 [sYSTEM]: WLAN, start LLTD

Jan 1 00:00:04 [sYSTEM]: HTTP, start

Jan 1 00:00:04 [sYSTEM]: UPnP, Start

Jan 1 00:00:04 [sYSTEM]: NET, start Firewall

Jan 1 00:00:04 [sYSTEM]: NET, start NAT

Jan 1 00:00:03 [sYSTEM]: SCHEDULE, Wireless Radio On

Jan 1 00:00:03 [sYSTEM]: DHCP, start DHCP Server

Jan 1 00:00:03 [sYSTEM]: DNS, start DNS Proxy

Jan 1 00:00:03 [sYSTEM]: IPv6, Link Local mode

Jan 1 00:00:02 [sYSTEM]: WAN, start DHCP mode

Jan 1 00:00:02 [sYSTEM]: UPnP, start

Jan 1 00:00:02 [sYSTEM]: WLAN[2.4G], Channel = AutoSelect

Jan 1 00:00:02 [sYSTEM]: WLAN[2.4G], CountryRegion = 0

Jan 1 00:00:01 [sYSTEM]: LAN, IP address=192.168.0.1

Jan 1 00:00:01 [sYSTEM]: LAN, start

Jan 1 00:00:01 [sYSTEM]: BR, start

Jan 1 00:00:01 [sYSTEM]: SYS, Application Version: 0.3.2

Jan 1 00:00:01 [NOTICE]: Start Log Message Service!

Jan 1 00:00:01 [DROP]: Start Log Message Service!

Jan 1 00:00:01 [ATTACK]: Start Log Message Service!

Jan 1 00:00:01 [DEBUG]: Start Log Message Service!

Jan 1 00:00:01 [sYSTEM]: Start Log Message Service!

ruffio · 24 Sierpnia 2012

Moja propozycja - ustaw na sztywno kanał nadawania dla WIFI (router wybierał 1, 3, 6), włącz firewalla, sprawdź czy nie masz w zadaniach jakiś badziewi ustawionych typu pory dostępności usług, netu. Sprawdź czy masz możliwość ustawienia droopowania pakietów na firewallu .

IMO router zalicza zwiechy przy zmianie kanału nadawania (zresztą po co to zmieniać?). Teoretycznie zmiana kanału nadawania nie powinna wpłynąć na połączenia, ale to różnie bywa.

mithi · 26 Sierpnia 2012

Firewall jest włączony, zadań żadnych nie ma ustawionych, ustawiłem teraz kanał wi-fi na 1 i zobaczymy co będzie.

Przeglądając logi kiedy to się dzieje to wykazuje,że mam Syn Flood od blizzarda , google , itp... a więc od serwerów s których najczęściej "korzystam".

ruffio · 27 Sierpnia 2012

Spróbuj jeszcze jedną rzecz: zrób aktualizację firmware ftp://ftp.dlink.pl/dir/dir-615/driver_software/

mithi · 27 Sierpnia 2012

Nie pomogło, Firmware mam najnowszy.

Zaloguj się

Problem z Dir-615

Recommended Posts

mithi 12

Link to post

Share on other sites

ruffio 4

Link to post

Share on other sites

mithi 12

Link to post

Share on other sites

ruffio 4

Link to post

Share on other sites

mithi 12

Link to post

Share on other sites

ruffio 4

Link to post

Share on other sites

mithi 12

Link to post

Share on other sites

Dołącz do dyskusji

Ostatnio przeglądający 0 użytkowników