Модем D-Link 504T
Прошивка: V3.02B01T01.RU.20070402
Проблема: модем переодически теряет связь (на время перестает гореть лампочка Status и ADSL), потом модем соеденяется самостоятельно.
Лог:
Jan 1 12:00:12> NTP Polling Timer for DHCP Started succesfully.
Jan 1 12:00:12> DSL Polling Timer Started succesfully.
Jan 1 12:00:13> Firewall NAT service started
Jan 1 12:00:15> starting on port 80
Jan 1 12:00:15> Initializing the WAN Bridge.
Jan 1 12:00:15> Please set the MAC Address for the WAN Bridge.
Jan 1 12:00:15> Set the Environment variable 'wan_br_mac'.
Jan 1 12:00:15> xx.xx.xx.xx.xx.xx
Jan 1 12:00:15> Mounted root (squashfs filesystem) readonly.
Jan 1 12:00:15> Mounted devfs on /dev
Jan 1 12:00:15> 64k freed
Jan 1 12:00:15> Algorithmics/MIPS FPU Emulator v1.5
Jan 1 12:00:15> registered device TI Avalanche SAR
Jan 1 12:00:15> Sangam detected
Jan 1 12:00:15> DSP binary filesize = 356930 bytes
Jan 1 12:00:15> Setting mode to 0xffff
Jan 1 12:00:15> version:[6.00.01.00]
Jan 1 12:00:15> Setting mode to 0xffff
Jan 1 12:00:15> Default Asymmetric MTU for nas0 1500
Jan 1 12:00:15> Registering protocol inspector: 0x941716c8 for VCC:0x9423ba00
Jan 1 12:00:15> Default Asymmetric MTU for nas1 1500
Jan 1 12:00:15> Registering protocol inspector: 0x941716c8 for VCC:0x945f2000
Jan 1 12:00:16> Default Asymmetric MTU for br0 1500
Jan 1 12:00:16> Bridge Created: br0
Jan 1 12:00:17> Bridge Created: br1
Jan 1 12:00:18> Bridge Interface Added: eth0
Jan 1 12:00:18> Bridge Interface Added: nas1
Jan 1 12:00:18> Add Bridge Iface Error: 1
Jan 1 12:00:18> Duplicate Bridge Iface: nas1
Jan 1 12:00:18> Bridge Interface Added: nas0
Jan 1 12:00:18> Add Bridge Iface Error: 1
Jan 1 12:00:18> Duplicate Bridge Iface: nas0
Jan 1 12:00:19> 2
Jan 1 12:00:19> Default Asymmetric MTU for br1 1500
Jan 1 12:00:19> 2
Jan 1 12:00:22> DSL Carrier is down
Jan 1 12:00:26> DSL in Sync
Jan 1 12:00:32> DSL Carrier is up
Jan 1 12:00:33> sar read trained mode (1)(ADSL_G.dmt)
Jan 1 12:00:33> pingStat 2, oamHdr 230 result 0
View Log
View Log displays the activities occurring on the DSL-504T .
n 1 12:00:33> pingStat 2, oamHdr 200 result 0
Jan 1 12:00:33> pingStat 2, oamHdr 280 result 0
Jan 1 12:00:33> pingStat 2, oamHdr 240 result 0
Jan 1 12:00:33> pingStat 2, oamHdr 260 result 0
Jan 1 12:00:33> pingStat 2, oamHdr 600 result 0
Jan 1 12:00:33> pingStat 2, oamHdr 230 result 0
Jan 1 12:00:33> pingStat 2, oamHdr 800230 result 0
Jan 1 12:00:33> pingStat 2, oamHdr 2B0 result 0
Jan 1 12:00:33> pingStat 2, oamHdr 330 result 0
Jan 1 12:00:33> pingStat 2, oamHdr 3B0 result 0
Jan 1 12:00:33> pingStat 2, oamHdr 8002B0 result 0
Jan 1 12:00:33> pingStat 2, oamHdr 800330 result 0
Jan 1 12:00:33> pingStat 2, oamHdr 8003B0 result 0
Jan 1 12:00:33> get 0xF at Addr 0xA30085B0

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

_________________
С уважением, Давыдов Денис.