- 0
50A3 попадание клиента в разряд зарегистрированных - самостоятельно.
-
Recently Browsing 0 members
- No registered users viewing this page.
This site uses cookies. By clicking "I accept" or continuing to browse the site, you authorize their use in accordance with the Privacy Policy.
Question
vasek00
ПО 50A3, клиентов не планировалось регистрировать. KN1010 в хитром режиме, т.е. все порты WAN и LAN в месте.
---------W-| NAT |-Wifi- PS1-----L1-+ PS2-----L2-+ PS3-----L3-+ PS4-----L4-/ interface GigabitEthernet0 up ! interface GigabitEthernet0/Vlan1 ip dhcp client dns-routes up ! interface GigabitEthernet0/Vlan4 ip dhcp client dns-routes up ! interface GigabitEthernet1 rename ISP description "Broadband connection" mac address factory wan ip dhcp client hostname G-KN ip dhcp client dns-routes ip mtu 1500 ipv6 name-servers auto up ! interface GigabitEthernet1/0 rename 0 up ! interface Bridge2 rename ISP-IPTV description AD role inet for ISP inherit ISP include GigabitEthernet0/Vlan4 mac address factory wan mac access-list type none security-level public ip address 192.168.15.239 255.255.255.0 ip dhcp client hostname G-KN ip dhcp client dns-routes ip mtu 1500 ip global 700 igmp upstream up ! interface GigabitEthernet0/0 rename 1 role iptv for ISP-IPTV switchport mode access switchport access vlan 4 up ! interface GigabitEthernet0/1 rename 2 role iptv for ISP-IPTV switchport mode access switchport access vlan 4 up ! interface GigabitEthernet0/2 rename 3 role iptv for ISP-IPTV switchport mode access switchport access vlan 4 up ! interface GigabitEthernet0/3 rename 4 role iptv for ISP-IPTV switchport mode access switchport access vlan 4 upдля клиентов wifi оставлен только - wifi.
interface Bridge0 rename Home description Wifi-AD include GigabitEthernet0/Vlan1 include AccessPoint include AccessPoint_5G mac address factory lan mac access-list type none security-level private ip address 192.168.30.1 255.255.255.0 ip dhcp client dns-routes band-steering iapp key ns3 *** upИтоге получаю несколько 8 зарегистрированных клиентов, остальные как и положено среди незарегистрированных. Что происходит на примере двух ниже
known host "M2010J19CG-POCOM3 - Wifi-AD - 2025-06-20 12:01" 24:хх:хх:хх:хх:b4 known host "M2004J19C-Redmi9 - Wifi-AD - 2025-06-20 08:49" 74:хх:хх:хх:хх:48 ip hotspot policy Home permit host 74:хх:хх:хх:хх:48 permit host 74:хх:хх:хх:хх:48 conform host 24:хх:хх:хх:хх:b4 permit host 24:хх:хх:хх:хх:b4 conform ... [I] Jun 20 08:01:12 ndm: Network::Interface::Mtk::WifiMonitor: "WifiMaster0/AccessPoint0": STA(24:xx:xx:xx:xx:b4) had associated (has FT caps). [I] Jun 20 08:01:13 ndm: Network::Interface::Mtk::WifiMonitor: "WifiMaster0/AccessPoint0": STA(24:xx:xx:xx:xx:b4) set key done in WPA2/WPA2PSK. [I] Jun 20 08:01:13 ndhcps: DHCPDISCOVER received from 24:xx:xx:xx:xx:b4. [I] Jun 20 08:01:13 ndhcps: making OFFER of 192.168.30.29 to 24:xx:xx:xx:xx:b4. [I] Jun 20 08:01:13 ndhcps: DHCPREQUEST received (STATE_SELECTING) for 192.168.30.29 from 24:xx:xx:xx:xx:b4. [I] Jun 20 08:01:14 ndhcps: sending ACK of 192.168.30.29 to 24:xx:xx:xx:xx:b4. [I] Jun 20 08:01:15 ndm: Core::KnownHosts: new host "M2010J19CG-POCOM3 - Wifi-AD - 2025-06-20 08:01" has been created. [I] Jun 20 08:01:15 ndm: Hotspot::Manager: conform applied to host "24:xx:xx:xx:xx:b4". [I] Jun 20 08:49:24 ndm: Network::Interface::Mtk::WifiMonitor: "WifiMaster0/AccessPoint0": STA(74:хх:хх:хх:хх:48) had associated (has FT caps). [I] Jun 20 08:49:24 ndm: Network::Interface::Mtk::WifiMonitor: "WifiMaster0/AccessPoint0": STA(74:хх:хх:хх:хх:48) set key done in WPA2/WPA2PSK. [I] Jun 20 08:49:24 ndhcps: DHCPDISCOVER received from 74:хх:хх:хх:хх:48. [I] Jun 20 08:49:25 ndhcps: making OFFER of 192.168.30.38 to 74:хх:хх:хх:хх:48. [I] Jun 20 08:49:25 ndhcps: DHCPREQUEST received (STATE_SELECTING) for 192.168.30.38 from 74:хх:хх:хх:хх:48. [I] Jun 20 08:49:25 ndhcps: sending ACK of 192.168.30.38 to 74:хх:хх:хх:хх:48. [I] Jun 20 08:49:26 ndm: Core::KnownHosts: new host "M2004J19C-Redmi9 - Wifi-AD - 2025-06-20 08:49" has been created. [I] Jun 20 08:49:26 ndm: Hotspot::Manager: conform applied to host "74:хх:хх:хх:хх:48". Клиент ушел [I] Jun 20 16:45:53 ndm: Network::Interface::Mtk::WifiMonitor: "WifiMaster0/AccessPoint0": STA(74:хх:хх:хх:хх:48) had deauthenticated by STA (reason: STA is leaving or has left BSS). [I] Jun 20 17:08:59 ndm: Network::Interface::Mtk::WifiMonitor: "WifiMaster0/AccessPoint0": STA(24:хх:хх:хх:хх:b4) had been aged-out and disassociated (idle silence). И так все ушли в WEB остались записи данных клиентов как зарегистрированыУдаляю данных клиентов, потом selftest в нем все чисто, нет записи "known host/ip hotspot".
На утро следующего дня все повторяется заново. Могу даже в течение дня удалить регистрацию данных клиентов, но они появляются снова.
0 answers to this question
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.