RDKCOM-5492: RDKBDEV-3336 De-authenticating Hotspot Clients Upon DHCP Failure#32
RDKCOM-5492: RDKBDEV-3336 De-authenticating Hotspot Clients Upon DHCP Failure#32rhegde114 wants to merge 25 commits intordkcentral:developfrom
Conversation
publish the client mac if DHCP server has
not assigned ip address within 4 secs
publish the client mac if DHCP server has
not assigned ip address within 4 secs
publish the client mac if DHCP server has
not assigned ip address within 4 secs
publish the client mac if DHCP server has
not assigned ip address within 4 secs
publish the client mac if DHCP server has
not assigned ip address within 4 secs
publish the client mac if DHCP server has
not assigned ip address within 4 secs
Reason for change: Improvement to disassoc hotspot client
when dhcp has not assigned ip address
within 4 secs
Test Procedure: 1.Connect a client device to the hotspot VAP
2.Wait for 4 seconds and verify that the client
successfully associates with the Access Point
(AP) but does not receive a valid IP address
from the DHCP server
Risks: None
Signed-off-by: raghavendra.hegde2@comcast.com
publish the client mac if DHCP server has
not assigned ip address within 4 secs
Reason for change: Improvement to disassoc hotspot client
when dhcp has not assigned ip address
within 4 secs
Test Procedure: 1.Connect a client device to the hotspot VAP
2.Wait for 4 seconds and verify that the client
successfully associates with the Access Point
(AP) but does not receive a valid IP address
from the DHCP server
Risks: None
Signed-off-by: raghavendra.hegde2@comcast.com
This reverts commit 4effa6c.
publish the client mac if DHCP server has
not assigned ip address within 4 secs
Reason for change: Improvement to disassoc hotspot client
when dhcp has not assigned ip address
within 4 secs
Test Procedure: 1.Connect a client device to the hotspot VAP
2.Wait for 4 seconds and verify that the client
successfully associates with the Access Point
(AP) but does not receive a valid IP address
from the DHCP server
Risks: None
Signed-off-by: raghavendra.hegde2@comcast.com
publish the client mac if DHCP server has
not assigned ip address within 4 secs
Reason for change: Improvement to disassoc hotspot client
when dhcp has not assigned ip address
within 4 secs
Test Procedure: 1.Connect a client device to the hotspot VAP
2.Wait for 4 seconds and verify that the client
successfully associates with the Access Point
(AP) but does not receive a valid IP address
from the DHCP server
Risks: None
Signed-off-by: raghavendra.hegde2@comcast.com
publish the client mac if DHCP server has
not assigned ip address within 4 secs
Reason for change: Improvement to disassoc hotspot client
when dhcp has not assigned ip address
within 4 secs
Test Procedure: 1.Connect a client device to the hotspot VAP
2.Wait for 4 seconds and verify that the client
successfully associates with the Access Point
(AP) but does not receive a valid IP address
from the DHCP server
Risks: None
Signed-off-by: raghavendra.hegde2@comcast.com
anoopchelakkode
left a comment
There was a problem hiding this comment.
Can you please confirm what are the test cases executed and planned for this feature? Test procedure, both regression and progression should be documented as this is a feature request.
|
Hi Anoop, |
publish the client mac if DHCP server has
not assigned ip address within 4 secs
publish the client mac if DHCP server has
not assigned ip address within 4 secs
publish the client mac if DHCP server has
not assigned ip address within 4 secs
publish the client mac if DHCP server has
not assigned ip address within 4 secs
publish the client mac if DHCP server has
not assigned ip address within 4 secs
| return -1; | ||
| } | ||
| snoop_AddClientListEntry(gRemote_id, gCircuit_id, "ACK", ipv4_addr, l_cHostName, 0); | ||
| snoop_AddClientListEntry(gRemote_id, gCircuit_id, "ACK", ipv4_addr, l_cHostName, 0,0); |
There was a problem hiding this comment.
I see that vap_index is being passed as 0 here unconditionally. When this entry is later picked up by constructCommand() to build the deauth string sent to OneWifi, it would always report VAP index 0, regardless of which VAP the client is actually on.
There was a problem hiding this comment.
This call happens inside the DHCP ACK processing path (server-to-client direction). At this point, the code only has information extracted from the DHCP packet itself (MAC, IP, hostname, circuit ID). The vapIndex is set in updateRssiForClient(), which is called when a client connects. I think sending 0 is fine for VAP Index.
|
@rhegde114 |
publish the client mac if DHCP server has
not assigned ip address within 4 secs
publish the client mac if DHCP server has
not assigned ip address within 4 secs
Device.X_COMCAST-COM_GRE.Hotspot.RejectAssociatedClient)for the Rbus event, which will be triggered whenever a client's DHCP transaction fails to assign an IP address within a specified period (i.e., a timeout).