I’m using a GLA1300 and need help distinguishing between my actual IP address and the IP address provided by the TCP/UDP VPN configuration I uploaded. I’m on a MacBook and would like to know which commands will show my real IP address versus the VPN IP address.
In the router’s main page, I see a certain IP address listed—does that refer to the server I’m connected to through the VPN configuration, or is it my own IP address? I need to whitelist the correct IP for my developer job, so it’s crucial to understand how to identify my “real” IP versus the VPN IP, and also confirm that my internet traffic is truly going through the VPN rather than my local network.
hmm weird, so if I want to add an IP Address to a white list how can I retrieve the right one? I thought that curl -4 ifconfig.me(begins with (begins with 213..) would give me the IP Address to whitelist and not the one on the Glinet VPN website (begins with 192. ....). In other words is the IP Address to whitelist the one I get from websites like whatismyip.com or ipleak.net
Can you orient me more here?
Are you referring to the public IP address you're connected from? The easiest way is to access a web browser (https://whatismyipaddress.com/) from a device to see what your real public IP address is. On Linux, "curl ip.me".
If you're tunneling all traffic through the VPN when you connect, the public IP address will be the one on the other end. If you're not tunneling public traffic, the public IP address will be your local location.
Or are you referring to your laptop's private IP address?
Well, that's the question I am trying to answer. The thing is that in Cosmos DB on Azure it is not possible to access the service if my IP Address is not whitelisted. Based on your explanation, I should definitely use the one from curl ip.me. I am not an expert here but from what I understood there is the real IP Address, the VPN IP Address and the Router IP Address. The router IP makes no sense here, so I assume that what Cosmos DB needs is the public IP and not the VPN IP.
I hope this makes it clear Thanks a lot !
well that raises the question on whether Cosmos DB and Azure services need the real IP Address without VPN or the public IP address. I will ask the admins to test with both
p.s I am on MAC and this dies not work
If the VPN doesn't connect to an endpoint that provides access to Azure, how will you access it?
If that Azure service is public, what they're asking for is your public IP. But if you connect your router and tunnel all traffic, your public IP will be the one at the VPN endpoint. Not your local one.
Well that's the thing we have our main router in a room and I am having the glinet router in my room and both are connected and work fine. Since I will be moving from one place to another due to a business trip and that my glinet will be with me and connected to another router in another room, then do I need to take the IP Address from curl ip.me or the one shown on the routers main page (see screenshot) for whitelisting and accessing cosmos DB/Azure?
That's cool but this does not answer the question regarding which IP Address do external services like Azure Cosmos DB use. Do they use the nonvpn or the public IP Address. I asked our friend ChatGPT and it kept saying that the public IP Address retrieved with curl ifconfig.me is used for that. Can you confirm this? Again the main router is in another room and I am using TP-Link Powerline Adapter Set TL-PA4010P KIT to connect both.
As you can see in my previous screenshot the UI gives an IP Address of 192. ...., routing through SSH gives an IP Address 88. ... and using curl ifconfig.me gives an IP Address 213. ....
Your gl.inet router isn't directly connected to a WAN. That's why the dashboard doesn't show a public IP.
You need to run the commands we've told you about several times to find your public IP. When you find that IP, that's the one you need to enter for the whitelist.
However, if you connect through a VPN and tunnel ALL traffic, your public IP may be different. Then, you'll need to run the command again to find out what public IP you have when you're connected through the VPN.