Jump to content

loco m2 сбрасывает на дефолт иногда


Recommended Posts

Posted

кабель 10 метров  уличный новый поменял, 

Firmware Version:

XM.v6.3.16

 

 

Reset Button отключена. Что можно попробовать

 

 

Quote
Oct 04 17:08:41 system: Start
Oct  4 17:08:41 syslogd started: BusyBox v1.24.2
Oct  4 17:08:41 init: Run: /bin/lighttpd -D -f /etc/lighttpd.conf
Oct  4 17:08:41 init: starting pid 1001, tty '/dev/null': '/bin/lighttpd -D -f /etc/lighttpd.conf'
Oct  4 17:08:41 dropbear[1000]: Not backgrounding
Oct  4 17:08:42 init: Run: /bin/udapi-bridge -w -g -k -p 61780
Oct  4 17:08:42 init: starting pid 1006, tty '/dev/null': '/bin/udapi-bridge -w -g -k -p 61780'
Oct  4 17:08:42 FileSystem: Start check...
Oct  4 17:08:42 zcip: init br0
Oct  4 17:08:42 init: Run: /bin/udapi-server -g
Oct  4 17:08:42 init: starting pid 1017, tty '/dev/null': '/bin/udapi-server -g'
Oct  4 17:08:43 init: Run: /sbin/getty -L ttyS0 115200 vt100
Oct  4 17:08:43 udapi-bridge[1006]: watchdog: started with interval 60 seconds
Oct  4 17:08:44 udapi-bridge[1019]: udapi-bridge 0.13.3-no-git
Oct  4 17:08:44 udapi-bridge[1019]: HTTP server started on interface 'lo', port '61780'
Oct  4 17:08:44 udapi-bridge[1019]: LLDP: Skipping interface ath0 (Wireless)
Oct  4 17:08:44 udapi-bridge[1019]: LLDP: Skipping interface br0 (bridge)
Oct  4 17:08:44 udapi-server[1017]: udapi-server c45c459dee2039c2b326b6cc1b35f0f3509b3055
Oct  4 17:08:44 udapi-server[1017]: UDAPI version v1.0
Oct  4 17:08:48 FileSystem: End check.
Oct  4 17:08:58 zcip: config br0 169.254.154.226
Oct  4 17:08:58 zcip: init br0
Oct  4 17:09:14 zcip: config br0 169.254.154.226
Oct  4 17:09:14 zcip: script /usr/etc/zcip.script config failed, exitcode=2
Oct  4 17:09:32 zcip: init br0
Oct  4 17:09:48 zcip: config br0 169.254.154.226
Oct  4 17:10:07 zcip: init br0
Oct  4 17:10:23 zcip: config br0 169.254.154.226
Oct  4 17:10:24 httpd[1098]: Password auth succeeded for 'ubnt' from 192.168.1.45
Oct  4 17:10:24 wireless: ath0     New Access Point/Cell address:Not-Associated
Oct  4 17:10:29 wireless: ath0     Set Channel=0
Oct  4 17:10:41 zcip: init br0
Oct  4 17:10:57 zcip: config br0 169.254.154.226
Oct  4 17:11:15 zcip: init br0
Oct  4 17:11:31 init: reloading /etc/inittab
Oct  4 17:11:31 system: Stop
Oct  4 17:11:31 zcip: config br0 169.254.154.226
Oct  4 17:11:32 dropbear[1000]: Early exit: Terminated by signal
Oct  4 17:11:32 init: process '/sbin/udhcpc -f -i br0 -s /etc/udhcpc/udhcpc -p /var/run/udhcpc.br0.pid -h "UBNT"' (pid 998) exited. Scheduling for 
Oct  4 17:11:32 init: process '/bin/dropbear -F -r /etc/persistent/dropbear_dss_host_key -r /etc/persistent/dropbear_rsa_host_key -p 22 ' (pid 1000
Oct  4 17:11:33 init: process '/bin/lighttpd -D -f /etc/lighttpd.conf' (pid 1001) exited. Scheduling for restart.
Oct  4 17:11:34 syslogd exiting
Oct 04 17:11:56 system: Start
Oct  4 17:11:57 syslogd started: BusyBox v1.24.2
Oct  4 17:11:57 init: Run: /bin/dropbear -F -r /etc/persistent/dropbear_dss_host_key -r /etc/persistent/dropbear_rsa_host_key -p 22 
Oct  4 17:11:57 init: starting pid 1754, tty '/dev/null': '/bin/dropbear -F -r /etc/persistent/dropbear_dss_host_key -r /etc/persistent/dropbear_rs
Oct  4 17:11:58 init: Run: /bin/lighttpd -D -f /etc/lighttpd.conf
Oct  4 17:11:58 init: starting pid 1755, tty '/dev/null': '/bin/lighttpd -D -f /etc/lighttpd.conf'
Oct  4 17:12:00 dropbear[1754]: Not backgrounding
Oct  4 17:12:01 zcip: init br0
Oct  4 17:12:02 wireless: ath0     Set Mode:Managed
Oct  4 17:12:05 zcip: config br0 169.254.154.226
Oct  4 17:12:08 wireless: ath0     Set Mode:Managed
Oct  4 17:12:08 wireless: ath0     Set Frequency:2.447 GHz (Channel 8)
Oct  4 17:12:08 wireless: ath0     New Access Point/Cell address:F8:1A:67:F1:37:58
Oct  4 17:12:08 init: process '/sbin/udhcpc -f -i br0 -s /etc/udhcpc/udhcpc -p /var/run/udhcpc.br0.pid -h "UBNT"' (pid 1747) exited. Scheduling for
Oct  4 17:12:08 init: Run: /sbin/udhcpc -f -i br0 -s /etc/udhcpc/udhcpc -p /var/run/udhcpc.br0.pid -h "UBNT"
Oct  4 17:12:08 init: starting pid 1778, tty '/dev/null': '/sbin/udhcpc -f -i br0 -s /etc/udhcpc/udhcpc -p /var/run/udhcpc.br0.pid -h "UBNT"'
Oct  4 17:12:08 zcip: init br0
Oct  4 17:12:16 zcip: init br0
Oct  4 17:12:17 zcip: config br0 169.254.154.226
Oct  4 17:12:24 zcip: config br0 169.254.154.226
Oct  4 17:12:24 zcip: script /usr/etc/zcip.script config failed, exitcode=2
Oct  4 17:12:32 zcip: config br0 169.254.154.226
Oct  4 17:12:32 zcip: script /usr/etc/zcip.script config failed, exitcode=2
Oct  4 17:13:16 httpd[1826]: Password auth succeeded for 'ubnt' from 192.168.1.45
Oct  4 17:13:31 init: reloading /etc/inittab
Oct  4 17:13:31 system: Stop
Oct  4 17:13:31 dropbear[1754]: Early exit: Terminated by signal
Oct  4 17:13:31 wireless: ath0     Sending disassoc to f8:1a:67:f1:37:58. Reason: Disassociated because sending STA is leaving (or has left) BSS (8).
Oct  4 17:13:31 wireless: ath0     New Access Point/Cell address:Not-Associated
Oct  4 17:13:32 init: process '/bin/dropbear -F -r /etc/persistent/dropbear_dss_host_key -r /etc/persistent/dropbear_rsa_host_key -p 22 ' (pid 1754
Oct  4 17:13:32 init: process '/sbin/udhcpc -f -i br0 -s /etc/udhcpc/udhcpc -p /var/run/udhcpc.br0.pid -h "UBNT"' (pid 1778) exited. Scheduling for
Oct  4 17:13:33 init: process '/bin/wpa_supplicant -D wext -i ath0 -c /etc/wpasupplicant_WPA-PSK.conf' (pid 1748) exited. Scheduling for restart.
Oct  4 17:13:33 init: process '/bin/lighttpd -D -f /etc/lighttpd.conf' (pid 1755) exited. Scheduling for restart.
Oct  4 17:13:34 syslogd exiting
Oct 04 17:13:56 system: Start
Oct  4 17:13:56 syslogd started: BusyBox v1.24.2
Oct  4 17:13:57 init: Run: /bin/dropbear -F -r /etc/persistent/dropbear_dss_host_key -r /etc/persistent/dropbear_rsa_host_key -p 22 
Oct  4 17:13:57 init: starting pid 2273, tty '/dev/null': '/bin/dropbear -F -r /etc/persistent/dropbear_dss_host_key -r /etc/persistent/dropbear_rs
Oct  4 17:13:58 init: Run: /bin/lighttpd -D -f /etc/lighttpd.conf
Oct  4 17:13:58 init: starting pid 2275, tty '/dev/null': '/bin/lighttpd -D -f /etc/lighttpd.conf'
Oct  4 17:13:59 dropbear[2273]: Not backgrounding
Oct  4 17:14:01 zcip: init br0
Oct  4 17:14:01 wireless: ath0     Set Mode:Managed
Oct  4 17:14:05 zcip: config br0 169.254.154.226
Oct  4 17:14:07 wireless: ath0     Set Mode:Managed
Oct  4 17:14:07 wireless: ath0     Set Frequency:2.447 GHz (Channel 8)
Oct  4 17:14:07 wireless: ath0     New Access Point/Cell address:F8:1A:67:F1:37:58
Oct  4 17:14:07 init: process '/sbin/udhcpc -f -i br0 -s /etc/udhcpc/udhcpc -p /var/run/udhcpc.br0.pid -h "NanoStation loco M2"' (pid 2266) exited.
Oct  4 17:14:07 init: Run: /sbin/udhcpc -f -i br0 -s /etc/udhcpc/udhcpc -p /var/run/udhcpc.br0.pid -h "NanoStation loco M2"
Oct  4 17:14:07 init: starting pid 2297, tty '/dev/null': '/sbin/udhcpc -f -i br0 -s /etc/udhcpc/udhcpc -p /var/run/udhcpc.br0.pid -h "NanoStation 
Oct  4 17:14:07 zcip: init br0
Oct  4 17:14:12 zcip: init br0
Oct  4 17:14:17 zcip: config br0 169.254.154.226
Oct  4 17:14:23 zcip: config br0 169.254.154.226
Oct  4 17:14:23 zcip: script /usr/etc/zcip.script config failed, exitcode=2
Oct  4 17:14:28 zcip: config br0 169.254.154.226
Oct  4 17:14:28 zcip: script /usr/etc/zcip.script config failed, exitcode=2

 

Posted

Сбрасывать может если замыкают жилки кабеля, т.к. есть функционал сброса через кнопку на блоке питания.

 

Так же в самом устройстве есть схема защиты от статики по сетевому порту, действует она путем замыкания контактов сетевого разъема на массу (заземление). Если эта схема повреждена (мало ли что там по порту прилетало), то может иногда сама по себе замыкать, что приводит к сбросу настроек.

  • 2 months later...

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...
На сайте используются файлы cookie и сервисы аналитики для корректной работы форума и улучшения качества обслуживания. Продолжая использовать сайт, вы соглашаетесь с использованием файлов cookie и с Политикой конфиденциальности.