ru.celebi

Does this feature really work? If it does, what format should be used for DoQ and DoH/3 specifically with NextDNS or AdGuard DNS?

Here’s the issue I’m facing: When clients on the network are not registered, their traffic is displayed collectively under a single entry as "unregistered clients." For example, if there are 20 unregistered clients, the total traffic shown might be 10GB, but it’s impossible to determine how much data each individual device has used. The feature to automatically register new clients is useful, but over time, hundreds of device records accumulate, which becomes unmanageable. A potential solution would be to enable the automatic registration of new clients while clearing the list of auto-registered clients whenever the Keenetic device restarts.

Currently, the router interface has an automatic device registration feature that solves the issue of unregistered clients. However, there are some challenges with the current implementation: Accumulation of Registered Devices: Over time, hundreds of registered devices accumulate in the list, making it difficult to manage. For instance, I recently deleted over 500 automatically registered clients from a router used in a corporate environment. While it's possible to clear these devices by modifying the startup-config file in one go, this would require restarting the router. Proposed Solution: After a router restart, the registered device list should be cleared automatically. Only devices that reconnect after the restart should be re-registered. This approach would keep the list clean and manageable while ensuring only actively connected devices remain registered. Unnecessary Details in Registered Device Names: When devices are automatically registered, their names include unnecessary details like the date and time of registration, which makes the list cluttered and difficult to read. Proposed Solution: Allow users to customize the naming format for automatically registered devices. Options could include: A user-defined prefix (e.g., "unregistered_"). The device’s name (if available). The device’s MAC address (if no name is available). This flexibility would make the list more organized and user-friendly. By implementing these improvements, the device registration process can be made significantly more efficient and easier to manage for end users.

Yes. However, this error does not occur when connecting from the local network.

Unpatched problem may persist? Because I use 4.3.A10.1.

The drive size appears normal on my home computer, exactly as it should be. However, on the work computer, it looks like it does in the picture. The file size doesn't matter; the same issue occurs with files of different sizes. I think third-party software is needed for this, as there seem to be no problems with them. However, I’m still curious about the cause of this error; ndm: Core::Scgi::Session: unsupported method "PROPFIND" for "/".

Hello all, I have added a WebDAV drive on Windows, but the drive size appears identical to my system drive, which seems incorrect. When I try to copy a file from the WebDAV drive, I get an error saying, "The file size exceeds the limit allowed." After some attempts to troubleshoot, the WebDAV folder became unresponsive, and my router ended up banning me. Could this be a bug, or am I missing something? The following log entry frequently appears. I researched this error a bit and learned that it might be related to the WebDAV server. ndm: Core::Scgi::Session: unsupported method "PROPFIND" for "/". ndm: Netfilter::Util::Conntrack: flushed 131 IPv4 connections for 212.175.X.X Netfilter::Lockout::Manager: "Http": ban remote host 212.175.X.X for 15 minutes.

If you are using PPPoE, you should disable these settings.

If no custom DNS addresses are entered for the clients, all devices will broadcast with the name set on the router. However, if a different name is desired, the custom DNS address must be set on the individual client. In this scenario, you cannot assign different profiles on a client-by-client basis using the profile set on the router; all devices will use the same profile. However, if you enter the details of a different profile on the client, it will work with that profile.

The cloud-based content filtering and ad blocking component is not installed on my device. I use it as shown in the image. I've never experienced the problem you mentioned.

In version 4.3.A9, the System Settings menu cannot be accessed. Manually navigating to /system via the URL also does not resolve the issue.

Are the suggestions we submit taken into consideration, or is it just a waste of time? If they are evaluated, where are the results published? For example, what happened with my specific request?

I’m not asking for the ability to add or remove components without a reboot. I simply want the system to allow me to choose when to reboot after adding or removing a component, rather than forcing an immediate reboot.

Hello, When adding or removing a component on the router, the system automatically restarts immediately after the process. This can cause interruptions, especially during times when an active internet connection is critical. A more user-friendly solution, similar to modern operating systems like Windows, could be implemented: "Restart Now" or "Restart Later" options: Allow users to manually trigger the restart after completing their tasks. Active hours setting: Schedule automatic restarts during specific time periods (e.g., nighttime). Partial configuration application: Enable configurations that don’t require a restart to take effect immediately. Such a feature would significantly enhance the user experience and help ensure uninterrupted internet connectivity. I hope you consider this suggestion and look forward to seeing if it can be implemented in future updates. Thank you!

This morning, I tried 4.3.A6.1, but the issue persists.

@eralde Is there any progress on this issue? Client devices are unable to obtain an IP address from Buddy6 with A6

Edit: With the A6 update, clients connected to Buddy6 are not receiving IP addresses. We temporarily resolved the issue by downgrading to the A5 version.

After updating to version 4.3 Alpha 6, I noticed the following issues: The Buddy 6 mesh device does not display the settings for the Home segment. The Hero mesh device shows the Home segment settings as locked, which seems to be a bug. Additionally, since our mesh device might be operating in wired mode, it should be possible to adjust the 2.4GHz channel independently from the controller. Greetings from Türkiye, together with @KYTECHNGAMING

Ohh. That's great ^^

Hello. I'm getting a warning or error like the one below with yellow text. Does anyone know what this is? [W] Nov 14 08:16:33 kernel: nf_conntrack: public connections unlocked [W] Nov 14 08:16:40 kernel: nf_conntrack: lockout threshold reached (4294967290), public connections locked for 600 s

I would like to bring to your attention an issue regarding the speed graph displayed on the interface. Currently, the units are incorrectly represented as follows: The graph shows kbit units as Mbit, and Mbit units as Gbit. The following values are also incorrectly labeled: Download: 4.69 Gbit/s Upload: 281 Mbit/s Received: 94.7 TB Sent: 6.61 TB This discrepancy may lead to confusion for users trying to interpret the speed data accurately. I recommend correcting the unit displays to ensure clarity.

I don't need it, it just looks nice Alignments and appearance are always important.

What I mean is that there are differences in the output screens of the two versions. The properly formatted one is v4.1.7, but in v4.2.1, only the QR code, name, and password are displayed. There's no alignment. The 'Keenetic' text and the information message are also missing.

The visual difference between v4.1.7 and v4.2.1 when printing WiFi information is noticeable. I believe the new version is incorrect. for v4.1.7 for v4.2.1

Hello to all. I play an MMORPG game called Silkroad Online. This game has a significant number of players, especially in Turkey and Russia. However, there is a limitation in the game: only two characters can be logged in at the same time per IP address. The only way to bypass this is by connecting to the game through a proxy. However, most proxy servers sold on the market are either banned or datacenter accounts, and these addresses cannot connect to the game. What we need are IP addresses used by home users. In this case, we need to set up a SOCKS5-supported proxy server from home. However, I have no doubt that Keenetic can easily run a simple SOCKS5 server. I'm confident that once the gaming community hears about this feature, more people will purchase Keenetic products. Perhaps it's not a protocol that's widely used anymore, but a feature is still a feature