Windows 10: Unable to get public ipv4 address on Windows 10

Hi, I'm unable to get a public IPv4 address and need this for routing purposes to get access to cloud provider.

For example, when I got to https://whatsmyip.com/, it only shows me an IPv6 address.

It also shows "My Public IPv4:Not Detected"....and I've tried multiple websites showing pullic ips -- all show the same results.


So it looks like DHCP is not doing its job for ipv4 but is working just fine for IPv6. Don't understand that.


When I try "ipconfig /release" or "ipconfig /renew", the output leads with these weird errors:

No operation can be performed on Local Area Connection* 6 while it has its media disconnected.

No operation can be performed on Local Area Connection* 10 while it has its media disconnected.


This is weird to me because my "Wireless LAN adapter Wi-Fi:" see below is up and kicking and providing healthy internet, other than the fact I'm not getting an ipv4 address. I would like to try to delete these "Media Disconnected" connections. Does anyone know how to do this?



I've deleted all my adapters in device manager and rebooted, then reconnected to my wifi access point.....still no public ip.

I've also updated the network drivers for my wireless card, still no public ip.




Thank you in advance for any help you can provide, see my ipconfig /all output below.


--Erik



C:\WINDOWS\system32>ipconfig /all



Windows IP Configuration



Host Name . . . . . . . . . . . . : DESKTOP-2URE8SU

Primary Dns Suffix . . . . . . . :

Node Type . . . . . . . . . . . . : Hybrid

IP Routing Enabled. . . . . . . . : No

WINS Proxy Enabled. . . . . . . . : No

DNS Suffix Search List. . . . . . : attlocal.net



Wireless LAN adapter Local Area Connection* 6:



Media State . . . . . . . . . . . : Media disconnected

Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter

Physical Address. . . . . . . . . : 50-EB-71-57-CC-78

DHCP Enabled. . . . . . . . . . . : Yes

Autoconfiguration Enabled . . . . : Yes



Wireless LAN adapter Local Area Connection* 10:



Media State . . . . . . . . . . . : Media disconnected

Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter #2

Physical Address. . . . . . . . . : 52-EB-71-57-CC-77

DHCP Enabled. . . . . . . . . . . : Yes

Autoconfiguration Enabled . . . . : Yes



Wireless LAN adapter Wi-Fi:



Connection-specific DNS Suffix . : attlocal.net

Description . . . . . . . . . . . : KillerR Wi-Fi 6 AX1650x 160MHz Wireless Network Adapter 200NGW

Physical Address. . . . . . . . . : 50-EB-71-57-CC-77

DHCP Enabled. . . . . . . . . . . : Yes

Autoconfiguration Enabled . . . . : Yes

IPv6 Address. . . . . . . . . . . : 2600:1700:b0c0:de90::49Preferred

Lease Obtained. . . . . . . . . . : Friday, April 9, 2021 8:13:40 AM

Lease Expires . . . . . . . . . . : Friday, April 9, 2021 9:28:10 AM

IPv6 Address. . . . . . . . . . . : 2600:1700:b0c0:de90:1094:5844:588b:7f1fPreferred

Temporary IPv6 Address. . . . . . : 2600:1700:b0c0:de90:d830:298d:2e15:9686Preferred

Link-local IPv6 Address . . . . . : fe80::1094:5844:588b:7f1f%8Preferred

IPv4 Address. . . . . . . . . . . : 192.168.1.224Preferred

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Lease Obtained. . . . . . . . . . : Friday, April 9, 2021 8:13:38 AM

Lease Expires . . . . . . . . . . : Saturday, April 10, 2021 8:14:07 AM

Default Gateway . . . . . . . . . : fe80::1e1b:68ff:fed5:8f90%8

192.168.1.254

DHCP Server . . . . . . . . . . . : 192.168.1.254

DHCPv6 IAID . . . . . . . . . . . : 122743665

DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-25-B7-9D-A6-50-EB-71-57-CC-77

DNS Servers . . . . . . . . . . . : 2600:1700:b0c0:de90::1

192.168.1.254

NetBIOS over Tcpip. . . . . . . . : Enabled

Connection-specific DNS Suffix Search List :

attlocal.net



Ethernet adapter Bluetooth Network Connection:



Media State . . . . . . . . . . . : Media disconnected

Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : Bluetooth Device Personal Area Network

Physical Address. . . . . . . . . : 50-EB-71-57-CC-7B

DHCP Enabled. . . . . . . . . . . : Yes

Autoconfiguration Enabled . . . . : Yes

:)

 

Asus RT-AC88U problem with public ip starting with 10.xxx.xxx.xxx

10.x subnets are quite common. Everyone seems to think that 10.x or 172.x subnets or anything other than 192.168.x.x. = public IP when there's actually 3 private IP ranges in use on IPv4 protocol.

Most enterprises actually use the 10.x.x.x

I use all 3 for each VLAN to make it easy to tell which VLAN a device is on.

• 10.0.0.0/8 IP addresses: 10.0.0.0 -- 10.255.255.255.
• 172.16.0.0/12 IP addresses: 172.16.0.0 -- 172.31.255.255.
• 192.168.0.0/16 IP addresses: 192.168.0.0 – 192.168.255.255.

 

IPV4 ADDRESSES

Hi Gerald,

If you mean when the first octet is static,

IPV4 Total Addresses = 4,294,967,296 (2^32)

There are 588,514,304 reserved addresses

Therefore there is 3,706,452,992 public addresses in total

Given that, it would be hard to actually work out and answer for this question

But theoretically (if we disregard reserves addresses) the answer is 255 X 255 X 255 = 16,581,375

 

Asus RT-AC88U problem with public ip starting with 10.xxx.xxx.xxx

For extra points, which range belongs to which class? *Stick Out Tongue

(for even more points, what is one of the reasons for the IP number shortage?)