System log empty

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.

System log empty

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
System log empty
System log empty
2023-06-06 06:35:04
Model: CPE510  
Hardware Version:
Firmware Version:

Have 2 CPE510s running as AP and client to bridge LAN between 2 buildings. For troubleshooting it would be nice to log important events, but the log on both devices remain empty except from one entry for the time of boot and one for activating the configured address/netmask. 

 

Is there a way to change log-level so that the units at least record link down/up events? Debugging with logging changes to signal-level etc could also be useful at times.

 

Is there a MIB-file somewhere? It would be nice to know which device-specific (enterprise) objects are available.

 

Is it possible to detect and log sudden changes in the the frequency-range like the presence of strong signals like those emitted by WiFi jammers?

 

  0      
  0      
#1
Options
2 Reply
Re:System log empty
2023-10-30 00:25:41 - last edited 2023-10-30 00:53:06

Digging through the forum and files via SSH now - I'm unable to find anything useful. Would love to know and see these logs too

 

Closest I've come is in /tmp/ath0.ap_bss

ignore_file_errors=1
logger_syslog=-1
logger_syslog_level=2
logger_stdout=-1
logger_stdout_level=2
debug=0
dump_file=/tmp/hostapd.dump
ctrl_interface=/var/run/hostapd
ctrl_interface_group=0
ssid="XXXXXXXX"
dtim_period=2
max_num_sta=256
ignore_broadcast_ssid=0
wme_enabled=0
ieee8021x=0
eapol_version=2
eapol_key_index_workaround=0
eap_server=1
eap_user_file=/tmp/hostapd.eap_user
wps_disable=1
wps_upnp_disable=1
auth_algs=1
wpa=3
wpa_passphrase="XXXXXX"
wpa_key_mgmt=WPA-PSK
wpa_pairwise=CCMP TKIP
wpa_group_rekey=86400

 

I'm assuming we need to change the logger_syslog_level but I can't figure out how. Probably don't have access via SSH with the configured user login

  0  
  0  
#2
Options
Re:System log empty
2023-10-30 01:13:48

Looks like I've found an additional command here: klogd

 

BusyBox v1.01 (2023.06.16-00:54+0000) multi-call binary

Usage: klogd [-c n] [-n]

Kernel logger.
Options:
    -c n    Sets the default log level of console messages to n.
    -n    Run as a foreground process.

I've tried running klogd -c 1 and unable to see any changes

  0  
  0  
#3
Options