Дорогие пользователи! У нас появился новый форум на платформе tp-link.community (Сообщество)

Форум доступен по ссылке https://community.tp-link.com/ru

Если при регистрации в Сообществе Вы укажете адрес электронный почты, который используете на данном форуме, то Ваши данные будут перенесены на форум Сообщества автоматически.
Также, если на форуме Сообщества Ваш никнейм будет занят, то Вам предложат сменить его или оставить, но с приставкой "_RU".

Подробнее Вы можете прочитать тут: https://community.tp-link.com/ru/home/f ... pic/501542

Убедительная просьба не дублировать темы на старом/новом форуме.

Проблемы при подключении к сети интернет

Многофункциональный беспроводной маршрутизатор серии N со скоростью передачи данных до 300 Мбит/с
Dmitriy
Модератор
Модератор
Сообщения: 2716
Зарегистрирован: 19 авг 2011, 14:59
Страна: Россия
Откуда: Москва
Контактная информация:

Проблемы при подключении к сети интернет

Сообщение Dmitriy » 01 мар 2012, 14:56

Если ваше устройство не подключается к сети интернет, пожалуйста заполните следующую форму перед обращением:

1. Hardware версия устройства (посмотреть можно в статусе, либо на коробке)
2. Версия прошивки (смотреть там же)
3. Ваша страна.
4. Название провайдера.
5. Тип подключения (например PPTP\L2TP\PPPoE\dynamic ip)

Если вы испытываете проблемы подключения непосредственно к роутеру, пожалуйста, максимально подробно опишите ситуацию(когда возникла проблема) и настройки (роутера и компьютера).


Добавьте скриншот настроек Network - WAN.
Также обязательно выложить содержимое LOG файла. Это можно сделать, если зайти в меню роутера System Tools - System LOG, нажать SAVE LOG и содержимое этого лога выложить здесь.

Первичные сообщения без данной формы не рассматриваются и удаляются.

XarconneN
Сообщения: 6
Зарегистрирован: 04 июн 2017, 13:36
Страна: Россия

Re: Проблемы при подключении к сети интернет

Сообщение XarconneN » 05 июн 2017, 13:59

####################################################################
# TL-WR842N System Log
# Time = 2015-01-01 17:49:00 64142s
# H-Ver = WR842N v3 00000000 : S-Ver = 3.16.9 Build 151214 Rel.61635n
# L = 192.168.0.1 : M = 255.255.255.0
# W1 = DHCP : W = 87.240.37.236 : M = 255.255.248.0 : G = 87.240.32.1
####################################################################

1st day 16:13:46 3G/4G INFO primary device is not in
1st day 16:14:16 3G/4G INFO primary device is not in
1st day 16:14:46 3G/4G INFO primary device is not in
1st day 16:15:17 3G/4G INFO primary device is not in
1st day 16:15:47 3G/4G INFO primary device is not in
1st day 16:16:17 3G/4G INFO primary device is not in
1st day 16:16:47 3G/4G INFO primary device is not in
1st day 16:17:17 3G/4G INFO primary device is not in
1st day 16:17:47 3G/4G INFO primary device is not in
1st day 16:18:17 3G/4G INFO primary device is not in
1st day 16:18:48 3G/4G INFO primary device is not in
1st day 16:19:18 3G/4G INFO primary device is not in
1st day 16:19:48 3G/4G INFO primary device is not in
1st day 16:20:18 3G/4G INFO primary device is not in
1st day 16:20:48 3G/4G INFO primary device is not in
1st day 16:21:18 3G/4G INFO primary device is not in
1st day 16:21:48 3G/4G INFO primary device is not in
1st day 16:22:19 3G/4G INFO primary device is not in
1st day 16:22:49 3G/4G INFO primary device is not in
1st day 16:23:19 3G/4G INFO primary device is not in
1st day 16:23:49 3G/4G INFO primary device is not in
1st day 16:24:19 3G/4G INFO primary device is not in
1st day 16:24:49 3G/4G INFO primary device is not in
1st day 16:25:19 3G/4G INFO primary device is not in
1st day 16:25:49 3G/4G INFO primary device is not in
1st day 16:26:20 3G/4G INFO primary device is not in
1st day 16:26:50 3G/4G INFO primary device is not in
1st day 16:27:20 3G/4G INFO primary device is not in
1st day 16:27:50 3G/4G INFO primary device is not in
1st day 16:28:20 3G/4G INFO primary device is not in
1st day 16:28:50 3G/4G INFO primary device is not in
1st day 16:29:20 3G/4G INFO primary device is not in
1st day 16:29:51 3G/4G INFO primary device is not in
1st day 16:30:21 3G/4G INFO primary device is not in
1st day 16:30:51 3G/4G INFO primary device is not in
1st day 16:31:21 3G/4G INFO primary device is not in
1st day 16:31:51 3G/4G INFO primary device is not in
1st day 16:32:21 3G/4G INFO primary device is not in
1st day 16:32:51 3G/4G INFO primary device is not in
1st day 16:33:22 3G/4G INFO primary device is not in
1st day 16:33:52 3G/4G INFO primary device is not in
1st day 16:34:22 3G/4G INFO primary device is not in
1st day 16:34:52 3G/4G INFO primary device is not in
1st day 16:35:22 3G/4G INFO primary device is not in
1st day 16:35:52 3G/4G INFO primary device is not in
1st day 16:36:22 3G/4G INFO primary device is not in
1st day 16:36:52 3G/4G INFO primary device is not in
1st day 16:37:23 3G/4G INFO primary device is not in
1st day 16:37:53 3G/4G INFO primary device is not in
1st day 16:38:23 3G/4G INFO primary device is not in
1st day 16:38:53 3G/4G INFO primary device is not in
1st day 16:39:23 3G/4G INFO primary device is not in
1st day 16:39:53 3G/4G INFO primary device is not in
1st day 16:40:23 3G/4G INFO primary device is not in
1st day 16:40:54 3G/4G INFO primary device is not in
1st day 16:41:24 3G/4G INFO primary device is not in
1st day 16:41:54 3G/4G INFO primary device is not in
1st day 16:42:24 3G/4G INFO primary device is not in
1st day 16:42:54 3G/4G INFO primary device is not in
1st day 16:43:24 3G/4G INFO primary device is not in
1st day 16:43:54 3G/4G INFO primary device is not in
1st day 16:44:25 3G/4G INFO primary device is not in
1st day 16:44:55 3G/4G INFO primary device is not in
1st day 16:45:25 3G/4G INFO primary device is not in
1st day 16:45:55 3G/4G INFO primary device is not in
1st day 16:46:25 3G/4G INFO primary device is not in
1st day 16:46:55 3G/4G INFO primary device is not in
1st day 16:47:25 3G/4G INFO primary device is not in
1st day 16:47:55 3G/4G INFO primary device is not in
1st day 16:48:26 3G/4G INFO primary device is not in
1st day 16:48:56 3G/4G INFO primary device is not in
1st day 16:49:26 3G/4G INFO primary device is not in
1st day 16:49:56 3G/4G INFO primary device is not in
1st day 16:50:26 3G/4G INFO primary device is not in
1st day 16:50:56 3G/4G INFO primary device is not in
1st day 16:51:26 3G/4G INFO primary device is not in
1st day 16:51:57 3G/4G INFO primary device is not in
1st day 16:52:27 3G/4G INFO primary device is not in
1st day 16:52:57 3G/4G INFO primary device is not in
1st day 16:53:27 3G/4G INFO primary device is not in
1st day 16:53:57 3G/4G INFO primary device is not in
1st day 16:54:27 3G/4G INFO primary device is not in
1st day 16:54:57 3G/4G INFO primary device is not in
1st day 16:55:28 3G/4G INFO primary device is not in
1st day 16:55:58 3G/4G INFO primary device is not in
1st day 16:56:28 3G/4G INFO primary device is not in
1st day 16:56:58 3G/4G INFO primary device is not in
1st day 16:57:28 3G/4G INFO primary device is not in
1st day 16:57:58 3G/4G INFO primary device is not in
1st day 16:58:28 3G/4G INFO primary device is not in
1st day 16:58:58 3G/4G INFO primary device is not in
1st day 16:59:29 3G/4G INFO primary device is not in
1st day 16:59:59 3G/4G INFO primary device is not in
1st day 17:00:29 3G/4G INFO primary device is not in
1st day 17:00:59 3G/4G INFO primary device is not in
1st day 17:01:29 3G/4G INFO primary device is not in
1st day 17:01:59 3G/4G INFO primary device is not in
1st day 17:02:29 3G/4G INFO primary device is not in
1st day 17:03:00 3G/4G INFO primary device is not in
1st day 17:03:30 3G/4G INFO primary device is not in
1st day 17:04:00 3G/4G INFO primary device is not in
1st day 17:04:30 3G/4G INFO primary device is not in
1st day 17:05:00 3G/4G INFO primary device is not in
1st day 17:05:30 3G/4G INFO primary device is not in
1st day 17:06:00 3G/4G INFO primary device is not in
1st day 17:06:30 3G/4G INFO primary device is not in
1st day 17:07:01 3G/4G INFO primary device is not in
1st day 17:07:31 3G/4G INFO primary device is not in
1st day 17:08:01 3G/4G INFO primary device is not in
1st day 17:08:31 3G/4G INFO primary device is not in
1st day 17:09:01 3G/4G INFO primary device is not in
1st day 17:09:31 3G/4G INFO primary device is not in
1st day 17:10:01 3G/4G INFO primary device is not in
1st day 17:10:32 3G/4G INFO primary device is not in
1st day 17:11:02 3G/4G INFO primary device is not in
1st day 17:11:32 3G/4G INFO primary device is not in
1st day 17:12:02 3G/4G INFO primary device is not in
1st day 17:12:32 3G/4G INFO primary device is not in
1st day 17:13:02 3G/4G INFO primary device is not in
1st day 17:13:32 3G/4G INFO primary device is not in
1st day 17:14:03 3G/4G INFO primary device is not in
1st day 17:14:33 3G/4G INFO primary device is not in
1st day 17:15:03 3G/4G INFO primary device is not in
1st day 17:15:33 3G/4G INFO primary device is not in
1st day 17:16:03 3G/4G INFO primary device is not in
1st day 17:16:33 3G/4G INFO primary device is not in
1st day 17:17:03 3G/4G INFO primary device is not in
1st day 17:17:33 3G/4G INFO primary device is not in
1st day 17:18:04 3G/4G INFO primary device is not in
1st day 17:18:34 3G/4G INFO primary device is not in
1st day 17:19:04 3G/4G INFO primary device is not in
1st day 17:19:34 3G/4G INFO primary device is not in
1st day 17:20:04 3G/4G INFO primary device is not in
1st day 17:20:34 3G/4G INFO primary device is not in
1st day 17:21:04 3G/4G INFO primary device is not in
1st day 17:21:35 3G/4G INFO primary device is not in
1st day 17:22:05 3G/4G INFO primary device is not in
1st day 17:22:35 3G/4G INFO primary device is not in
1st day 17:23:05 3G/4G INFO primary device is not in
1st day 17:23:35 3G/4G INFO primary device is not in
1st day 17:24:05 3G/4G INFO primary device is not in
1st day 17:24:35 3G/4G INFO primary device is not in
1st day 17:25:06 3G/4G INFO primary device is not in
1st day 17:25:36 3G/4G INFO primary device is not in
1st day 17:26:06 3G/4G INFO primary device is not in
1st day 17:26:36 3G/4G INFO primary device is not in
1st day 17:27:06 3G/4G INFO primary device is not in
1st day 17:27:36 3G/4G INFO primary device is not in
1st day 17:28:06 3G/4G INFO primary device is not in
1st day 17:28:36 3G/4G INFO primary device is not in
1st day 17:29:07 3G/4G INFO primary device is not in
1st day 17:29:37 3G/4G INFO primary device is not in
1st day 17:30:07 3G/4G INFO primary device is not in
1st day 17:30:37 3G/4G INFO primary device is not in
1st day 17:31:07 3G/4G INFO primary device is not in
1st day 17:31:37 3G/4G INFO primary device is not in
1st day 17:32:07 3G/4G INFO primary device is not in
1st day 17:32:38 3G/4G INFO primary device is not in
1st day 17:33:08 3G/4G INFO primary device is not in
1st day 17:33:38 3G/4G INFO primary device is not in
1st day 17:34:08 3G/4G INFO primary device is not in
1st day 17:34:38 3G/4G INFO primary device is not in
1st day 17:35:08 3G/4G INFO primary device is not in
1st day 17:35:38 3G/4G INFO primary device is not in
1st day 17:36:09 3G/4G INFO primary device is not in
1st day 17:36:39 3G/4G INFO primary device is not in
1st day 17:37:09 3G/4G INFO primary device is not in
1st day 17:37:39 3G/4G INFO primary device is not in
1st day 17:38:09 3G/4G INFO primary device is not in
1st day 17:38:39 3G/4G INFO primary device is not in
1st day 17:39:09 3G/4G INFO primary device is not in
1st day 17:39:39 3G/4G INFO primary device is not in
1st day 17:40:10 3G/4G INFO primary device is not in
1st day 17:40:40 3G/4G INFO primary device is not in
1st day 17:41:10 3G/4G INFO primary device is not in
1st day 17:41:40 3G/4G INFO primary device is not in
1st day 17:42:10 3G/4G INFO primary device is not in
1st day 17:42:40 3G/4G INFO primary device is not in
1st day 17:43:10 3G/4G INFO primary device is not in
1st day 17:43:41 3G/4G INFO primary device is not in
1st day 17:44:11 3G/4G INFO primary device is not in
1st day 17:44:41 3G/4G INFO primary device is not in
1st day 17:45:11 3G/4G INFO primary device is not in
1st day 17:45:41 3G/4G INFO primary device is not in
1st day 17:46:11 3G/4G INFO primary device is not in
1st day 17:46:41 3G/4G INFO primary device is not in
1st day 17:47:12 3G/4G INFO primary device is not in
1st day 17:47:42 3G/4G INFO primary device is not in
1st day 17:48:11 IPv6 INFO DHCP6C: Actual network device is eth1, DUID type is 0.
1st day 17:48:11 IPv6 INFO wide-dhcpv6: get hardware ID on device eth1.
1st day 17:48:11 IPv6 INFO wide-dhcpv6: Get a hardware address on device eth1 successfully.
1st day 17:48:11 IPv6 INFO Generated a new DUID: 00:01:00:01:1c:38:44:d9:84:16:f9:22:7f:4d
1st day 17:48:11 IPv6 INFO Fork a child process to communicate with httpd.
1st day 17:48:11 IPv6 INFO DHCP6C main loop running.
1st day 17:48:11 IPv6 NOTICE Run cmd dhcp6c -c /tmp/dhcp6c.conf -I eth1 -p /tmp/dhcp6c.pid eth1 OK.
1st day 17:48:11 DHCP INFO DHCPC perform a DHCP renew
1st day 17:48:11 DHCP INFO DHCPC Send DISCOVER with request ip 57F0232C and unicast flag 0
1st day 17:48:13 DHCP INFO DHCPC Send DISCOVER with request ip 57F0232C and unicast flag 0
1st day 17:48:15 DHCP INFO DHCPC Send DISCOVER with request ip 57F0232C and unicast flag 0
1st day 17:48:19 DHCP INFO DHCPC Send DISCOVER with request ip 57F0232C and unicast flag 1
1st day 17:48:21 DHCP INFO DHCPC Send DISCOVER with request ip 57F0232C and unicast flag 1
1st day 17:48:21 DHCP INFO DHCPS:Recv REQUEST from 34:97:F6:37:AF:3D
1st day 17:48:22 DHCP INFO DHCPS:REQUEST ip 57f0252d is not in the address pool
1st day 17:48:22 DHCP INFO DHCPS:Send NAK
1st day 17:48:22 DHCP INFO DHCPS:Recv DISCOVER from 34:97:F6:37:AF:3D
1st day 17:48:23 DHCP INFO DHCPS:Send OFFER with ip 192.168.0.100
1st day 17:48:23 DHCP INFO DHCPS:Recv REQUEST from 34:97:F6:37:AF:3D
1st day 17:48:23 DHCP INFO DHCPS:Send ACK to 192.168.0.100
1st day 17:48:23 DHCP INFO DHCPC DHCP Service unavailable, recv no OFFER
1st day 17:48:23 DHCP INFO dhcpc_ipc_data_rcv_router 846 : current network type = 0
1st day 17:48:33 DHCP INFO DHCPC Send DISCOVER with request ip 57F0232C and unicast flag 0
1st day 17:48:33 DHCP INFO DHCPC Recv OFFER from server abb4001 with ip 57f025ec
1st day 17:48:33 DHCP INFO DHCPC Send REQUEST to server abb4001 with request ip 57f025ec
1st day 17:48:35 DHCP INFO DHCPC Send REQUEST to server abb4001 with request ip 57f025ec
1st day 17:48:36 DHCP INFO DHCPC Recv ACK from server abb4001 with ip 57f025ec lease time 3599
1st day 17:48:36 DHCP INFO DHCPC:GET ip:57f025ec mask:fffff800 gateway:57f02001 dns1:d555ccbe dns2:d555ccdc static route:0
1st day 17:48:36 DHCP INFO Mark the ip 57f025ec for option 50.
1st day 17:48:37 DHCP INFO dhcpc_ipc_data_rcv_router 846 : current network type = 0
1st day 17:48:37 DHCP NOTICE Dynamic IP(DHCP Client) obtained an IP successfully
1st day 17:48:42 IPv6 NOTICE Dhcp6c is timeout.
1st day 17:48:42 IPv6 NOTICE Reset DHCPv6 information.
1st day 17:48:44 IPv6 INFO DHCP6C: Actual network device is eth1, DUID type is 0.
1st day 17:48:44 IPv6 INFO wide-dhcpv6: get hardware ID on device eth1.
1st day 17:48:44 IPv6 INFO wide-dhcpv6: Get a hardware address on device eth1 successfully.
1st day 17:48:44 IPv6 INFO Generated a new DUID: 00:01:00:01:1c:38:44:fb:84:16:f9:22:7f:4d
1st day 17:48:44 IPv6 INFO Fork a child process to communicate with httpd.
1st day 17:48:44 IPv6 INFO DHCP6C main loop running.
1st day 17:48:44 IPv6 NOTICE Run cmd dhcp6c -c /tmp/dhcp6c.conf -I eth1 -p /tmp/dhcp6c.pid eth1 OK.
поменял на старый dir-320 все работает,вопросов нет,на новом по прежнему горит лампа о проблемах с вап.

Goodwin
Сообщения: 4361
Зарегистрирован: 25 май 2011, 10:56
Страна: Россия

Re: Проблемы при подключении к сети интернет

Сообщение Goodwin » 05 июн 2017, 14:01

1st day 17:45:41 3G/4G INFO primary device is not in
Роутер ВООБЩЕ не видит что к нему что-либо через WAN порт было подключено. Проверяли провод - рабочий? Индикатор WAN горит когда кабель в WAN подключаете?
Перед тем, как создать тему, посетите раздел ЧАСТО ЗАДАВАЕМЫЕ ВОПРОСЫ
TP-LINK Archer C7v2
Личные сообщения по техническим проблемам без сообщения на форуме не рассматриваются!

XarconneN
Сообщения: 6
Зарегистрирован: 04 июн 2017, 13:36
Страна: Россия

Re: Проблемы при подключении к сети интернет

Сообщение XarconneN » 05 июн 2017, 14:04

Goodwin писал(а):
1st day 17:45:41 3G/4G INFO primary device is not in
Роутер ВООБЩЕ не видит что к нему что-либо через WAN порт было подключено. Проверяли провод - рабочий? Индикатор WAN горит когда кабель в WAN подключаете?
Кабель рабочий,при подключении загораеться зеленый индикатор,через 10 секунд он оранджевый,кабель проверил через прямое подключение и 2 роутера,через последний сейчас печатаю этот текст.

Goodwin
Сообщения: 4361
Зарегистрирован: 25 май 2011, 10:56
Страна: Россия

Re: Проблемы при подключении к сети интернет

Сообщение Goodwin » 05 июн 2017, 14:10

В таком случае остаётся последнее попробовать: В настройках роутера Сеть - IPTV, МОСТ - настроить порт LAN4 как мост, сохранить, перезагрузить и подключить кабель провайдера туда. Если так заработает, значит сгорел WAN порт, но можно работать через LAN4
Перед тем, как создать тему, посетите раздел ЧАСТО ЗАДАВАЕМЫЕ ВОПРОСЫ
TP-LINK Archer C7v2
Личные сообщения по техническим проблемам без сообщения на форуме не рассматриваются!

XarconneN
Сообщения: 6
Зарегистрирован: 04 июн 2017, 13:36
Страна: Россия

Re: Проблемы при подключении к сети интернет

Сообщение XarconneN » 05 июн 2017, 15:07

Goodwin писал(а):В таком случае остаётся последнее попробовать: В настройках роутера Сеть - IPTV, МОСТ - настроить порт LAN4 как мост, сохранить, перезагрузить и подключить кабель провайдера туда. Если так заработает, значит сгорел WAN порт, но можно работать через LAN4
а не проще тогда понести в гарантийку?я купил уже роутер на замену,если это не мой косяк,то почему бы не извращаться и не сдать роутер,который сгорел за 3 месяца?

Goodwin
Сообщения: 4361
Зарегистрирован: 25 май 2011, 10:56
Страна: Россия

Re: Проблемы при подключении к сети интернет

Сообщение Goodwin » 05 июн 2017, 15:35

а не проще тогда понести в гарантийку?я купил уже роутер на замену,если это не мой косяк,то почему бы не извращаться и не сдать роутер,который сгорел за 3 месяца?
Можно и по гарантии, если гарантия есть. Но это уже не тема данного форума. Моя задача предложить вам решение и не гнать вас в сервис.
Перед тем, как создать тему, посетите раздел ЧАСТО ЗАДАВАЕМЫЕ ВОПРОСЫ
TP-LINK Archer C7v2
Личные сообщения по техническим проблемам без сообщения на форуме не рассматриваются!

XarconneN
Сообщения: 6
Зарегистрирован: 04 июн 2017, 13:36
Страна: Россия

Re: Проблемы при подключении к сети интернет

Сообщение XarconneN » 05 июн 2017, 15:39

Goodwin писал(а):
а не проще тогда понести в гарантийку?я купил уже роутер на замену,если это не мой косяк,то почему бы не извращаться и не сдать роутер,который сгорел за 3 месяца?
Можно и по гарантии, если гарантия есть. Но это уже не тема данного форума. Моя задача предложить вам решение и не гнать вас в сервис.
Спасибо за консультацию :) Гарантия есть

Jutah
Сообщения: 1
Зарегистрирован: 26 мар 2019, 14:08
Страна: Россия

Re: Проблемы при подключении к сети интернет

Сообщение Jutah » 26 мар 2019, 15:33

Добрый день, у меня следующая проблема: При включении роутера не подключается автоматически интернет по PPTP. Если зайти в настройки WAN и нажать кнопку сохранить - интернет тут же подключается. С компьютера всё работает. Видел тему с такой проблемой у другой модели только там был L2TP протокол. Прикладываю лог с двух попыток в которых я: Включил роутер, подождал пока загрузится, зашёл в настройки WAN и нажал сохранить. PPTP после этого подключился.

1. WR842N v5 00000001
2. 1.1.0 0.9.1 v0001.0 Build 180425 Rel.71779n
3. РФ
4. Никос (nicos.ru)
5. PPTP
Изображение
2016-01-01 03:00:14 [6] 3G: Hotplug: id[0]=12d1_1446, class[0]=unswitched_3g, action[0]=add
2016-01-01 03:00:17 [6] 3G: 134: handle_card add card.
2016-01-01 03:00:18 [6] 3G: 3G/4G Modem vendorID: 0x12d1; productID: 0x1446
2016-01-01 03:00:18 [5] DHCPD: Recv REQUEST from 78:F2:9E:90:DF:EA
2016-01-01 03:00:19 [5] DHCPD: Send ACK to 192.168.0.100
2016-01-01 03:00:19 [5] DHCPD: Recv REQUEST from 94:C6:91:15:B0:3F
2016-01-01 03:00:19 [6] 3G: 319: can't switch usb device.
2016-01-01 03:00:19 [5] DHCPD: Send ACK to 192.168.0.197
2016-01-01 03:00:19 [5] DHCPD: Recv DISCOVER from 00:17:C8:56:DB:78
2016-01-01 03:00:19 [5] DHCPD: Send OFFER with ip 192.168.0.101
2016-01-01 03:00:19 [5] DHCPD: Recv REQUEST from 00:17:C8:56:DB:78
2016-01-01 03:00:20 [5] DHCPD: Send ACK to 192.168.0.101
2016-01-01 03:00:22 [5] DHCPD: Recv INFORM from 94:C6:91:15:B0:3F
2016-01-01 03:00:22 [3] 3G: 421: get card info error, maybe usb_modeswitch.
2016-01-01 03:00:31 [5] DHCPD: Recv DISCOVER from 00:17:C8:56:DB:78
2016-01-01 03:00:31 [5] DHCPD: Send OFFER with ip 192.168.0.101
2016-01-01 03:00:31 [5] DHCPD: Recv REQUEST from 00:17:C8:56:DB:78
2016-01-01 03:00:32 [5] DHCPD: Send ACK to 192.168.0.101
2016-01-01 03:00:33 [3] 3G: 792: handle_card failed.
2016-01-01 03:00:35 [6] 3G: Hotplug: id[0]=12d1_1446, class[0]=unswitched_3g, action[0]=remove
2016-01-01 03:00:35 [6] 3G: Hotplug: id[1]=12d1_1003, class[1]=switched_3g, action[1]=add
2016-01-01 03:00:37 [6] 3G: 134: handle_card add card.
2016-01-01 03:00:38 [6] 3G: 3G/4G Modem vendorID: 0x12d1; productID: 0x1003
2016-01-01 03:00:39 [6] 3G: 314: go to already_switched.
2016-01-01 03:00:39 [6] 3G: 558: already_switched.
2016-01-01 03:00:40 [6] 3G: 576: After switch:cinfo.idVendor(12d1), cinfo.idProduct(1003).
2016-01-01 03:00:40 [6] 3G: 585 File:
2016-01-01 03:00:40 [6] 3G: 589 Before judgeModemTypeByAfterSwitchID, isNeedSwitch = 1, targetPid = 0x1003
2016-01-01 03:00:40 [6] 3G: 613 After judgeModemTypeByAfterSwitchID, modemType = 0
2016-01-01 03:00:41 [5] DHCPD: Recv REQUEST from 18:56:80:AB:AB:D0
2016-01-01 03:00:42 [5] DHCPD: Send ACK to 192.168.0.102
2016-01-01 03:00:45 [6] 3G: =>I:* If#= 1 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=usbserial_generic

2016-01-01 03:00:45 [6] 3G: =>E: Ad=83(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms

2016-01-01 03:00:45 [6] 3G: =>E: Ad=02(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms

2016-01-01 03:00:45 [6] 3G: =>I:* If#= 2 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 Driver=usb-storage

2016-01-01 03:00:45 [6] 3G: =>E: Ad=84(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms

2016-01-01 03:00:45 [6] 3G: =>E: Ad=03(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms

2016-01-01 03:00:45 [6] 3G: =>I:* If#= 3 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 Driver=usb-storage

2016-01-01 03:00:45 [6] 3G: =>E: Ad=04(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms

2016-01-01 03:00:45 [6] 3G: =>E: Ad=85(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms

2016-01-01 03:00:45 [6] 3G: =>

2016-01-01 03:00:45 [6] 3G: =>T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=480 MxCh= 1

2016-01-01 03:00:45 [6] 3G: =>B: Alloc= 0/800 us ( 0%), #Int= 0, #Iso= 0

2016-01-01 03:00:45 [6] 3G: =>D: Ver= 2.00 Cls=09(hub ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1

2016-01-01 03:00:45 [6] 3G: =>P: Vendor=1d6b ProdID=0002 Rev= 2.06

2016-01-01 03:00:45 [6] 3G: =>S: Manufacturer=Linux 2.6.36 ehci_hcd

2016-01-01 03:00:45 [6] 3G: =>S: Product=Ralink EHCI Host Controller

2016-01-01 03:00:45 [6] 3G: =>S: SerialNumber=rt3xxx

2016-01-01 03:00:45 [6] 3G: =>C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA

2016-01-01 03:00:45 [6] 3G: =>I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub

2016-01-01 03:00:45 [6] 3G: =>E: Ad=81(I) Atr=03(Int.) MxPS= 4 Ivl=256ms

2016-01-01 03:00:46 [6] 3G: Main interface_index[0] = 0
2016-01-01 03:00:46 [6] 3G: Vice interface_index[1] = 1
2016-01-01 03:00:47 [6] 3G: Switched 3G modem vendorId:0x12d1; productId:0x1003
2016-01-01 03:00:47 [6] 3G: Line:1152 cmd: modem_scan -d /dev/ttyUSB0 -f "/usr/bin/chat -S -V -f /var/3G/script" > /var/3G/modem_info 2>&1 &
2016-01-01 03:00:48 [6] 3G: Line 1190:
2016-01-01 03:00:48 [6] 3G: Line 1190: OK
2016-01-01 03:00:48 [6] 3G: Line 1190: ATZ
2016-01-01 03:00:48 [6] 3G: Line 1190: OK
2016-01-01 03:00:48 [6] 3G: Line 1190: AT+CGMM
2016-01-01 03:00:48 [6] 3G: get_modem_info_file 107 getModemParamByScript return valid type = 1
2016-01-01 03:00:48 [6] 3G: Line:1152 cmd: modem_scan -d /dev/ttyUSB0 -f "/usr/bin/chat -S -V -f /var/3G/script" > /var/3G/modem_info 2>&1 &
2016-01-01 03:00:49 [6] 3G: Line 1190:
2016-01-01 03:00:49 [6] 3G: Line 1190: E1550
2016-01-01 03:00:49 [6] 3G: Line 1190:
2016-01-01 03:00:49 [6] 3G: Line 1190: OK
2016-01-01 03:00:49 [6] 3G: Line 1190: ATZ
2016-01-01 03:00:49 [6] 3G: Line 1190: OK
2016-01-01 03:00:49 [6] 3G: Line 1190: AT+CSQ
2016-01-01 03:00:49 [6] 3G: Line 1190:
2016-01-01 03:00:49 [6] 3G: Line 1190: OK

2016-01-01 03:00:49 [6] 3G: Line 1190: Serial connection established.
2016-01-01 03:00:49 [6] 3G: Line 1190: Serial link disconnected.
2016-01-01 03:00:49 [6] 3G: get_modem_info_file 124 getModemParamByScript return valid type = 1
2016-01-01 03:00:49 [6] 3G: Line:1152 cmd: modem_scan -d /dev/ttyUSB0 -f "/usr/bin/chat -S -V -f /var/3G/script" > /var/3G/modem_info 2>&1 &
2016-01-01 03:00:50 [6] 3G: Line 1190:
2016-01-01 03:00:50 [6] 3G: Line 1190: +CSQ: 15,99
2016-01-01 03:00:50 [6] 3G: Line 1190:
2016-01-01 03:00:50 [6] 3G: Line 1190: OK
2016-01-01 03:00:50 [6] 3G: Line 1190: ATZ
2016-01-01 03:00:50 [6] 3G: Line 1190: OK
2016-01-01 03:00:50 [6] 3G: Line 1190: AT+CPIN?
2016-01-01 03:00:50 [6] 3G: Line 1190:
2016-01-01 03:00:50 [6] 3G: Line 1190: OK

2016-01-01 03:00:50 [6] 3G: Line 1190: Serial connection established.
2016-01-01 03:00:50 [6] 3G: Line 1190: Serial link disconnected.
2016-01-01 03:00:50 [6] 3G: get_modem_info_file 140 getModemParamByScript return valid type = 1
2016-01-01 03:00:50 [6] 3G: get_modem_info_file 156 Return chip type = 1
2016-01-01 03:00:50 [6] 3G: 1241 modemName = E1550, deviceName = ttyUSB0, simLock = 16, modemChipType = 1
2016-01-01 03:00:53 [6] 3G: oal_3g_getIspIdxFromSimCard 1185: mcc is 250, mnc is 026
2016-01-01 03:01:45 [5] DHCPD: Recv INFORM from 94:C6:91:15:B0:3F
2016-01-01 03:03:53 [5] DHCPD: Recv DISCOVER from 00:17:C8:56:DB:78
2016-01-01 03:03:53 [5] DHCPD: Send OFFER with ip 192.168.0.101
2016-01-01 03:03:53 [5] DHCPD: Recv REQUEST from 00:17:C8:56:DB:78
2016-01-01 03:03:54 [5] DHCPD: Send ACK to 192.168.0.101
2016-01-01 03:05:24 [5] DHCPD: Recv DISCOVER from 00:17:C8:56:DB:78
2016-01-01 03:05:24 [5] DHCPD: Send OFFER with ip 192.168.0.101
2016-01-01 03:05:24 [5] DHCPD: Recv REQUEST from 00:17:C8:56:DB:78
2016-01-01 03:05:24 [5] DHCPD: Send ACK to 192.168.0.101
2016-01-01 03:07:33 [5] DHCPD: Recv DISCOVER from 00:17:C8:56:DB:78
2016-01-01 03:07:33 [5] DHCPD: Send OFFER with ip 192.168.0.101
2016-01-01 03:07:33 [5] DHCPD: Recv REQUEST from 00:17:C8:56:DB:78
2016-01-01 03:07:33 [5] DHCPD: Send ACK to 192.168.0.101
2016-01-01 03:08:02 [6] PPP: ppp9 sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0x7a7d92d0> <pcomp> <accomp>]
2016-01-01 03:08:02 [6] PPP: ppp9 rcvd [LCP ConfReq id=0x1 <mru 1464> <auth chap MS-v2> <quality lqr 00 00 00 00> <magic 0xa10955ad>]
2016-01-01 03:08:02 [6] PPP: ppp9 sent [LCP ConfRej id=0x1 <quality lqr 00 00 00 00>]
2016-01-01 03:08:02 [6] PPP: ppp9 rcvd [LCP ConfAck id=0x1 <asyncmap 0x0> <magic 0x7a7d92d0> <pcomp> <accomp>]
2016-01-01 03:08:02 [6] PPP: ppp9 rcvd [LCP ConfReq id=0x2 <mru 1464> <auth chap MS-v2> <magic 0xa10955ad>]
2016-01-01 03:08:02 [6] PPP: ppp9 sent [LCP ConfAck id=0x2 <mru 1464> <auth chap MS-v2> <magic 0xa10955ad>]
2016-01-01 03:08:03 [6] PPP: ppp9 rcvd [CHAP Challenge id=0x1 <8203be867618e9c794be4d9af007bfcd>, name = "honor-pptp"]
2016-01-01 03:08:03 [6] PPP: ppp9 sent [CHAP Response id=0x1 <f8cfcdc139aa40bcdd6f8a5642e86446000000000000000078ea6840dc2ce4ad0fde6eda5800319ae934a578f95e7ca200>, name = "10.20.40.15"]
2016-01-01 03:08:03 [6] PPP: ppp9 rcvd [CHAP Success id=0x1 "S=A7FED53326D9FBA831EA4F18789B07A357EA2722"]
2016-01-01 03:08:03 [6] PPP: ppp9 sent [IPCP ConfReq id=0x1 <compress VJ 0f 01> <addr 0.0.0.0> <ms-dns1 0.0.0.0> <ms-dns2 0.0.0.0>]
2016-01-01 03:08:03 [6] PPP: ppp9 rcvd [IPCP ConfReq id=0x1 <addr 83.166.96.4>]
2016-01-01 03:08:03 [6] PPP: ppp9 sent [IPCP ConfAck id=0x1 <addr 83.166.96.4>]
2016-01-01 03:08:03 [6] PPP: ppp9 rcvd [IPCP ConfRej id=0x1 <compress VJ 0f 01>]
2016-01-01 03:08:03 [6] PPP: ppp9 sent [IPCP ConfReq id=0x2 <addr 0.0.0.0> <ms-dns1 0.0.0.0> <ms-dns2 0.0.0.0>]
2016-01-01 03:08:03 [6] PPP: ppp9 rcvd [IPCP ConfNak id=0x2 <addr 83.166.100.8> <ms-dns1 83.166.96.9> <ms-dns2 83.166.96.10>]
2016-01-01 03:08:03 [6] PPP: ppp9 sent [IPCP ConfReq id=0x3 <addr 83.166.100.8> <ms-dns1 83.166.96.9> <ms-dns2 83.166.96.10>]
2016-01-01 03:08:03 [6] PPP: ppp9 rcvd [IPCP ConfAck id=0x3 <addr 83.166.100.8> <ms-dns1 83.166.96.9> <ms-dns2 83.166.96.10>]
2019-03-26 14:01:58 [5] DHCPD: Recv INFORM from 94:C6:91:15:B0:3F
2016-01-01 03:00:14 [6] 3G: Hotplug: id[0]=12d1_1003, class[0]=switched_3g, action[0]=add
2016-01-01 03:00:16 [6] 3G: 134: handle_card add card.
2016-01-01 03:00:18 [6] 3G: 3G/4G Modem vendorID: 0x12d1; productID: 0x1003
2016-01-01 03:00:18 [5] DHCPD: Recv REQUEST from 78:F2:9E:90:DF:EA
2016-01-01 03:00:19 [5] DHCPD: Send ACK to 192.168.0.100
2016-01-01 03:00:19 [6] 3G: 314: go to already_switched.
2016-01-01 03:00:19 [6] 3G: 558: already_switched.
2016-01-01 03:00:19 [5] DHCPD: Recv REQUEST from 94:C6:91:15:B0:3F
2016-01-01 03:00:19 [5] DHCPD: Send ACK to 192.168.0.197
2016-01-01 03:00:20 [6] 3G: 576: After switch:cinfo.idVendor(12d1), cinfo.idProduct(1003).
2016-01-01 03:00:20 [6] 3G: 585 File:
2016-01-01 03:00:20 [6] 3G: 589 Before judgeModemTypeByAfterSwitchID, isNeedSwitch = 1, targetPid = 0x1003
2016-01-01 03:00:20 [6] 3G: 613 After judgeModemTypeByAfterSwitchID, modemType = 0
2016-01-01 03:00:21 [5] DHCPD: Recv DISCOVER from 00:17:C8:56:DB:78
2016-01-01 03:00:21 [5] DHCPD: Send OFFER with ip 192.168.0.101
2016-01-01 03:00:21 [5] DHCPD: Recv REQUEST from 00:17:C8:56:DB:78
2016-01-01 03:00:21 [5] DHCPD: Send ACK to 192.168.0.101
2016-01-01 03:00:24 [5] DHCPD: Recv INFORM from 94:C6:91:15:B0:3F
2016-01-01 03:00:25 [5] DHCPD: Recv RELEASE from 00:17:C8:56:DB:78
2016-01-01 03:00:26 [6] 3G: =>I:* If#= 1 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=usbserial_generic

2016-01-01 03:00:26 [6] 3G: =>E: Ad=83(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms

2016-01-01 03:00:26 [6] 3G: =>E: Ad=02(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms

2016-01-01 03:00:26 [6] 3G: =>I:* If#= 2 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 Driver=usb-storage

2016-01-01 03:00:26 [6] 3G: =>E: Ad=84(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms

2016-01-01 03:00:26 [6] 3G: =>E: Ad=03(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms

2016-01-01 03:00:26 [6] 3G: =>I:* If#= 3 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 Driver=usb-storage

2016-01-01 03:00:26 [6] 3G: =>E: Ad=04(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms

2016-01-01 03:00:26 [6] 3G: =>E: Ad=85(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms

2016-01-01 03:00:26 [6] 3G: =>

2016-01-01 03:00:26 [6] 3G: =>T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=480 MxCh= 1

2016-01-01 03:00:26 [6] 3G: =>B: Alloc= 0/800 us ( 0%), #Int= 0, #Iso= 0

2016-01-01 03:00:26 [6] 3G: =>D: Ver= 2.00 Cls=09(hub ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1

2016-01-01 03:00:26 [6] 3G: =>P: Vendor=1d6b ProdID=0002 Rev= 2.06

2016-01-01 03:00:26 [6] 3G: =>S: Manufacturer=Linux 2.6.36 ehci_hcd

2016-01-01 03:00:26 [6] 3G: =>S: Product=Ralink EHCI Host Controller

2016-01-01 03:00:26 [6] 3G: =>S: SerialNumber=rt3xxx

2016-01-01 03:00:26 [6] 3G: =>C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA

2016-01-01 03:00:26 [6] 3G: =>I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub

2016-01-01 03:00:26 [6] 3G: =>E: Ad=81(I) Atr=03(Int.) MxPS= 4 Ivl=256ms

2016-01-01 03:00:28 [5] DHCPD: Recv DISCOVER from 00:17:C8:56:DB:78
2016-01-01 03:00:28 [5] DHCPD: Send OFFER with ip 192.168.0.101
2016-01-01 03:00:28 [5] DHCPD: Recv REQUEST from 00:17:C8:56:DB:78
2016-01-01 03:00:29 [5] DHCPD: Send ACK to 192.168.0.101
2016-01-01 03:00:32 [6] 3G: Main interface_index[0] = 0
2016-01-01 03:00:32 [6] 3G: Vice interface_index[1] = 1
2016-01-01 03:00:33 [6] 3G: Switched 3G modem vendorId:0x12d1; productId:0x1003
2016-01-01 03:00:33 [6] 3G: Line:1152 cmd: modem_scan -d /dev/ttyUSB0 -f "/usr/bin/chat -S -V -f /var/3G/script" > /var/3G/modem_info 2>&1 &
2016-01-01 03:00:34 [6] 3G: Line 1190:
2016-01-01 03:00:34 [6] 3G: Line 1190: OK
2016-01-01 03:00:34 [6] 3G: Line 1190: ATZ
2016-01-01 03:00:34 [6] 3G: Line 1190: OK
2016-01-01 03:00:34 [6] 3G: Line 1190: AT+CGMM
2016-01-01 03:00:34 [6] 3G: get_modem_info_file 107 getModemParamByScript return valid type = 1
2016-01-01 03:00:34 [6] 3G: Line:1152 cmd: modem_scan -d /dev/ttyUSB0 -f "/usr/bin/chat -S -V -f /var/3G/script" > /var/3G/modem_info 2>&1 &
2016-01-01 03:00:35 [6] 3G: Line 1190:
2016-01-01 03:00:35 [6] 3G: Line 1190: E1550
2016-01-01 03:00:35 [6] 3G: Line 1190:
2016-01-01 03:00:35 [6] 3G: Line 1190: OK
2016-01-01 03:00:35 [6] 3G: Line 1190: ATZ
2016-01-01 03:00:35 [6] 3G: Line 1190: OK
2016-01-01 03:00:35 [6] 3G: Line 1190: AT+CSQ
2016-01-01 03:00:35 [6] 3G: Line 1190:
2016-01-01 03:00:35 [6] 3G: Line 1190: OK

2016-01-01 03:00:35 [6] 3G: Line 1190: Serial connection established.
2016-01-01 03:00:35 [6] 3G: Line 1190: Serial link disconnected.
2016-01-01 03:00:35 [6] 3G: get_modem_info_file 124 getModemParamByScript return valid type = 1
2016-01-01 03:00:35 [6] 3G: Line:1152 cmd: modem_scan -d /dev/ttyUSB0 -f "/usr/bin/chat -S -V -f /var/3G/script" > /var/3G/modem_info 2>&1 &
2016-01-01 03:00:36 [6] 3G: Line 1190:
2016-01-01 03:00:36 [6] 3G: Line 1190: +CSQ: 15,99
2016-01-01 03:00:36 [6] 3G: Line 1190:
2016-01-01 03:00:36 [6] 3G: Line 1190: OK
2016-01-01 03:00:36 [6] 3G: Line 1190: ATZ
2016-01-01 03:00:36 [6] 3G: Line 1190: OK
2016-01-01 03:00:36 [6] 3G: Line 1190: AT+CPIN?
2016-01-01 03:00:36 [6] 3G: Line 1190:
2016-01-01 03:00:36 [6] 3G: Line 1190: OK

2016-01-01 03:00:36 [6] 3G: Line 1190: Serial connection established.
2016-01-01 03:00:36 [6] 3G: Line 1190: Serial link disconnected.
2016-01-01 03:00:36 [6] 3G: get_modem_info_file 140 getModemParamByScript return valid type = 1
2016-01-01 03:00:36 [6] 3G: get_modem_info_file 156 Return chip type = 1
2016-01-01 03:00:36 [6] 3G: 1241 modemName = E1550, deviceName = ttyUSB0, simLock = 16, modemChipType = 1
2016-01-01 03:00:39 [6] 3G: oal_3g_getIspIdxFromSimCard 1185: mcc is 250, mnc is 026
2016-01-01 03:00:47 [5] DHCPD: Recv REQUEST from 18:56:80:AB:AB:D0
2016-01-01 03:00:48 [5] DHCPD: Send ACK to 192.168.0.102
2016-01-01 03:01:02 [6] PPP: ppp9 sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0x4d8f471d> <pcomp> <accomp>]
2016-01-01 03:01:02 [6] PPP: ppp9 rcvd [LCP ConfReq id=0x1 <mru 1464> <auth chap MS-v2> <quality lqr 00 00 00 00> <magic 0x93316c19>]
2016-01-01 03:01:02 [6] PPP: ppp9 sent [LCP ConfRej id=0x1 <quality lqr 00 00 00 00>]
2016-01-01 03:01:02 [6] PPP: ppp9 rcvd [LCP ConfAck id=0x1 <asyncmap 0x0> <magic 0x4d8f471d> <pcomp> <accomp>]
2016-01-01 03:01:02 [6] PPP: ppp9 rcvd [LCP ConfReq id=0x2 <mru 1464> <auth chap MS-v2> <magic 0x93316c19>]
2016-01-01 03:01:02 [6] PPP: ppp9 sent [LCP ConfAck id=0x2 <mru 1464> <auth chap MS-v2> <magic 0x93316c19>]
2016-01-01 03:01:02 [6] PPP: ppp9 rcvd [CHAP Challenge id=0x1 <ff10bce0fac953f2147b26bded29b786>, name = "glory-pptp"]
2016-01-01 03:01:02 [6] PPP: ppp9 sent [CHAP Response id=0x1 <bbd37b20f67841d2558e6267275da793000000000000000091bf65afb6b5efe6fa40c6aa8ba47c6c2837c7ec87c8d62e00>, name = "10.20.40.15"]
2016-01-01 03:01:03 [6] PPP: ppp9 rcvd [CHAP Success id=0x1 "S=B01ED168664239DBB6320E6B1732D2C1579D06C1"]
2016-01-01 03:01:03 [6] PPP: ppp9 sent [IPCP ConfReq id=0x1 <compress VJ 0f 01> <addr 0.0.0.0> <ms-dns1 0.0.0.0> <ms-dns2 0.0.0.0>]
2016-01-01 03:01:03 [6] PPP: ppp9 rcvd [IPCP ConfReq id=0x1 <addr 83.166.96.8>]
2016-01-01 03:01:03 [6] PPP: ppp9 sent [IPCP ConfAck id=0x1 <addr 83.166.96.8>]
2016-01-01 03:01:03 [6] PPP: ppp9 rcvd [IPCP ConfRej id=0x1 <compress VJ 0f 01>]
2016-01-01 03:01:03 [6] PPP: ppp9 sent [IPCP ConfReq id=0x2 <addr 0.0.0.0> <ms-dns1 0.0.0.0> <ms-dns2 0.0.0.0>]
2016-01-01 03:01:03 [6] PPP: ppp9 rcvd [IPCP ConfNak id=0x2 <addr 83.166.107.159> <ms-dns1 83.166.96.9> <ms-dns2 83.166.96.10>]
2016-01-01 03:01:03 [6] PPP: ppp9 sent [IPCP ConfReq id=0x3 <addr 83.166.107.159> <ms-dns1 83.166.96.9> <ms-dns2 83.166.96.10>]
2016-01-01 03:01:03 [6] PPP: ppp9 rcvd [IPCP ConfAck id=0x3 <addr 83.166.107.159> <ms-dns1 83.166.96.9> <ms-dns2 83.166.96.10>]

Richik
Сообщения: 4
Зарегистрирован: 17 дек 2019, 19:19
Страна: Россия

Re: Проблемы при подключении к сети интернет

Сообщение Richik » 17 дек 2019, 20:36

1. TL-WR842N(RU) Ver:5.0
2. Укажу позже, не с собой
3. РФ
4. LAN
5. LAN

Инет предоставляет вышестоящая организация по LAN, по средствам МАК-адреса.
Бухта кабелей приходит к свичу - один от ВышеСтоящих и много локальных клиентов.
На части из них открыт доступ в Инет.
Необходимо разделиться на разные подсети, но с сохранение коннекта, и всех своих пустить через наш роутр.
От свича кинул кабель на роутр (к LAN порту) и настроил так:

Прописал в "Сеть -> Интернет" IP внешней сети:
IP роутера - 192.168.0.161
маска - 255.255.255.0
шлюз - 192.168.0.2

LAN:
192.168.200.1
255.255.255.0
DHCP

Маршрутизация:
IP назначения - 192.168.0.2
Маска - 255.255.255.0
Шлюз - 192.168.200.1

Вроде так, пишу по памяти

Без маршрутизации вышестоящие не видят роутр (почему-то не пингуется), если включить - все ок.
Техники дали добро на своем оборудовании, но Инета нет.

Из сети "200" не пингуется 192.168.200.1 - Что я делаю не так?

Может входящий кабель необходимо подключать к WAN-порту роутера :shock: ?

И еще, сам роутр умеет пингавать заданный IP? - что-то не нашел и интерфейсе

Изображение

Richik
Сообщения: 4
Зарегистрирован: 17 дек 2019, 19:19
Страна: Россия

Re: Проблемы при подключении к сети интернет

Сообщение Richik » 18 дек 2019, 08:47

Wan - так и есть, один кабель в ван, второй в лан, и оба в свич. И все начало работать.

Ответить

Вернуться в «TL-WR842N (RU)»