Здравствуйте, недавно приобрел D-Link DSL-2640U NRU/C4. У меня он настроен в режиме роутер тип соединения PPPoE. У меня такая проблема, после разрыва соединения, автоматически оно не восстанавливается, только после перезагрузки роутера. Как сделать чтобы после разрыва соединения оно автоматически восстанавливалось?

Такая же проблема . Все испробовал не получается. Как настроить?

Так кто нибудь на мой вопрос ответит . Или ни кто не знает?!

Какая версия прошивки?
Представьте параметры настройки рррое соединения и записи журнала событий с моментами возникновения проблемы.

Версия прошивки 1.0.20
Вот настройки:
VPI (0-255): 0
I (32-65535): 33
MTU: 1492
Keep Alive: Включен
LCP интервал (сек): 30
LCP провалы: 3
Отладка PPP: Включен
Проброс PPPoE: Включен
NAT: Включен
Сетевой экран: Включен

Включить G.Dmt: Включен
Включить G.lite: Включен
Включить T1.413: Включен
Включить ADSL2: Включен
Включить AnnexL: Включен
Включить ADSL2+: Включен
Тип телефонной пары: Внешняя пара
Включить SRA: Включен

Jan 1 02:22:10 (none) user.alert kernel: Intrusion -> IN=ppp1 OUT= MAC= SRC=87.255.14.129 DST=85.172.184.166 LEN=48 TOS=0x00 PREC=0x00 TTL=113 ID=49072 DF PROTO=TCP SPT=2521 DPT=18907 WINDOW=65535 RES=0x00 SYN URGP=0 MARK=0x8000000 239
Jan 1 02:31:17 (none) user.alert kernel: Intrusion -> IN=ppp1 OUT= MAC= SRC=37.112.50.89 DST=85.172.184.166 LEN=48 TOS=0x00 PREC=0x00 TTL=117 ID=5781 DF PROTO=TCP SPT=1046 DPT=18907 WINDOW=65535 RES=0x00 SYN URGP=0 MARK=0x8000000 237
Jan 1 02:42:22 (none) user.alert kernel: Intrusion -> IN=ppp1 OUT= MAC= SRC=37.112.50.89 DST=85.172.184.166 LEN=48 TOS=0x00 PREC=0x00 TTL=117 ID=52804 DF PROTO=TCP SPT=1348 DPT=18907 WINDOW=65535 RES=0x00 SYN URGP=0 MARK=0x8000000 238
Jan 1 02:51:03 (none) daemon.crit syslog: Clear IP addresses. PPP connection DOWN. 91
Jan 1 02:51:03 (none) daemon.crit syslog: Clear IP addresses. Connection DOWN. 87
Jan 1 02:51:05 (none) user.info kernel: device atm0 left promiscuous mode 80
Jan 1 02:51:05 (none) user.info kernel: br0: port 7(atm0) entering disabled state 88
Jan 1 02:51:09 (none) daemon.debug syslog: Sent packet: Ether addr: 00:90:1a:a3:8d:7c (PPPOE Discovery) PPPoE hdr: ver=0x1 type=0x1 code=0xa7 sid=0x2612 length=0x000c (PADT) PPPoE tag: type=0103 length=0004 (Host Uniq) data (bin): 00 48 90 18 PPPoE tag: type=0101 length=0000 (Service name) 301
Jan 1 02:51:12 (none) daemon.notice syslog: PPP: Start to connect ... 77
Jan 1 02:51:12 (none) daemon.debug syslog: Sent packet: Ether addr: 00:90:1a:a3:8d:7c (PPPOE Discovery) PPPoE hdr: ver=0x1 type=0x1 code=0xa7 sid=0x2612 length=0x000c (PADT) PPPoE tag: type=0103 length=0004 (Host Uniq) data (bin): 00 48 90 18 PPPoE tag: type=0101 length=0000 (Service name) 301
Jan 1 02:51:13 (none) daemon.debug syslog: Sent packet: Ether addr: 00:90:1a:a3:8d:7c (PPPOE Discovery) PPPoE hdr: ver=0x1 type=0x1 code=0xa7 sid=0x2612 length=0x000c (PADT) PPPoE tag: type=0103 length=0004 (Host Uniq) data (bin): 00 48 90 18 PPPoE tag: type=0101 length=0000 (Service name) 301
Jan 1 02:51:13 (none) daemon.info syslog: Sending PADI 61
Jan 1 02:51:13 (none) daemon.debug syslog: Sent packet: Ether addr: ff:ff:ff:ff:ff:ff (PPPOE Discovery) PPPoE hdr: ver=0x1 type=0x1 code=0x09 sid=0x0000 length=0x000c (PADI) PPPoE tag: type=0103 length=0004 (Host Uniq) data (bin): 00 48 90 18 PPPoE tag: type=0101 length=0000 (Service name) 301
Jan 1 02:51:15 (none) daemon.debug syslog: Sent packet: Ether addr: ff:ff:ff:ff:ff:ff (PPPOE Discovery) PPPoE hdr: ver=0x1 type=0x1 code=0x09 sid=0x0000 length=0x000c (PADI) PPPoE tag: type=0101 length=0000 (Service name) PPPoE tag: type=0103 length=0004 (Host Uniq) data (bin): 00 48 90 18 301
Jan 1 02:51:19 (none) daemon.debug syslog: Sent packet: Ether addr: ff:ff:ff:ff:ff:ff (PPPOE Discovery) PPPoE hdr: ver=0x1 type=0x1 code=0x09 sid=0x0000 length=0x000c (PADI) PPPoE tag: type=0101 length=0000 (Service name) PPPoE tag: type=0103 length=0004 (Host Uniq) data (bin): 00 48 90 18 301
Jan 1 02:51:19 (none) daemon.debug syslog: Recv'd packet: Ether addr: 00:90:1a:a2:ce:39 (PPPOE Discovery) PPPoE hdr: ver=0x1 type=0x1 code=0x07 sid=0x0000 length=0x002e (PADO) PPPoE tag: type=0102 length=000a (AC Name) data (UTF-8): KCR-E120-2 PPPoE tag: type=0103 length=0004 (Host Uniq) data ( 305
Jan 1 02:51:19 (none) daemon.info syslog: HOST_UNIQ successful match 76
Jan 1 02:51:19 (none) daemon.crit syslog: PPP server detected. 70
Jan 1 02:51:19 (none) daemon.debug syslog: Sent packet: Ether addr: 00:90:1a:a2:ce:39 (PPPOE Discovery) PPPoE hdr: ver=0x1 type=0x1 code=0x19 sid=0x0000 length=0x0020 (PADR) PPPoE tag: type=0101 length=0000 (Service name) PPPoE tag: type=0103 length=0004 (Host Uniq) data (bin): 00 48 90 18 PPP 305
Jan 1 02:51:21 (none) daemon.debug syslog: Sent packet: Ether addr: 00:90:1a:a2:ce:39 (PPPOE Discovery) PPPoE hdr: ver=0x1 type=0x1 code=0x19 sid=0x0000 length=0x0020 (PADR) PPPoE tag: type=0101 length=0000 (Service name) PPPoE tag: type=0103 length=0004 (Host Uniq) data (bin): 00 48 90 18 PPP 305
Jan 1 02:51:25 (none) daemon.debug syslog: Sent packet: Ether addr: 00:90:1a:a2:ce:39 (PPPOE Discovery) PPPoE hdr: ver=0x1 type=0x1 code=0x19 sid=0x0000 length=0x0020 (PADR) PPPoE tag: type=0101 length=0000 (Service name) PPPoE tag: type=0103 length=0004 (Host Uniq) data (bin): 00 48 90 18 PPP 305
Jan 1 02:51:33 (none) daemon.debug syslog: Sent packet: Ether addr: 00:90:1a:a2:ce:39 (PPPOE Discovery) PPPoE hdr: ver=0x1 type=0x1 code=0x19 sid=0x0000 length=0x0020 (PADR) PPPoE tag: type=0101 length=0000 (Service name) PPPoE tag: type=0103 length=0004 (Host Uniq) data (bin): 00 48 90 18 PPP 305

В представленном логе отображена только часть установления соединения после завершения сессии. Этапы установления соединения проходят, но с некоторой задержкой со стороны сервера.

an 1 00:00:08 (none) user.info kernel: 802.1Q VLAN Support v1.8 Ben Greear 108
Jan 1 00:00:08 (none) user.info kernel: All bugs added by David S. Miller 99
Jan 1 00:00:08 (none) user.warn kernel: VFS: Mounted root (squashfs filesystem) readonly on device 31:0. 111
Jan 1 00:00:08 (none) user.info kernel: Freeing unused kernel memory: 120k freed 87
Jan 1 00:00:08 (none) user.crit kernel: eth0 Link UP 100 mbps full duplex 80
Jan 1 00:00:08 (none) user.crit kernel: eth1 Link UP 100 mbps full duplex 80
Jan 1 00:00:08 (none) user.info kernel: message received before monitor task is initialized kerSysSendtoMonitorTask 123
Jan 1 00:00:08 (none) user.warn kernel: gpio: module license 'unspecified' taints kernel. 96
Jan 1 00:00:08 (none) user.warn kernel: Disabling lock debugging due to kernel taint 91
Jan 1 00:00:08 (none) user.warn kernel: Initialized fcache state 71
Jan 1 00:00:08 (none) user.warn kernel: Broadcom Packet Flow Cache Char Driver v2.2 Sep 24 2010 18:42:19 Registered<242> 128
Jan 1 00:00:08 (none) user.warn kernel: Created Proc FS /procfs/fcache 77
Jan 1 00:00:08 (none) user.warn kernel: Broadcom Packet Flow Cache registered with netdev chain 102
Jan 1 00:00:08 (none) user.warn kernel: Broadcom Packet Flow Cache learning via BLOG enabled. 100
Jan 1 00:00:08 (none) user.warn kernel: Constructed Broadcom Packet Flow Cache v2.2 Sep 24 2010 18:42:19 111
Jan 1 00:00:08 (none) user.warn kernel: PCI: Enabling device 0000:02:00.0 (0000 -> 0002) 95
Jan 1 00:00:08 (none) user.debug kernel: PCI: Setting latency timer of device 0000:02:00.0 to 64 103
Jan 1 00:00:08 (none) user.warn kernel: otp_read_pci: bad crc 68
Jan 1 00:00:08 (none) user.warn kernel: wl:not strapped or invalid data 78
Jan 1 00:00:08 (none) user.warn kernel: wl:srom not detected,using main memory mapped srom info(wombo board) 115
Jan 1 00:00:08 (none) user.warn kernel: wl:loading /etc/wlan/bcm4313_map.bin 83
Jan 1 00:00:08 (none) user.warn kernel: wl0: Broadcom BCM4313 802.11 Wireless Controller 5.60.120.11.cpe4.06L03.8 120
Jan 1 00:00:08 (none) user.warn kernel: dgasp: kerSysRegisterDyingGaspHandler: wl0 registered 101
Jan 1 00:00:08 (none) user.warn kernel: p8021ag: p8021ag_init entry 74
Jan 1 00:00:08 (none) user.info kernel: Broadcom 802.1Q VLAN Interface, v0.1 83
Jan 1 00:00:08 (none) user.info kernel: ip_tables: (C) 2000-2006 Netfilter Core Team 91
Jan 1 00:00:09 (none) user.warn kernel: Netfilter messages via NETLINK v0.30. 84
Jan 1 00:00:09 (none) user.warn kernel: nf_conntrack version 0.5.0 (496 buckets, 1984 max) 97
Jan 1 00:00:12 (none) user.info kernel: device eth0 entered promiscuous mode 83
Jan 1 00:00:12 (none) user.info kernel: br0: port 1(eth0) entering forwarding state 90
Jan 1 00:00:13 (none) user.info kernel: device eth1 entered promiscuous mode 83
Jan 1 00:00:13 (none) user.info kernel: br0: port 2(eth1) entering forwarding state 90
Jan 1 00:00:13 (none) user.info kernel: device eth2 entered promiscuous mode 83
Jan 1 00:00:14 (none) user.info kernel: device eth3 entered promiscuous mode 83
Jan 1 00:00:14 (none) user.info kernel: dhcpd uses obsolete (PF_INET,SOCK_PACKET) 88
Jan 1 00:00:15 (none) user.info kernel: device eth4 entered promiscuous mode 83
Jan 1 00:00:16 (none) user.info kernel: device wl0 entered promiscuous mode 82
Jan 1 00:00:16 (none) user.info kernel: br0: port 6(wl0) entering forwarding state 89
Jan 1 00:00:16 (none) user.warn kernel: BcmAdsl_Initialize=0x8016A06C, g_pFnNotifyCallback=0x802B6BB4 108
Jan 1 00:00:16 (none) user.warn kernel: pSdramPHY=0xA1FFFFF8, 0x801B5A8C 0x9A2DBEED 90
Jan 1 00:00:17 (none) user.warn kernel: AdslCoreSharedMemInit: shareMemAvailable=491424 94
Jan 1 00:00:17 (none) user.warn kernel: AdslCoreHwReset: AdslOemDataAddr = 0xA1F69564 93
Jan 1 00:00:17 (none) user.warn kernel: dgasp: kerSysRegisterDyingGaspHandler: dsl0 registered 102
Jan 1 00:00:17 (none) user.warn kernel: XTM Init: 400 rx BDs at 0xa0e2d000 81
Jan 1 00:00:17 (none) user.warn kernel: XTM Init: 100 rx BDs at 0xa0d0f800 81
Jan 1 00:00:17 (none) user.info kernel: monitor task is initialized pid= 249 84
Jan 1 00:00:18 (none) user.crit kernel: Line 0: xDSL G.994 training 74
Jan 1 00:00:19 (none) user.info kernel: device wl0 left promiscuous mode 79
Jan 1 00:00:19 (none) user.info kernel: br0: port 6(wl0) entering disabled state 87
Jan 1 00:00:19 (none) user.info kernel: device wl0 entered promiscuous mode 82
Jan 1 00:00:19 (none) user.info kernel: br0: port 6(wl0) entering forwarding state 89
Jan 1 00:00:19 (none) user.info kernel: wl0.1 (): not using net_device_ops yet 85
Jan 1 00:00:19 (none) user.info kernel: wl0.2 (): not using net_device_ops yet 85
Jan 1 00:00:20 (none) user.info kernel: wl0.3 (): not using net_device_ops yet 85
Jan 1 00:00:20 (none) user.info kernel: br0: port 6(wl0) entering disabled state 87
Jan 1 00:00:22 (none) user.info kernel: device wl0 left promiscuous mode 79
Jan 1 00:00:22 (none) user.info kernel: br0: port 6(wl0) entering disabled state 87
Jan 1 00:00:22 (none) user.info kernel: device wl0 entered promiscuous mode 82
Jan 1 00:00:22 (none) user.info kernel: br0: port 6(wl0) entering forwarding state 89
Jan 1 00:00:25 (none) user.crit kernel: Line 0: ADSL G.992 started 73
Jan 1 00:00:27 (none) user.crit kernel: Line 0: ADSL G.992 channel analysis 82
Jan 1 00:00:32 (none) user.crit kernel: Line 0: ADSL link down 69
Jan 1 00:00:32 (none) user.warn kernel: bcmxtmcfg: XTM Link Information, port = 0, State = DOWN, Service Support = PTM 126
Jan 1 00:00:51 (none) user.crit kernel: Line 0: xDSL G.994 training 74
Jan 1 00:00:57 (none) user.crit kernel: Line 0: ADSL G.992 started 73
Jan 1 00:01:00 (none) user.crit kernel: Line 0: ADSL G.992 channel analysis 82
Jan 1 00:01:04 (none) user.crit kernel: Line 0: ADSL G.992 message exchange 82
Jan 1 00:01:04 (none) user.crit kernel: Line 0: ADSL link up, fast, us=1056, ds=4128 91
Jan 1 00:01:04 (none) user.warn kernel: bcmxtmcfg: XTM Link Information, port = 0, State = UP, Service Support = ATM 124
Jan 1 00:01:04 (none) user.warn kernel: bcmxtmrt: MAC address: b8 a3 86 45 b3 57 87
Jan 1 00:01:04 (none) user.warn kernel: [DoCreateDeviceReq.2603]: register_netdev 88
Jan 1 00:01:05 (none) user.warn kernel: [DoCreateDeviceReq.2605]: register_netdev done 93
Jan 1 00:01:05 (none) user.warn kernel: XTM Init: 400 tx BDs at 0xa0dfc000 81
Jan 1 00:01:05 (none) user.warn kernel: bcmxtmcfg: Connection UP, LinkActiveStatus=0x1, US=1056000, DS=4128000 118
Jan 1 00:01:05 (none) user.info kernel: device atm0 entered promiscuous mode 83
Jan 1 00:01:05 (none) user.info kernel: br0: port 7(atm0) entering forwarding state 90
Jan 1 00:01:05 (none) daemon.notice syslog: pppd 2.4.1 started by admin, uid 0 85
Jan 1 00:01:05 (none) daemon.notice syslog: PPP: Start to connect ... 77
Jan 1 00:01:05 (none) daemon.debug syslog: Sent packet: Ether addr: 00:90:1a:a3:8d:7c (PPPOE Discovery) PPPoE hdr: ver=0x1 type=0x1 code=0xa7 sid=0x374a length=0x000c (PADT) PPPoE tag: type=0103 length=0004 (Host Uniq) data (bin): 00 48 90 18 PPPoE tag: type=0101 length=0000 (Service name) 301
Jan 1 00:01:06 (none) daemon.debug syslog: Sent packet: Ether addr: 00:90:1a:a3:8d:7c (PPPOE Discovery) PPPoE hdr: ver=0x1 type=0x1 code=0xa7 sid=0x374a length=0x000c (PADT) PPPoE tag: type=0103 length=0004 (Host Uniq) data (bin): 00 48 90 18 PPPoE tag: type=0101 length=0000 (Service name) 301
Jan 1 00:01:06 (none) daemon.info syslog: Sending PADI 61
Jan 1 00:01:06 (none) daemon.debug syslog: Sent packet: Ether addr: ff:ff:ff:ff:ff:ff (PPPOE Discovery) PPPoE hdr: ver=0x1 type=0x1 code=0x09 sid=0x0000 length=0x000c (PADI) PPPoE tag: type=0103 length=0004 (Host Uniq) data (bin): 00 48 90 18 PPPoE tag: type=0101 length=0000 (Service name) 301
Jan 1 00:01:06 (none) daemon.debug syslog: Recv'd packet: Ether addr: 00:90:1a:a4:4a:98 (PPPOE Discovery) PPPoE hdr: ver=0x1 type=0x1 code=0x07 sid=0x0000 length=0x002e (PADO) PPPoE tag: type=0102 length=000a (AC Name) data (UTF-8): KCR-E120-1 PPPoE tag: type=0103 length=0004 (Host Uniq) data ( 305
Jan 1 00:01:06 (none) daemon.info syslog: HOST_UNIQ successful match 76
Jan 1 00:01:06 (none) daemon.crit syslog: PPP server detected. 70
Jan 1 00:01:06 (none) daemon.debug syslog: Sent packet: Ether addr: 00:90:1a:a4:4a:98 (PPPOE Discovery) PPPoE hdr: ver=0x1 type=0x1 code=0x19 sid=0x0000 length=0x0020 (PADR) PPPoE tag: type=0101 length=0000 (Service name) PPPoE tag: type=0103 length=0004 (Host Uniq) data (bin): 00 48 90 18 PPP 305
Jan 1 00:01:06 (none) daemon.debug syslog: Recv'd packet: Ether addr: 00:90:1a:a3:8d:7c (PPPOE Discovery) PPPoE hdr: ver=0x1 type=0x1 code=0x07 sid=0x0000 length=0x002e (PADO) PPPoE tag: type=0102 length=000a (AC Name) data (UTF-8): KCR-E120-1 PPPoE tag: type=0103 length=0004 (Host Uniq) data ( 305
Jan 1 00:01:06 (none) daemon.info syslog: HOST_UNIQ successful match 76
Jan 1 00:01:06 (none) daemon.err syslog: Unexpected packet: Ether addr: 00:90:1a:a3:8d:7c (PPPOE Discovery) PPPoE hdr: ver=0x1 type=0x1 code=0x07 sid=0x0000 length=0x002e (PADO) PPPoE tag: type=0102 length=000a (AC Name) data (UTF-8): KCR-E120-1 PPPoE tag: type=0103 length=0004 (Host Uniq) da 303
Jan 1 00:01:06 (none) daemon.debug syslog: Recv'd packet: Ether addr: 00:90:1a:a2:ce:39 (PPPOE Discovery) PPPoE hdr: ver=0x1 type=0x1 code=0x07 sid=0x0000 length=0x002e (PADO) PPPoE tag: type=0102 length=000a (AC Name) data (UTF-8): KCR-E120-2 PPPoE tag: type=0103 length=0004 (Host Uniq) data ( 305
Jan 1 00:01:06 (none) daemon.info syslog: HOST_UNIQ successful match 76
Jan 1 00:01:06 (none) daemon.err syslog: Unexpected packet: Ether addr: 00:90:1a:a2:ce:39 (PPPOE Discovery) PPPoE hdr: ver=0x1 type=0x1 code=0x07 sid=0x0000 length=0x002e (PADO) PPPoE tag: type=0102 length=000a (AC Name) data (UTF-8): KCR-E120-2 PPPoE tag: type=0103 length=0004 (Host Uniq) da 303
Jan 1 00:01:06 (none) daemon.debug syslog: Recv'd packet: Ether addr: 00:90:1a:a4:4a:98 (PPPOE Discovery) PPPoE hdr: ver=0x1 type=0x1 code=0x65 sid=0x0e3e length=0x000c (PADS) PPPoE tag: type=0101 length=0000 (Service name) PPPoE tag: type=0103 length=0004 (Host Uniq) data (bin): 00 48 90 18 303
Jan 1 00:01:06 (none) daemon.info syslog: HOST_UNIQ successful match 76
Jan 1 00:01:06 (none) daemon.info syslog: Got connection: e3e 68
Jan 1 00:01:06 (none) daemon.crit syslog: PPP session established. 74
Jan 1 00:01:06 (none) user.warn kernel: netdev path : ppp1 -> atm0 73
Jan 1 00:01:06 (none) daemon.crit syslog: PPP LCP UP. 61
Jan 1 00:01:10 (none) daemon.crit syslog: Received valid IP address from server. Connection UP. 104
Jan 1 00:01:29 (none) user.alert kernel: Intrusion -> IN=ppp1 OUT= MAC= SRC=176.212.192.124 DST=85.172.184.166 LEN=52 TOS=0x00 PREC=0x00 TTL=117 ID=4640 DF PROTO=TCP SPT=55267 DPT=18907 WINDOW=8192 RES=0x00 SYN URGP=0 MARK=0x8000000 240
Jan 1 00:01:32 (none) user.alert kernel: Intrusion -> IN=ppp1 OUT= MAC= SRC=176.212.192.124 DST=85.172.184.166 LEN=52 TOS=0x00 PREC=0x00 TTL=117 ID=13797 DF PROTO=TCP SPT=55267 DPT=18907 WINDOW=8192 RES=0x00 SYN URGP=0 MARK=0x8000000 241
Jan 1 00:01:38 (none) user.alert kernel: Intrusion -> IN=ppp1 OUT= MAC= SRC=176.212.192.124 DST=85.172.184.166 LEN=48 TOS=0x00 PREC=0x00 TTL=117 ID=31969 DF PROTO=TCP SPT=55267 DPT=18907 WINDOW=8192 RES=0x00 SYN URGP=0 MARK=0x8000000 241
Jan 1 00:02:21 (none) user.alert kernel: Intrusion -> IN=ppp1 OUT= MAC= SRC=86.100.147.92 DST=85.172.184.166 LEN=52 TOS=0x00 PREC=0x00 TTL=115 ID=3556 DF PROTO=TCP SPT=9432 DPT=18907 WINDOW=8192 RES=0x00 SYN URGP=0 MARK=0x8000000 237
Jan 1 00:02:24 (none) user.alert kernel: Intrusion -> IN=ppp1 OUT= MAC= SRC=86.100.147.92 DST=85.172.184.166 LEN=52 TOS=0x00 PREC=0x00 TTL=115 ID=4596 DF PROTO=TCP SPT=9432 DPT=18907 WINDOW=8192 RES=0x00 SYN URGP=0 MARK=0x8000000 237
Jan 1 00:11:53 (none) user.alert kernel: Intrusion -> IN=ppp1 OUT= MAC= SRC=86.100.147.92 DST=85.172.184.166 LEN=52 TOS=0x00 PREC=0x00 TTL=115 ID=6198 DF PROTO=TCP SPT=9732 DPT=18907 WINDOW=8192 RES=0x00 SYN URGP=0 MARK=0x8000000 237
Jan 1 00:14:27 (none) user.info kernel: device atm0 left promiscuous mode 80
Jan 1 00:14:27 (none) user.info kernel: br0: port 7(atm0) entering disabled state 88
Jan 1 00:14:27 (none) daemon.crit syslog: Clear IP addresses. PPP connection DOWN. 91
Jan 1 00:14:27 (none) daemon.crit syslog: Clear IP addresses. Connection DOWN. 87
Jan 1 00:14:33 (none) user.warn kernel: HOST XTM Tx ch 0 down success 76
Jan 1 00:14:33 (none) user.warn kernel: bcmxtmcfg: Connection DOWN, LinkActiveStatus=0x0 96
Jan 1 00:14:33 (none) user.warn kernel: bcmxtmrt: MAC address: b8 a3 86 45 b3 57 87
Jan 1 00:14:33 (none) user.warn kernel: [DoCreateDeviceReq.2603]: register_netdev 88
Jan 1 00:14:33 (none) user.warn kernel: [DoCreateDeviceReq.2605]: register_netdev done 93
Jan 1 00:14:33 (none) user.warn kernel: XTM Init: 400 tx BDs at 0xa0dfc000 81
Jan 1 00:14:33 (none) user.warn kernel: bcmxtmcfg: Connection UP, LinkActiveStatus=0x1, US=1056000, DS=4128000 118
Jan 1 00:14:34 (none) daemon.notice syslog: pppd 2.4.1 started by admin, uid 0 85
Jan 1 00:14:34 (none) user.info kernel: device atm0 entered promiscuous mode 83
Jan 1 00:14:34 (none) user.info kernel: br0: port 7(atm0) entering forwarding state 90
Jan 1 00:14:34 (none) daemon.notice syslog: PPP: Start to connect ... 77
Jan 1 00:14:34 (none) daemon.debug syslog: Sent packet: Ether addr: 00:90:1a:a4:4a:98 (PPPOE Discovery) PPPoE hdr: ver=0x1 type=0x1 code=0xa7 sid=0x0e3e length=0x000c (PADT) PPPoE tag: type=0103 length=0004 (Host Uniq) data (bin): 00 48 90 18 PPPoE tag: type=0101 length=0000 (Service name) 301
Jan 1 00:14:35 (none) daemon.debug syslog: Sent packet: Ether addr: 00:90:1a:a4:4a:98 (PPPOE Discovery) PPPoE hdr: ver=0x1 type=0x1 code=0xa7 sid=0x0e3e length=0x000c (PADT) PPPoE tag: type=0103 length=0004 (Host Uniq) data (bin): 00 48 90 18 PPPoE tag: type=0101 length=0000 (Service name) 301
Jan 1 00:14:35 (none) daemon.info syslog: Sending PADI 61
Jan 1 00:14:35 (none) daemon.debug syslog: Sent packet: Ether addr: ff:ff:ff:ff:ff:ff (PPPOE Discovery) PPPoE hdr: ver=0x1 type=0x1 code=0x09 sid=0x0000 length=0x000c (PADI) PPPoE tag: type=0103 length=0004 (Host Uniq) data (bin): 00 48 90 18 PPPoE tag: type=0101 length=0000 (Service name) 301
Jan 1 00:14:35 (none) daemon.debug syslog: Recv'd packet: Ether addr: 00:90:1a:a2:ce:39 (PPPOE Discovery) PPPoE hdr: ver=0x1 type=0x1 code=0x07 sid=0x0000 length=0x002e (PADO) PPPoE tag: type=0102 length=000a (AC Name) data (UTF-8): KCR-E120-2 PPPoE tag: type=0103 length=0004 (Host Uniq) data ( 305
Jan 1 00:14:35 (none) daemon.info syslog: HOST_UNIQ successful match 76
Jan 1 00:14:35 (none) daemon.crit syslog: PPP server detected. 70
Jan 1 00:14:35 (none) daemon.debug syslog: Sent packet: Ether addr: 00:90:1a:a2:ce:39 (PPPOE Discovery) PPPoE hdr: ver=0x1 type=0x1 code=0x19 sid=0x0000 length=0x0020 (PADR) PPPoE tag: type=0101 length=0000 (Service name) PPPoE tag: type=0103 length=0004 (Host Uniq) data (bin): 00 48 90 18 PPP 305
Jan 1 00:14:35 (none) daemon.debug syslog: Recv'd packet: Ether addr: 00:90:1a:a2:ce:39 (PPPOE Discovery) PPPoE hdr: ver=0x1 type=0x1 code=0x65 sid=0x1e43 length=0x000c (PADS) PPPoE tag: type=0101 length=0000 (Service name) PPPoE tag: type=0103 length=0004 (Host Uniq) data (bin): 00 48 90 18 303
Jan 1 00:14:35 (none) daemon.info syslog: HOST_UNIQ successful match 76
Jan 1 00:14:35 (none) daemon.info syslog: Got connection: 1e43 69
Jan 1 00:14:35 (none) daemon.crit syslog: PPP session established. 74
Jan 1 00:14:35 (none) user.warn kernel: netdev path : ppp1 -> atm0 73
Jan 1 00:14:41 (none) daemon.crit syslog: PPP LCP UP. 61
Jan 1 00:14:48 (none) daemon.crit syslog: Received valid IP address from server. Connection UP. 104
Jan 1 00:15:43 (none) user.alert kernel: Intrusion -> IN=ppp1 OUT= MAC= SRC=176.96.193.7 DST=85.172.184.166 LEN=48 TOS=0x00 PREC=0x00 TTL=50 ID=26481 DF PROTO=TCP SPT=52159 DPT=18907 WINDOW=8192 RES=0x00 SYN URGP=0 MARK=0x8000000 237

Разрыв происходит после входящих SYN запросов.
Прична:
1. р2р клиенты( например торрент). Выход - уменьшение максимального количества одновременных соединений в торренте.
2. syn-флуд. Выход- уточнить у провайдера о механизме защиты с его стороны.

2Oleg Syrbu
А вы можете пояснить про "син флуд"
Это насколько я понял вот эти строчки в логе?



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

1. В настройках торрента есть параметр "Максимальное число соединений"
2. О syn-флуде много информаци в интернете.

Мда...вместо простого ответа да/нет - меня посылают курить интернеты.
Просто фраза о син флуде, при неработающем, или плохо работающем интернете, заканчивается рекомендацией обратиться к провайдеру по поводу syn-флуда.

Вот это количество соединений торрент клиенты уже давно выставляют автоматом, с учётом максимально возможной скорости соединения и комфортной работы в сети.

зы: может тут боты отвечают...

Максимальное количество одновременных TCP соединений зависит от объёма оперативной памяти устройства. Если Вы подключены через маршрутизатор то всё упирается именно в его возможности( 32 МБ оперативной памяти в отличае от прямого соединения с ПК, имеющего гигабайти оперативной памяти)

Спасибо за пояснение.

Спасибо.

А как настроить чтоб она сама переподключалась при обрыве