Networking Requirements for Winget-AutoUpdate

[devSpart]

Hello, great tool! Been testing it and it works really well.

I wanted to ask though: What network traffic is happening during the tool checking for an internet connection?
I'd imagine it should just be 443 for the "checking internet connection" function to succeed, but there appears to be something else happening.

Context:
On our corporate network, we block all outbound traffic expect 443, 80, 53 (with exceptions for required users). We also block DNS-Over-HTTPS to known / popular DNS Servers such as cloudflare and google. When this tool runs under those conditions, it can't get past the check for internet connection stage. Of course when I exclude my test device from these baseline network restrictions, it works fine.

So my question is what specific network checks, ports, destination addresses are involved in this part of the function?

Thank you!

[Romanitho]

Here is your answer:

Winget-AutoUpdate/Sources/Winget-AutoUpdate/functions/Test-Network.ps1

Lines 11 to 21 in 2e4f1a2

	try {
	$NlaRegKey = "HKLM:\SYSTEM\CurrentControlSet\Services\NlaSvc\Parameters\Internet"
	$ncsiHost = Get-ItemPropertyValue -Path $NlaRegKey -Name ActiveWebProbeHost
	$ncsiPath = Get-ItemPropertyValue -Path $NlaRegKey -Name ActiveWebProbePath
	$ncsiContent = Get-ItemPropertyValue -Path $NlaRegKey -Name ActiveWebProbeContent
	}
	catch {
	$ncsiHost = "www.msftconnecttest.com"
	$ncsiPath = "connecttest.txt"
	$ncsiContent = "Microsoft Connect Test"
	}

Winget-AutoUpdate/Sources/Winget-AutoUpdate/functions/Test-Network.ps1

Lines 24 to 29 in 2e4f1a2

	try {
	$ncsiResponse = Invoke-WebRequest -Uri "http://$($ncsiHost)/$($ncsiPath)" -UseBasicParsing -UserAgent ([Microsoft.PowerShell.Commands.PSUserAgent]::Chrome); # DevSkim: ignore DS137138 Insecure URL
	}
	catch {
	$ncsiResponse = $false
	}

[devSpart]

ffs forgot I could just go in and check the functions! Thank you solves my issue

[Romanitho]

no worries :)