значицца делаем "Опция "Bridge PPPoE Frames Between WAN and Local Ports" выключена; Опция KeepAlive включена."

что для лога поставить? оба пункта ДЕБАГ?

Верно.

вчерась с вечера поставил. как учили. модем до теперешнего времени пока трудится. только лог забит вот таким:
типа пяток сообщений
Jul 18 13:46:31 user alert kernel: Intrusion -> IN=ppp_1_32_1 OUT= MAC= SRC=92.112.95.9 DST=92.112.80.1 LEN=52 TOS=0x00 PREC=0x00 TTL=63 ID=19947 DF PROTO=TCP SPT=4374 DPT=445 WINDOW=60352 RES=0x00 SYN URGP=0

и все время, де-то с 11:00 утра :
Jul 18 13:47:02 user warn dnsprobe[862]: dns query failed
Jul 18 13:47:35 user warn dnsprobe[862]: dns query failed
Jul 18 13:47:37 user warn dnsprobe[862]: dns query failed
Jul 18 13:47:39 user warn dnsprobe[862]: dns query failed
Jul 18 13:47:39 user notice dnsprobe[862]: Primary DNS server Is Down... Switching To Secondary DNS server
Jul 18 13:48:11 user warn dnsprobe[862]: dns query failed
Jul 18 13:48:13 user warn dnsprobe[862]: dns query failed
Jul 18 13:48:14 user notice dnsprobe[862]: Switching Back To Primary DNS server
Jul 18 13:49:48 user warn dnsprobe[862]: dns query failed
Jul 18 13:51:24 user warn dnsprobe[862]: dns query failed
Jul 18 13:53:30 user warn dnsprobe[862]: dns query failed
Jul 18 13:54:03 user warn dnsprobe[862]: dns query failed
Jul 18 13:54:05 user warn dnsprobe[862]: dns query failed
Jul 18 13:54:07 user warn dnsprobe[862]: dns query failed
Jul 18 13:54:07 user notice dnsprobe[862]: Primary DNS server Is Down... Switching To Secondary DNS server
Jul 18 13:54:38 user notice dnsprobe[862]: Switching Back To Primary DNS server

ну и свежачок снова:
Jul 18 13:57:35 user alert kernel: Intrusion -> IN=ppp_1_32_1 OUT= MAC= SRC=92.112.54.75 DST=92.112.80.1 LEN=48 TOS=0x00 PREC=0x00 TTL=126 ID=14784 DF PROTO=TCP SPT=4409 DPT=135 WINDOW=64800 RES=0x00 SYN URGP=0


наблюдаем дальше

Блин, таки не уследил....
Пришел вечером в 19:00 домой. Инета нету. модем честно ледами имитирует рабочее состояние.
Сразу полез в лог. мало места под логи выделено. нашел только вот это:
Jul 18 18:18:11 user warn dnsprobe[862]: dns query failed
Jul 18 18:18:13 user warn dnsprobe[862]: dns query failed
Jul 18 18:18:15 user warn dnsprobe[862]: dns query failed
Jul 18 18:18:47 user warn dnsprobe[862]: dns query failed
Jul 18 18:18:49 user warn dnsprobe[862]: dns query failed
Jul 18 18:18:51 user warn dnsprobe[862]: dns query failed
Jul 18 18:19:23 user warn dnsprobe[862]: dns query failed
Jul 18 18:19:25 user warn dnsprobe[862]: dns query failed
Jul 18 18:19:27 user warn dnsprobe[862]: dns query failed
Jul 18 18:19:59 user warn dnsprobe[862]: dns query failed
Jul 18 18:20:01 user warn dnsprobe[862]: dns query failed
Jul 18 18:20:03 user warn dnsprobe[862]: dns query failed
Jul 18 18:20:35 user warn dnsprobe[862]: dns query failed
Jul 18 18:20:37 user warn dnsprobe[862]: dns query failed
Jul 18 18:20:39 user warn dnsprobe[862]: dns query failed

...

Jul 18 19:02:18 syslog info -- MARK --
Jul 18 19:02:37 user warn dnsprobe[862]: dns query failed
Jul 18 19:02:39 user warn dnsprobe[862]: dns query failed
Jul 18 19:02:41 user warn dnsprobe[862]: dns query failed
Jul 18 19:03:13 user warn dnsprobe[862]: dns query failed
Jul 18 19:03:15 user warn dnsprobe[862]: dns query failed
Jul 18 19:03:17 user warn dnsprobe[862]: dns query failed
Jul 18 19:03:49 user warn dnsprobe[862]: dns query failed
Jul 18 19:03:51 user warn dnsprobe[862]: dns query failed
Jul 18 19:03:53 user warn dnsprobe[862]: dns query failed
Jul 18 19:04:25 user warn dnsprobe[862]: dns query failed
Jul 18 19:04:27 user warn dnsprobe[862]: dns query failed
Jul 18 19:04:29 user warn dnsprobe[862]: dns query failed

прошелся по состояниям:

This information reflects the current status of your DSL connection.

Line Rate - Upstream (Kbps): 613
Line Rate - Downstream (Kbps): 2471
LAN IP Address: 192.168.1.1
Default Gateway:
Primary DNS Server: 195.5.46.12
Secondary DNS Server: 195.5.46.11
Date/Time: Fri Jul 18 19:05:36 2008



WAN Info

VPI/VCI Category Service Name Interface Name Protocol State Status IP Address
1/32 UBR pppoe_1_32_1 ppp_1_32_1 PPPoE Enabled PPP Down



ADSL Statistics


Mode: ADSL2+
Line Coding: Trellis On
Status: No Defect
Link Power State: L0

Downstream Upstream
SNR Margin (dB): 32.8 23.6
Attenuation (dB): 19.0 8.1
Output Power (dBm): 11.7 1.0
Attainable Rate (Kbps): 18032 1279
Rate (Kbps): 2471 613
MSGc (number of bytes in overhead channel message): 59 19
B (number of bytes in Mux Data Frame): 71 46
M (number of Mux Data Frames in FEC Data Frame): 1 1
T (Mux Data Frames over sync bytes): 1 1
R (number of check bytes in FEC Data Frame): 16 16
S (ratio of FEC over PMD Data Frame length): 0.9944 2.5979
L (number of bits in PMD Data Frame): 708 194
D (interleaver depth): 64 8
Delay (msec): 15 5

Super Frames: 5810352 5810350
Super Frame Errors: 1 1173
RS Words: 377672926 395103800
RS Correctable Errors: 401 298918
RS Uncorrectable Errors: 2 N/A

HEC Errors: 0 14273
OCD Errors: 0 0
LCD Errors: 0 0
Total Cells: 547146351 295006844
Data Cells: 8008611 810382115
Bit Errors: 0 1078509

Total ES: 1 436
Total SES: 0 130
Total UAS: 17 1966953

далее пытаемся поднять соединение: ХОМЕ --> ВАН--> ЭКШН -->АП
смотрим лог:

Jul 18 19:08:29 user debug syslog: wlctl country list a > /var/wlclist
Jul 18 19:08:29 user debug syslog: wlctl country list b > /var/wlclist
Jul 18 19:08:30 user debug syslog: ifconfig wl0 > /var/hwaddr
Jul 18 19:08:30 user debug syslog: wlctl country list a > /var/wlclist
Jul 18 19:08:30 user debug syslog: wlctl country list b > /var/wlclist
Jul 18 19:08:30 user debug syslog: ifconfig wl0 > /var/hwaddr
Jul 18 19:08:30 user debug syslog: wlctl country list a > /var/wlclist
Jul 18 19:08:30 user debug syslog: wlctl country list b > /var/wlclist
Jul 18 19:08:30 user debug syslog: ifconfig wl0 > /var/hwaddr
Jul 18 19:08:38 user warn dnsprobe[862]: dns query failed
Jul 18 19:08:40 user warn dnsprobe[862]: dns query failed
Jul 18 19:08:42 user warn dnsprobe[862]: dns query failed
Jul 18 19:08:48 user debug syslog: wlctl country list a > /var/wlclist
Jul 18 19:08:49 user debug syslog: wlctl country list b > /var/wlclist
Jul 18 19:08:49 user debug syslog: ifconfig wl0 > /var/hwaddr
Jul 18 19:08:49 user debug syslog: wlctl country list a > /var/wlclist
Jul 18 19:08:49 user debug syslog: wlctl country list b > /var/wlclist
Jul 18 19:08:49 user debug syslog: ifconfig wl0 > /var/hwaddr
Jul 18 19:09:14 user warn dnsprobe[862]: dns query failed
Jul 18 19:09:16 user warn dnsprobe[862]: dns query failed
Jul 18 19:09:18 user warn dnsprobe[862]: dns query failed
Jul 18 19:09:39 user debug syslog: echo 1 > /proc/var/fyi/wan/ppp_1_32_1/wanup
Jul 18 19:09:50 user warn dnsprobe[862]: dns query failed
Jul 18 19:09:52 user warn dnsprobe[862]: dns query failed
Jul 18 19:09:54 user warn dnsprobe[862]: dns query failed
Jul 18 19:10:26 user warn dnsprobe[862]: dns query failed
Jul 18 19:10:28 user warn dnsprobe[862]: dns query failed
Jul 18 19:10:30 user warn dnsprobe[862]: dns query failed
Jul 18 19:11:02 user warn dnsprobe[862]: dns query failed
Jul 18 19:11:04 user warn dnsprobe[862]: dns query failed
Jul 18 19:11:06 user warn dnsprobe[862]: dns query failed

теперь можно модем выключить и включить снова. но можно и так:
ТУЛЗ --> СИСТЕМ--> СЕЙВ/РЕБУТ
(хорошо бы если б была кнопка просто ребут, без сейва)

ну теперь конечно:

System Log


Date/Time Facility Severity Message
Jan 1 00:00:17 syslog emerg BCM96345 started: BusyBox v1.00 (2005.04.12-18:11+0000)
Jan 1 00:00:17 user warn kernel: Can't analyze prologue code at 80171a04
Jan 1 00:00:17 user info kernel: Initializing Cryptographic API
Jan 1 00:00:17 user info kernel: PPP generic driver version 2.4.2
Jan 1 00:00:17 user info kernel: NET: Registered protocol family 24
Jan 1 00:00:17 user warn kernel: Using noop io scheduler
Jan 1 00:00:17 user warn kernel: bcm963xx_mtd driver v1.0
Jan 1 00:00:17 user warn kernel: brcmboard: brcm_board_init entry
Jan 1 00:00:17 user warn kernel: bcm963xx_serial driver v2.0
Jan 1 00:00:17 user info kernel: NET: Registered protocol family 2
Jan 1 00:00:17 user info kernel: IP: routing cache hash table of 512 buckets, 4Kbytes
Jan 1 00:00:17 user info kernel: TCP: Hash tables configured (established 512 bind 1024)
Jan 1 00:00:17 user info kernel: Initializing IPsec netlink socket
Jan 1 00:00:17 user debug syslog: bftpd
Jan 1 00:00:17 user info kernel: NET: Registered protocol family 1
Jan 1 00:00:17 user info kernel: NET: Registered protocol family 17
Jan 1 00:00:17 user info kernel: NET: Registered protocol family 15
Jan 1 00:00:17 user notice kernel: Ebtables v2.0 registered
Jan 1 00:00:17 user info kernel: NET: Registered protocol family 8
Jan 1 00:00:17 user info kernel: NET: Registered protocol family 20
Jan 1 00:00:17 user info kernel: 802.1Q VLAN Support v1.8 Ben Greear
Jan 1 00:00:17 user info kernel: All bugs added by David S. Miller
Jan 1 00:00:17 user warn kernel: VFS: Mounted root (squashfs filesystem) readonly.
Jan 1 00:00:17 user info kernel: Freeing unused kernel memory: 72k freed
Jan 1 00:00:17 user warn kernel: Algorithmics/MIPS FPU Emulator v1.5
Jan 1 00:00:17 user warn kernel: atmapi: module license 'Proprietary' taints kernel.
Jan 1 00:00:17 user warn kernel: blaadd: blaa_detect entry
Jan 1 00:00:17 user warn kernel: adsl: adsl_init entry
Jan 1 00:00:17 user info kernel: Broadcom BCMPROCFS v1.0 initialized
Jan 1 00:00:17 user warn kernel: Broadcom BCM6348B0 Ethernet Network Device v0.3
Jan 1 00:00:17 user warn kernel: Config Ethernet Switch Through SPI Slave Select 0
Jan 1 00:00:17 user warn kernel: dgasp: kerSysRegisterDyingGaspHandler: eth0 registered
Jan 1 00:00:17 user warn kernel: eth0: MAC Address: 00:19:5B:C2:0D:AE
Jan 1 00:00:17 user debug kernel: PCI: Setting latency timer of device 0000:00:01.0 to 64
Jan 1 00:00:17 user warn kernel: PCI: Enabling device 0000:00:01.0 (0004 -> 0006)
Jan 1 00:00:17 user warn kernel: wl: srom not detected, using main memory mapped srom info (wombo board)
Jan 1 00:00:17 user warn kernel: wl0: wlc_attach: using main board MAC address base in NVRAM (wombo board)
Jan 1 00:00:17 user warn kernel: wl0 MAC Address: 02:19:5B:C2:0D:AE
Jan 1 00:00:17 user warn kernel: wl0: Broadcom BCM4318 802.11 Wireless Controller 3.131.35.0.cpe2.3
Jan 1 00:00:17 user warn kernel: dgasp: kerSysRegisterDyingGaspHandler: wl0 registered
Jan 1 00:00:17 user warn kernel: BcmAdsl_Initialize=0xC00613B8, g_pFnNotifyCallback=0xC0078AC4
Jan 1 00:00:17 user warn kernel: pSdramPHY=0xA0FFFFF8, 0x1B779A 0xDEADBEEF
Jan 1 00:00:17 user warn kernel: AdslCoreHwReset: AdslOemDataAddr = 0xA0FFA744
Jan 1 00:00:17 user warn kernel: dgasp: kerSysRegisterDyingGaspHandler: dsl0 registered
Jan 1 00:00:17 user warn kernel: ip_tables: (C) 2000-2002 Netfilter core team
Jan 1 00:00:17 user warn kernel: ip_conntrack version 2.1 (125 buckets, 0 max) - 368 bytes per conntrack
Jan 1 00:00:17 user warn kernel: ip_conntrack_pptp version 2.1 loaded
Jan 1 00:00:17 user warn kernel: ip_nat_pptp version 2.0 loaded
Jan 1 00:00:17 user warn kernel: ip_conntrack_h323: init
Jan 1 00:00:17 user warn kernel: ip_nat_h323: initialize the module!
Jan 1 00:00:17 user warn kernel: ip_conntrack_rtsp v0.01 loading
Jan 1 00:00:17 user warn kernel: ip_nat_rtsp v0.01 loading
Jan 1 00:00:17 user crit kernel: ADSL G.994 training
Jan 1 00:00:17 user info kernel: device eth0 entered promiscuous mode
Jan 1 00:00:17 user info kernel: br0: port 1(eth0) entering learning state
Jan 1 00:00:17 user info kernel: br0: topology change detected, propagating
Jan 1 00:00:17 user info kernel: br0: port 1(eth0) entering forwarding state
Jan 1 00:00:17 user info kernel: device wl0 entered promiscuous mode
Jan 1 00:00:17 user info kernel: br0: port 2(wl0) entering learning state
Jan 1 00:00:17 user info kernel: br0: topology change detected, propagating
Jan 1 00:00:17 user info kernel: br0: port 2(wl0) entering forwarding state
Jan 1 00:00:17 user info kernel: device wl0.1 entered promiscuous mode
Jan 1 00:00:17 user info kernel: device eth0 left promiscuous mode
Jan 1 00:00:17 user info kernel: br0: port 1(eth0) entering disabled state
Jan 1 00:00:17 user crit kernel: ADSL G.992 started
Jan 1 00:00:17 user info kernel: device eth0 entered promiscuous mode
Jan 1 00:00:17 user info kernel: br0: port 1(eth0) entering learning state
Jan 1 00:00:17 user info kernel: y change detected, propagating
Jan 1 00:00:17 user info kernel: br0: port 1(eth0) entering forwarding state
Jan 1 00:00:17 user info kernel: device wl0 left promiscuous mode
Jan 1 00:00:17 user info kernel: br0: port 2(wl0) entering disabled state
Jan 1 00:00:17 user info kernel: device wl0 entered promiscuous mode
Jan 1 00:00:17 user info kernel: br0: port 2(wl0) entering learning state
Jan 1 00:00:17 user info kernel: br0: topology change detected, propagating
Jan 1 00:00:17 user info kernel: br0: port 2(wl0) entering forwarding state
Jan 1 00:00:17 user info kernel: device wl0.1 left promiscuous mode
Jan 1 00:00:17 user info kernel: br0: port 3(wl0.1) entering disabled state
Jan 1 00:00:17 user info kernel: device wl0.1 entered promiscuous mode
Jan 1 00:00:17 user debug syslog: tftpd
Jan 1 00:00:18 user debug syslog: pppd
Jan 1 00:00:18 user debug syslog: ifconfig nas_1_32 mtu 1492
Jan 1 00:00:18 user info kernel: br0: port 1(eth0) entering disabled state
Jan 1 00:00:18 daemon notice pppd[563]: pppd 2.4.1 started by admin, uid 0
Jan 1 00:00:20 user crit kernel: ADSL G.992 channel analysis
Jan 1 00:00:27 user crit kernel: ADSL G.992 message exchange
Jan 1 00:00:27 user crit kernel: ADSL link up, interleaved, us=613, ds=2471
Jan 1 00:00:28 user debug syslog: iptables -t nat -A PREROUTING -i br0 -d 192.168.1.1 -p udp --dport 53 -j DNAT --to 128.9.0.107
Jan 1 00:00:29 daemon notice pppd[563]: PPP: Start to connect ...
Jan 1 00:00:29 daemon crit pppd[563]: PPP server detected.
Jan 1 00:00:30 daemon crit pppd[563]: PPP session established.
Jan 1 00:00:30 daemon crit pppd[563]: PPP LCP UP.
Jan 1 00:00:32 daemon crit pppd[563]: Received valid IP address from server. Connection UP.
Jan 1 00:00:32 user debug syslog: route add default gw 195.5.5.185 2>/dev/null
Jan 1 00:00:32 user debug syslog: iptables -A FORWARD -o ppp_1_32_1 -p tcp --tcp-flags SYN,RST SYN -j TCPMSS --clamp-mss-to-pmtu
Jan 1 00:00:32 user debug syslog: iptables -A FORWARD -i ppp_1_32_1 -p tcp --tcp-flags SYN,RST SYN -j TCPMSS --clamp-mss-to-pmtu
Jan 1 00:00:32 user debug syslog: echo > /proc/net/ip_conntrack
Jan 1 00:00:32 user debug syslog: echo "1024" > /proc/sys/net/ipv4/ip_conntrack_max
Jan 1 00:00:32 user debug syslog: iptables -t nat -D PREROUTING -i br0 -d 192.168.1.1 -p udp --dport 53 -j DNAT --to 128.9.0.107 2>/dev/null
Jan 1 00:00:32 user debug syslog: iptables -t nat -D POSTROUTING -o ppp_1_32_1 -s 192.168.1.0/255.255.255.0 -j MASQUERADE 2>/dev/null
Jan 1 00:00:32 user debug syslog: iptables -t nat -A POSTROUTING -o ppp_1_32_1 -s 192.168.1.0/255.255.255.0 -j MASQUERADE
Jan 1 00:00:32 user debug syslog: iptables -t nat -D PREROUTING -i br0 -d 192.168.1.1 -p udp --dport 53 -j DNAT --to 195.5.46.12 2>/dev/null
Jan 1 00:00:32 user debug syslog: iptables -t nat -A PREROUTING -i br0 -d 192.168.1.1 -p udp --dport 53 -j DNAT --to 195.5.46.12
Jan 1 00:00:32 user debug syslog: /bin/dnsprobe &
Jan 1 00:00:32 user debug syslog: reaim -e 92.112.97.69 &
Jan 1 00:00:32 user debug syslog: iptables -t nat -D PREROUTING -i br0 -p tcp --dport 5190 -j REDIRECT --to-ports 5190 2>/dev/null
Jan 1 00:00:32 user notice dnsprobe[756]: dnsprobe started!
Jan 1 00:00:32 user debug syslog: iptables -t nat -D PREROUTING -i br0 -p tcp --dport 1863 -j REDIRECT --to-ports 1863 2>/dev/null
Jan 1 00:00:32 user debug syslog: iptables -t nat -A PREROUTING -i br0 -p tcp --dport 5190 -j REDIRECT --to-ports 5190
Jan 1 00:00:33 user debug syslog: iptables -t nat -A PREROUTING -i br0 -p tcp --dport 1863 -j REDIRECT --to-ports 1863
Jan 1 00:00:33 user debug syslog: iptables -D INPUT -i ppp_1_32_1 -j DROP
Jan 1 00:00:33 user debug syslog: iptables -A INPUT -i ppp_1_32_1 -j DROP
Jan 1 00:00:33 user debug syslog: iptables -I INPUT 1 -i ppp_1_32_1 -p udp --dport 5060 -j ACCEPT 2>/dev/null
Jan 1 00:00:33 user debug syslog: iptables -I INPUT 1 -i ppp_1_32_1 -p udp --dport 7070:7079 -j ACCEPT 2>/dev/null
Jan 1 00:00:33 user debug syslog: iptables -t nat -A PREROUTING -i br0 -p udp --dport 5060 -j REDIRECT --to-ports 5060 2>/dev/null
Jan 1 00:00:33 user debug syslog: siproxd --config /var/siproxd/siproxd.conf &
Jan 1 00:00:33 user debug syslog: iptables -I INPUT 1 -j ACCEPT -i ppp_1_32_1 -p tcp --dport 30005
Jan 1 00:00:33 user debug syslog: iptables -I FORWARD 1 -j ACCEPT -i ppp_1_32_1 -p tcp --dport 30005
Jan 1 00:00:34 user debug syslog: iptables -I INPUT 1 -j ACCEPT -i ppp_1_32_1 -p udp -s 192.168.1.1/24 --dport 30006
Jan 1 00:00:34 user debug syslog: iptables -I FORWARD 1 -j ACCEPT -i ppp_1_32_1 -p udp -s 192.168.1.1/24 --dport 30006
Jan 1 00:00:34 user notice syslog: siproxd.c:192 INFO:siproxd-0.5.10-2879 i686-redhat-linux-gnu starting up
Jan 1 00:00:34 user notice syslog: siproxd.c:218 INFO:daemonized, pid=825
Jan 1 00:00:34 user notice syslog: sock.c:65 INFO:bound to port 5060
Jan 1 00:00:34 user notice syslog: register.c:65 WARNING:registration file not found, starting with empty table
Jan 1 00:00:34 user notice syslog: siproxd.c:265 INFO:siproxd-0.5.10-2879 i686-redhat-linux-gnu started
Jan 1 00:00:38 user alert kernel: Intrusion -> IN=ppp_1_32_1 OUT= MAC= SRC=92.112.70.126 DST=92.112.97.69 LEN=48 TOS=0x00 PREC=0x00 TTL=127 ID=15314 DF PROTO=TCP SPT=4361 DPT=135 WINDOW=64240 RES=0x00 SYN URGP=0
Jan 1 00:00:39 daemon err user: tr69c: Unable to retrieve attributes in scratch PAD
Jan 1 00:00:39 daemon err user: Stored Parameter Attribute data is corrupt or missing
Jul 18 19:14:15 user alert kernel: Intrusion -> IN=ppp_1_32_1 OUT= MAC= SRC=92.112.209.98 DST=92.112.97.69 LEN=48 TOS=0x00 PREC=0x00 TTL=126 ID=10878 DF PROTO=TCP SPT=2495 DPT=445 WINDOW=64800



и вдогонку уже мои любимые:
Jul 18 19:18:18 user alert kernel: Intrusion -> IN=ppp_1_32_1 OUT= MAC= SRC=92.112.191.193 DST=92.112.97.69 LEN=48 TOS=0x00 PREC=0x00 TTL=126 ID=26923 DF PROTO=TCP SPT=1321 DPT=445 WINDOW=64800 RES=0x00 SYN URGP=0
Jul 18 19:18:21 user alert kernel: Intrusion -> IN=ppp_1_32_1 OUT= MAC= SRC=92.112.191.193 DST=92.112.97.69 LEN=48 TOS=0x00 PREC=0x00 TTL=126 ID=27803 DF PROTO=TCP SPT=1321 DPT=445 WINDOW=64800 RES=0x00 SYN URGP=0
Jul 18 19:18:32 user alert kernel: Intrusion -> IN=ppp_1_32_1 OUT= MAC= SRC=92.112.237.42 DST=92.112.97.69 LEN=48 TOS=0x00 PREC=0x00 TTL=126 ID=28193 DF PROTO=TCP SPT=3540 DPT=135 WINDOW=64800 RES=0x00 SYN URGP=0
Jul 18 19:18:38 user alert kernel: Intrusion -> IN=ppp_1_32_1 OUT= MAC= SRC=92.112.237.42 DST=92.112.97.69 LEN=48 TOS=0x00 PREC=0x00 TTL=126 ID=29978 DF PROTO=TCP SPT=3540 DPT=135 WINDOW=64800 RES=0x00 SYN URGP=0
Jul 18 19:18:49 user alert kernel: Intrusion -> IN=ppp_1_32_1 OUT= MAC= SRC=92.112.93.203 DST=92.112.97.69 LEN=52 TOS=0x00 PREC=0x00 TTL=63 ID=4911 DF PROTO=TCP SPT=2278 DPT=2967 WINDOW=60352 RES=0x00 SYN URGP=0
Jul 18 19:28:31 user alert kernel: Intrusion -> IN=ppp_1_32_1 OUT= MAC= SRC=213.234.219.105 DST=92.112.97.69 LEN=48 TOS=0x00 PREC=0x00 TTL=118 ID=42696 PROTO=TCP SPT=17313 DPT=1080 WINDOW=65535 RES=0x00 SYN URGP=0

GINic, Ваши любимые - ничто иное, как отчет firewall о попытках внешних соединений с Вашим модемом.
Проблему подтверждаю. DSL2640U, клиенты на Wi-Fi, сессия устанавливается средствами модема, провайдер - ЮТК (Краснодарский край), Software Version: RU_DSL-2640U_3-06-04-3H00.A2pB023g2.d19b. Настраивал по руководству для DSL2640U с сайта провайдера, затем брал руководство здесь, различий не увидел. Связь рвется минимум раз в сутки, иногда и чаще. В Status -> WAN Info в графе Status стоит при этом PPP Down. После перезапуска модема связь восстанавливается. Я, конечно, не Антон Уральский, мне не стоит особого труда перезагрузить модем раз в сутки - но соседу, у которого этот модем стоит, так и не смог дать вразумительного ответа. Попробую включить указанную выше опцию, надеюсь, поможет.

присоединяюсь.
проблема действительно существует.
причем в прошивке 3H00 по-умолчанию после обырыва (если заглянуть в лог обнаружим:как-будто мы сами нажали нажали на разрыв соединения)
модем не поднимает pppoe до перезагрузки (сама dsl линия отлично работает по сообщениям модема).
Если же активировать птичку Bridge PPPoE Frames Between WAN and Local Ports, модем сам восстанавливает pppoe.
зы. хочу добавить, что у меня после разрыва, модем начинал дико тормозить, веб-морда очень тяжело загружаться, telnet еле шевелиться.

_________________
DSL-2640U (3H00)

та да, я знаю, просто наличие этих сообщений греет душу - значицца модем работает и я даже нахожусь под защитой от вторжений

включение опции таки поможет. я пробовал уже.

да, забыл, мой провайдер Укртелеком. Услуга ОГО 512.

опа, таки словил. прямо во время работы инет упал. бегом лог смотрим:


вот и видим в логе атаку, потом коннект падает. и фсе.

искомое получили. так что включил псису под названием Bridge PPPoE Frames Between WAN and Local Ports и ожидаем дальше.

Ваш ход, саппорт.

По советам включил опцию "Bridge PPPoE Frames Between WAN and Local Ports", вторые сутки полет нормальный. Ни одного РАЗРЫВА! Так что, несмотря на все заявления уважаемых D-Link-овцев, проблема всё-таки существует...

опция не влияет на разрывы
активируя ее, удается избежать перезагрузки модема для восстановления связи.

_________________
DSL-2640U (3H00)

включил бридж фреймов в субботу вечером, вот уже почти полдень понедельника, кроме вот такого, в логе ничего другого нету:


значит таки влияет на разрывы...

MaKCuMyC, спасибо, я в курсе... Просто ранее приходилось, как я писал выше, перезагружать модем каждый день, а то и по несколько раз за день. При этом, как тут кто-то писал уже, возникали проблемы при работе Wi-Fi - до модема достучаться было практически невозможно как по веб-интерфейсу, так и по телнет. А если учесть тот факт, что модем установлен у соседа, и физический доступ к нему затруднен, то перезагрузка удаленно вызывала большие затруднения. Сейчас модем корректно восстанавливает соединение после обрыва/завершения сессии, мы разрывов просто не замечаем.