Wi5/odin-wi5

some problem after running

peterrz opened this issue · 5 comments

peterrz commented

I have 3 problem currently with whole system:

  1. i have 3 Access point now :
    A: openwrt (wlan0,main access point),
    B:wrt (wlan1,TL-WN722N),
    C: odin_unizer (build with click),
    whats is wrong ? how i turn off A & B without turn off C ??.

  2. every time when i turn on router, I should run you script start.sh again,

  3. i run showstatistics in controller, when any device join, it show all information about current state, but after reconnect it didn't work anymore, when device left the network console show that :

INFO n.f.odin.master.OdinMaster - Client ::::: completed the association
19:25:12.940 [pool-3-thread-12] INFO n.f.odin.master.OdinMaster - Clearing Lvap :::::
from agent:/192.168.1.32 due to deauthentication/inactivity

after some minutes device request for reconnecting, the association will be complete, but on controller console didn't show any statistics about this device anymore, why ?!

josemariasaldana commented

Problem 1:
i have 3 Access point now :
A: openwrt (wlan0,main access point),
B:wrt (wlan1,TL-WN722N),
C: odin_unizer (build with click),
whats is wrong ? how i turn off A & B without turn off C ??.

I don't understand your question. Everything has to run in a single Access Point (one device).
You will see three Wi-Fi SSIDs: the one created by wlan0, the one created by wlan1 and the last one. The three of them have to work at the same time. You cannot switch off A and B.

Problem 2:
every time when i turn on router, I should run you script start.sh again,

Yes. This is how it works. Take into account that this is not a commercial product, but just a proof-of-concept.

Problem 3:
i run showstatistics in controller, when any device join, it show all information about current state, but after reconnect it didn't work anymore, when device left the network console show that :

INFO n.f.odin.master.OdinMaster - Client ::::: completed the association
19:25:12.940 [pool-3-thread-12] INFO n.f.odin.master.OdinMaster - Clearing Lvap :::::
from agent:/192.168.1.32 due to deauthentication/inactivity
after some minutes device request for reconnecting, the association will be complete, but on controller console didn't show any statistics about this device anymore, why ?!

We would have to explore this.

peterrz commented

I don't understand your question. Everything has to run in a single Access Point (one device).
You will see three Wi-Fi SSIDs: the one created by wlan0, the one created by wlan1 and the last one. The three of them have to work at the same time. You cannot switch off A and B.
everything run in one device, i have 3 access point now
here is ifconfig command:
ap Link encap:Ethernet HWaddr C6:3B:92:76:74:DE
inet6 addr: fe80::c43b:92ff:fe76:74de/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:7 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:500
RX bytes:0 (0.0 B) TX bytes:738 (738.0 B)

mon0 Link encap:UNSPEC HWaddr A4-2B-B0-CA-91-CE-00-44-00-00-00-00-00-00-00-00 UP BROADCAST RUNNING MULTICAST MTU:1532 Metric:1 RX packets:4302 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:890941 (870.0 KiB) TX bytes:0 (0.0 B)

mon1 Link encap:UNSPEC HWaddr 84-16-F9-17-71-5C-00-44-00-00-00-00-00-00-00-00 UP BROADCAST RUNNING MULTICAST MTU:1532 Metric:1 RX packets:6899 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1440988 (1.3 MiB) TX bytes:0 (0.0 B)

wlan0 Link encap:Ethernet HWaddr A4:2B:B0:CA:91:CE inet6 addr: fe80::a62b:b0ff:feca:91ce/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:15 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:1816 (1.7 KiB)

wlan1 Link encap:Ethernet HWaddr 84:16:F9:17:71:5C inet6 addr: fe80::8616:f9ff:fe17:715c/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:15 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:1816 (1.7 KiB)
i understand they should be up (wlan0 and wlan1 ) to build LVAP but they shouldn't work separately, if A ( wlan0) and B ( wlan1) cannot be turn off, client can join them while they should join C ( odin_unizer build with click). we can hide A and B to refuse join client.

Problem 3:
i run showstatistics in controller, when any device join, it show all information about current state, but after reconnect it didn't work anymore, when device left the network console show that :

INFO n.f.odin.master.OdinMaster - Client ::::: completed the association
19:25:12.940 [pool-3-thread-12] INFO n.f.odin.master.OdinMaster - Clearing Lvap :::::
from agent:/192.168.1.32 due to deauthentication/inactivity
after some minutes device request for reconnecting, the association will be complete, but on controller console didn't show any statistics about this device anymore, why ?!

i have this problem in agent too, at the agent didn't show anything, here is more info:

##################################################################
[Odinagent.cc] OpenAuth request STA (80:5A:04:CE:7E:0F) ----> AP (00:1B:B3:CE:7E:0F) [Odinagent.cc] OpenAuth response STA (80:5A:04:CE:7E:0F) <---- AP (00:1B:B3:CE:7E:0F)
##################################################################
[Odinagent.cc] OpenAuth request STA (80:5A:04:CE:7E:0F) ----> AP (00:1B:B3:CE:7E:0F)
[Odinagent.cc] OpenAuth response STA (80:5A:04:CE:7E:0F) <---- AP (00:1B:B3:CE:7E:0F)
[Odinagent.cc] Association request STA (80:5A:04:CE:7E:0F) ----> AP (00:1B:B3:CE:7E:0F)
[Odinagent.cc] Association response STA (80:5A:04:CE:7E:0F) <---- AP (00:1B:B3:CE:7E:0F)
##################################################################

##################################################################
[Odinagent.cc] OpenAuth request STA (80:5A:04:CE:7E:0F) ----> AP (00:1B:B3:CE:7E:0F) [Odinagent.cc] OpenAuth response STA (80:5A:04:CE:7E:0F) <---- AP (00:1B:B3:CE:7E:0F) [Odinagent.cc] Association request STA (80:5A:04:CE:7E:0F) ----> AP (00:1B:B3:CE:7E:0F) [Odinagent.cc] Association response STA (80:5A:04:CE:7E:0F) <---- AP (00:1B:B3:CE:7E:0F)
##################################################################

##################################################################
[Odinagent.cc] ##### Periodic report. Number of stations associated: 1
##################################################################

[Odinagent.cc] Cleaning old info from stations not associated
##################################################################
[Odinagent.cc] ##### Periodic report. Number of stations associated: 1
##################################################################

after reconnecting device (80:5A:04:CE:7E:0F) had IpAddres "192.168.1.13" which was set manually,
but it didn't show in controller, i guess that is the problem.

curl http://127.0.0.1:8080/odin/clients/all/json | python -m json.tool
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 275 0 275 0 0 31267 0 --:--:-- --:--:-- --:--:-- 39285
[
{
"agent": "192.168.1.32",
"ipAddress": "0.0.0.0",
"lvapBssid": "00:1B:B3:CE:7E:0F",
"lvapSsid": "odin-unizar",
"macAddress": "80:5A:04:CE:7E:0F"
}
]

peterrz commented

when i run :
./click < click-align agent.cli & show me this message

agent.cli:41: While configuring '':
warning: alignment unknown, but machine is sensitive to alignment
(Classifier must be told how its input packets are aligned in memory.
Fix this error either by passing your configuration through click-align,
or by providing explicit AlignmentInfo. I am assuming the equivalent
of 'AlignmentInfo(fhcl 4 0)'.)
agent.cli:101: While configuring '':
warning: alignment unknown, but machine is sensitive to alignment

josemariasaldana commented

The warning: alignment unknow, is not a problem at all. Everything works anyway.

josemariasaldana commented

Regarding this question

i understand they should be up (wlan0 and wlan1 ) to build LVAP but they shouldn't work separately, if A ( wlan0) and B ( wlan1) cannot be turn off, client can join them while they should join C ( odin_unizer build with click). we can hide A and B to refuse join client.

  • The interface wlan0 and mon0 are the same physical interface. So if you shut down wlan0, then mon0 will not work. The same happens with wlan1 and mon1.

  • Using wlan0, the AP creates an SSID which is managed by OpenWrt.

  • Using wlan1, the AP creates another SSID which is managed by OpenWrt.

  • Using mon0, we (through Odin) create a third ssid (odin-unizar) for Odin.