@mylifeisgame

Подключен компьютер через кабель динамический ip win7 64 bit.Интернет пропадает примерно раз в 20 минут на 25-30 секунд и снова появляется. Пропадает только на компьютере. Во время дисконнекта захожу на страницу роутера и он показывает что соединение есть.Настройка протокола IP для Windows

Имя компьютера . . . . . . . . . : 321
Основной DNS-суффикс . . . . . . :
Тип узла. . . . . . . . . . . . . : Гибридный
IP-маршрутизация включена . . . . : Нет
WINS-прокси включен . . . . . . . : Нет

Ethernet adapter Подключение по локальной сети:

DNS-суффикс подключения . . . . . :
Описание. . . . . . . . . . . . . : Realtek PCIe GBE Family Controlle
Физический адрес. . . . . . . . . : D8-CB-8A-9E-70-40
DHCP включен. . . . . . . . . . . : Да
Автонастройка включена. . . . . . : Да
Локальный IPv6-адрес канала . . . : fe80::9147:4c94:8d63:9cf0%15(Осно
IPv4-адрес. . . . . . . . . . . . : 192.168.1.220(Основной)
Маска подсети . . . . . . . . . . : 255.255.255.0
Аренда получена. . . . . . . . . . : 12 ???? 2016 10.25.58
Срок аренды истекает. . . . . . . . . . : 13 ???? 2016 10.25.56
Основной шлюз. . . . . . . . . : 192.168.1.1
DHCP-сервер. . . . . . . . . . . : 192.168.1.1
IAID DHCPv6 . . . . . . . . . . . : 198757258
DUID клиента DHCPv6 . . . . . . . : 00-01-00-01-1F-16-52-F1-C8-60-00-

DNS-серверы. . . . . . . . . . . : 192.168.1.1
NetBios через TCP/IP. . . . . . . . : Включен

Туннельный адаптер isatap.{99710A16-B54A-4E47-8499-76836C107563}:

Состояние среды. . . . . . . . : Среда передачи недоступна.
DNS-суффикс подключения . . . . . :
Описание. . . . . . . . . . . . . : Адаптер Microsoft ISATAP
Физический адрес. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP включен. . . . . . . . . . . : Нет
Автонастройка включена. . . . . . : Да

Туннельный адаптер isatap.{7641D1B9-17CC-4C39-9600-5BA03A301A13}:

Состояние среды. . . . . . . . : Среда передачи недоступна.
DNS-суффикс подключения . . . . . :
Описание. . . . . . . . . . . . . : Адаптер Microsoft ISATAP #2
Физический адрес. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP включен. . . . . . . . . . . : Нет
Автонастройка включена. . . . . . : Да
Логи роутера
03:00:08 syslogd started: BusyBox v1.17.4
Jan 1 03:00:08 kernel: klogd started: BusyBox v1.17.4 (2015-01-10 21:47:55 CST)
Jan 1 03:00:08 kernel: start_kernel
Jan 1 03:00:08 kernel: Linux version 2.6.22.19 (root@asus) (gcc version 4.2.4) #1 Sat Jan 10 21:50:58 CST 2015
Jan 1 03:00:08 kernel: CPU revision is: 00019749
Jan 1 03:00:08 kernel: Found an ST compatible serial flash with 128 64KB blocks; total size 8MB
Jan 1 03:00:08 kernel: Determined physical RAM map:
Jan 1 03:00:08 kernel: memory: 02000000 @ 00000000 (usable)
Jan 1 03:00:08 kernel: Built 1 zonelists. Total pages: 8128
Jan 1 03:00:08 kernel: Kernel command line: root=/dev/mtdblock2 noinitrd console=ttyS0,115200
Jan 1 03:00:08 kernel: Primary instruction cache 32kB, physically tagged, 4-way, linesize 32 bytes.
Jan 1 03:00:08 kernel: Primary data cache 32kB, 4-way, linesize 32 bytes.
Jan 1 03:00:08 kernel: PID hash table entries: 128 (order: 7, 512 bytes)
Jan 1 03:00:08 kernel: CPU: BCM53572 rev 1 pkg 8 at 300 MHz
Jan 1 03:00:08 kernel: Using 150.000 MHz high precision timer.
Jan 1 03:00:08 kernel: Dentry cache hash table entries: 4096 (order: 2, 16384 bytes)
Jan 1 03:00:08 kernel: Inode-cache hash table entries: 2048 (order: 1, 8192 bytes)
Jan 1 03:00:08 kernel: Mount-cache hash table entries: 512
Jan 1 03:00:08 kernel: PCI: no core
Jan 1 03:00:08 kernel: PCI: no core
Jan 1 03:00:08 kernel: PCI: Fixing up bus 0
Jan 1 03:00:08 kernel: IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
Jan 1 03:00:08 kernel: TCP established hash table entries: 1024 (order: 1, 8192 bytes)
Jan 1 03:00:08 kernel: TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
Jan 1 03:00:08 kernel: pflash: found no supported devices
Jan 1 03:00:08 kernel: Creating 5 MTD partitions on "sflash":
Jan 1 03:00:08 kernel: 0x00000000-0x00020000 : "pmon"
Jan 1 03:00:08 kernel: 0x00020000-0x007f0000 : "linux"
Jan 1 03:00:08 kernel: 0x00148a7c-0x005f0000 : "rootfs"
Jan 1 03:00:08 kernel: 0x007f0000-0x00800000 : "nvram"
Jan 1 03:00:08 kernel: 0x00770000-0x007f0000 : "jffs2"
Jan 1 03:00:08 kernel: dev_nvram_init: _nvram_init
Jan 1 03:00:08 kernel: _nvram_init: allocat header: 2151546880, size= 32768
Jan 1 03:00:08 kernel: u32 classifier
Jan 1 03:00:08 kernel: OLD policer on
Jan 1 03:00:08 kernel: Netfilter messages via NETLINK v0.30.
Jan 1 03:00:08 kernel: nf_conntrack version 0.5.0 (512 buckets, 4096 max)
Jan 1 03:00:08 kernel: ipt_time loading
Jan 1 03:00:08 kernel: ip_tables: (C) 2000-2006 Netfilter Core Team
Jan 1 03:00:08 kernel: net/ipv4/netfilter/tomato_ct.c [Jan 10 2015 21:50:20]
Jan 1 03:00:08 kernel: ip6_tables: (C) 2000-2006 Netfilter Core Team
Jan 1 03:00:08 kernel: VFS: Mounted root (squashfs filesystem) readonly.
Jan 1 03:00:08 kernel: Warning: unable to open an initial console.
Jan 1 03:00:08 kernel: ctf: module license 'Proprietary' taints kernel.
Jan 1 03:00:08 kernel: et_module_init: passivemode set to 0x0
Jan 1 03:00:08 kernel: eth0: Broadcom BCM47XX 10/100/1000 Mbps Ethernet Controller 5.110.27.20012
Jan 1 03:00:08 kernel: wl_module_init: passivemode set to 0x0
Jan 1 03:00:08 kernel: eth1: Broadcom BCM4329 802.11 Wireless Controller 5.110.27.20012
Jan 1 03:00:08 kernel: Algorithmics/MIPS FPU Emulator v1.5
Jan 1 03:00:12 stop_nat_rules: apply the redirect_rules!
Jan 1 03:00:12 WAN Connection: ISP's DHCP did not function properly.
Jan 1 03:00:13 dnsmasq[222]: warning: interface ppp1* does not currently exist
Jan 1 03:00:13 RT-N12C1: start httpd
Jan 1 03:00:14 miniupnpd[242]: HTTP listening on port 41836
Jan 1 03:00:14 miniupnpd[242]: Listening for NAT-PMP traffic on port 5351
Jan 1 03:00:14 start_nat_rules: apply the nat_rules(/tmp/nat_rules_eth0_eth0)!
Jan 1 03:00:14 kernel: nf_conntrack_rtsp v0.6.21 loading
Jan 1 03:00:14 kernel: nf_nat_rtsp v0.6.21 loading
Jan 1 03:00:15 rc_service: udhcpc 248:notify_rc stop_upnp
Jan 1 03:00:15 miniupnpd[242]: received signal 15, good-bye
Jan 1 03:00:15 rc_service: udhcpc 248:notify_rc start_upnp
Jan 1 03:00:15 miniupnpd[296]: HTTP listening on port 33223
Jan 1 03:00:15 miniupnpd[296]: Listening for NAT-PMP traffic on port 5351
Jan 1 03:00:15 dhcp client: bound 172.25.2.254 via 172.25.0.1 during 86400 seconds.
Jan 1 03:00:17 WAN Connection: WAN was restored.
Jan 1 03:00:18 ntp: start NTP update
Jul 12 10:19:49 rc_service: ntp 297:notify_rc restart_upnp
Jul 12 10:19:49 miniupnpd[296]: received signal 15, good-bye
Jul 12 10:19:49 miniupnpd[306]: HTTP listening on port 57451
Jul 12 10:19:49 miniupnpd[306]: Listening for NAT-PMP traffic on port 5351
Jul 12 10:21:57 kernel: vlan0: received packet with own address as source address
Jul 12 10:21:57 kernel: vlan0: received packet with own address as source address
Jul 12 10:21:57 kernel: vlan0: received packet with own address as source address
Jul 12 10:21:57 kernel: vlan0: received packet with own address as source address
Jul 12 10:21:58 kernel: vlan0: received packet with own address as source address
Jul 12 10:22:01 kernel: vlan0: received packet with own address as source address
Jul 12 10:22:02 kernel: vlan0: received packet with own address as source address
Jul 12 10:22:02 kernel: vlan0: received packet with own address as source address
Jul 12 10:22:02 kernel: vlan0: received packet with own address as source address
Jul 12 10:22:02 kernel: vlan0: received packet with own address as source address
Jul 12 10:22:02 kernel: vlan0: received packet with own address as source address
Jul 12 10:22:07 kernel: printk: 20 messages suppressed.
Jul 12 10:22:07 kernel: vlan0: received packet with own address as source address
Jul 12 10:22:12 kernel: printk: 30 messages suppressed.
Jul 12 10:22:12 kernel: vlan0: received packet with own address as source address
Jul 12 10:22:17 kernel: printk: 17 messages suppressed.
Jul 12 10:22:17 kernel: vlan0: received packet with own address as source address
Jul 12 10:22:22 kernel: printk: 8 messages suppressed.
Jul 12 10:22:22 kernel: vlan0: received packet with own address as source address
Jul 12 10:22:29 kernel: printk: 2 messages suppressed.
Jul 12 10:22:29 kernel: vlan0: received packet with own address as source address
Jul 12 10:22:40 kernel: vlan0: received packet with own address as source address
Jul 12 10:22:44 kernel: vlan0: received packet with own address as source address
Jul 12 10:22:44 kernel: vlan0: received packet with own address as source address
Jul 12 10:22:52 kernel: printk: 5 messages suppressed.
Jul 12 10:22:52 kernel: vlan0: received packet with own address as source address
Jul 12 10:22:53 kernel: vlan0: received packet with own address as source address
Jul 12 10:22:57 kernel: printk: 10 messages suppressed.
Jul 12 10:22:57 kernel: vlan0: received packet with own address as source address
Jul 12 10:23:02 kernel: printk: 45 messages suppressed.
Jul 12 10:23:02 kernel: vlan0: received packet with own address as source address
Jul 12 10:23:09 kernel: printk: 3 messages suppressed.
Jul 12 10:23:09 kernel: vlan0: received packet with own address as source address
Jul 12 10:23:17 kernel: printk: 8 messages suppressed.
Jul 12 10:23:17 kernel: vlan0: received packet with own address as source address
Jul 12 10:23:18 kernel: vlan0: received packet with own address as source address
Jul 12 10:23:26 kernel: printk: 1 messages suppressed.
Jul 12 10:23:26 kernel: vlan0: received packet with own address as source address
Jul 12 10:23:30 kernel: vlan0: received packet with own address as source address
Jul 12 10:24:10 kernel: printk: 6 messages suppressed.
Jul 12 10:24:10 kernel: vlan0: received packet with own address as source address
Jul 12 10:24:10 kernel: vlan0: received packet with own address as source address
Jul 12 10:24:10 kernel: vlan0: received packet with own address as source address
Jul 12 10:24:10 kernel: vlan0: received packet with own address as source address
Jul 12 10:24:47 kernel: vlan0: received packet with own address as source address
Jul 12 10:24:47 kernel: vlan0: received packet with own address as source address
Jul 12 10:24:47 kernel: vlan0: received packet with own address as source address
Jul 12 10:24:47 kernel: vlan0: received packet with own address as source address
Jul 12 10:24:47 kernel: vlan0: received packet with own address as source address
Jul 12 10:24:47 kernel: vlan0: received packet with own address as source address
Jul 12 10:24:47 kernel: vlan0: received packet with own address as source address
Jul 12 10:24:48 kernel: vlan0: received packet with own address as source address
Jul 12 10:24:48 kernel: vlan0: received packet with own address as source address
Jul 12 10:24:48 kernel: vlan0: received packet with own address as source address
Jul 12 10:24:52 kernel: printk: 73 messages suppressed.
Jul 12 10:24:52 kernel: vlan0: received packet with own address as source address
Jul 12 10:24:57 kernel: printk: 42 messages suppressed.
Jul 12 10:24:57 kernel: vlan0: received packet with own address as source address
Jul 12 10:25:05 kernel: printk: 22 messages suppressed.
Jul 12 10:25:05 kernel: vlan0: received packet with own address as source address
Jul 12 10:25:15 kernel: printk: 13 messages suppressed.
Jul 12 10:25:15 kernel: vlan0: received packet with own address as source address
Jul 12 10:25:18 kernel: vlan0: received packet with own address as source address
Jul 12 10:25:40 kernel: vlan0: received packet with own address as source address
Jul 12 10:25:40 kernel: vlan0: received packet with own address as source address
Jul 12 10:25:40 kernel: vlan0: received packet with own address as source address
Jul 12 10:25:40 kernel: vlan0: received packet with own address as source address
Jul 12 10:25:40 kernel: vlan0: received packet with own address as source address
Jul 12 10:25:47 kernel: printk: 2 messages suppressed.
Jul 12 10:25:47 kernel: vlan0: received packet with own address as source address
Jul 12 10:25:48 kernel: vlan0: received packet with own address as source address
Jul 12 10:35:00 rc_service: httpd 223:notify_rc restart_wan_if 0
Jul 12 10:35:01 WAN Connection: ISP's DHCP did not function properly.
Jul 12 10:35:01 stop_nat_rules: apply the redirect_rules!
Jul 12 10:35:02 start_nat_rules: apply the nat_rules(/tmp/nat_rules_eth0_eth0)!
Jul 12 10:35:03 rc_service: udhcpc 390:notify_rc stop_upnp
Jul 12 10:35:03 miniupnpd[306]: received signal 15, good-bye
Jul 12 10:35:03 rc_service: udhcpc 390:notify_rc start_upnp
Jul 12 10:35:03 rc_service: waitting "stop_upnp" via udhcpc ...
Jul 12 10:35:04 miniupnpd[421]: HTTP listening on port 60014
Jul 12 10:35:04 miniupnpd[421]: Listening for NAT-PMP traffic on port 5351
Jul 12 10:35:04 dhcp client: bound 172.25.2.254 via 172.25.0.1 during 86400 seconds.
Jul 12 10:35:06 WAN Connection: WAN was restored.
Jul 12 10:35:07 ntp: start NTP update
DHCP запросы переставлял с агрессивного на обычный .

Судя по логам что-то с DHCP но я к сожалению не разбираюсь в достаточной мере в этом.

Добавлено через 17 минут
Роутер Asus RTN 12 C

0

@VexMD

звоните провайдеру
это у него проблема

0

@mylifeisgame

Провайдер говорит что все оборудование работает нормально а роутеры он настривать и не обязан

Добавлено через 1 минуту
Провайдер говорит что у него оборудование работает нормально а роутеры он настраивает только за деньги. Что конкретно сказать ему?
двойное сообщение кстати из-за того самого дисконнекта.

Добавлено через 11 часов 17 минут
Выставление айпи в ручную из диапазона роутера не помогло.

0

@.None

покажите скрин статус WAN подключения в роутере

адреса вручную где выставляли?

0