faq обучение настройка
Текущее время: Вс июл 20, 2025 18:53

Часовой пояс: UTC + 3 часа




Начать новую тему Ответить на тему  [ Сообщений: 31 ]  На страницу Пред.  1, 2, 3  След.
Автор Сообщение
 Заголовок сообщения: Re: DIR-620/D1 и LAN
СообщениеДобавлено: Пт фев 01, 2013 10:38 
Не в сети

Зарегистрирован: Ср дек 16, 2009 08:51
Сообщений: 19
в предыдущее сообщение не влезли еще пара картинок:


Вложения:
Комментарий к файлу: DIR-620/В1 пинг до соседнего компа
620-2.jpg
620-2.jpg [ 141.65 KiB | Просмотров: 3362 ]
Комментарий к файлу: DIR-300N/RU пинг до соседнего компа
300-2.jpg
300-2.jpg [ 168.46 KiB | Просмотров: 3362 ]
Вернуться наверх
 Профиль  
 
 Заголовок сообщения: Re: DIR-620/D1 и LAN
СообщениеДобавлено: Пт фев 01, 2013 18:32 
Не в сети

Зарегистрирован: Ср дек 16, 2009 08:51
Сообщений: 19
хммм... дозвонился до техподдержки... сказали, что о проблеме знают и очень активно пытаются ее решить... может через 2 недели или позже выкатят новое обновление... а мне-то что делать???
В магазине, естественно, хотят послать роутер на экспертизу... на 45 дней!!! АГА!!!
Получается, что у меня ни денег, ни нормально работающей железяки... ПИСЕЦ!!!


Вернуться наверх
 Профиль  
 
 Заголовок сообщения: Re: DIR-620/D1 и LAN
СообщениеДобавлено: Сб фев 02, 2013 18:33 
Не в сети
Сотрудник D-LINK
Сотрудник D-LINK

Зарегистрирован: Пн авг 17, 2009 17:18
Сообщений: 7330
boris_moscow писал(а):
хммм... дозвонился до техподдержки... сказали, что о проблеме знают и очень активно пытаются ее решить... может через 2 недели или позже выкатят новое обновление... а мне-то что делать???
В магазине, естественно, хотят послать роутер на экспертизу... на 45 дней!!! АГА!!!
Получается, что у меня ни денег, ни нормально работающей железяки... ПИСЕЦ!!!

На данный момент потерь пакетов нет, я бы не сказал, что проблема критична, задержка в 5-7 мс вполне допустима, однако данный вопрос сейчас прорабатывается у разработчика, следите за обновлениями на FTP.

_________________
Форум не подразумевает под собой быстрый ответ, хотите быстрый и квалифицированный ответ - звоните в техподдержку компании D-Link 8-800-700-5465


Вернуться наверх
 Профиль  
 
 Заголовок сообщения: Re: DIR-620/D1 и LAN
СообщениеДобавлено: Вт фев 05, 2013 07:46 
Не в сети

Зарегистрирован: Вт фев 05, 2013 07:29
Сообщений: 11
Помогите разобраться с логами пожалуйста.
Проблема в том что соединение рвется каждые 20-30 минут. Иногда мой dir-620 revD пересоединяется, а иногда нет.
Меня смущает что реконнект происходит к ip-шникам из разных подсетей. Например работает под 91.205.120.228, происходит разрыв+реконнект, может подключиться к подсети 91.205.ХХХ,ХХХ а может к 109.94.ХХХ.ХХХ Затем опять разрыв+реконнект..........
Разве такое может быть?

Прилагаю логи
Вариант1
Скрытый текст: показать
Код:
Jan  1 00:00:13 resident: init lan
Jan  1 00:00:13 resident: start ipoe
Jan  1 00:00:13 start_ip: begin (br0 -> br0)
Jan  1 00:00:13 resident: start ipoe (v717903456) on br0
Jan  1 00:00:14 resident: init wan
Jan  1 00:00:14 resident: start ipoe
Jan  1 00:00:14 start_ip: begin (eth2.5 -> eth2.5_1)
Jan  1 00:00:14 resident: start ipoe (v717587016) on eth2.5
Jan  1 00:00:14 update_ddns: start
Jan  1 00:00:14 telnet-start: begin...
Jan  1 00:00:14 event: send event "ipoe down"
Jan  1 00:00:14 telnet-start: running on 23 port
Jan  1 00:00:14 telnet-start: succes!
Jan  1 00:00:14 printserver-start: begin...
Jan  1 00:00:14 printserver-start: success!
Jan  1 00:00:14 start_sysusers: init ...
Jan  1 00:00:14 start_sysusers: conf not NULL ...
Jan  1 00:00:15 event: send event "ipoe up"
Jan  1 00:00:15 resident: record = action:up;iface:br0;contag:0;ipaddr:192.168.1.1;netmask:255.255.255.0;dns1:;dns2:;
Jan  1 00:00:15 resident: phys_iface br0
Jan  1 00:00:15 test: ip_type = (null)
Jan  1 00:00:15 resident: resident_ipoe_handler - Set default type: ipv4
Jan  1 00:00:15 resident: phys_iface
Jan  1 00:00:15 resident: resident_ipoe_handler - 1
Jan  1 00:00:15 resident: resident_ipoe_handler - 3, name: br0
Jan  1 00:00:15 resident: resident_ipoe_handler - l2:br0, l3:br0, tun:, ip_type:0
Jan  1 00:00:15 resident: resident_ipoe_handler - ipv4
Jan  1 00:00:15 resident: start ip_is_up on iface br0
Jan  1 00:00:15 resident: ip_is_up for link br0
Jan  1 00:00:15 resident: start dhcp+dns on br0
Jan  1 00:00:16 upnp: start - begin
Jan  1 00:00:17 resident: record = action:down;iface:eth2.5;contag:1;
Jan  1 00:00:17 resident: phys_iface eth2.5
Jan  1 00:00:17 test: ip_type = (null)
Jan  1 00:00:17 resident: resident_ipoe_handler - Set default type: ipv4
Jan  1 00:00:17 resident: phys_iface
Jan  1 00:00:17 resident: resident_ipoe_handler - 2
Jan  1 00:00:17 resident: resident_ipoe_handler - 3, name: eth2.5_1
Jan  1 00:00:17 resident: resident_ipoe_handler - l2:eth2.5, l3:eth2.5_1, tun:eth2.5_2, ip_type:0
Jan  1 00:00:17 resident: ip_is_down on eth2.5_1
Jan  1 00:00:17 resident: record = action:up;iface:eth2.5;contag:1;ipaddr:192.168.141.188 ;netmask:255.255.255.128 ;gateway:192.168.141.130 ;dns1:192.168.10.7;
Jan  1 00:00:17 resident: phys_iface eth2.5
Jan  1 00:00:17 test: ip_type = (null)
Jan  1 00:00:17 resident: resident_ipoe_handler - Set default type: ipv4
Jan  1 00:00:17 resident: phys_iface
Jan  1 00:00:17 resident: resident_ipoe_handler - 2
Jan  1 00:00:17 resident: resident_ipoe_handler - 3, name: eth2.5_1
Jan  1 00:00:17 resident: resident_ipoe_handler - l2:eth2.5, l3:eth2.5_1, tun:eth2.5_2, ip_type:0
Jan  1 00:00:17 resident: resident_ipoe_handler - ipv4
Jan  1 00:00:17 resident: start ip_is_up on iface eth2.5_1
Jan  1 00:00:17 resident: ip_is_up for link eth2.5_1
Jan  1 00:00:17 set_dhcp_routes: set routes for iface eth2.5
Jan  1 00:00:17 resident: update dns
Jan  1 00:00:17 resident: update rip
Jan  1 00:00:17 resident: update igmpx
Jan  1 00:00:17 resident: stop igmpx
Jan  1 00:00:17 iface: this is eth2.5
Jan  1 00:00:17 resident: igmpx eth2.5
Jan  1 00:00:17 resident: update igmpx compiled
Jan  1 00:00:17 resident: update ntpclient
Jan  1 04:00:17 start_pppd: tunnel: ifaces/eth2.5/services/eth2.5_1/tunnels/eth2.5_2/
Jan  1 04:00:17 resident: start pppd on eth2.5_2
Jan  1 04:00:17 resident: stop pppd on eth2.5_2
Jan  1 04:00:17 resident: set lock on eth2.5_2, with "/var/lock/eth2.5_2.lock"
Jan  1 04:00:17 resident: stopped link(contype:pptp, iface:eth2.5_2)
Jan  1 04:00:17 start_pppd: get_subnet_class 
Jan  1 04:00:17 start_pppd: get_subnet_class  close
Jan  1 04:00:17 start_pppd: get_subnet_class 
Jan  1 04:00:17 start_pppd: get_subnet_class  close
Jan  1 04:00:17 start_pppd: get_subnet_class 
Jan  1 04:00:17 start_pppd: get_subnet_class  close
Jan  1 04:00:17 start_pppd: check_subnets
Jan  1 04:00:17 start_pppd:  ip1=192.168.192.1 ip2=192.168.141.130 class=2
Jan  1 04:00:17 start_pppd: check_subnets close
Jan  1 04:00:17 start_pppd: sec if
Jan  1 04:00:24 resident_ppp_handler: record = action:up;iface:ppp0;link:eth2.5_2;ipaddr:109.94.200.125;netmask:255.255.255.255;gateway:91.205.123.250;dns1:192.168.10.7;dns2:8.8.8.8;
Jan  1 04:00:24 resident: resident_ipoe_handler - Set default type: ipv4
Jan  1 04:00:24 resident: resident_ppp_handler - l2:eth2.5, l3:eth2.5_1, tun:eth2.5_2
Jan  1 04:00:24 resident: update dns
Jan  1 04:00:24 resident: update ntpclient
Jan  1 04:00:27 dnsmasq: RESTARTING
Feb  5 06:24:23 event: send event "ipoe lease fail"
Feb  5 06:24:23 resident: record = action:leasefail;iface:eth2.5;contag:1;
Feb  5 06:24:23 resident: phys_iface eth2.5
Feb  5 06:24:23 test: ip_type = (null)
Feb  5 06:24:23 resident: resident_ipoe_handler - Set default type: ipv4
Feb  5 06:24:23 resident: phys_iface
Feb  5 06:24:23 resident: resident_ipoe_handler - 2
Feb  5 06:24:23 resident: resident_ipoe_handler - 3, name: eth2.5_1
Feb  5 06:24:23 resident: resident_ipoe_handler - l2:eth2.5, l3:eth2.5_1, tun:eth2.5_2, ip_type:0
Feb  5 06:24:23 resident: ip_is_down on eth2.5_1
Feb  5 06:24:23 event: send event "ipoe up"
Feb  5 06:24:23 resident: record = action:up;iface:eth2.5;contag:1;ipaddr:192.168.141.188 ;netmask:255.255.255.128 ;gateway:192.168.141.130 ;dns1:192.168.10.7;
Feb  5 06:24:23 resident: phys_iface eth2.5
Feb  5 06:24:23 test: ip_type = (null)
Feb  5 06:24:23 resident: resident_ipoe_handler - Set default type: ipv4
Feb  5 06:24:23 resident: phys_iface
Feb  5 06:24:23 resident: resident_ipoe_handler - 2
Feb  5 06:24:23 resident: resident_ipoe_handler - 3, name: eth2.5_1
Feb  5 06:24:23 resident: resident_ipoe_handler - l2:eth2.5, l3:eth2.5_1, tun:eth2.5_2, ip_type:0
Feb  5 06:24:23 resident: resident_ipoe_handler - ipv4
Feb  5 06:24:23 resident: start ip_is_up on iface eth2.5_1
Feb  5 06:24:23 resident: ip_is_up for link eth2.5_1
Feb  5 06:24:23 set_dhcp_routes: set routes for iface eth2.5
Feb  5 06:24:23 resident: update dns
Feb  5 06:24:23 resident: update rip
Feb  5 06:24:23 resident: update igmpx
Feb  5 06:24:23 resident: stop igmpx
Feb  5 06:24:23 iface: this is eth2.5
Feb  5 06:24:23 resident: igmpx eth2.5
Feb  5 06:24:23 resident: update igmpx compiled
Feb  5 06:24:23 resident: update ntpclient
Feb  5 06:24:23 start_pppd: tunnel: ifaces/eth2.5/services/eth2.5_1/tunnels/eth2.5_2/
Feb  5 06:24:23 resident: start pppd on eth2.5_2
Feb  5 06:24:23 resident: stop pppd on eth2.5_2
Feb  5 06:24:24 resident: set lock on eth2.5_2, with "/var/lock/eth2.5_2.lock"
Feb  5 06:24:24 resident: stopped link(contype:pptp, iface:eth2.5_2)
Feb  5 06:24:24 event:  ppp_down - do event
Feb  5 06:24:24 start_pppd: get_subnet_class 
Feb  5 06:24:24 start_pppd: get_subnet_class  close
Feb  5 06:24:24 start_pppd: get_subnet_class 
Feb  5 06:24:24 start_pppd: get_subnet_class  close
Feb  5 06:24:24 start_pppd: get_subnet_class 
Feb  5 06:24:24 start_pppd: get_subnet_class  close
Feb  5 06:24:24 start_pppd: check_subnets
Feb  5 06:24:24 start_pppd:  ip1=192.168.192.1 ip2=192.168.141.130 class=2
Feb  5 06:24:24 start_pppd: check_subnets close
Feb  5 06:24:24 start_pppd: sec if
Feb  5 06:24:24 miniupnpd[880]: upnp_event_recv: recv(): Connection reset by peer
Feb  5 06:24:30 resident_ppp_handler: record = action:down;iface:ppp0;link:eth2.5_2;status:5;
Feb  5 06:24:30 resident: resident_ipoe_handler - Set default type: ipv4
Feb  5 06:24:30 resident: resident_ppp_handler - l2:eth2.5, l3:eth2.5_1, tun:eth2.5_2
Feb  5 06:24:30 ppp_handler: ppp state 5
Feb  5 06:24:30 resident: resident_ppp_handler - status: 5 (5)
Feb  5 06:24:30 resident: ppp_is_down on eth2.5_2
Feb  5 06:24:30 resident_ppp_handler: record = action:up;iface:ppp0;link:eth2.5_2;ipaddr:109.94.200.3;netmask:255.255.255.255;gateway:91.205.123.250;dns1:192.168.10.7;dns2:8.8.8.8;
Feb  5 06:24:30 resident: resident_ipoe_handler - Set default type: ipv4
Feb  5 06:24:30 resident: resident_ppp_handler - l2:eth2.5, l3:eth2.5_1, tun:eth2.5_2
Feb  5 06:24:30 resident: update dns
Feb  5 06:24:30 resident: update ntpclient
Feb  5 06:24:30 resident: update dns
Feb  5 06:24:32 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:24:32 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:24:33 dnsmasq: RESTARTING
Feb  5 06:24:52 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:24:52 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:25:12 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:25:12 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:25:32 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:25:32 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:25:52 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:25:53 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:26:13 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:26:13 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:26:33 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:26:33 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:26:53 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:26:53 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:27:13 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:27:13 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:27:33 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:27:34 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:27:54 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:27:54 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:28:14 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:28:14 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:28:34 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:28:34 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:28:54 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:28:54 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:29:15 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:29:15 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:29:35 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:29:35 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:29:55 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:29:55 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:30:15 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:30:15 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:30:35 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:30:35 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:30:56 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:30:56 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:31:16 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:31:16 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:31:36 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:31:36 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:31:56 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:31:56 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:32:16 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:32:17 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:32:37 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:32:37 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:32:57 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:32:57 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:33:17 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:33:17 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:33:37 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:33:37 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:33:57 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:33:58 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:34:18 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:34:18 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:34:38 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:34:38 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:34:58 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:34:58 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:35:18 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:35:18 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:35:39 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:35:39 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:35:59 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:35:59 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:36:19 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:36:19 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:36:39 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:36:39 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:36:59 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:36:59 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:37:20 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:37:20 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:37:40 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:37:40 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:38:00 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:38:00 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:38:09 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:38:14 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:38:19 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:38:20 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:38:20 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:38:21 miniupnpd[880]: Failed to get ip address for interface
Feb  5 06:38:40 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:38:41 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:39:01 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:39:01 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:39:21 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:39:21 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:39:41 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:39:41 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:40:01 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:40:01 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:40:21 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:40:22 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:40:42 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:40:42 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:41:02 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:41:02 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:41:22 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:41:22 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:41:42 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:41:42 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:42:03 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:42:03 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:42:23 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:42:23 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:42:43 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:42:43 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:43:03 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:43:03 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:43:23 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:43:23 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:43:44 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:43:44 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:44:04 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:44:04 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:44:24 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:44:24 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:44:44 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:44:44 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:45:04 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:45:05 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:45:25 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:45:25 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:45:45 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:45:45 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:46:05 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:46:05 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:46:25 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:46:25 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:46:45 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:46:46 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:47:06 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:47:06 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:47:26 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:47:26 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:47:46 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:47:46 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:48:06 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:48:06 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:48:27 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:48:27 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:48:47 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:48:47 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:49:07 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:49:07 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:49:27 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:49:27 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:49:47 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:49:47 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:50:08 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:50:08 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:50:28 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:50:28 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:50:48 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:50:48 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:51:08 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:51:08 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:51:28 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:51:29 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:51:49 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:51:49 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:52:09 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:52:09 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:52:29 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:52:29 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:52:49 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:52:49 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:53:09 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:53:10 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:53:30 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:53:30 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:53:50 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:53:50 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:54:10 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:54:10 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:54:30 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:54:30 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:54:51 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:54:51 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:55:11 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:55:11 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:55:31 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:55:31 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:55:51 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:55:51 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:56:11 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:56:11 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:56:32 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:56:32 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:56:52 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:56:52 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:57:12 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:57:12 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:57:32 miniupnpd[880]: Can't find in which sub network the client is
Feb  5 06:57:32 miniupnpd[880]: Can't find in which sub network the client is

Вариант2
Скрытый текст: показать
Код:
Jan  1 00:00:13 resident: init lan
Jan  1 00:00:13 resident: start ipoe
Jan  1 00:00:13 start_ip: begin (br0 -> br0)
Jan  1 00:00:13 resident: start ipoe (v717903456) on br0
Jan  1 00:00:14 resident: init wan
Jan  1 00:00:14 resident: start ipoe
Jan  1 00:00:14 start_ip: begin (eth2.5 -> eth2.5_1)
Jan  1 00:00:14 resident: start ipoe (v717587016) on eth2.5
Jan  1 00:00:14 event: send event "ipoe down"
Jan  1 00:00:14 update_ddns: start
Jan  1 00:00:14 telnet-start: begin...
Jan  1 00:00:14 telnet-start: running on 23 port
Jan  1 00:00:14 telnet-start: succes!
Jan  1 00:00:14 printserver-start: begin...
Jan  1 00:00:14 printserver-start: success!
Jan  1 00:00:14 start_sysusers: init ...
Jan  1 00:00:14 start_sysusers: conf not NULL ...
Jan  1 00:00:14 event: send event "ipoe up"
Jan  1 00:00:15 resident: record = action:up;iface:br0;contag:0;ipaddr:192.168.1.1;netmask:255.255.255.0;dns1:;dns2:;
Jan  1 00:00:15 resident: phys_iface br0
Jan  1 00:00:15 test: ip_type = (null)
Jan  1 00:00:15 resident: resident_ipoe_handler - Set default type: ipv4
Jan  1 00:00:15 resident: phys_iface
Jan  1 00:00:15 resident: resident_ipoe_handler - 1
Jan  1 00:00:15 resident: resident_ipoe_handler - 3, name: br0
Jan  1 00:00:15 resident: resident_ipoe_handler - l2:br0, l3:br0, tun:, ip_type:0
Jan  1 00:00:15 resident: resident_ipoe_handler - ipv4
Jan  1 00:00:15 resident: start ip_is_up on iface br0
Jan  1 00:00:15 resident: ip_is_up for link br0
Jan  1 00:00:15 resident: start dhcp+dns on br0
Jan  1 00:00:15 upnp: start - begin
Jan  1 00:00:17 resident: record = action:down;iface:eth2.5;contag:1;
Jan  1 00:00:17 resident: phys_iface eth2.5
Jan  1 00:00:17 test: ip_type = (null)
Jan  1 00:00:17 resident: resident_ipoe_handler - Set default type: ipv4
Jan  1 00:00:17 resident: phys_iface
Jan  1 00:00:17 resident: resident_ipoe_handler - 2
Jan  1 00:00:17 resident: resident_ipoe_handler - 3, name: eth2.5_1
Jan  1 00:00:17 resident: resident_ipoe_handler - l2:eth2.5, l3:eth2.5_1, tun:eth2.5_2, ip_type:0
Jan  1 00:00:17 resident: ip_is_down on eth2.5_1
Jan  1 00:00:17 resident: record = action:up;iface:eth2.5;contag:1;ipaddr:192.168.141.188 ;netmask:255.255.255.128 ;gateway:192.168.141.130 ;dns1:192.168.10.7;
Jan  1 00:00:17 resident: phys_iface eth2.5
Jan  1 00:00:17 test: ip_type = (null)
Jan  1 00:00:17 resident: resident_ipoe_handler - Set default type: ipv4
Jan  1 00:00:17 resident: phys_iface
Jan  1 00:00:17 resident: resident_ipoe_handler - 2
Jan  1 00:00:17 resident: resident_ipoe_handler - 3, name: eth2.5_1
Jan  1 00:00:17 resident: resident_ipoe_handler - l2:eth2.5, l3:eth2.5_1, tun:eth2.5_2, ip_type:0
Jan  1 00:00:17 resident: resident_ipoe_handler - ipv4
Jan  1 00:00:17 resident: start ip_is_up on iface eth2.5_1
Jan  1 00:00:17 resident: ip_is_up for link eth2.5_1
Jan  1 00:00:17 set_dhcp_routes: set routes for iface eth2.5
Jan  1 00:00:17 resident: update dns
Jan  1 00:00:17 resident: update rip
Jan  1 00:00:17 resident: update igmpx
Jan  1 00:00:17 resident: stop igmpx
Jan  1 00:00:17 iface: this is eth2.5
Jan  1 00:00:17 resident: igmpx eth2.5
Jan  1 00:00:17 resident: update igmpx compiled
Jan  1 00:00:17 resident: update ntpclient
Jan  1 04:00:17 start_pppd: tunnel: ifaces/eth2.5/services/eth2.5_1/tunnels/eth2.5_2/
Jan  1 04:00:17 resident: start pppd on eth2.5_2
Jan  1 04:00:17 resident: stop pppd on eth2.5_2
Jan  1 04:00:17 resident: set lock on eth2.5_2, with "/var/lock/eth2.5_2.lock"
Jan  1 04:00:17 resident: stopped link(contype:pptp, iface:eth2.5_2)
Jan  1 04:00:17 start_pppd: get_subnet_class 
Jan  1 04:00:17 start_pppd: get_subnet_class  close
Jan  1 04:00:17 start_pppd: get_subnet_class 
Jan  1 04:00:17 start_pppd: get_subnet_class  close
Jan  1 04:00:17 start_pppd: get_subnet_class 
Jan  1 04:00:17 start_pppd: get_subnet_class  close
Jan  1 04:00:17 start_pppd: check_subnets
Jan  1 04:00:17 start_pppd:  ip1=192.168.192.1 ip2=192.168.141.130 class=2
Jan  1 04:00:17 start_pppd: check_subnets close
Jan  1 04:00:17 start_pppd: sec if
Jan  1 04:00:24 resident_ppp_handler: record = action:down;iface:ppp0;status:16;link:eth2.5_2;
Jan  1 04:00:24 resident: resident_ipoe_handler - Set default type: ipv4
Jan  1 04:00:24 resident: resident_ppp_handler - l2:eth2.5, l3:eth2.5_1, tun:eth2.5_2
Jan  1 04:00:24 ppp_handler: ppp state 1
Jan  1 04:00:24 ppp_handler: Restart pppd
Jan  1 04:00:24 start_pppd: tunnel: ifaces/eth2.5/services/eth2.5_1/tunnels/eth2.5_2/
Jan  1 04:00:24 resident: start pppd on eth2.5_2
Jan  1 04:00:24 resident: stop pppd on eth2.5_2
Jan  1 04:00:24 resident: set lock on eth2.5_2, with "/var/lock/eth2.5_2.lock"
Jan  1 04:00:24 resident: stopped link(contype:pptp, iface:eth2.5_2)
Jan  1 04:00:24 start_pppd: get_subnet_class 
Jan  1 04:00:24 start_pppd: get_subnet_class  close
Jan  1 04:00:24 start_pppd: get_subnet_class 
Jan  1 04:00:24 start_pppd: get_subnet_class  close
Jan  1 04:00:24 start_pppd: get_subnet_class 
Jan  1 04:00:24 start_pppd: get_subnet_class  close
Jan  1 04:00:24 start_pppd: check_subnets
Jan  1 04:00:24 start_pppd:  ip1=192.168.192.1 ip2=192.168.141.130 class=2
Jan  1 04:00:24 start_pppd: check_subnets close
Jan  1 04:00:24 start_pppd: sec if
Jan  1 04:00:27 resident_ppp_handler: record = action:up;iface:ppp0;link:eth2.5_2;ipaddr:91.205.122.190;netmask:255.255.255.255;gateway:91.205.123.250;dns1:192.168.10.7;dns2:8.8.8.8;
Jan  1 04:00:27 resident: resident_ipoe_handler - Set default type: ipv4
Jan  1 04:00:27 resident: resident_ppp_handler - l2:eth2.5, l3:eth2.5_1, tun:eth2.5_2
Jan  1 04:00:27 resident: update dns
Jan  1 04:00:27 resident: update ntpclient
Jan  1 04:00:30 dnsmasq: RESTARTING
Feb  3 17:35:13 event: send event "ipoe lease fail"
Feb  3 17:35:13 resident: record = action:leasefail;iface:eth2.5;contag:1;
Feb  3 17:35:13 resident: phys_iface eth2.5
Feb  3 17:35:13 test: ip_type = (null)
Feb  3 17:35:13 resident: resident_ipoe_handler - Set default type: ipv4
Feb  3 17:35:13 resident: phys_iface
Feb  3 17:35:13 resident: resident_ipoe_handler - 2
Feb  3 17:35:13 resident: resident_ipoe_handler - 3, name: eth2.5_1
Feb  3 17:35:13 resident: resident_ipoe_handler - l2:eth2.5, l3:eth2.5_1, tun:eth2.5_2, ip_type:0
Feb  3 17:35:13 resident: ip_is_down on eth2.5_1
Feb  3 17:35:13 event: send event "ipoe up"
Feb  3 17:35:13 resident: record = action:up;iface:eth2.5;contag:1;ipaddr:192.168.141.188 ;netmask:255.255.255.128 ;gateway:192.168.141.130 ;dns1:192.168.10.7;
Feb  3 17:35:13 resident: phys_iface eth2.5
Feb  3 17:35:13 test: ip_type = (null)
Feb  3 17:35:13 resident: resident_ipoe_handler - Set default type: ipv4
Feb  3 17:35:13 resident: phys_iface
Feb  3 17:35:13 resident: resident_ipoe_handler - 2
Feb  3 17:35:13 resident: resident_ipoe_handler - 3, name: eth2.5_1
Feb  3 17:35:13 resident: resident_ipoe_handler - l2:eth2.5, l3:eth2.5_1, tun:eth2.5_2, ip_type:0
Feb  3 17:35:13 resident: resident_ipoe_handler - ipv4
Feb  3 17:35:13 resident: start ip_is_up on iface eth2.5_1
Feb  3 17:35:13 resident: ip_is_up for link eth2.5_1
Feb  3 17:35:13 set_dhcp_routes: set routes for iface eth2.5
Feb  3 17:35:13 resident: update dns
Feb  3 17:35:13 resident: update rip
Feb  3 17:35:13 resident: update igmpx
Feb  3 17:35:13 resident: stop igmpx
Feb  3 17:35:13 iface: this is eth2.5
Feb  3 17:35:13 resident: igmpx eth2.5
Feb  3 17:35:13 resident: update igmpx compiled
Feb  3 17:35:13 resident: update ntpclient
Feb  3 17:35:14 start_pppd: tunnel: ifaces/eth2.5/services/eth2.5_1/tunnels/eth2.5_2/
Feb  3 17:35:14 resident: start pppd on eth2.5_2
Feb  3 17:35:14 resident: stop pppd on eth2.5_2
Feb  3 17:35:14 resident: set lock on eth2.5_2, with "/var/lock/eth2.5_2.lock"
Feb  3 17:35:14 resident: stopped link(contype:pptp, iface:eth2.5_2)
Feb  3 17:35:14 event:  ppp_down - do event
Feb  3 17:35:14 start_pppd: get_subnet_class 
Feb  3 17:35:14 start_pppd: get_subnet_class  close
Feb  3 17:35:14 start_pppd: get_subnet_class 
Feb  3 17:35:14 start_pppd: get_subnet_class  close
Feb  3 17:35:14 start_pppd: get_subnet_class 
Feb  3 17:35:14 start_pppd: get_subnet_class  close
Feb  3 17:35:14 start_pppd: check_subnets
Feb  3 17:35:14 start_pppd:  ip1=192.168.192.1 ip2=192.168.141.130 class=2
Feb  3 17:35:14 start_pppd: check_subnets close
Feb  3 17:35:14 start_pppd: sec if
Feb  3 17:35:17 event:  ppp_down - do event
Feb  3 17:35:20 resident_ppp_handler: record = action:down;iface:ppp0;link:eth2.5_2;status:5;
Feb  3 17:35:20 resident: resident_ipoe_handler - Set default type: ipv4
Feb  3 17:35:20 resident: resident_ppp_handler - l2:eth2.5, l3:eth2.5_1, tun:eth2.5_2
Feb  3 17:35:20 ppp_handler: ppp state 5
Feb  3 17:35:20 resident: resident_ppp_handler - status: 5 (5)
Feb  3 17:35:20 resident: ppp_is_down on eth2.5_2
Feb  3 17:35:20 resident_ppp_handler: record = action:up;iface:ppp0;link:eth2.5_2;ipaddr:91.205.121.126;netmask:255.255.255.255;gateway:91.205.123.250;dns1:192.168.10.7;dns2:8.8.8.8;
Feb  3 17:35:20 resident: resident_ipoe_handler - Set default type: ipv4
Feb  3 17:35:20 resident: resident_ppp_handler - l2:eth2.5, l3:eth2.5_1, tun:eth2.5_2
Feb  3 17:35:20 resident_ppp_handler: record = action:down;iface:ppp0;link:eth2.5_2;status:0;
Feb  3 17:35:20 resident: resident_ipoe_handler - Set default type: ipv4
Feb  3 17:35:20 resident: resident_ppp_handler - l2:eth2.5, l3:eth2.5_1, tun:eth2.5_2
Feb  3 17:35:20 ppp_handler: ppp state 0
Feb  3 17:35:20 ppp_handler: Restart pppd
Feb  3 17:35:20 start_pppd: tunnel: ifaces/eth2.5/services/eth2.5_1/tunnels/eth2.5_2/
Feb  3 17:35:20 resident: start pppd on eth2.5_2
Feb  3 17:35:20 resident: stop pppd on eth2.5_2
Feb  3 17:35:20 resident: set lock on eth2.5_2, with "/var/lock/eth2.5_2.lock"
Feb  3 17:35:20 resident: stopped link(contype:pptp, iface:eth2.5_2)
Feb  3 17:35:20 start_pppd: get_subnet_class 
Feb  3 17:35:20 start_pppd: get_subnet_class  close
Feb  3 17:35:20 start_pppd: get_subnet_class 
Feb  3 17:35:20 start_pppd: get_subnet_class  close
Feb  3 17:35:20 start_pppd: get_subnet_class 
Feb  3 17:35:20 start_pppd: get_subnet_class  close
Feb  3 17:35:20 start_pppd: check_subnets
Feb  3 17:35:20 start_pppd:  ip1=192.168.192.1 ip2=192.168.141.130 class=2
Feb  3 17:35:20 start_pppd: check_subnets close
Feb  3 17:35:20 start_pppd: sec if
Feb  3 17:35:20 resident_ppp_handler: record = action:down;iface:ppp0;status:16;link:eth2.5_2;
Feb  3 17:35:20 resident: resident_ipoe_handler - Set default type: ipv4
Feb  3 17:35:20 resident: resident_ppp_handler - l2:eth2.5, l3:eth2.5_1, tun:eth2.5_2
Feb  3 17:35:20 ppp_handler: ppp state 1
Feb  3 17:35:20 ppp_handler: Restart pppd
Feb  3 17:35:20 start_pppd: tunnel: ifaces/eth2.5/services/eth2.5_1/tunnels/eth2.5_2/
Feb  3 17:35:20 resident: start pppd on eth2.5_2
Feb  3 17:35:20 resident: stop pppd on eth2.5_2
Feb  3 17:35:20 resident: update dns
Feb  3 17:35:20 resident: update ntpclient
Feb  3 17:35:20 resident: update dns
Feb  3 17:35:20 resident: set lock on eth2.5_2, with "/var/lock/eth2.5_2.lock"
Feb  3 17:35:20 resident: stopped link(contype:pptp, iface:eth2.5_2)
Feb  3 17:35:20 start_pppd: get_subnet_class 
Feb  3 17:35:20 start_pppd: get_subnet_class  close
Feb  3 17:35:20 start_pppd: get_subnet_class 
Feb  3 17:35:20 start_pppd: get_subnet_class  close
Feb  3 17:35:20 start_pppd: get_subnet_class 
Feb  3 17:35:20 start_pppd: get_subnet_class  close
Feb  3 17:35:20 start_pppd: check_subnets
Feb  3 17:35:20 start_pppd:  ip1=192.168.192.1 ip2=192.168.141.130 class=2
Feb  3 17:35:20 start_pppd: check_subnets close
Feb  3 17:35:20 start_pppd: sec if
Feb  3 17:35:23 dnsmasq: RESTARTING
Feb  3 17:35:26 resident_ppp_handler: record = action:up;iface:ppp0;link:eth2.5_2;ipaddr:109.94.202.35;netmask:255.255.255.255;gateway:91.205.123.250;dns1:192.168.10.7;dns2:8.8.8.8;
Feb  3 17:35:26 resident: resident_ipoe_handler - Set default type: ipv4
Feb  3 17:35:26 resident: resident_ppp_handler - l2:eth2.5, l3:eth2.5_1, tun:eth2.5_2
Feb  3 17:35:26 resident: update dns
Feb  3 17:35:26 resident: update ntpclient
Feb  3 17:35:29 dnsmasq: RESTARTING
Feb  3 17:38:34 miniupnpd[880]: Can't find in which sub network the client is
Feb  3 17:38:35 miniupnpd[880]: Can't find in which sub network the client is
Feb  3 17:38:40 miniupnpd[880]: Can't find in which sub network the client is
Feb  3 17:38:45 miniupnpd[880]: Can't find in which sub network the client is
Feb  3 17:38:50 miniupnpd[880]: Can't find in which sub network the client is
Feb  3 17:39:12 miniupnpd[880]: Failed to get ip address for interface


Вернуться наверх
 Профиль  
 
 Заголовок сообщения: Re: DIR-620/D1 и LAN
СообщениеДобавлено: Вт фев 05, 2013 08:47 
Не в сети

Зарегистрирован: Вт фев 05, 2013 07:29
Сообщений: 11
общался с провайлером про разные подсети - говорит что это нормально


Вернуться наверх
 Профиль  
 
 Заголовок сообщения: Re: DIR-620/D1 и LAN
СообщениеДобавлено: Вт фев 05, 2013 09:56 
Не в сети
Сотрудник D-LINK
Сотрудник D-LINK

Зарегистрирован: Ср окт 17, 2012 10:02
Сообщений: 2921
Откуда: D-Link, Ryazan
sash333l писал(а):
общался с провайлером про разные подсети - говорит что это нормально

Что у вас за версия прошивки?

_________________
Полезные настройки


Вернуться наверх
 Профиль  
 
 Заголовок сообщения: Re: DIR-620/D1 и LAN
СообщениеДобавлено: Вт фев 05, 2013 10:22 
Не в сети

Зарегистрирован: Вт фев 05, 2013 07:29
Сообщений: 11
Прошивка последняя из доступных - 1.3.6


Вернуться наверх
 Профиль  
 
 Заголовок сообщения: Re: DIR-620/D1 и LAN
СообщениеДобавлено: Вт фев 05, 2013 13:48 
Не в сети
Сотрудник D-LINK
Сотрудник D-LINK

Зарегистрирован: Ср окт 17, 2012 10:02
Сообщений: 2921
Откуда: D-Link, Ryazan
sash333l писал(а):
Прошивка последняя из доступных - 1.3.6

Вы сброс настроек после обновления делали? Кабель интернета не поврежден? Провайдер ничего не говорит о причинах разрыва?

_________________
Полезные настройки


Вернуться наверх
 Профиль  
 
 Заголовок сообщения: Re: DIR-620/D1 и LAN
СообщениеДобавлено: Вт фев 05, 2013 14:53 
Не в сети

Зарегистрирован: Вт фев 05, 2013 07:29
Сообщений: 11
Сброс настроек не делал, сегодня сделаю.
Провайдер тоже грешит на кабель. Его (кабель) можно проверить как-то наверняка?


Вернуться наверх
 Профиль  
 
 Заголовок сообщения: Re: DIR-620/D1 и LAN
СообщениеДобавлено: Вт фев 05, 2013 16:28 
Не в сети
Сотрудник D-LINK
Сотрудник D-LINK

Зарегистрирован: Ср окт 17, 2012 10:02
Сообщений: 2921
Откуда: D-Link, Ryazan
Можно попробовать другой 100% рабочий роутер или вызвать инженера провайдера.

_________________
Полезные настройки


Вернуться наверх
 Профиль  
 
 Заголовок сообщения: Re: DIR-620/D1 и LAN
СообщениеДобавлено: Ср фев 06, 2013 12:49 
Не в сети

Зарегистрирован: Вт фев 05, 2013 07:29
Сообщений: 11
Сброс роутера+перенастройка+заново переобжал кабель - стало получше, но разрывы полностью не пропали.
На пятницу вызвал инженера


Вернуться наверх
 Профиль  
 
 Заголовок сообщения: Re: DIR-620/D1 и LAN
СообщениеДобавлено: Ср фев 13, 2013 20:29 
Не в сети

Зарегистрирован: Ср дек 16, 2009 08:51
Сообщений: 19
скачал прошивку от 11.02.2013г.

ЗДЕСЬ она лежит

завтра-послезавтра попытаюсь потестировать...


Вернуться наверх
 Профиль  
 
 Заголовок сообщения: Re: DIR-620/D1 и LAN
СообщениеДобавлено: Чт фев 14, 2013 07:15 
Не в сети

Зарегистрирован: Вт фев 05, 2013 07:29
Сообщений: 11
Итак после недели боданий результат таков.
Приходили мастера-наладчики от провайдера. С их слов на моем порту оч.много src-ошибок.
- с линией/кабелями все ОК, проверено подключением кабеля напрямую к компу, за 3 дня никаких обрывов;
- проблема очеведно в маршрутизаторе.
Проявляется это следующим образом - подключение обрывается раз в 2-3 часа, при этом в 90% случаев маршрутизатор пингуется, я на него захожу, на заглавной страничке вижу что подключение есть, горит зеленая точка и вижу присвоенный мне IP, но интернет сервера не пингуются.
Исправляется ситуация только перезагрузкой маршрутизатора.

Обновился с 1.3.6 на 1.3.7. Субъективно сократилось количество обрывов. Сейчас где-то 1-2 раза в день.
Итак вопрос что делать и как исправлять ситуацию? Это гарантийный случай? Если лечения не существует хочу сдать назад в магазин.


Вернуться наверх
 Профиль  
 
 Заголовок сообщения: Re: DIR-620/D1 и LAN
СообщениеДобавлено: Чт фев 14, 2013 08:06 
Не в сети

Зарегистрирован: Вт фев 26, 2008 19:07
Сообщений: 9130
Откуда: Москва
сдавайте если сможите ....

_________________
Своим вопросом Вы загоняете меня в ГУГЛ.....
DFL-210 -архив образов
Меня можно найти в боте Телеграмма @MyKingdombot когда РКН перестанет заниматься ерундой :-)
Готовыe платить - пишите
Прикуплю неисправные девайсы ради корпусов ....-> в личку


Вернуться наверх
 Профиль  
 
 Заголовок сообщения: Re: DIR-620/D1 и LAN
СообщениеДобавлено: Пт фев 15, 2013 12:32 
Не в сети

Зарегистрирован: Вт фев 05, 2013 07:29
Сообщений: 11
ну а служба тех.поддержки даст свои комментарии или тихо промолчит?
К сожалению 14-и дневный срок прошляпил, просто сдать в магазин теперь не получится, придется бодаться с сервисом и доказывать что я не дурак.


Вернуться наверх
 Профиль  
 
Показать сообщения за:  Сортировать по:  
Начать новую тему Ответить на тему  [ Сообщений: 31 ]  На страницу Пред.  1, 2, 3  След.

Часовой пояс: UTC + 3 часа


Кто сейчас на форуме

Сейчас этот форум просматривают: нет зарегистрированных пользователей и гости: 575


Вы не можете начинать темы
Вы не можете отвечать на сообщения
Вы не можете редактировать свои сообщения
Вы не можете удалять свои сообщения
Вы не можете добавлять вложения

Найти:
Перейти:  
Создано на основе phpBB® Forum Software © phpBB Group
Русская поддержка phpBB