KYTECHNGAMING

I am using 5v 5a adapter for usb hub. The modem is plugged in and the switch is not active. Also, ping check is disabled in the settings. I think it might be better to buy a new usb hub or remove the modem.

Wow! I've realized now. The disc was gone again at around 6 in the morning. I/O failure hub or disk? I think this recording is what you want to tell me. But on the same hub, the OPKG disk continues to work without any problems. 10.101.0.1 Oct 2 06:06:31 10.101.0.1 kern info kernel usb 1-2.4: reset high-speed USB device number 10 using xhci-mtk 10.101.0.1 Oct 2 06:06:31 10.101.0.1 kern err kernel usb 1-2.4: device descriptor read/64, error -71 10.101.0.1 Oct 2 06:06:32 10.101.0.1 kern info kernel usb 1-2.4: reset high-speed USB device number 10 using xhci-mtk 10.101.0.1 Oct 2 06:06:32 10.101.0.1 kern warning kernel usb 1-2.4: Device not responding to setup address. 10.101.0.1 Oct 2 06:06:33 10.101.0.1 kern info kernel usb 1-2.4: reset high-speed USB device number 10 using xhci-mtk 10.101.0.1 Oct 2 06:06:33 10.101.0.1 kern err kernel usb 1-2.4: device descriptor read/all, error -71 10.101.0.1 Oct 2 06:06:34 10.101.0.1 kern info kernel usb 1-2.4: reset high-speed USB device number 10 using xhci-mtk 10.101.0.1 Oct 2 06:06:34 10.101.0.1 kern info kernel usb 1-2.4: device firmware changed 10.101.0.1 Oct 2 06:06:34 10.101.0.1 kern info kernel usb 1-2.4: USB disconnect, device number 10 10.101.0.1 Oct 2 06:06:34 10.101.0.1 kern info kernel sd 2:0:0:0: [sdc] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x01 driverbyte=0x00 10.101.0.1 Oct 2 06:06:34 10.101.0.1 kern err kernel Aborting journal on device sdc1-8. 10.101.0.1 Oct 2 06:06:34 10.101.0.1 kern err kernel JBD2: Error -5 detected when updating journal superblock for sdc1-8. 10.101.0.1 Oct 2 06:06:34 10.101.0.1 kern info kernel sd 2:0:0:0: [sdc] tag#0 CDB: opcode=0x2a 2a 00 00 03 4e 58 00 00 08 00 10.101.0.1 Oct 2 06:06:34 10.101.0.1 kern err kernel blk_update_request: I/O error, dev sdc, sector 216664 10.101.0.1 Oct 2 06:06:34 10.101.0.1 kern warning kernel EXT4-fs warning (device sdc1): ext4_end_bio:307: I/O error -5 writing to inode 13 (offset 0 size 0 starting block 27084) 10.101.0.1 Oct 2 06:06:34 10.101.0.1 kern err kernel Buffer I/O error on device sdc1, logical block 26827 10.101.0.1 Oct 2 06:06:34 10.101.0.1 kern crit kernel EXT4-fs error (device sdc1) in ext4_writepages:2810: IO failure 10.101.0.1 Oct 2 06:06:34 10.101.0.1 kern warning kernel EXT4-fs warning (device sdc1): ext4_end_bio:307: I/O error -5 writing to inode 13 (offset 0 size 0 starting block 27084) 10.101.0.1 Oct 2 06:06:34 10.101.0.1 kern err kernel Buffer I/O error on device sdc1, logical block 26827 10.101.0.1 Oct 2 06:06:34 10.101.0.1 kern warning kernel sd 2:0:0:0: [sdc] Stopping disk 10.101.0.1 Oct 2 06:06:34 10.101.0.1 kern info kernel sd 2:0:0:0: [sdc] Start/Stop Unit failed: Result: hostbyte=0x01 driverbyte=0x00 10.101.0.1 Oct 2 06:06:34 10.101.0.1 kern info kernel usb 1-2.4: new high-speed USB device number 11 using xhci-mtk 10.101.0.1 Oct 2 06:06:34 10.101.0.1 user info ndm Core::FileSystem::Repository: unregistering "29bf1f34-afcb-4e89-b976-0e9033e236fe:" filesystem... 10.101.0.1 Oct 2 06:06:34 10.101.0.1 kern info kernel usb 1-2.4: New USB device found, idVendor=0930, idProduct=6544 10.101.0.1 Oct 2 06:06:34 10.101.0.1 kern info kernel usb 1-2.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 10.101.0.1 Oct 2 06:06:34 10.101.0.1 kern info kernel usb 1-2.4: Product: TransMemory 10.101.0.1 Oct 2 06:06:34 10.101.0.1 kern info kernel usb 1-2.4: Manufacturer: TOSHIBA 10.101.0.1 Oct 2 06:06:34 10.101.0.1 kern info kernel usb 1-2.4: SerialNumber: 001D92AD6BE2C96093800AAA 10.101.0.1 Oct 2 06:06:34 10.101.0.1 kern info kernel usb-storage 1-2.4:1.0: USB Mass Storage device detected 10.101.0.1 Oct 2 06:06:34 10.101.0.1 kern info kernel scsi host3: usb-storage 1-2.4:1.0 10.101.0.1 Oct 2 06:06:34 10.101.0.1 user info ndm Ntce::Database: cleared classification data. 10.101.0.1 Oct 2 06:06:34 10.101.0.1 kern crit kernel EXT4-fs error (device sdc1): ext4_journal_check_start:56: Detected aborted journal 10.101.0.1 Oct 2 06:06:34 10.101.0.1 kern crit kernel EXT4-fs (sdc1): Remounting filesystem read-only 10.101.0.1 Oct 2 06:06:34 10.101.0.1 kern warning kernel ------------[ cut here ]------------ 10.101.0.1 Oct 2 06:06:34 10.101.0.1 kern warning kernel WARNING: CPU: 3 PID: 15846 at fs/fs-writeback.c:2197 __mark_inode_dirty+0x264/0x284 10.101.0.1 Oct 2 06:06:34 10.101.0.1 kern warning kernel bdi-block not registered 10.101.0.1 Oct 2 06:06:34 10.101.0.1 kern warning kernel Modules linked in: eip93_cryptoapi(O) nf_nat_sip nf_conntrack_sip fastvpn(PO) xhci_mtk xhci_hcd nf_nat_ftp nf_conntrack_ftp zram ntc(PO) ensoc_dsl(PO) ensoc_dmt(PO) ensoc_flt(O) nnfm(O) mt7615_ap(PO) ubifs ubi ensoc_eth(PO) nacct(PO) rndis_host qcserial cdc_ether huawei_cdc_ncm asix qmi_wwan option cdc_ncm ccm usb_wwan usbextras(O) gcm seqiv authenc exfat(O) nls_utf8 esp4 zstd kalmia cp210x thfsplus(O) nf_nat_rtsp(O) nls_cp1251 cypress_m8 ax88179_178a usb_storage cdc_acm l2tp_ppp usblp dm9601 sd_mod sr_mod nls_cp437 sierra sg usbnet ext4 tfat(PO) zstd_decompress xfrm_user deflate nls_cp866 chacha20poly1305 echainiv tntfs(PO) af_key pl2303 jffs2 cdc_wdm ghash_generic r8152 l2tp_core rtl8150 zstd_compress aead ftdi_sio ch341 usbserial nf_nat_pptp nf_nat_h323 usbcore nf_conntrack_pptp wireguard 10.101.0.1 Oct 2 06:06:34 10.101.0.1 kern warning kernel xfrm_interface crc32c_generic libphy cdrom tunnel6 resetnds(PO) hmac des_generic mtdoops_proc(O) ansi_cprng ctr jitterentropy_rng gf128mul nf_conntrack_h323 xt_esp chacha_generic zlib_deflate jbd2 nls_base ip6_udp_tunnel poly1305_generic xxhash sch_cake(O) nf_conntrack_proto_gre phr(PO) mbcache nf_conntrack_rtsp(O) xt_policy ndm_storage dummy ip_gre zlib_inflate crc16 loop xfrm4_mode_tunnel md5 scsi_mod udp_tunnel crypto_null xfrm4_mode_transport cbc tsmb(PO) drbg usb_common sit nf_nat_proto_gre xfrm_algo xfrm4_tunnel 10.101.0.1 Oct 2 06:06:34 10.101.0.1 kern warning kernel CPU: 3 PID: 15846 Comm: syslog-ng Tainted: P O 4.9-ndm-5 #2 10.101.0.1 Oct 2 06:06:34 10.101.0.1 kern warning kernel Stack : 00000000 00000000 80528152 00000048 00000048 80528150 8045d2c0 00000009 10.101.0.1 Oct 2 06:06:34 10.101.0.1 kern warning kernel 80444f38 830d6f8c 804b4e83 80523ecc 00000895 00000000 77bfeb18 77c05000 10.101.0.1 Oct 2 06:06:34 10.101.0.1 kern warning kernel 77c05000 8008de54 00000000 0000000a 80528152 00000000 8044ae28 8aef7c2c 10.101.0.1 Oct 2 06:06:34 10.101.0.1 kern warning kernel 8044d404 8008b048 00000895 00000000 00000003 00003de6 8aef7c2c 80444f38 10.101.0.1 Oct 2 06:06:34 10.101.0.1 kern warning kernel 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 10.101.0.1 Oct 2 06:06:34 10.101.0.1 kern warning kernel ... 10.101.0.1 Oct 2 06:06:34 10.101.0.1 kern warning kernel Call Trace: 10.101.0.1 Oct 2 06:06:34 10.101.0.1 kern warning kernel [<f3332257>] show_stack+0x2c/0x88 10.101.0.1 Oct 2 06:06:34 10.101.0.1 kern warning kernel [<8a339aee>] dump_stack+0x9c/0xd4 10.101.0.1 Oct 2 06:06:34 10.101.0.1 kern warning kernel [<8c645cd5>] __warn+0xe0/0x114 10.101.0.1 Oct 2 06:06:34 10.101.0.1 kern warning kernel [<04186378>] warn_slowpath_fmt+0x34/0x40 10.101.0.1 Oct 2 06:06:34 10.101.0.1 kern warning kernel [<0a9ce964>] __mark_inode_dirty+0x264/0x284 10.101.0.1 Oct 2 06:06:34 10.101.0.1 kern warning kernel [<91040a7c>] generic_update_time+0xa4/0x104 10.101.0.1 Oct 2 06:06:34 10.101.0.1 kern warning kernel [<0cafa713>] file_update_time+0xc0/0x130 10.101.0.1 Oct 2 06:06:34 10.101.0.1 kern warning kernel [<75c39b06>] __generic_file_write_iter+0xb8/0x280 10.101.0.1 Oct 2 06:06:34 10.101.0.1 kern warning kernel [<674566b3>] ext4_llseek+0xb6c/0xf9c [ext4] 10.101.0.1 Oct 2 06:06:34 10.101.0.1 kern warning kernel [<13864622>] ep_scan_ready_list.constprop.0+0x98/0x21c 10.101.0.1 Oct 2 06:06:34 10.101.0.1 kern warning kernel ---[ end trace a57548a6aa657f34 ]--- 10.101.0.1 Oct 2 06:06:34 Keenetic-0615 syslog err syslog-ng[917] I/O error occurred while writing; fd='5', error='Read-only file system (30)' 10.101.0.1 Oct 2 06:06:34 Keenetic-0615 syslog notice syslog-ng[917] Suspending write operation because of an I/O error; fd='5', time_reopen='60' 10.101.0.1 Oct 2 06:06:35 10.101.0.1 kern info kernel ndm (15856): drop_caches: 3 10.101.0.1 Oct 2 06:06:35 10.101.0.1 user err ndm Core::FileSystem::Native: unable to disable swap: no device found. 10.101.0.1 Oct 2 06:06:35 10.101.0.1 user info ndm Storage::Manager: "Media2": unregistered partition "29bf1f34-afcb-4e89-b976-0e9033e236fe:". 10.101.0.1 Oct 2 06:06:35 10.101.0.1 user info ndm Storage::Manager: "Media2": removed partition "29bf1f34-afcb-4e89-b976-0e9033e236fe:". 10.101.0.1 Oct 2 06:06:35 10.101.0.1 user info ndm Core::FileSystem::Repository: unregistering "144c8094-b6cc-4e2c-b39d-a5fe18b4948c:" filesystem... 10.101.0.1 Oct 2 06:06:35 10.101.0.1 kern info kernel scsi 3:0:0:0: Direct-Access TOSHIBA TransMemory 1.00 PQ: 0 ANSI: 2 10.101.0.1 Oct 2 06:06:35 10.101.0.1 kern info kernel sd 3:0:0:0: Attached scsi generic sg2 type 0 10.101.0.1 Oct 2 06:06:35 10.101.0.1 kern info kernel sd 3:0:0:0: [sdd] 7823296 512-byte logical blocks: (4.01 GB/3.73 GiB) 10.101.0.1 Oct 2 06:06:35 10.101.0.1 kern info kernel sd 3:0:0:0: [sdd] Write Protect is off 10.101.0.1 Oct 2 06:06:35 10.101.0.1 kern info kernel sd 3:0:0:0: [sdd] Mode Sense: 65 44 09 30 10.101.0.1 Oct 2 06:06:35 10.101.0.1 kern info kernel sd 3:0:0:0: [sdd] No Caching mode page found 10.101.0.1 Oct 2 06:06:35 10.101.0.1 kern info kernel sd 3:0:0:0: [sdd] Assuming drive cache: write through 10.101.0.1 Oct 2 06:06:35 10.101.0.1 kern info kernel sd 3:0:0:0: [sdd] Attached SCSI removable disk 10.101.0.1 Oct 2 06:06:49 10.101.0.1 user err ndm Core::FileSystem::Native: failed to unmount "/tmp/mnt/144c8094-b6cc-4e2c-b39d-a5fe18b4948c": device or resource busy. 10.101.0.1 Oct 2 06:06:49 10.101.0.1 user err ndm Storage::Partition: failed to unmount. 10.101.0.1 Oct 2 06:06:49 10.101.0.1 user info ndm Storage::Manager: "Media2": unregistered partition "144c8094-b6cc-4e2c-b39d-a5fe18b4948c:". 10.101.0.1 Oct 2 06:06:49 10.101.0.1 user err ndm Core::FileSystem::Native: failed to unmount "/tmp/mnt/144c8094-b6cc-4e2c-b39d-a5fe18b4948c": device or resource busy. 10.101.0.1 Oct 2 06:06:49 10.101.0.1 user crit ndm FileSystem::Directory: system failed [0xcffd00ec], unable to remove "/tmp/mnt/144c8094-b6cc-4e2c-b39d-a5fe18b4948c": device or resource busy. 10.101.0.1 Oct 2 06:06:49 10.101.0.1 user info ndm Storage::Manager: "Media2": removed partition "144c8094-b6cc-4e2c-b39d-a5fe18b4948c:". 10.101.0.1 Oct 2 06:06:49 10.101.0.1 user crit ndm Storage::Manager: "Media2": a media was unsafely unplugged without ejecting. 10.101.0.1 Oct 2 06:06:49 10.101.0.1 user info ndm Storage::Manager: removed "Media2", port 2. 10.101.0.1 Oct 2 06:06:49 10.101.0.1 user info ndm Storage::Manager: "Media3": enabled a disk spin down. 10.101.0.1 Oct 2 06:06:49 10.101.0.1 user info ndm Storage::Manager: created "Media3", port 2. 10.101.0.1 Oct 2 06:07:34 Keenetic-0615 syslog notice syslog-ng[917] Error suspend timeout has elapsed, attempting to write again; fd='5' 10.101.0.1 Oct 2 06:07:34 Keenetic-0615 syslog err syslog-ng[917] I/O error occurred while writing; fd='5', error='Read-only file system (30)' 10.101.0.1 Oct 2 06:07:34 Keenetic-0615 syslog notice syslog-ng[917] Suspending write operation because of an I/O error; fd='5', time_reopen='60' 10.101.0.1 Oct 2 06:08:34 Keenetic-0615 syslog notice syslog-ng[917] Error suspend timeout has elapsed, attempting to write again; fd='5' 10.101.0.1 Oct 2 06:08:34 Keenetic-0615 syslog err syslog-ng[917] I/O error occurred while writing; fd='5', error='Read-only file system (30)' 10.101.0.1 Oct 2 06:08:34 Keenetic-0615 syslog notice syslog-ng[917] Suspending write operation because of an I/O error; fd='5', time_reopen='60' 10.101.0.1 Oct 2 06:08:46 10.101.0.1 user info ndm Core::Scgi::AuthPool: cleanup: 15 -> 14. opkg disk is mounted on the same hub and usb modem. @Le ecureuil

It is very rare that my OPKG disk in the same hub is not visible after restarting the modem. Very rare though. In this case, I just have to unplug the usb and plug it back in. But in case of lost partition, re-mounting it doesn't work. I need to remove /tmp/3947347kdfdnf path from SMB.

Good news 💙🤞 But my problem description was other previous message which it is quoted below. Why is partition lost? When checking partition, no such issue. I will record a video if it will be happen again.

I've been observing the situation for a long time. Thought it was fixed, after a while, it also happened that it could not connect other than 2.4 ghz. I even bought the ZYXEL NWD6602 AC1200 Dual-Band Wireless Nano USB Adapter. It also came out with Realtek 8812BU chipset. I've been through similar situations. We are also monitoring the situation with Keenetic TR RD. The other day I saw that my notebook wifi card driver had a new update. Version number: 2024.0.10.133 Release date: 23.08.2021 For 2 days, when I checked the wifi connection after turning the router and laptop off and on, waking up from sleep mode, I haven't seen it connect at 2.4ghz yet. It can connect at 5ghz.

This question point the same issue which I informed.

Column of Name is limited characters. and also fixed size

Sorting by main screen name and host number only does not work properly. ?Not decimal sort, it can be text sort? It works fine within the specific network.

Is it possible to add a responsive scrolling style of the list on the network screen in the future? Like adjusting ordering on connection priorities in the interface. (move up - move down)

This question point the same issue which I informed. No. I am using only one partition which name is TEMP. This usb have 2 partition ext3(temp) and ext4(swap) That's the issue. When the partition is lost, just delete this partition label in smb settings and reboot. Everything should work.

It might be a long post. Hopefully we can catch something for the fix. I upgraded my device to 3.7 Beta 3 and when the device was turned on, this disk partition was still not visible. I removed the disk and when I checked with gparted, the partitions were standing. I rebooted my router with no disk and inserted the disk. Again, there was no partition. But other discs were fine. Run e2fsck: I rebooted the device and also tried inserting the disk into another usb port. I put the USB hub and disks back. Error occurred on my disk with OPKG. I just unplugged that usb and plugged it back in. Seeing suggestions to do e2fsck, I checked the other 2 disks. I rebooted the router and inserted the disks. Again the same media2 did not have a partition. Other discs are fine. I tried 1-2 more times by plugging it into a different port. In the interface, I deleted the /tmp entry under the smb application. The disk was mounted. And I rebooted. Finally the partition is back. I didn't know how to deal with this situation. Why can this problem occur with more than one disk? Why am I getting this result on all the different disks I use to save syslog? @Le ecureuil

Hello, How to make this script for pyhton application? Vitaliy's grafana monitoring works perfectly, if Keenetic is collector. He shared a script included nohup (background execute) but it does not start at boot. need to manually execute; python /opt/home/keenetic-grafana-monitoring/keentic_influxdb_exporter.py Vitaliy's script #!/bin/sh [ "$1" != "start" ] && exit 0 nohup python /opt/home/keenetic-grafana-monitoring/keentic_influxdb_exporter.py >/dev/null 2>&1 &

Why is domain name not allowed for syslog server? It can also be done with the config of the syslog-ng entware package. Link In the Keenetic interface, I can only listen remotely if the server has a static ip. I can listen to my friend's syslog on tcp 514 port. I would like to write a 4th level domain instead of writing a static ip. Ex: entware * syslog-ng config In addition, why is it not stated in the interface and articles that these records can be sent to a remote location? All examples are given with local networks.

Why is this line which under DSL/PPPoE deleted? @AlexSP @Le ecureuil

If that's what you're talking about, I can't get past it by removing it. Is just restarting the solution?

Checked with e2fsck again while restarting my KN. Yes, partition re-appeared with same UUID. (so syslog is written to file in disk) Some reasons partition gets corrupted. OK. Just syslog send log to this disk. can it happen when too much log line arrives? Shouldn't it continue to work again when I plug it into KN after fixing it? Why doesn't it get proper journal or information without rebooting? @Le ecureuil

I really can't understand why. 😔 Part is corrupted. It doesn't show up when I fix it and mount into Keenetic. I can use the disk in Linux. @Le ecureuil

After fixing all, partition appear again. But when I mount into Keenetic, partition is not available.

10.101.0.1 Sep 21 10:46:27 10.101.0.1 kern info kernel scsi host2: usb-storage 1-2.4:1.0 10.101.0.1 Sep 21 10:46:28 10.101.0.1 kern info kernel scsi 2:0:0:0: Direct-Access TOSHIBA TransMemory 1.00 PQ: 0 ANSI: 2 10.101.0.1 Sep 21 10:46:28 10.101.0.1 kern info kernel sd 2:0:0:0: Attached scsi generic sg2 type 0 10.101.0.1 Sep 21 10:46:28 10.101.0.1 kern info kernel sd 2:0:0:0: [sdc] 7823296 512-byte logical blocks: (4.01 GB/3.73 GiB) 10.101.0.1 Sep 21 10:46:28 10.101.0.1 kern info kernel sd 2:0:0:0: [sdc] Write Protect is off 10.101.0.1 Sep 21 10:46:28 10.101.0.1 kern info kernel sd 2:0:0:0: [sdc] Mode Sense: 65 44 09 30 10.101.0.1 Sep 21 10:46:28 10.101.0.1 kern info kernel sd 2:0:0:0: [sdc] No Caching mode page found 10.101.0.1 Sep 21 10:46:28 10.101.0.1 kern info kernel sd 2:0:0:0: [sdc] Assuming drive cache: write through 10.101.0.1 Sep 21 10:46:28 10.101.0.1 kern info kernel sdc: sdc1 sdc2 10.101.0.1 Sep 21 10:46:28 10.101.0.1 kern info kernel sd 2:0:0:0: [sdc] Attached SCSI removable disk 10.101.0.1 Sep 21 10:46:28 10.101.0.1 user info ndm Storage::Manager: "Media2": enabled a disk spin down. 10.101.0.1 Sep 21 10:46:28 10.101.0.1 user info ndm Storage::Manager: created "Media2", port 2. 10.101.0.1 Sep 21 10:46:28 10.101.0.1 user err ndm Storage::Partition: a filesystem with the same label (TEMP, 144c8094-b6cc-4e2c-b39d-a5fe18b4948c) already mounted. 10.101.0.1 Sep 21 10:46:28 10.101.0.1 user err ndm Storage::Manager: "Media2": failed to create a new partition. 10.101.0.1 Sep 21 10:46:28 10.101.0.1 user crit ndm FileSystem::Directory: system failed [0xcffd00ec], unable to remove "/tmp/mnt/144c8094-b6cc-4e2c-b39d-a5fe18b4948c": directory not empty. 10.101.0.1 Sep 21 10:46:28 10.101.0.1 user info ndm Storage::Partition: swap "29bf1f34-afcb-4e89-b976-0e9033e236fe:": filesystem initialized. 10.101.0.1 Sep 21 10:46:28 10.101.0.1 kern info kernel Adding 780284k swap on /dev/sdc2. Priority:-1 extents:1 across:780284k

it is the gparted image after the situation in my message above while the disk is working. How can the partition be corrupted? The disk with exfat file system attached to peak DSL, which I use in the same way, has been working smoothly for more than 1 week. 🙄

According to these outputs, which one is the problem and the partition is lost. - disk (I tried a different disk this time) - writing syslog to disk - usb hub (but it still works for other usb opkg in the same hub.) - partitions (had the same issue with ext3 and ext4) @Le ecureuil

As an article this command make wan to lan in router mode. Is SFP port inclueded? https://help.keenetic.com/hc/en-us/articles/115005486085-Setting-up-the-WAN-port-as-a-LAN-port-in-KN-2610-KN-1810-KN-1010-KN-1910-and-KN-3010 I know SFP-Gigabit combo port. But SFP id is GigabitEthernet1/0. Since I don't have a router with an sfp port at the moment, I couldn't test it and be sure. interface Bridge0 include GigabitEthernet1 Does gigabit ethernet cover all? All for ISP 🙄 For example; "ISP": { "id": "GigabitEthernet1", "index": 1, "type": "GigabitEthernet", "description": "Broadband connection", "interface-name": "ISP", "port": { "id": "GigabitEthernet1/0", "index": 0, "interface-name": "0", "type": "Port", "link": "up", "auto-negotiation": "on", "speed": "100", "duplex": "full", "flow-control": "off", "transceiver": "internal", "sfp-combo": true "ISP-Vlan": { "id": "GigabitEthernet1/Vlan107", "index": 107, "type": "Vlan", "description": "Metronet TTNET", "interface-name": "ISP-Vlan", An another article said yes it is. https://help.keenetic.com/hc/en-us/articles/360000893880-Internet-connection-via-an-optical-fiber-link-SFP-module- So, can the SFP port connect to the mesh in AP mode? No need to even enter this command, right? As a result, in AP mode, all ports turn into Lan ports. Can I include it in the mesh with fiber or ethernet cable with my sfp module? I wrote this topic because I am very curious about the answer. thanks.

Thanks for answer. I prefer built-in solutions. I believe nextdns will be integrated into KeeneticOs. 🙏

Do kernel.warning messages indicate a serious problem? I've been seeing it in syslog for a long time. Device: Keenetic Peak DSL KN-2510 / OS: KeeneticOS 3.6.10 Stable Date Time Priority Hostname Message 09-19-2021 09:07:31 Kernel.Warning HIDE Sep 19 09:07:37 192.168.1.1 kernel: ra = 77880138 in libc.so[77850000+d2000] 09-19-2021 09:07:31 Kernel.Warning HIDE Sep 19 09:07:37 192.168.1.1 kernel: epc = 7787fb8c in libc.so[77850000+d2000] 09-19-2021 09:07:31 Kernel.Warning HIDE Sep 19 09:07:37 192.168.1.1 kernel: do_page_fault(): sending SIGSEGV to ntce_sink for invalid read access from 00000008