AppRF doesn't classify traffic, if server initiates through eth0 ?

Aruba Employee
Q:

AppRF doesn't classify traffic if server initiates through eth0 ?



A:

As per the IAP design, if server initiates traffic and if the session gets created through eth0, those sessions are not classified by apprf.

Steps to reproduce:

step1.wireless client associates with IAP
step2.send iperf traffic from eth0 to wireless client
step3.check the classification via "show datapath session dpi | in 5001",the application shows App-Not-Class.

topology:                                  wireless
PC1(client)--------eth0 IAP--------------------PC2(server)

script:
client:iperf -c 192.168.1.103 -t 1000
server:iperf.exe -s -i 2 -B 192.168.1.103 -w 1m

Outputs:

ac:a3:1e:c5:29:bc# show  datapath session dpi | inc 5001
192.168.1.103     192.168.1.100   6    5001  52248 App-Not-Class       [0   ] Web-Not-Class       [0  ] 0      9d2c    1896cc 0       
192.168.1.100     192.168.1.103   6    52248 5001  App-Not-Class       [0   ] Web-Not-Class       [0  ] 0      26d6b   d535406 0       C

So typically, clients are usually behind a private network and sessions are usually initated by clients, so this should work in all cases. 
Iperf starting from server would a special case where the session gets created through eth0 and it is by design that these are not classified.

Version history
Revision #:
2 of 2
Last update:
‎05-18-2016 01:09 PM
Updated by:
 
Labels (1)
Contributors
Search Airheads
cancel
Showing results for 
Search instead for 
Did you mean: