Your computer needs a static IP. This can be set either manually at the operating system level, or via DHCP. Once this is done the things you should test are a) that the computer works and can still access the internet and b) that another computer or device on your home network can ping that first computer. If you don't have another computer, I have had good success using the hurricane electric network... Source: over 2 years ago

To test whether your Guest Wifi is “properly implemented” download something like HE.NET Network Tools. Then log into your guest WiFi, and using the network tool, perform a “ping sweep” of your home network. If your home network is at 192.168.1.XXX, you would do a ping sweep of 192.168.1.1/24 . If you see nothing, then your guest network is “properly implemented.” If IP numbers come up in the sweep, then that... Source: over 2 years ago

I use https://networktools.he.net/ Android app and I think it's relatively easy to use. It looks like there is an option to share test results too. Source: about 3 years ago

For mobile devices, try https://networktools.he.net. Source: almost 4 years ago

Name: Deploy or Update SuiteCRM Permissions: id-token: write contents: read On: push: branches: - main paths: - 'infrastructure/**' Jobs: setup: uses: ./.github/workflows/main.yaml secrets: AWS_ROLE_TO_ASSUME: ${{ secrets.AWS_ROLE_TO_ASSUME }} with: aws-region: us-east-1 role-session-name: 'InfraDeployment' deploy: needs: setup runs-on:... - Source: dev.to / 7 months ago

It might be even easier this way:

    $ curl https://ifconfig.me --libcurl ip_fetcher.c.

- Source: Hacker News / over 1 year ago

To compile it you'll need to tell it to link to libcurl, e.g. With -lcurl on gcc:

    curl https://ifconfig.me --libcurl ip_fetcher.c.

- Source: Hacker News / over 1 year ago

This issue is due to Netflix flagging the wifi's public IP as a VPN Only way to fix this is to get a new one on that network. 9 times out of 10, a reboot of the ISP's equipment will grant you a new one (check ifconfig.me to confirm this). Source: over 1 year ago

For some weird reason, the WAN IP (100.67.XXX.XXX) is very different from my public IP that I can see with ifconfig.me (185.89.XXX.XXX). Not sure why is that, probably it's some Ubiquity 'feature' to access the UDM via the Unifi portal. Source: over 1 year ago