Leaderboard

Request: The user should not change the type of the port used for the mesh or the warning must be added. Today I met a user scenario. It was completely inexperienced. There is a Keenetic cable mesh system and there was a change of ISP. The user has chosen the ethernet port (Port 1) that be mesh with the cable as a provider. (Actually, it is enough to change the existing provider (port 0) that only PPPOE information.) After that, problem is occured. He removed it from the interface, but the mesh did not continue as a cable. When Backhaul activated it, mesh continued via wireless. When I looked at the Running-Config, there were outputs that were not in the interface but were configuated. And this was integrated with the Wan (Gigabitethernet1) connection. Sağlayıcı 2 is not visible in the interface. Starting with 10.160.xx.yy IP is for IpoE. (ONT without pppoe) Instead of cleaning the crumbs with the command, I created a provider in the interface again, and I chose the port default. Then I deleted this interface. Mesh was active again via cable. (I removed extender before, so I added it again.) I'm adding the self-test that I have taken to the next message after I follow these steps. I hope it's not wrong and you can catch the situation. @eralde @Le ecureuil

Yes, thank you! This will be fixed in one of the future versions. That is a separate issue (both the KeenDNS name/icon alignment and the spacing in the clients table have the same underlying cause). It also will be fixed

Thank you for your kind reminder. In this context, I wanted to re-upload the relevant screenshots. It seems like the issue occurs on Edge, while everything looks normal on Firefox. Some of the lines are missing. The menus I could identify are 'Registered Clients,' 'IPv6 Route Table,' and 'System Files.' Additionally, with the latest version 4.3.B4, the spacing between client entries has increased. Maybe you could use this space to display clients' IPv6 addresses as well. Sounds like a great idea, doesn’t it? Firefox: Edge: Another issue was that the address field next to the KeenDNS name is not perfectly aligned. For someone like me, who has a thing for symmetry, this is quite annoying!

@ru.celebi thank you for the report! It would be better if you don't hide the posts you publish here. If you don't want to include personal information (e.g. device names / IP addresses / MAC addresses) in your screenshots – blur them out before uploading the images. Firstly, this way you won't post two identical posts, and secondly, if your posts are visible, other users will also be able to check if they have the same problem. Thanks again for reporting the problems

Release 4.3 Beta 4 (preview): IGMP: fixed multicast forwarding to IPTV ports [NDM-3767] IPsec: fixed adding route to client network on L2TP/IPsec server [NDM-3758] NTCE: fixed "system failed [0xcffd00bd]" error when saving filtering profiles (reported by @dimon27254) [NDM-3770] Web: fixed mandatory password input when creating a user for OPKG and applications (reported by @spatiumstas) [NWI-3700] Web: fixed tooltip behaviour on Mesh Wi-Fi system card [NWI-4062] Wi-Fi: fixed configuration of channel width [NDM-3764] Wi-Fi: fixed connection issues with Intel AC9260/9560 adapters in WPA3 PSK mode [SYS-1325]

Release 4.3 Beta 3 (preview): DNS: fixed "duplicate key: group" error when using FQDN object groups (reported by @dimon27254) [NDM-3755] HTTP: implemented blacklisting of remote hosts sending invalid POST requests [NDM-3716] NTCE: fixed "detected 5 attributes, only 4 supported" error (reported by @Strider78) [NDM-3756] OpenConnect: fixed User-Agent header when using "anyconnect" protocol [NDM-3733] SSTP: fixed access to SSTP VPN server when "ip http security-level private" is set [NDM-3747] USB: added support for Telit FN990 modem [NDM-3743] VPN: fixed WireGuard and OpenVPN port collision when creating tunnels [NDM-3732] Web: changed view of Connection Policies on mobile screens (reported by @dimon27254) [NWI-4049] Web: fixed display of SFP/Ethernet combo port connection mode (reported by @Gim12) [NWI-3319] Web: fixed opening Mesh Wi-Fi System page after a new Extender is acquired (reported by @KYTECHNGAMING) [NDM-3757] Web: fixed the inability to turn on the Ethernet port after it has been turned off [NWI-4066] Web: fixed unwanted reset of PPPoE authentication settings when selecting "Automatic (DHCP)" option (reported by @Leshiyart) [NWI-4065] Web: increased the number of visible options in drop-down lists (reported by @spatiumstas) [NWI-3756] Wi-Fi: fixed connection instability for some wireless client devices when "target-waketime" setting is enabled [SYS-1266] Wireguard: fixed losing "asc" settings after reconfiguration (reported by @FLK) [SYS-1320]

Release 4.3 Beta 2 (preview): DNS: implemented subdomain resolution in "object-group fqdn" (reported by @avn) [NDM-3726] HTTP: fixed Cookie handling and related "Core::Scgi::Tools: bad request: no session" error during authorization (reported by @snark) [NDM-3713] HTTP: fixed missing static DNS records when "ip http proxy dns-override" is enabled (reported by @Leshiyart) [NDM-3718] IPv6: fixed 6in4 tunnel performance when hardware packet engine is enabled [SYS-1271] OpenSSL: updated to 3.3.3 [SYS-1306] Proxy: fixed resetting of interface counters when it is shut down (reported by @keenet07) [NDM-3724] SFP: fixed KN-1012 compatibility with RTL9601D-based SFP modules [SYS-1313] Web: fixed redundant warning about unsaved changes during firmware upgrade (reported by @dimon27254) [NWI-3944] Web: fixed showing a scroll-bar when dragging objects in the connection priority list (reported by @dimon27254) [NWI-4044] Web: fixed showing an alert about unset password when it's already set (reported by @dimon27254) [NWI-4033] Web: fixed status showing not inserted SIM card on the dashboard (reported by @spatiumstas) [NWI-4016] Web: fixed tooltip readability in the Application Traffic Analyser table (reported by @dimon27254) [NWI-4020] Web: fixed unexpected second reboot after a system update (reported by @spatiumstas) [NWI-4047] Web: fixed Wi-Fi network shutdown despite canceling this action in a pop-up dialog box (reported by @dimon27254) [NWI-4010] Web: improved appearance of the side menu [NWI-3839] Web: locked the LTE signal metrics button when no connection is established (reported by @spatiumstas) [NWI-4015] Web: redesigned password input field with indication of password strength [NWI-4030]

You can check the signal levels in the device web UI. It works in a mobile browser. To access the web UI you can use http://my.keenetic.net while your phone is connected to Wi-Fi or a KeenDNS name you chose. The signal levels dialog will look like that: And it has a block with info about antennas: