"
I didn't explain it properly, I apologize for that.
I said Windows 10 because I'm using pnetlab to test all this before taking it to production. Before Windows 10, I tested a PC with Windows 7 and it worked perfectly. When I tested Windows 10 and Windows 11, the same problems appear:
I connect the PC with Windows 10/11 to a switch port (the same one that was previously in Windows 7 where the captive portal worked) Microsoft Edge opens with a link in the address bar "www.msftconnecttest.com/redirect" and the page tries to load indefinitely and doesn't appear.
Because of this, I asked if there was any reason why the captive portal doesn't appear in Windows 10, specifically.
My PC with Windows 10/11 receives the IP address and DNS from my opnsense DHCP server. The ip is correct (172.16.100.14) and the dns server on windows is the ip of my opnsense is (172.16.100.5)
I only have 172.16.100.5 as my DNS server
There is no log of blocking in opnsense coming from the ip of my windows 10/11
I said Windows 10 because I'm using pnetlab to test all this before taking it to production. Before Windows 10, I tested a PC with Windows 7 and it worked perfectly. When I tested Windows 10 and Windows 11, the same problems appear:
I connect the PC with Windows 10/11 to a switch port (the same one that was previously in Windows 7 where the captive portal worked) Microsoft Edge opens with a link in the address bar "www.msftconnecttest.com/redirect" and the page tries to load indefinitely and doesn't appear.
Because of this, I asked if there was any reason why the captive portal doesn't appear in Windows 10, specifically.
My PC with Windows 10/11 receives the IP address and DNS from my opnsense DHCP server. The ip is correct (172.16.100.14) and the dns server on windows is the ip of my opnsense is (172.16.100.5)
I only have 172.16.100.5 as my DNS server
There is no log of blocking in opnsense coming from the ip of my windows 10/11
