Leaderboard

Now, both on the http://192.168.1.1/wifi-monitor/utilization tab and on the widget, you can alternately view the load of the selected channel, i.e. choosing either 2.4 GHz or 5 GHz. I would like to be able to view both ranges simultaneously, both on the widget and on the tab!!!

Please consider adding a "Reboot" button next to the existing Edit and Remove buttons in the mesh device management interface. Currently, restarting a mesh node requires logging into each device separately, which is inefficient and time-consuming. Suggested Placement: [Update] [Edit] [Remove] [Reboot] This addition would make it much easier to manage and restart mesh nodes directly from the controller interface.

Release 4.3.1 (preview): DynDNS: fixed saving of 'dyndns nobind' setting [NDM-3816] HTTP: fixed redundant disclosure device information [NDM-3783]: CVE-2024-4021 CVE-2024-4022 IP: fixed applying static routes in multiple IP policies [NDM-3814] IP: fixed assignment of "conform" policy after automatic client registration [NDM-3810] IPsec: fixed wrong "crypto map" use in L2TP/IPSec server settings [NDM-3811] OpenConnect: added random padding to packets to improve connection resistance (reported by @dimon27254) [NDM-3791] OpenConnect: fixed access to the VPN server's attached network [NDM-3820] TSMB: enabled support for extended attributes (reported by @dimon27254) [NDM-3645] VPN: added 'session-logout' command to terminate VPN sessions (reported by @CBLoner) [NDM-3788]: crypto map l2tp-server session-logout {session} crypto map virtual-ip session-logout {session} sstp-server session-logout {session} vpn-server session-logout {session} oc-server session-logout {session} Web: added "https://" to OpenConnect VPN server URI when camouflage is enabled [NWI-4146] Web: added alphabetical sorting to Policy Bindings [NWI-4092] Web: fixed various bugs and layout issues on different screen sizes (reported by @dimon27254, @spatiumstas, @enterfaza, @FLK, @mrGhotius) [NWI-4191]: NWI-4168, NWI-4161, NWI-3901, NWI-4108, NWI-3922, NWI-4083, NWI-4085, NWI-4122, NWI-4125, NWI-4136, NWI-4134, NWI-4135, NWI-4139, NWI-4141, NWI-4130, NWI-4169, NWI-4080, NWI-4160, NWI-4151 Web: implemented display of users in file ACLs for which the system has no accounts configured [NWI-3951]

In this text, I meant that: Network: IP address: 192.168.1.1 Subnet mask: 255.255.255.0 (/24) I divided it into three parts according to the created segments: a) Segment "Home network" (segments/Bridge0): IP address: 192.168.1.1 Subnet mask: 255.255.255.224 (/27) b) Segment "Guest network" (segments/Bridge1): IP address: 192.168.1.32 Subnet mask: 255.255.255.224 (/27) c) Segment "WorkStation network" (segments/Bridge3): IP address: 192.168.1.96 Subnet mask: 255.255.255.224 (/27) Yes, saved successfully. Got it. I'll send it in the next post.

Hello. There is a small problem I am having. It has appeared recently, I have come across it several times on several different devices. Namely: when the device is away from home, when it is not at home at that moment, it does not fall off the device list. It's been a few hours on average and it's still on the list. When I wake up the wifi of a different device, it falls off the network within a few minutes. The device that is having problems now was dropped from the network in the morning in a few minutes without any problem. So the problem occurs for a random device at a random time. The device moved away from home 2 hours ago, but it is still listed as such in the device list. The "show ip arp" output does not show any beri of the problematic device. I will attach the device information and selftest file in the next secret message.

Давно хотел добавить, как раз вспомнил когда надоело видеть как винт просыпается из-за ресканов, поставил 24 часа. На форуме 4pda тоже было решение, про способ ниже увидел позже ARGS="--config=/opt/etc/syncthing/ --data=/opt/root/.local/state/syncthing"

В файле /opt/etc/init.d/S92syncthing Меняем строку ARGS="" На ARGS="--config=/opt/etc/syncthing/ --data=/opt/root/.local/state/syncthing"

Support for use keenetic modem as Tailscale exit node and access home/work network from keenetic modem. Subnet routers and traffic relay nodes · Tailscale Exit Nodes (route all traffic) · Tailscale I currently use raspberry pi as exit node in my network. Here is a client github repository tailscale/tailscale: The easiest, most secure way to use WireGuard and 2FA. (github.com) Tailscale is a VPN that modifies the Wireguard protocol slightly by adding Tailscale discovery messages. Relevant code: https://github.com/tailscale/tailscale/blob/main/disco/disco.go

Tailscale is available as an open package in the open package manager. It should be no problem for the devs to add some web UI voodoo. Tailscale in short: Tailscale is a control plane for Wireguard managing the configuration of the nodes. It easily creates a mesh-overlay network with NAT traversal and access control lists. All configuration is done via the web interface or the API of the control server. Btw. there is an open-source control server called headscale.