KYTECHNGAMING
-
Posts
641 -
Joined
-
Last visited
-
Days Won
3
Content Type
Profiles
Forums
Gallery
Downloads
Blogs
Events
Posts posted by KYTECHNGAMING
-
-
12 minutes ago, Alexander Titov said:
Absolutely agree with you. That’s strange design’s decision.
https://prnt.sc/lKft3JN2-M-L https://prnt.sc/df8AQIVuwQMb
Because I use it this way on my other device. This is for local network only.
-
1
-
-
Hello there,
When I want to send many files to disk in the file browser, there is no scroll bar on the page that opens.
It causes the progress not to display properly.the other is that the new PPPOE button in the mobile browser does not fit in Turkish.
-
1
-
-
21 minutes ago, Alexander Titov said:
Did you sharpen heat sink near an antenna?
Yeah. I disassembled a heatsink. In this photo, the module was not fully inserted.
If I used the Keenetic upright and rotated the antenna it would be fine. That's why I made the heatsinks that way. But my plan has changed.
However, I wish the sfp input and antenna weren't so close by design. -
On 8/15/2021 at 12:59 AM, Le ecureuil said:
Thanks, we are working on this.
Hello,
This issue may not have been fixed.Keenetic_DATA - f3cff6b6-fe95-d701-0085-f6b6fe95d701
Keenetic_Data - 4b6ce681-0d37-442e-82fb-c9c89b3cf249I wanted to change disk.
I'll use the one starting with 4b instead of the one starting with f3. I inserted both disks into the Keenetic. I also removed the disks from SMB beforehand.I authorize access to disks. One is not accepted.
SpoilerAug 10 11:45:31 ndm
Cifs::ServerTsmb: share record "Keenetic_DATA" already exists.
Aug 10 11:45:31 ndm
Cifs::ServerTsmb: share record "Keenetic_DATA" already exists.
Aug 10 11:45:31 ndm
Cifs::ServerTsmb: failed to automount "f3cff6b6-fe95-d701-0085-f6b6fe95d701:", ignored.
Aug 10 11:45:31 ndm
Cifs::ServerTsmb: skip "f3cff6b6-fe95-d701-0085-f6b6fe95d701:".
Aug 10 11:45:31 ndm
Cifs::ServerTsmb: automount enabled.
Aug 10 11:45:31 ndm
Cifs::ServerTsmb: permissive mode disabled.
Aug 10 11:45:31 ndm
Core::System::StartupConfig: saving (http/rci).
Aug 10 11:45:32 kernel
TSMB module stopped.Image of the two disks in the interface:
Screen Record: https://disk.yandex.com.tr/i/qXclBGqGC-gM6w
-
9 minutes ago, vst said:
@KYTECHNGAMING I can see that with your settings a modem can't even connect to the network. Maybe it's because certain bands are disabled.
Does the modem connect if you activate pdp ipv4?
It's because it's a twin sim card. So the other sim card was active.
Otherwise, I don't have a connection problem.When I took the self-test, it had ip. After 30 seconds, I saw that it was broken. As I said in my first sentence, because of the twin sim card.
When available, I can try with only one sim card active.3g bands are inefficient in Türkiye and even do not receive data. That's why the bands that I can use are selected. I checked with cellmapper before.
-
58 minutes ago, Роман Шевелуев said:
Good afternoon! Regarding the temperature of the SFP module: I switched to PEAK, the temperature dropped noticeably (still measured by hand). Maybe the counterpart in PEAK is different, or maybe the ventilation inside its case is better and there is more space.
In the meantime, I'm starting to think that the passive cooling of the module inside the router is a very interesting topic.
KN-1011 - ODI and Carlitoxx
https://prnt.sc/bRbujWhnsq9n-
1
-
-
On 2/21/2022 at 9:10 AM, vasek00 said:
KN1011
[I] Jan 1 00:00:03 kernel: mtd: creating 17 MTD partitions on "MT7621-NAND": [I] Jan 1 00:00:03 kernel: 0x000000000000-0x000000080000 : "U-Boot" [I] Jan 1 00:00:03 kernel: 0x000000080000-0x000000100000 : "U-Config" [I] Jan 1 00:00:03 kernel: 0x000000100000-0x000000180000 : "RF-EEPROM" [I] Jan 1 00:00:03 kernel: 0x000000180000-0x000000340000 : "Kernel_1" [I] Jan 1 00:00:03 kernel: 0x000000340000-0x000002bc0000 : "RootFS_1" [I] Jan 1 00:00:03 kernel: mtd: device 4 (RootFS_1) set to be root filesystem [I] Jan 1 00:00:03 kernel: 0x000000180000-0x000002bc0000 : "Firmware_1" [I] Jan 1 00:00:03 kernel: 0x000002bc0000-0x000002dc0000 : "Config_1" [I] Jan 1 00:00:03 kernel: 0x000002dc0000-0x000002fc0000 : "Storage_Legacy" [I] Jan 1 00:00:03 kernel: 0x000002fc0000-0x000003000000 : "Dump" [I] Jan 1 00:00:03 kernel: 0x000003000000-0x000003fc0000 : "Storage_A" [I] Jan 1 00:00:03 kernel: 0x000003fc0000-0x000004040000 : "U-State" [I] Jan 1 00:00:03 kernel: 0x000004040000-0x0000040c0000 : "U-Config_res" [I] Jan 1 00:00:03 kernel: 0x0000040c0000-0x000004140000 : "RF-EEPROM_res" [I] Jan 1 00:00:03 kernel: 0x000004140000-0x000006b80000 : "Firmware_2" [I] Jan 1 00:00:03 kernel: 0x000006b80000-0x000006d80000 : "Config_2" [I] Jan 1 00:00:03 kernel: 0x000006d80000-0x000007f80000 : "Storage_B" [I] Jan 1 00:00:03 kernel: 0x000000000000-0x000007f80000 : "Full" [I] Jan 1 00:00:07 kernel: Searching for suitable storage partitions... [I] Jan 1 00:00:07 kernel: Found 1st storage partition of size 16515072 bytes [I] Jan 1 00:00:07 kernel: Found 2nd storage partition of size 18874368 bytes [I] Jan 1 00:00:07 kernel: Registering UBI data partitions parser [W] Jan 1 00:00:07 kernel: Concatenating MTD devices: [W] Jan 1 00:00:07 kernel: (0): "Storage_A" [W] Jan 1 00:00:07 kernel: (1): "Storage_B" [W] Jan 1 00:00:07 kernel: into device "NDM combined UBI partition" [I] Jan 1 00:00:07 kernel: 1 ndmubipart partitions found on MTD device NDM combined UBI partition [I] Jan 1 00:00:07 kernel: mtd: creating 1 MTD partitions on "NDM combined UBI partition": [I] Jan 1 00:00:07 kernel: 0x000000000000-0x0000021c0000 : "Storage" [I] Jan 1 00:00:07 kernel: Merging storage partitions OK [W] Jan 1 03:00:11 kernel: ubi0: attaching mtd17 [W] Jan 1 03:00:11 kernel: ubi0: scanning is finished [W] Jan 1 03:00:11 kernel: ubi0: attached mtd17 (name "Storage", size 33 MiB) [W] Jan 1 03:00:11 kernel: ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes [W] Jan 1 03:00:11 kernel: ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 2048 [W] Jan 1 03:00:11 kernel: ubi0: VID header offset: 2048 (aligned 2048), data offset: 4096 [W] Jan 1 03:00:11 kernel: ubi0: good PEBs: 270, bad PEBs: 0, corrupted PEBs: 0 [W] Jan 1 03:00:11 kernel: ubi0: user volume: 1, internal volumes: 1, max. volumes count: 128 [W] Jan 1 03:00:11 kernel: ubi0: max/mean erase counter: 2/1, WL threshold: 2048, image sequence number: 4028866988 [W] Jan 1 03:00:11 kernel: ubi0: available PEBs: 0, total reserved PEBs: 270, PEBs reserved for bad PEB handling: 7 [W] Jan 1 03:00:11 kernel: ubi0: background thread "ubi_bgt0d" started, PID 549 [W] Jan 1 03:00:11 kernel: UBIFS (ubi0:0): background thread "ubifs_bgt0_0" started, PID 551 [W] Jan 1 03:00:11 kernel: UBIFS (ubi0:0): UBIFS: mounted UBI device 0, volume 0, name "storage" [W] Jan 1 03:00:11 kernel: UBIFS (ubi0:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes [W] Jan 1 03:00:11 kernel: UBIFS (ubi0:0): FS size: 31617024 bytes (30 MiB, 249 LEBs), journal size 1523712 bytes (1 MiB, 12 LEBs) [W] Jan 1 03:00:11 kernel: UBIFS (ubi0:0): reserved for root: 1493350 bytes (1458 KiB) [W] Jan 1 03:00:11 kernel: UBIFS (ubi0:0): media format: w4/r0 (latest is w4/r0), UUID 10........04, small LPT modelOr KN1810
[I] Jan 1 00:00:04 kernel: mtd: creating 17 MTD partitions on "MT7621-NAND": [I] Jan 1 00:00:04 kernel: 0x000000000000-0x000000080000 : "U-Boot" [I] Jan 1 00:00:04 kernel: 0x000000080000-0x000000100000 : "U-Config" [I] Jan 1 00:00:04 kernel: 0x000000100000-0x000000180000 : "RF-EEPROM" [I] Jan 1 00:00:04 kernel: 0x000000180000-0x000000360000 : "Kernel_1" [I] Jan 1 00:00:04 kernel: 0x000000360000-0x000001d40000 : "RootFS_1" [I] Jan 1 00:00:04 kernel: mtd: device 4 (RootFS_1) set to be root filesystem [I] Jan 1 00:00:04 kernel: 0x000000180000-0x000001d40000 : "Firmware_1" [I] Jan 1 00:00:04 kernel: 0x000001d40000-0x000001dc0000 : "Config_1" [I] Jan 1 00:00:04 kernel: 0x000001dc0000-0x000001fc0000 : "Storage_Legacy" [I] Jan 1 00:00:04 kernel: 0x000001fc0000-0x000002000000 : "Dump" [I] Jan 1 00:00:04 kernel: 0x000002000000-0x000003fc0000 : "Storage_A" [I] Jan 1 00:00:04 kernel: 0x000003fc0000-0x000004040000 : "U-State" [I] Jan 1 00:00:04 kernel: 0x000004040000-0x0000040c0000 : "U-Config_res" [I] Jan 1 00:00:04 kernel: 0x0000040c0000-0x000004140000 : "RF-EEPROM_res" [I] Jan 1 00:00:04 kernel: 0x000004140000-0x000005d00000 : "Firmware_2" [I] Jan 1 00:00:04 kernel: 0x000005d00000-0x000005d80000 : "Config_2" [I] Jan 1 00:00:04 kernel: 0x000005d80000-0x000007f80000 : "Storage_B" [I] Jan 1 00:00:04 kernel: 0x000000000000-0x000007f80000 : "Full" [I] Jan 1 00:00:07 kernel: Searching for suitable storage partitions... [I] Jan 1 00:00:07 kernel: Found 1st storage partition of size 33292288 bytes [I] Jan 1 00:00:07 kernel: Found 2nd storage partition of size 35651584 bytes [I] Jan 1 00:00:07 kernel: Registering UBI data partitions parser [W] Jan 1 00:00:07 kernel: Concatenating MTD devices: [W] Jan 1 00:00:07 kernel: (0): "Storage_A" [W] Jan 1 00:00:07 kernel: (1): "Storage_B" [W] Jan 1 00:00:07 kernel: into device "NDM combined UBI partition" [I] Jan 1 00:00:07 kernel: 1 ndmubipart partitions found on MTD device NDM combined UBI partition [I] Jan 1 00:00:07 kernel: mtd: creating 1 MTD partitions on "NDM combined UBI partition": [I] Jan 1 00:00:07 kernel: 0x000000000000-0x0000041c0000 : "Storage" [I] Jan 1 00:00:07 kernel: Merging storage partitions OK [W] Jan 1 03:00:11 kernel: ubi0: attaching mtd17 [W] Jan 1 03:00:12 kernel: ubi0: scanning is finished [W] Jan 1 03:00:12 kernel: ubi0: attached mtd17 (name "Storage", size 65 MiB) [W] Jan 1 03:00:12 kernel: ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes [W] Jan 1 03:00:12 kernel: ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 2048 [W] Jan 1 03:00:12 kernel: ubi0: VID header offset: 2048 (aligned 2048), data offset: 4096 [W] Jan 1 03:00:12 kernel: ubi0: good PEBs: 525, bad PEBs: 1, corrupted PEBs: 0 [W] Jan 1 03:00:12 kernel: ubi0: user volume: 1, internal volumes: 1, max. volumes count: 128 [W] Jan 1 03:00:12 kernel: ubi0: max/mean erase counter: 2/1, WL threshold: 2048, image sequence number: 876655129 [W] Jan 1 03:00:12 kernel: ubi0: available PEBs: 0, total reserved PEBs: 525, PEBs reserved for bad PEB handling: 12 [W] Jan 1 03:00:12 kernel: ubi0: background thread "ubi_bgt0d" started, PID 545 [W] Jan 1 03:00:12 kernel: UBIFS (ubi0:0): background thread "ubifs_bgt0_0" started, PID 547 [W] Jan 1 03:00:12 kernel: UBIFS (ubi0:0): UBIFS: mounted UBI device 0, volume 0, name "storage" [W] Jan 1 03:00:12 kernel: UBIFS (ubi0:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes [W] Jan 1 03:00:12 kernel: UBIFS (ubi0:0): FS size: 63361024 bytes (60 MiB, 499 LEBs), journal size 3174400 bytes (3 MiB, 25 LEBs) [W] Jan 1 03:00:12 kernel: UBIFS (ubi0:0): reserved for root: 2992697 bytes (2922 KiB) [W] Jan 1 03:00:12 kernel: UBIFS (ubi0:0): media format: w4/r0 (latest is w4/r0), UUID 5A.....59, small LPT modelThe question for this model of the KN1011 router will remain the size of storage = 33Mib but in real life
/dev/ubi0_0 27868 24 26388 0% /storageKN-1011: https://prnt.sc/KnagJ8CnQXE3
KN-2510: https://prnt.sc/y-ZA-0FIGGIe
-
1
-
-
Everything seems to be fine with 3.9.a.5. @Julia Rybakova
-
4 hours ago, vst said:
@KYTECHNGAMINGPlease share a self-test file. Are you sure that your mobile operator supports IPv6?
Please verify that your UsbQmi0 configuration contains the following:
Hello,
I'm not sure my provider supports ipv6.
I wanted to enable ipv6 and see results. but I observed that the button does not register.
I re-entered the commands in webcli. an ipv6 address was not obtained as a result. Self-test will be forwarded in the next message. -
Hello,
I am doing the PPPOE information test of different Keenetic models with different routers.
In the Hero KN-1011 model, information is received on the interface, but the window does not close. For this reason, you cannot save the received information.
My ticket number about the results of other tests: 591186
-
I noticed that with KeeneticOS 3.9.a.5, Ipv6 is not activated in modem settings.
I entered the commands with the CLI.
I can't see any sign that it's active again in the interface. https://prnt.sc/snKQbeRh4gHT
The button is not selected. Also, there is no line about ipv6 under ipv4 in the dashboard. If the rope is not provided; it may not come out. I do not know this. https://prnt.sc/rg4mHtgcpMcg -
On 7/24/2022 at 10:28 PM, LexBart said:
The problem was still there, but I think I understood what was the reason.
Ports on which mesh repeaters were connected were not included in the segment with vlan "T"
Perhaps the vehicle also had some confusion with segment and vlan connectors
-
30 minutes ago, Julia Rybakova said:
Hej!
Is it actual now?
The reason for the problem of not receiving sms in Runner 4G, 3.9.a versions has been changed to 3.8.3 version. It appears online in RMM.
But this time another network has gone offline. Keenetic Hero with KeeneticOS 3.9.a.4. I noticed it in version 3.9.a.3 too. But after a while, it became online by itself.
-
Clear browser's cookie.
-
1 hour ago, Ahmed Ensar said:
Wifi ye bağlanan windows cihaz yokki evde hepsi telefon
You can see bssid on your phone with various Wi-Fi analyzer programs.
-
With the 3.9.a.2 update on the Runner 4g model and now the 3.9.a.3 update on my Hero model, my networks appear offline in RMM.
Also, I am currently using 3.8.x version because I have sms problem in Runenr 4G. However, KeenDNS addresses were also encountering 502 Bad Gateway errors.
-
bssid and mac address are slightly different.
Enter the following command in CMD while connected to whichever device you need bssid. (Omni DSL)
netsh wlan show networks mode=Bssid
-
Hello,
I cannot exit the "event log" page when viewing RMM from my mobile phone.
When I do it back, it returns to another page I opened before rmm. -
5Ghz
interface WifiMaster1/WifiStation0 mac bssid baglanacakcihazinbssidsi
2.4 Ghz
interface WifiMaster0/WifiStation0 mac bssid omnidslbssid
Just enter the command for 2.4ghz on the Lite-1 device. Because your devices only have 2.4ghz AP.
-
On 7/21/2022 at 6:34 PM, Yakotik said:
Could be very useful to include the feature to make that the keenetic. Routers with SFP/SFP+ ports be able to do sequential Single-Byte reads to obtain the transceiver specs and ddm from the EEPROM tables A0h/A2h for transceivers like GPON ONU SFP and others than only supports Single-Byte Reads and not multi-bytes reads (255 Bytes read per call).
Some of this transceivers doesn't have connected the two-wire interface SFP pins directly to the EEPROM, They have connected the 2-wire interface to a slave i2c interface of the SoC and then the SoC have a master i2c connection to the EEPROM.
in other cases the transceiver doesn't have a physically EEPROM and use a virtualized EEPROM allocated on the SPI Flash chip that comes available after the embedded OS is booted.
Implementing the detection of the EEPROM reads to switch automatically between Single-Byte and Multi-Byte reads should not so complex and will gives a plus in the interoperability between the different brands and models of SFP Transceivers apart of to make complies the SFF-8431I asked these questions a long time ago with the advice of the manufacturer Carlitoxx.
-
1
-
-
Wouldn't it be nice if new components in KeeneticOS versions had a sign next to them?
If the HTTP(S)/SOCK proxy that came with 3.9.A.1 looked like this, I would have noticed it more quickly.
-
3
-
-
3.9.A.1
When closing the window in the device setting, the gui looks like this for 1-2 seconds.
-
1
-
-
-
27 minutes ago, Twilight said:
Hello Keenetic Support,
almost 10 years I've been using Buffalo WZR-600DHP. Last month I thought it would be a wise move to upgrade my home network and switch to a reliable solution as my old buffalo after all that time might be fail prone. Kn-1011 seemed like obvious choice and I was happy to buy and install it.
All nice and shiny it didn't last even a week and today right in the middle of the work call I lost my wifi (both 2.4 and 5 Ghz connectivity).
After router reload I got:
"The maximum number of wireless networks has been reached. To assign a wireless network, remove an existing wireless network in another segment."for the both wireless interfaces.Revert to default settings fixed nothing.Is it a sign of a new keenetic "quality" or what? Is it still possible to fix it and what's probability I'll face this nonsense again?Should I return it to the store tomorrow and forget about "the most reliable SOHO solution on the market"?I guess it's a hardware failure. 😟 I've heard it 1-2 times before on another model. RD will support you.
-
1
-
Reset, Wizard: Downgrade forced?
in Dev channel issues & test reports
Posted
when you exit the wizard, it stays in the version it should be.
I did not understand why an experienced person is so stuck in this situation in the installation with the wizard. Or I don't quite understand what you want to say.
Could it be a solution to remove the initial wizard component?