admin
-
Posts
308 -
Joined
-
Last visited
-
Days Won
115
Content Type
Profiles
Forums
Gallery
Downloads
Blogs
Events
Posts posted by admin
-
-
Release 4.3.4 (preview):
- IPv4: fixed "out of memory" error when creating an IP policy (reported by @Ponywka) [NDM-3907]
- IPv6: fixed inbound connections to SSH server (reported by @ru.celebi) [NDM-3891]
- IPv6: fixed inbound connections to VPN servers [NDM-3886]
- Kernel: removed excessive debug messages from ntc [SYS-1384]
- Web: added VLAN 802.1p settings to Ethernet Cable Connections (reported by @czerniewski) [NWI-3726]
- Web: fixed appearance of table row borders (reported by @AndreBA, @dimon27254) [NWI-4250, NWI-4299]
- Web: fixed color notations on the Traffic Monitor page (reported by @keenet07) [NWI-4243]
- Web: fixed device name display in WebCLI (reported by @qmxocynjca) [NWI-4240]
- Web: fixed minor issues with Mesh Wi-Fi system tile (reported by @dimon27254) [NWI-4275]
- Web: fixed saving of G.INP settings for ADSL [NWI-4270]
- Web: fixed saving of "TCP/UDP (all ports) and ICMP" forwarding rules [NWI-4253]
- Web: removed Users configuration description from "IKEv2/IPsec VPN server" page (reported by @project_fcc) [NWI-4245]
- Wi-Fi: fixed WPS when WPA2-Enterprise is enabled [SYS-1361]
- Wireguard: fixed AllowIPs validator to allow overlapping networks with a warning message (reported by @Александр Гольдварг) [NDM-3888]
- ZeroTier: removed repetitive "install accepted route" messages [NDM-3903]
-
3
-
Release 5.0 Alpha 4:
- Dns: fixed forwarding of negative responses to local clients at 127.0.0.1 (reported by @dchusovitin) [SYS-1382]
- Web: fixed appearance of table row borders (reported by @AndreBA) [NWI-4250]
- Web: fixed behavior of the menu items in expanded view (reported by @dimon27254) [NWI-4198]
- Web: fixed device name display in WebCLI (reported by @qmxocynjca) [NWI-4240]
- Web: fixed minor issues with Mesh Wi-Fi system tile (reported by @dimon27254) [NWI-4275]
- Web: fixed saving of "TCP/UDP (all ports) and ICMP" forwarding rules [NWI-4253]
-
2
-
Hi, you can do that. If you're having trouble turning on the Wi-Fi backhaul, please contact tech support in your country. Of course, 867 Mbit will be shared between backhaul and wireless devices on the same radio channel, so you will not get that much.
-
Release 4.3 Alpha 10.1:
- IPsec: fixed printing of redundant "vici client" log messages (reported by @Denis P) [NDM-3617]
- IP: fixed access to my.keenetic.net from the home network (reported by @Denis P) [NDM-3618]
- MWS: fixed password configuration on acquired Extenders [NDM-3619]
- NTCE: fixed "system failed [0xcffd0532], unable to write to control file" error (reported by @Denis P) [NDM-3614]
-
1
-
Release 4.3 Alpha 6.2:
- MWS: fixed Home segment configuration on Extenders (reported by @ru.celebi) [NDM-3578]
-
SFP: added quirks for GPON modules on KN-1012 [SYS-1248]:
- ODI DFP-34X-2I3
- ODI DFP-34X-2IY3
-
2
-
Release 4.3 Alpha 6.1:
- Core: fixed "interface mac address factory wan" setting (reported by @lighting) [NDM-3574]
- Wireguard: fixed connection uptime (reported by @spatiumstas) [NDM-3567]
-
2
-
Release 4.3 Alpha 3.1:
- NTC: fixed crash in the traffic shaper (reported by @dmroot) [SYS-1226]
-
1
-
On 10/3/2024 at 7:08 AM, Radyohead said:
switch to other node, than duration resets 0 because it shows the other node connection time. I dont need how long it is connected specific node. I need how long it is connected any node (all network). I believe the purpose of mesh system is to behave like one network.
Thanks for reporting; it's not supposed to be like this, and it can be fixed. The uptime indication is broken here so that a shorter time from the Wi-Fi association table overwrites the network-wide value.
It's too late to push any changes to the upcoming release 4.2.1, but the fix itself is trivial and will be released in 4.2.2 or so.
-
1
-
-
It is an operator's equipment issue. KeeneticOS has a feature that restarts the underlying ethernet port automatically after 5 PADO timeouts in a row. This feature is enabled by default.
You are welcome to share your ideas on how to improve it.
-
Keenetic has necessary firewall rules enabled by default so that you don't need to duplicate them manually, and therefore, it's secure by default. The provider's router does not add any extra isolation, nor does it break any existing Keenetic isolation. The provider's router is simply a part "provider" for Keenetic, which is, by default, an untrusted (public) network. Keenetic permits no incoming connections from the outside.
Keenetic segmentation adds security to your network so that if your IoT device is compromised, it will not allow access to other devices on another segment as long as they are isolated. And the ISP router in no way reduces security in this scenario.
-
1
-
-
Hi, security is enabled by default. It is based on so-called security levels. There are three security levels in KeeneticOS: private (default for Home segments), public (default for WAN connections), protected (default for Guest segment). You can get more information here: https://docs.keenetic.com/eu/carrier/kn-1713/en/22346-configuring-firewall-rules-from-the-command-line-interface.html
-
1
-
-
You may connect your Keenetic to the RMM service (https://support.keenetic.ru/eaeu/ultra/kn-1811/ru/31407-keenetic-remote-monitoring-and-management.html) and then subscribe to online/offline notifications in Telegram https://support.keenetic.ru/eaeu/ultra/kn-1811/ru/31412-telegram-notifications.html.
Another option would be to book a KeenDNS domain name (https://support.keenetic.ru/eaeu/ultra/kn-1811/ru/15881-domain-name.html ) and open access to your device's web interface (https://support.keenetic.ru/eaeu/ultra/kn-1811/ru/18524-changing-the-router-management-port.html). Remember to set a strong password. KeenDNS does not need a public IP address on the device, as it can tunnel your HTTPS traffic through the cloud. Then, you may configure a third-party service such as https://uptimerobot.com/ to check your device's uptime for free.
There are also options through the external package system to develop whatever you need using cron and shell scripts.
-
9 минут назад, oguzde сказал:
Hı
i want to install an openvpn server on my keenetic modem(Hero DSL) so i can connect through my home internet from my phone anywhere. i follow the openvpn server and client setup on keenetic user guide(https://help.keenetic.com/hc/en-us/articles/360000880359-OpenVPN-server-and-client) but it always gives error and cant connect. is there any other guide or someone to help ?
I'm afraid that no one can help based on the information you gave us.
The best option for you is to talk to Keenetic's official tech support, as they can professionally request all details about your error.
-
This is not implemented for IPv6.
Can you tell what address you expect in response to AAAA? IPv4 simply uses addresses from DHCP leases. IPv6, in contrast, has both SLAAC and DHCP (not enabled by default), and the addresses themselves are generated from multiple prefixes, which may be obtained from your ISP (multiple ISPs) and ULA.
(Suppose, you want to see ULA addresses since you asked about it.)
-
1 час назад, renne сказал:
How can we enable an IPv6 ULA prefix on the Hopper DSL including advertisement to the subnet?
To do that, use the "ipv6 local-prefix" command. The DHCPv6 server will slice it based on the subnet number and prefix length configured for the subnet, and use it along with the ISP's prefix.
- ipv6 local-prefix default — enable the default ULA prefix
- ipv6 local-prefix fd00:caba::/48 — set a specific ULA prefix
-
show ipv6 prefixes — view the available prefixes, for example
prefix:
prefix: 2a01:c23:XXXX::/48 <---- prefix from ISP
interface: PPPoE0
valid-lifetime: 251717
preferred-lifetime: 165317
global: yes
prefix:
prefix: fdf2:cc10:506a::/48 <---- ULA
interface:
valid-lifetime: infinite
preferred-lifetime: infinite
global: yes
-
5 часов назад, kiltum сказал:
Again.
After change main ip address of router extenders NO MORE works.
My reply was based on your initial descriptions of what you were trying to do to fix the problem.
22 часа назад, kiltum сказал:what i try:
- reset extenders by pressing reset button. indicator blinking for some seconds, and return to amber. after some time devices are switches to "dumb access point". Whey are visible in wifi, i can connect to them (by password on back) and get access to network by main router. but i cannot access to dashboard of "damaged switch"
and sure, no any sign in "Mesh Wi-Fi System" page
- turn switch to position A. they are start working as usual router, I can access them, configure, etc. I can even ask "reset to factory state" - all ok, they refreshed, I got initial startup wizard, etc... No extender mode, only router. For extender mode - turn switch
- return switch to position B - still no luck. no any sign of device. you can reset it again by button or repeat reset to factory from router mode - it does not matter. amber light and all
Now I has 7 "routers" and no extenders
None of those actions is helpful, because:
- reset by pressing the RESET button clears the Wi-Fi-system binding keys, so you have to acquire the extender again. To do that, however, you will have to erase it from the controller as well.
- turning the switch to A makes the device a router, but not an extender
- turning the switch back to B has no effect after pressing the RESET button, because (see above) the controller still remembers it under the old keys, so you have to erase it from the controller.
So, the only thing you need to do after steps 2,3 and changing the IP address of the home network, is to make the extender get a new IP address from the controller. The extender's DHCP client doesn't react quickly enough, because it waits for the lease to expire. (We can try to improve it later by sending a special command to extenders when changing the controller's IP address.) Anyway, if simple restarting of the extender (power off and on) doesn't help after steps 2,3, please file a bug report to our tech support and provide all the diagnostics they will ask for.
Apart from that, you can do the procedure another way:
1. Reset the controller to factory defaults.
2. Set the IP address you wanted initially.
3. Reset the extender devices to factory defaults and turn them to B mode (extender).
4. Connect them to the controller and acquire them, just like you did initially. -
After doing steps 1-3 you are not supposed to hard-reset the extenders, because this way you erase the binding keys, and you have to acquire the extenders again.
So, if your extenders do not appear after changing the IP address of the main router, just re-plug their ethernet cable or reboot them to let their DHCP client get an IP address from the new network.
-
1
-
-
Hi, sorry for that, we've had a deployment issue on the weekend, so it didn't go out for some devices. We are fixing it right now.
-
4
-
-
Please make sure the problem persists after upgrading to 4.0.5. Then address this issue with the official tech support. Be ready to provide the diagnostic files when they ask.
-
That's a mistakenly late-activated protection rule, previously intended to protect users from installation of Alpha 12. It is supposed to be active until at least tomorrow. The mechanism of these rules still clearly needs to be further developed for such cases. We apologize for the inconvenience.
-
3
-
1
-
-
2 часа назад, Lichtfunke сказал:
Good day, I have an issue with a decrease in speed. I've tried everything I knew and didn't know, and I decided to reach out for help.
I have two routers in my house. One is the main router located one floor below, connected to the internet, and it provides a speed of 60 Mbps. Everything is okay with it.
On top, I have your Speedster (KN-3010) router. It's connected wirelessly to the main router, and from there, a cable goes to my PC.
For the past two years, everything worked perfectly. Occasionally, I updated it once every six months without any problems. The speed was at its maximum, and everything was good.
However, a couple of days ago, I accessed the menu, and it showed version 3.9.2. I decided to update it to 4.0.4. After this update, the speed dropped from 60 Mbps to 8-11 Mbps.
I've been struggling with this issue for the past two days with no results. Could you please suggest what might be causing this problem? I'm running out of ideas.
Regarding the stable firmware, please send a report to support@keenetic.de. They will instruct you how to download the diagnostics file and help with further steps.
-
The current implementation of KeenDNS does not support direct IPv6. It resolves your KeenDNS name into the cloud IPv6 addresses only. The only option is to connect to the IPv6 address directly without HTTPS. The Web interface is accessible by IPv6 in version 4.0 only, so please upgrade your device to 4.0 (Preview).
-
1
-
-
Hi, this is not a "Dev channel issue", please continue communicating with the official tech support.
-
@roman_sh: thanks for reporting! The bug will be fixed in the next releases.
Changelog 5.0
in Changelog
Posted
Release 5.0 Alpha 5: