Office-docs-powershell: Subnet length

Created on 7 Apr 2020  Â·  9Comments  Â·  Source: MicrosoftDocs/office-docs-powershell

There is no mask defined for this command, how is the client subnet determined accurately without that?


Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

teams / skype

All 9 comments

@officedocsbot assign @yogkumgit

Hello @kaishuipinggai Jundong, can you please shed some light here on the way the cmdlet determines the mask? I appreciate
Also, I see that the GitHub login metadata for you on this and other cmdlets is not correct.

@kaishuipinggai Jundong, Can you kindly reply to my inquiry? Thank you

@tomkau Tom, can you help here? Thanks

Hi sorry for the late response I might have missed this one.
So for the length and mask, we don't specify them in this commandlet. This is kind of by design since we agreed within the team to only let the tenant admin input the subnet, that is good enough for the functionality. The Lis subnet is mapping with the location information, with the location ID, with the same purpose of finding the location information by subnet/WirelessAccessPoint/Port/Switch.

Thanks @kaishuipinggai Jundong for that explanation.
I hope @vnewbaker-bw it clarifies to you.

Forget to add:
Let me give one example, assume the following is a valid input into our service to query for retrieving the LocationInfo:

{
"tenantid": "ffffffff-ffff-ffff-ffff-ffff0000ffff",
"publicIp": "100.100.100.200",
"networkinformation": {
"ipv4": "200.100.222.111",
"subnetLengthIpv4": "24",
"bssid": "02-15-03-49-CF-6D",
"e911": [
{
"chassisId": "12345",
"portId": "8"
}
]
}
}

So internally what happens is, when a Microsoft Teams app user logs in, it brings the current client's IPv4 address "200.100.222.111" and his subnetlength, and we DO the masking and then use "200.100.222.0" to see if we find any records that Tenant Admin have once input by using "Set-CsOnlineLisSubnet -Subnet 200.100.222.0 -LocationId [ID]". If it finds the match based on the same subnet then it will return the correct location information for "200.100.222.0". Otherwise, it will try bssid, portid, or chassisId to see any matching. If there's no matched location information from any of these, it will return not found to the Teams client.

Thanks for the clarification, that is what I wanted to know

@get-itips and @kaishuipinggai Thank you very much for the contribution and sharing this explanation. @vnewbaker-bw Hope this comment is helpful for you. If you see a documentation update is required, please feel free to open an issue for the same. We proceed here to close it. Thanks for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

ykuijs picture ykuijs  Â·  5Comments

TobieFysh picture TobieFysh  Â·  3Comments

BlasMS picture BlasMS  Â·  5Comments

Archehandoro picture Archehandoro  Â·  4Comments

KevinNSTA picture KevinNSTA  Â·  4Comments