Is this instructions for public IP, or static IP?

Hi,

I'm reading these instructions which explain how to tell if my ISP is currently providing me a public IP. I arrived at these instructions from trying to setup a Wireguard server.

Thing is, those instructions sound a lot like checking if my ISP assigned me a static IP, unless I'm misunderstanding something. There's instructions explaining if I have a dynamic IP that I can use a DDNS.

I'm just trying to figure out if I should shell out extra $ for a static IP address because I don't want to deal with AstroRelay. If I have a public, dynamic IP address, it sounds from the instructions like I can use DDNS and I won't have to use AstroRelay, is this true?

Public but dynamic is fine, you can just use GLDDNS then.

CGNAT (non-public) would be a deal breaker.

1 Like

Does this mean I have CGNAT (screenshot)? Addresses are different and my IP showing up on the router admin panel starts with a 10.

I hear from places that some ISPs confuse the terms Public and Static IP.

I think you need to look at your gateway router that is physically connected to your internet. Repeater mode only shows its parent - which is why you see a 10. address. And repeater mode doesn’t offer vpn and WireGuard.

Currently I set my Gateway router to Bridge mode and it's connected to my AXT1800 via LAN <-> LAN Ethernet. Not sure if this is the correct setup. But I can't access the admin panel. I looked through the forum and it seems to be related to me having set my Gateway router to Bridge mode.

I'm not sure what I'm doing incorrectly here as I'm still pretty new to networking. But basically I want to set up a VPN Server and I put it in Bridge mode as a reaction to seeing my IP address on my admin panel to be 10.x.x.x

Are you sure about that? Using Wireguard vpn works fine for me in repeater mode.

WireGuard works through a repeater, but did you set up the WireGuard server on the repeater ?

EDIT - I'm hardly an expert on networks, but as I understand things repeater mode is just that - a repeater and not a server. But I could be wrong.

Fair warning - I know just enough to be dangerous and often appear smarter than I actually am lol

But I always understood Bridge Mode to be very similar to repeater mode (only the originator), and bridge mode usually disables the routing functions of the router. I think subsequent repeaters can be used downstream with the master in 'normal' router mode.

Can you test by resetting your gateway to 'normal' mode and set up the WireGuard server on that, then try adding the other as a repeater tied to the gateway ?

EDIT - see the GL reference for Repeater mode... They show the repeater tied to a 'normal' gateway router, not a bridge.

Of course not - the Wireguard sever is running on my router at home, and the client is running on my travel router, which is in Repeater mode.

So, is the travel router configured with your WireGuard information? Does it connect correctly?

The question about whether your ISP provides a dynamic or static IP has more to do with your home router.

I have WireGuard set up on my main router and it works fine. My Xfinity provides a dynamic address, so I use the GL ddns feature. When you set that up, the WireGuard configuration file uses the GL dynamic domain for the destination address. I’m struggling to understand what you are asking when you show the travel router image.

And if the travel router connects to your home router, the setup is obviously working. And if you’re not sure, just use the GL dynamic dns option - it won’t hurt even if you have a static ip.

Who are you replying to?

Lol I got you confused with the op.

My bad.

Fair enough - but next time maybe use the "Quote" button - it makes it much easier to figure out who's talking to whom. :wink: