Не могу настроить роутер ASUS RT 12N/D1

Описание: Обсуждаем все что связано с модемами, радиомодемами, маршрутизаторами, сетевыми картами, а также администрирование сетей и сетевых протоколов.
Правила раздела: http://pc-forums.ru/topic1880.html
Модератор: Junior

#1 chudesnyj » 12.08.2014, 15:58

Доброго времени суток!
проблема с настройкой данного девайса.
Работал нормально, сбросил настройки так как был утерян пароль на wi fi и на вход web морды самого роутера.
Восстановил заводские настройки, прошил последней оф.прошивкой, снова сбросил все настройки, вбил все данные (тип соединения "статический IP", при других вобще не реагирует). После нажатия "применить" появляется интет, работает в течении минуты и пропадает...далее если снова нажать "прменить" вновь инет на минуту и пропадает...
Подскажите пожалуйста в чем проблема может быть???

ЛОГ
Нажмите, чтобы показать/скрыть...
Jan 1 06:00:07 syslogd started: BusyBox v1.17.4
Jan 1 06:00:07 kernel: klogd started: BusyBox v1.17.4 (2014-02-21 17:31:35 CST)
Jan 1 06:00:07 kernel: start_kernel
Jan 1 06:00:07 kernel: Linux version 2.6.22.19 (root@asus) (gcc version 4.2.4) #1 Fri Feb 21 17:34:39 CST 2014
Jan 1 06:00:07 kernel: CPU revision is: 00019749
Jan 1 06:00:07 kernel: Found an ST compatible serial flash with 128 64KB blocks; total size 8MB
Jan 1 06:00:07 kernel: Determined physical RAM map:
Jan 1 06:00:07 kernel: memory: 02000000 @ 00000000 (usable)
Jan 1 06:00:07 kernel: Built 1 zonelists. Total pages: 8128
Jan 1 06:00:07 kernel: Kernel command line: root=/dev/mtdblock2 noinitrd console=ttyS0,115200
Jan 1 06:00:07 kernel: Primary instruction cache 32kB, physically tagged, 4-way, linesize 32 bytes.
Jan 1 06:00:07 kernel: Primary data cache 32kB, 4-way, linesize 32 bytes.
Jan 1 06:00:07 kernel: PID hash table entries: 128 (order: 7, 512 bytes)
Jan 1 06:00:07 kernel: CPU: BCM53572 rev 1 pkg 8 at 300 MHz
Jan 1 06:00:07 kernel: Using 150.000 MHz high precision timer.
Jan 1 06:00:07 kernel: Dentry cache hash table entries: 4096 (order: 2, 16384 bytes)
Jan 1 06:00:07 kernel: Inode-cache hash table entries: 2048 (order: 1, 8192 bytes)
Jan 1 06:00:07 kernel: Mount-cache hash table entries: 512
Jan 1 06:00:07 kernel: PCI: no core
Jan 1 06:00:07 kernel: PCI: no core
Jan 1 06:00:07 kernel: PCI: Fixing up bus 0
Jan 1 06:00:07 kernel: IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
Jan 1 06:00:07 kernel: TCP established hash table entries: 1024 (order: 1, 8192 bytes)
Jan 1 06:00:07 kernel: TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
Jan 1 06:00:07 kernel: pflash: found no supported devices
Jan 1 06:00:07 kernel: Creating 5 MTD partitions on "sflash":
Jan 1 06:00:07 kernel: 0x00000000-0x00020000 : "pmon"
Jan 1 06:00:07 kernel: 0x00020000-0x007f0000 : "linux"
Jan 1 06:00:07 kernel: 0x0014885c-0x005c0000 : "rootfs"
Jan 1 06:00:07 kernel: 0x007f0000-0x00800000 : "nvram"
Jan 1 06:00:07 kernel: 0x00770000-0x007f0000 : "jffs2"
Jan 1 06:00:07 kernel: dev_nvram_init: _nvram_init
Jan 1 06:00:07 kernel: _nvram_init: allocat header: 2151579648, size= 32768
Jan 1 06:00:07 kernel: u32 classifier
Jan 1 06:00:07 kernel: OLD policer on
Jan 1 06:00:07 kernel: Netfilter messages via NETLINK v0.30.
Jan 1 06:00:07 kernel: nf_conntrack version 0.5.0 (512 buckets, 4096 max)
Jan 1 06:00:07 kernel: ipt_time loading
Jan 1 06:00:07 kernel: ip_tables: (C) 2000-2006 Netfilter Core Team
Jan 1 06:00:07 kernel: net/ipv4/netfilter/tomato_ct.c [Feb 21 2014 17:34:01]
Jan 1 06:00:07 kernel: ip6_tables: (C) 2000-2006 Netfilter Core Team
Jan 1 06:00:07 kernel: VFS: Mounted root (squashfs filesystem) readonly.
Jan 1 06:00:07 kernel: Warning: unable to open an initial console.
Jan 1 06:00:07 kernel: ctf: module license 'Proprietary' taints kernel.
Jan 1 06:00:07 kernel: et_module_init: passivemode set to 0x0
Jan 1 06:00:08 kernel: eth0: Broadcom BCM47XX 10/100/1000 Mbps Ethernet Controller 5.110.27.20012
Jan 1 06:00:08 kernel: wl_module_init: passivemode set to 0x0
Jan 1 06:00:08 kernel: eth1: Broadcom BCM4347 802.11 Wireless Controller 5.110.27.20012
Jan 1 06:00:08 kernel: Algorithmics/MIPS FPU Emulator v1.5
Jan 1 06:00:09 stop_nat_rules: apply the redirect_rules!
Jan 1 06:00:09 WAN Connection: Ethernet link down.
Jan 1 06:00:10 RT-N12D1: start httpd
Jan 1 06:00:11 miniupnpd[212]: HTTP listening on port 35022
Jan 1 06:00:11 miniupnpd[212]: Listening for NAT-PMP traffic on port 5351
Jan 1 06:00:12 kernel: nf_conntrack_rtsp v0.6.21 loading
Jan 1 06:00:12 kernel: nf_nat_rtsp v0.6.21 loading
Jan 1 06:00:12 miniupnpd[212]: received signal 15, good-bye
Jan 1 06:00:12 miniupnpd[266]: HTTP listening on port 42985
Jan 1 06:00:12 miniupnpd[266]: Listening for NAT-PMP traffic on port 5351
Jan 1 06:01:09 WAN Connection: WAN was restored.
Jan 1 06:01:09 start_nat_rules: apply the nat_rules(/tmp/nat_rules_eth0_eth0)!
Aug 12 17:20:00 rc_service: ntp 191:notify_rc restart_upnp
Aug 12 17:20:01 miniupnpd[266]: received signal 15, good-bye
Aug 12 17:20:01 miniupnpd[279]: HTTP listening on port 44822
Aug 12 17:20:01 miniupnpd[279]: Listening for NAT-PMP traffic on port 5351
Aug 12 17:20:03 802.1x client: authentication failed
Aug 12 17:20:06 WAN Connection: Detected that the WAN Connection Type was PPPoE. But the PPPoE Setting was not complete.
Aug 12 17:20:06 stop_nat_rules: apply the redirect_rules!
Aug 12 17:25:00 rc_service: httpd 192:notify_rc restart_wan_if 0
Aug 12 17:25:00 stop_wan(): perform DHCP release
Aug 12 17:25:03 start_nat_rules: apply the nat_rules(/tmp/nat_rules_eth0_eth0)!
Aug 12 17:25:03 miniupnpd[279]: received signal 15, good-bye
Aug 12 17:25:03 miniupnpd[320]: HTTP listening on port 51934
Aug 12 17:25:03 miniupnpd[320]: Listening for NAT-PMP traffic on port 5351
Aug 12 17:25:04 WAN Connection: WAN was restored.
Aug 12 17:26:04 802.1x client: authentication failed
Aug 12 17:26:06 WAN Connection: Detected that the WAN Connection Type was PPPoE. But the PPPoE Setting was not complete.
Aug 12 17:26:06 stop_nat_rules: apply the redirect_rules!
Aug 12 17:42:43 rc_service: httpd 192:notify_rc restart_wan_if 0
Aug 12 17:42:43 stop_wan(): perform DHCP release
Aug 12 17:42:45 WAN Connection: WAN was restored.
Aug 12 17:42:45 start_nat_rules: apply the nat_rules(/tmp/nat_rules_eth0_eth0)!
Aug 12 17:42:45 start_nat_rules: apply the nat_rules(/tmp/nat_rules_eth0_eth0)!
Aug 12 17:42:46 miniupnpd[320]: received signal 15, good-bye
Aug 12 17:42:46 miniupnpd[370]: HTTP listening on port 56999
Aug 12 17:42:46 miniupnpd[370]: Listening for NAT-PMP traffic on port 5351
Aug 12 17:43:46 802.1x client: authentication failed
Aug 12 17:43:46 WAN Connection: Detected that the WAN Connection Type was PPPoE. But the PPPoE Setting was not complete.
Aug 12 17:43:46 stop_nat_rules: apply the redirect_rules!
Aug 12 17:44:54 rc_service: httpd 192:notify_rc restart_wan_if 0
Aug 12 17:44:54 stop_wan(): perform DHCP release
Aug 12 17:44:55 WAN Connection: WAN was restored.
Aug 12 17:44:55 start_nat_rules: apply the nat_rules(/tmp/nat_rules_eth0_eth0)!
Aug 12 17:44:57 start_nat_rules: apply the nat_rules(/tmp/nat_rules_eth0_eth0)!
Aug 12 17:44:57 miniupnpd[370]: received signal 15, good-bye
Aug 12 17:44:57 miniupnpd[415]: HTTP listening on port 51010
Aug 12 17:44:57 miniupnpd[415]: Listening for NAT-PMP traffic on port 5351
Aug 12 17:45:58 802.1x client: authentication failed
Aug 12 17:46:01 WAN Connection: Detected that the WAN Connection Type was PPPoE. But the PPPoE Setting was not complete.
Aug 12 17:46:01 stop_nat_rules: apply the redirect_rules!
Aug 12 17:49:05 rc_service: httpd 192:notify_rc restart_wan_if 0
Aug 12 17:49:05 stop_wan(): perform DHCP release
Aug 12 17:49:06 WAN Connection: WAN was restored.
Aug 12 17:49:06 start_nat_rules: apply the nat_rules(/tmp/nat_rules_eth0_eth0)!
Aug 12 17:49:07 start_nat_rules: apply the nat_rules(/tmp/nat_rules_eth0_eth0)!
Aug 12 17:49:08 miniupnpd[415]: received signal 15, good-bye
Aug 12 17:49:08 miniupnpd[460]: HTTP listening on port 60482
Aug 12 17:49:08 miniupnpd[460]: Listening for NAT-PMP traffic on port 5351
Aug 12 17:50:09 802.1x client: authentication failed
Aug 12 17:50:12 WAN Connection: Detected that the WAN Connection Type was PPPoE. But the PPPoE Setting was not complete.
Aug 12 17:50:12 stop_nat_rules: apply the redirect_rules!
Aug 12 17:52:28 rc_service: httpd 192:notify_rc restart_wan_if 0
Aug 12 17:52:28 stop_wan(): perform DHCP release
Aug 12 17:52:31 start_nat_rules: apply the nat_rules(/tmp/nat_rules_eth0_eth0)!
Aug 12 17:52:31 miniupnpd[460]: received signal 15, good-bye
Aug 12 17:52:31 miniupnpd[500]: HTTP listening on port 52961
Aug 12 17:52:31 miniupnpd[500]: Listening for NAT-PMP traffic on port 5351
Aug 12 17:52:33 WAN Connection: WAN was restored.
Aug 12 17:53:32 802.1x client: authentication failed
Aug 12 17:53:34 WAN Connection: Detected that the WAN Connection Type was PPPoE. But the PPPoE Setting was not complete.
Aug 12 17:53:34 stop_nat_rules: apply the redirect_rules!
Aug 12 17:56:50 rc_service: httpd 192:notify_rc restart_wan_if 0
Aug 12 17:56:50 stop_wan(): perform DHCP release
Aug 12 17:56:52 start_nat_rules: apply the nat_rules(/tmp/nat_rules_eth0_eth0)!
Aug 12 17:56:52 miniupnpd[500]: received signal 15, good-bye
Aug 12 17:56:52 miniupnpd[544]: HTTP listening on port 59053
Aug 12 17:56:52 miniupnpd[544]: Listening for NAT-PMP traffic on port 5351
Aug 12 17:56:52 WAN Connection: WAN was restored.
Aug 12 17:57:54 802.1x client: authentication failed
Aug 12 17:57:55 WAN Connection: Detected that the WAN Connection Type was PPPoE. But the PPPoE Setting was not complete.
Aug 12 17:57:55 stop_nat_rules: apply the redirect_rules!
Aug 12 18:39:55 rc_service: httpd 192:notify_rc restart_wan_if 0
Aug 12 18:39:56 stop_wan(): perform DHCP release
Aug 12 18:39:56 WAN Connection: WAN was restored.
Aug 12 18:39:56 start_nat_rules: apply the nat_rules(/tmp/nat_rules_eth0_eth0)!
Aug 12 18:39:58 start_nat_rules: apply the nat_rules(/tmp/nat_rules_eth0_eth0)!
Aug 12 18:39:58 miniupnpd[544]: received signal 15, good-bye
Aug 12 18:39:58 miniupnpd[598]: HTTP listening on port 58112
Aug 12 18:39:58 miniupnpd[598]: Listening for NAT-PMP traffic on port 5351
Aug 12 18:40:59 802.1x client: authentication failed
Aug 12 18:41:03 WAN Connection: Detected that the WAN Connection Type was PPPoE. But the PPPoE Setting was not complete.
Aug 12 18:41:03 stop_nat_rules: apply the redirect_rules!
Aug 12 18:41:28 rc_service: httpd 192:notify_rc restart_wan_if 0
Aug 12 18:41:28 stop_wan(): perform DHCP release
Aug 12 18:41:30 start_nat_rules: apply the nat_rules(/tmp/nat_rules_eth0_eth0)!
Aug 12 18:41:31 miniupnpd[598]: received signal 15, good-bye
Aug 12 18:41:31 miniupnpd[637]: HTTP listening on port 51787
Aug 12 18:41:31 miniupnpd[637]: Listening for NAT-PMP traffic on port 5351
Aug 12 18:41:32 WAN Connection: WAN was restored.
Aug 12 18:42:32 802.1x client: authentication failed
Aug 12 18:42:32 WAN Connection: Detected that the WAN Connection Type was PPPoE. But the PPPoE Setting was not complete.
Aug 12 18:42:32 stop_nat_rules: apply the redirect_rules!
Aug 12 18:43:02 rc_service: httpd 192:notify_rc restart_wan_if 0
Aug 12 18:43:02 stop_wan(): perform DHCP release
Aug 12 18:43:05 start_nat_rules: apply the nat_rules(/tmp/nat_rules_eth0_eth0)!
Aug 12 18:43:05 miniupnpd[637]: received signal 15, good-bye
Aug 12 18:43:05 miniupnpd[681]: HTTP listening on port 39418
Aug 12 18:43:05 miniupnpd[681]: Listening for NAT-PMP traffic on port 5351
Aug 12 18:43:05 WAN Connection: WAN was restored.
Aug 12 18:44:06 802.1x client: authentication failed
Aug 12 18:44:06 WAN Connection: Detected that the WAN Connection Type was PPPoE. But the PPPoE Setting was not complete.
Aug 12 18:44:06 stop_nat_rules: apply the redirect_rules!
Aug 12 18:44:44 rc_service: httpd 192:notify_rc restart_wan_if 0
Aug 12 18:44:44 stop_wan(): perform DHCP release
Aug 12 18:44:46 start_nat_rules: apply the nat_rules(/tmp/nat_rules_eth0_eth0)!
Aug 12 18:44:47 miniupnpd[681]: received signal 15, good-bye
Aug 12 18:44:47 miniupnpd[725]: HTTP listening on port 43718
Aug 12 18:44:47 miniupnpd[725]: Listening for NAT-PMP traffic on port 5351
Aug 12 18:44:47 WAN Connection: WAN was restored.
Aug 12 18:45:48 802.1x client: authentication failed
Aug 12 18:45:49 WAN Connection: Detected that the WAN Connection Type was PPPoE. But the PPPoE Setting was not complete.
Aug 12 18:45:49 stop_nat_rules: apply the redirect_rules!
Aug 12 18:46:16 rc_service: httpd 192:notify_rc restart_wan_if 0
Aug 12 18:46:16 stop_wan(): perform DHCP release
Aug 12 18:46:18 start_nat_rules: apply the nat_rules(/tmp/nat_rules_eth0_eth0)!
Aug 12 18:46:18 miniupnpd[725]: received signal 15, good-bye
Aug 12 18:46:18 miniupnpd[769]: HTTP listening on port 51204
Aug 12 18:46:18 miniupnpd[769]: Listening for NAT-PMP traffic on port 5351
Aug 12 18:46:22 WAN Connection: WAN was restored.
Aug 12 18:47:19 802.1x client: authentication failed
Aug 12 18:47:23 WAN Connection: Detected that the WAN Connection Type was PPPoE. But the PPPoE Setting was not complete.
Aug 12 18:47:23 stop_nat_rules: apply the redirect_rules!
Aug 12 18:49:12 rc_service: httpd 192:notify_rc restart_wan_if 0
Aug 12 18:49:12 stop_wan(): perform DHCP release
Aug 12 18:49:14 start_nat_rules: apply the nat_rules(/tmp/nat_rules_eth0_eth0)!
Aug 12 18:49:14 WAN Connection: WAN was restored.
Aug 12 18:49:15 miniupnpd[769]: received signal 15, good-bye
Aug 12 18:49:15 miniupnpd[818]: HTTP listening on port 41429
Aug 12 18:49:15 miniupnpd[818]: Listening for NAT-PMP traffic on port 5351
Aug 12 18:50:16 802.1x client: authentication failed
Aug 12 18:50:16 WAN Connection: Detected that the WAN Connection Type was PPPoE. But the PPPoE Setting was not complete.
Aug 12 18:50:16 stop_nat_rules: apply the redirect_rules!
Aug 12 18:50:27 rc_service: httpd 192:notify_rc restart_wan_if 0
Aug 12 18:50:28 stop_wan(): perform DHCP release
Aug 12 18:50:30 start_nat_rules: apply the nat_rules(/tmp/nat_rules_eth0_eth0)!
Aug 12 18:50:30 miniupnpd[818]: received signal 15, good-bye
Aug 12 18:50:30 miniupnpd[857]: HTTP listening on port 50870
Aug 12 18:50:30 miniupnpd[857]: Listening for NAT-PMP traffic on port 5351
Aug 12 18:50:35 WAN Connection: WAN was restored.
Aug 12 18:51:31 802.1x client: authentication failed
Aug 12 18:51:36 WAN Connection: Detected that the WAN Connection Type was PPPoE. But the PPPoE Setting was not complete.
Aug 12 18:51:36 stop_nat_rules: apply the redirect_rules!
Aug 12 18:51:36 rc_service: httpd 192:notify_rc restart_wan_if 0
Aug 12 18:51:36 stop_wan(): perform DHCP release
Aug 12 18:51:39 start_nat_rules: apply the nat_rules(/tmp/nat_rules_eth0_eth0)!
Aug 12 18:51:39 miniupnpd[857]: received signal 15, good-bye
Aug 12 18:51:39 miniupnpd[901]: HTTP listening on port 58901
Aug 12 18:51:39 miniupnpd[901]: Listening for NAT-PMP traffic on port 5351
Aug 12 18:51:41 WAN Connection: WAN was restored.
Aug 12 18:52:40 802.1x client: authentication failed
Aug 12 18:52:43 WAN Connection: Detected that the WAN Connection Type was PPPoE. But the PPPoE Setting was not complete.
Aug 12 18:52:43 stop_nat_rules: apply the redirect_rules!
Aug 12 18:55:40 rc_service: httpd 192:notify_rc restart_wan_if 0
Aug 12 18:55:40 stop_wan(): perform DHCP release
Aug 12 18:55:43 start_nat_rules: apply the nat_rules(/tmp/nat_rules_eth0_eth0)!
Aug 12 18:55:43 miniupnpd[901]: received signal 15, good-bye
Aug 12 18:55:43 miniupnpd[945]: HTTP listening on port 42499
Aug 12 18:55:43 miniupnpd[945]: Listening for NAT-PMP traffic on port 5351
Aug 12 18:55:47 WAN Connection: WAN was restored.
Aug 12 18:56:44 802.1x client: authentication failed
Aug 12 18:56:49 WAN Connection: Detected that the WAN Connection Type was PPPoE. But the PPPoE Setting was not complete.
Aug 12 18:56:49 stop_nat_rules: apply the redirect_rules!
Aug 12 18:57:00 rc_service: httpd 192:notify_rc restart_wan_if 0
Aug 12 18:57:00 stop_wan(): perform DHCP release
Aug 12 18:57:02 start_nat_rules: apply the nat_rules(/tmp/nat_rules_eth0_eth0)!
Aug 12 18:57:02 miniupnpd[945]: received signal 15, good-bye
Aug 12 18:57:03 miniupnpd[989]: HTTP listening on port 42537
Aug 12 18:57:03 miniupnpd[989]: Listening for NAT-PMP traffic on port 5351
Aug 12 18:57:03 WAN Connection: WAN was restored.
chudesnyj
Автор темы, Прохожий
Прохожий
Репутация: 0
Лояльность: 0 (+0/−0)
Сообщения: 1
Темы: 1
Зарегистрирован: 12.08.2014
С нами: 2 года 3 месяца

Не могу настроить роутер ASUS RT 12N/D1

 

  • Понравилась тема? Поделись с друзьями!

Вернуться в Сетевое оборудование и технологии

 


  • Похожие темы
    Ответы
    Просмотры
    Последнее сообщение