Jump to content

Eduard Bogdanov

Forum Members
  • Posts

    36
  • Joined

  • Last visited

Posts posted by Eduard Bogdanov

  1. Есть точка доступа Ultra-II в одном контроллера Wifi

    Телефон IphoneX, подключенный к этой точке доступа.

    Проблема в том, что в логе появляются следующие нежелательные сообщения.

    Прошивки ТД и роутера - самые последние, тестовые.

    Исправите?

     
    Spoiler

     

    Апр 23 11:30:41
     
    wmond
    WifiMaster0/AccessPoint1: (MT76x2) STA(74:8d:08:d3:4a:c1) had been aged-out and disassociated (idle silence).
    Апр 23 11:31:16
     
    wmond
    WifiMaster0/AccessPoint1: (MT76x2) STA(74:9e:af:0b:ad:c1) had disassociated by STA (reason: STA is leaving or has left BSS).
    Апр 23 11:32:30
     
    wmond
    WifiMaster0/AccessPoint1: (MT76x2) STA(74:9e:af:0b:ad:c1) had associated successfully (FT mode).
    Апр 23 11:32:30
     
    wmond
    WifiMaster0/AccessPoint1: (MT76x2) STA(74:9e:af:0b:ad:c1) set key done in WPA2/WPA2PSK.
    Апр 23 11:32:32
     
    wmond
    WifiMaster1/AccessPoint1: (MT76x2) STA(74:9e:af:0b:ad:c1) FT authentication rejected (status code: 53).
    Апр 23 11:32:33
     
    wmond
    WifiMaster1/AccessPoint1: (MT76x2) STA(74:9e:af:0b:ad:c1) FT authentication rejected (status code: 28).
    Апр 23 11:32:45
     
    wmond
    WifiMaster1/AccessPoint1: (MT76x2) STA(74:9e:af:0b:ad:c1) FT authentication rejected (status code: 53).
    Апр 23 11:32:59
     
    wmond
    WifiMaster0/AccessPoint1: (MT76x2) STA(74:9e:af:0b:ad:c1) FT authentication rejected (status code: 53).
    Апр 23 11:33:23
     
    wmond
    WifiMaster0/AccessPoint1: (MT76x2) STA(74:9e:af:0b:ad:c1) FT authentication rejected (status code: 28).
    Апр 23 11:33:47
     
    wmond
    WifiMaster1/AccessPoint1: (MT76x2) STA(74:9e:af:0b:ad:c1) FT authentication rejected (status code: 53).
    Апр 23 11:33:49
     
    wmond
    WifiMaster0/AccessPoint1: (MT76x2) STA(74:9e:af:0b:ad:c1) had associated successfully (FT mode).
    Апр 23 11:33:50
     
    wmond
    WifiMaster0/AccessPoint1: (MT76x2) STA(74:9e:af:0b:ad:c1) set key done in WPA2/WPA2PSK.
    Апр 23 11:34:24
     
    ndm
    kernel: mt7621_eth: unable to find 38:63:bb:dc:69:22 / VLAN 1 user address in the LUT
    Апр 23 11:34:26
     
    wmond
    WifiMaster0/AccessPoint1: (MT76x2) STA(74:9e:af:0b:ad:c1) had disassociated by STA (reason: STA is leaving or has left BSS).
    Апр 23 11:34:50
     
    wmond
    WifiMaster0/AccessPoint1: (MT76x2) STA(74:9e:af:0b:ad:c1) had associated successfully (FT mode).
    Апр 23 11:34:51
     
    wmond
    WifiMaster0/AccessPoint1: (MT76x2) STA(74:9e:af:0b:ad:c1) set key done in WPA2/WPA2PSK.
    Апр 23 11:34:53
     
    wmond
    WifiMaster1/AccessPoint1: (MT76x2) STA(74:9e:af:0b:ad:c1) FT authentication rejected (status code: 53).


     

     

  2. 2 hours ago, r13 said:

    Убрали как раз из-за возможности назначить постоянный ip. 

    Идея в том что все в wifi системе настраивается автоматом (на тд можно перейти из вкладки wifi система)

    Не понимаю! Кому мешает привязка МАК адреса точки доступа к какому-то одному адресу из диапазона DHCP?!!!

    Какая разница какой IP адрес выдаст сервер DHCP - либо свободный незанятый, либо предварительно застолбленный?!!!

    Ведь в любом случае ТД получает адрес от DHCP сервера!

    В чем фишка то?!!!

  3. 6 minutes ago, r13 said:

    То что пропадает , так и задумано.

    Ошибки из-за фиксированнрго ip для точки доступа, его нужно удалить

     

    Там нет фиксированного IP

    При захвате точки доступа, фиксированный IP автоматически меняется на DHCP

    А вот в самом роутере, в DHCP стоит постоянный IP адрес

    У меня IP точки доступа совпадает с номером кабинета. 

    Убирать привязку IP адреса к мак адресу точки доступа НЕ ХОЧУ!

    Так как запутаюсь, где какая ТД у меня стоит!

     

    А зачем убрали захваченный ТД из списка устройств? Кому это мешало?!

    Спасибо!

  4. Есть Ultra-II в режиме захваченной точки доступа.

    В логе стали появляться странные сообщения

    Причем эти же сообщения на захваченных точках доступа на базе KN-1810 не появляются.

    Что за LUT?!

    Есть ли проблема в том, что эти сообщения лезут в лог?

    Спасибо!

     
    Апр 22 20:40:28
     
    ndm
    kernel: mt7621_eth: unable to find 5c:b9:01:0c:19:46 / VLAN 1 user address in the LUT
    Апр 22 20:42:33
     
    ndm
    kernel: mt7621_eth: unable to find 3c:a8:2a:06:7a:28 / VLAN 1 user address in the LUT
    Апр 22 20:49:38
     
    ndm
    kernel: mt7621_eth: unable to find 38:63:bb:dc:69:22 / VLAN 1 user address in the LUT
     
  5. При добавлении точки доступа в контроллер wifi системы, точка доступа сразу пропадает из списка устройств роутера.

    В логах контроллера Wifi появляется запись о невозможности обновить ip адрес захваченной точки доступа

    Все это наблюдается как на KN-1810, так и на ULTRA-II

     

    Весь лог роутера забит красными сообщениями от захваченных точек доступа!

     
    Пожалуйста исправьте!
     
     
    Spoiler
    Апр 22 20:41:41
     
    ndhcps
    DHCPDISCOVER received from 58:8b:f3:65:cc:d4.
    Апр 22 20:41:41
     
    ndhcps
    host 58:8b:f3:65:cc:d4 belongs to different network.
    Апр 22 20:41:41
     
    ndhcps
    failed to allocate new IP address.
    Апр 22 20:41:50
     
    ndhcps
    DHCPDISCOVER received from 50:ff:20:11:64:8c.
    Апр 22 20:41:50
     
    ndhcps
    host 50:ff:20:11:64:8c belongs to different network.
    Апр 22 20:41:50
     
    ndhcps
    failed to allocate new IP address.
    Апр 22 20:41:59
     
    ndhcps
    DHCPDISCOVER received from 50:ff:20:11:6b:25.
    Апр 22 20:41:59
     
    ndhcps
    host 50:ff:20:11:6b:25 belongs to different network.
    Апр 22 20:41:59
     
    ndhcps
    failed to allocate new IP address.
    Апр 22 20:42:00
     
    ndhcps
    DHCPREQUEST received (STATE_INIT) for 10.0.0.180 from 14:da:e9:2f:3a:20.
    Апр 22 20:42:00
     
    ndhcps
    sending ACK of 10.0.0.180 to 14:da:e9:2f:3a:20.
    Апр 22 20:42:06
     
    ndhcps
    DHCPDISCOVER received from 50:ff:20:11:6b:25.
    Апр 22 20:42:06
     
    ndhcps
    host 50:ff:20:11:6b:25 belongs to different network.
    Апр 22 20:42:06
     
    ndhcps
    failed to allocate new IP address.
    Апр 22 20:42:10
     
    ndhcps
    DHCPDISCOVER received from 50:ff:20:11:82:0b.
    Апр 22 20:42:10
     
    ndhcps
    host 50:ff:20:11:82:0b belongs to different network.
    Апр 22 20:42:10
     
    ndhcps
    failed to allocate new IP address.
    Апр 22 20:42:11
     
    ndhcps
    DHCPDISCOVER received from 50:ff:20:11:64:8c.
    Апр 22 20:42:11
     
    ndhcps
    host 50:ff:20:11:64:8c belongs to different network.
    Апр 22 20:42:11
     
    ndhcps
    failed to allocate new IP address.
    Апр 22 20:42:15
     
    ndhcps
    DHCPDISCOVER received from 50:ff:20:11:73:b9.
    Апр 22 20:42:15
     
    ndhcps
    host 50:ff:20:11:73:b9 belongs to different network.
    Апр 22 20:42:15
     
    ndhcps
    failed to allocate new IP address.
    Апр 22 20:42:17
     
    ndhcps
    DHCPDISCOVER received from 50:ff:20:11:82:0b.
    Апр 22 20:42:17
     
    ndhcps
    host 50:ff:20:11:82:0b belongs to different network.
    Апр 22 20:42:17
     
    ndhcps
    failed to allocate new IP address.
    Апр 22 20:42:20
     
    ndhcps
    DHCPDISCOVER received from 50:ff:20:11:6b:25.
    Апр 22 20:42:20
     
    ndhcps
    host 50:ff:20:11:6b:25 belongs to different network.
    Апр 22 20:42:20
     
    ndhcps
    failed to allocate new IP address.
    Апр 22 20:42:21
     
    ndhcps
    DHCPDISCOVER received from 58:8b:f3:65:cc:d4.
    Апр 22 20:42:21
     
    ndhcps
    host 58:8b:f3:65:cc:d4 belongs to different network.
    Апр 22 20:42:21
     
    ndhcps
    failed to allocate new IP address.
    Апр 22 20:42:22
     
    ndhcps
    DHCPDISCOVER received from 50:ff:20:11:73:b9.
    Апр 22 20:42:22
     
    ndhcps
    host 50:ff:20:11:73:b9 belongs to different network.
    Апр 22 20:42:22
     
    ndhcps
    failed to allocate new IP address.
    Апр 22 20:42:28
     
    ndhcps
    DHCPDISCOVER received from 58:8b:f3:65:cc:d4.
    Апр 22 20:42:28
     
    ndhcps
    host 58:8b:f3:65:cc:d4 belongs to different network.
    Апр 22 20:42:28
     
    ndhcps
    failed to allocate new IP address.
    Апр 22 20:42:31
     
    ndhcps
    DHCPDISCOVER received from 50:ff:20:11:82:0b.
    Апр 22 20:42:31
     
    ndhcps
    host 50:ff:20:11:82:0b belongs to different network.
    Апр 22 20:42:31
     
    ndhcps
    failed to allocate new IP address.
    Апр 22 20:42:36
     
    ndhcps
    DHCPDISCOVER received from 50:ff:20:11:73:b9.
    Апр 22 20:42:36
     
    ndhcps
    host 50:ff:20:11:73:b9 belongs to different network.
    Апр 22 20:42:36
     
    ndhcps
    failed to allocate new IP address.
    Апр 22 20:42:39
     
    ndhcps
    DHCPDISCOVER received from 50:ff:20:11:64:8c.
    Апр 22 20:42:39
     
    ndhcps
    host 50:ff:20:11:64:8c belongs to different network.
    Апр 22 20:42:39
     
    ndhcps
    failed to allocate new IP address.
    Апр 22 20:42:41
     
    ndhcps
    DHCPDISCOVER received from 50:ff:20:11:6b:25.
    Апр 22 20:42:41
     
    ndhcps
    host 50:ff:20:11:6b:25 belongs to different network.
    Апр 22 20:42:41
     
    ndhcps
    failed to allocate new IP address.
    Апр 22 20:42:42
     
    ndhcps
    DHCPDISCOVER received from 58:8b:f3:65:cc:d4.
    Апр 22 20:42:42
     
    ndhcps
    host 58:8b:f3:65:cc:d4 belongs to different network.
    Апр 22 20:42:42
     
    ndhcps
    failed to allocate new IP address.
    Апр 22 20:42:52
     
    ndhcps
    DHCPDISCOVER received from 50:ff:20:11:82:0b.
    Апр 22 20:42:52
     
    ndhcps
    host 50:ff:20:11:82:0b belongs to different network.
    Апр 22 20:42:52
     
    ndhcps
    failed to allocate new IP address.
    Апр 22 20:42:57
     
    ndhcps
    DHCPDISCOVER received from 50:ff:20:11:73:b9.
    Апр 22 20:42:57
     
    ndhcps
    host 50:ff:20:11:73:b9 belongs to different network.
    Апр 22 20:42:57
     
    ndhcps
    failed to allocate new IP address.
    Апр 22 20:43:03
     
    ndhcps
    DHCPDISCOVER received from 58:8b:f3:65:cc:d4.
    Апр 22 20:43:03
     
    ndhcps
    host 58:8b:f3:65:cc:d4 belongs to different network.
    Апр 22 20:43:03
     
    ndhcps
    failed to allocate new IP address.
    Апр 22 20:43:09
     
    ndhcps
    DHCPDISCOVER received from 50:ff:20:11:6b:25.
    Апр 22 20:43:09
     
    ndhcps
    host 50:ff:20:11:6b:25 belongs to different network.
    Апр 22 20:43:09
     
    ndhcps
    failed to allocate new IP address.
    Апр 22 20:43:09
     
    ndhcps
    DHCPDISCOVER received from 50:ff:20:11:64:8c.
    Апр 22 20:43:09
     
    ndhcps
    host 50:ff:20:11:64:8c belongs to different network.
    Апр 22 20:43:09
     
    ndhcps
    failed to allocate new IP address.
    Апр 22 20:43:20
     
    ndhcps
    DHCPDISCOVER received from 50:ff:20:11:82:0b.
    Апр 22 20:43:20
     
    ndhcps
    host 50:ff:20:11:82:0b belongs to different network.
    Апр 22 20:43:20
     
    ndhcps
    failed to allocate new IP address.
    Апр 22 20:43:25
     
    ndhcps
    DHCPDISCOVER received from 50:ff:20:11:73:b9.
    Апр 22 20:43:25
     
    ndhcps
    host 50:ff:20:11:73:b9 belongs to different network.
    Апр 22 20:43:25
     
    ndhcps
    failed to allocate new IP address.
    Апр 22 20:43:31
     
    ndhcps
    DHCPDISCOVER received from 58:8b:f3:65:cc:d4.
    Апр 22 20:43:31
     
    ndhcps
    host 58:8b:f3:65:cc:d4 belongs to different network.
    Апр 22 20:43:31
     
    ndhcps
    failed to allocate new IP address.
    Апр 22 20:43:39
     
    ndhcps
    DHCPDISCOVER received from 50:ff:20:11:6b:25.
    Апр 22 20:43:39
     
    ndhcps
    host 50:ff:20:11:6b:25 belongs to different network.
    Апр 22 20:43:39
     
    ndhcps
    failed to allocate new IP address.
    Апр 22 20:43:50
     
    ndhcps
    DHCPDISCOVER received from 50:ff:20:11:64:8c.
    Апр 22 20:43:50
     
    ndhcps
    host 50:ff:20:11:64:8c belongs to different network.
    Апр 22 20:43:50
     
    ndhcps
    failed to allocate new IP address.
    Апр 22 20:43:50
     
    ndhcps
    DHCPDISCOVER received from 50:ff:20:11:82:0b.
    Апр 22 20:43:50
     
    ndhcps
    host 50:ff:20:11:82:0b belongs to different network.
    Апр 22 20:43:50
     
    ndhcps
    failed to allocate new IP address.
    Апр 22 20:43:55
     
    ndhcps
    DHCPDISCOVER received from 50:ff:20:11:73:b9.
    Апр 22 20:43:55
     
    ndhcps
    host 50:ff:20:11:73:b9 belongs to different network.
    Апр 22 20:43:55
     
    ndhcps
    failed to allocate new IP address.
    Апр 22 20:43:57
     
    ndhcps
    DHCPDISCOVER received from 50:ff:20:11:64:8c.
    Апр 22 20:43:57
     
    ndhcps
    host 50:ff:20:11:64:8c belongs to different network.
    Апр 22 20:43:57
     
    ndhcps
    failed to allocate new IP address.
    Апр 22 20:44:01
     
    ndhcps
    DHCPDISCOVER received from 58:8b:f3:65:cc:d4.
    Апр 22 20:44:01
     
    ndhcps
    host 58:8b:f3:65:cc:d4 belongs to different network.
    Апр 22 20:44:01
     
    ndhcps
    failed to allocate new IP address.
    Апр 22 20:44:11
     
    ndhcps
    DHCPDISCOVER received from 50:ff:20:11:64:8c.
    Апр 22 20:44:11
     
    ndhcps
    host 50:ff:20:11:64:8c belongs to different network.
×
×
  • Create New...