F5F Stay Refreshed Power Users Networks Device connected via network, possibly using a unique default gateway setting.

Device connected via network, possibly using a unique default gateway setting.

Device connected via network, possibly using a unique default gateway setting.

B
BatmanLadie
Junior Member
Find
15
09-25-2016, 03:20 AM
#1
Hi Everyone. I thought this might be the right spot. I bought a new smart home gadget that functions as an RF blaster. I own storm shutters that can be controlled remotely using a 433MHz radio frequency, and I’ve always wanted to manage them from outside the house. To achieve this, I purchased a "MoesGo WiFi RF IR Universal Remote Controller." The tricky part is that its default gateway differs from my router. As a result, when I try to use it inside my home, I need to disable my phone’s Wi-Fi for it to connect properly if I’m on the same network. This was a bit confusing to figure out. Have you encountered this issue before? Do you have any suggestions on how to resolve it? Changing the IP address directly from the app isn’t possible. A screenshot is attached below. Thanks!
Reply
Reply
B
BatmanLadie
09-25-2016, 03:20 AM #1

Hi Everyone. I thought this might be the right spot. I bought a new smart home gadget that functions as an RF blaster. I own storm shutters that can be controlled remotely using a 433MHz radio frequency, and I’ve always wanted to manage them from outside the house. To achieve this, I purchased a "MoesGo WiFi RF IR Universal Remote Controller." The tricky part is that its default gateway differs from my router. As a result, when I try to use it inside my home, I need to disable my phone’s Wi-Fi for it to connect properly if I’m on the same network. This was a bit confusing to figure out. Have you encountered this issue before? Do you have any suggestions on how to resolve it? Changing the IP address directly from the app isn’t possible. A screenshot is attached below. Thanks!

Reply
Reply
N
Nitro_PT
Member
Find
182
09-27-2016, 08:24 AM
#2
Your public internet address is the one assigned by your service provider. Search for "my IP" to find it.
Reply
Reply
N
Nitro_PT
09-27-2016, 08:24 AM #2

Your public internet address is the one assigned by your service provider. Search for "my IP" to find it.

Reply
Reply
T
thefrogkid
Member
Find
209
09-30-2016, 12:15 AM
#3
The two screenshots depict identical error messages and interface states.
Reply
Reply
T
thefrogkid
09-30-2016, 12:15 AM #3

The two screenshots depict identical error messages and interface states.

Reply
Reply
M
MiMiaw
Junior Member
Find
11
10-03-2016, 12:45 AM
#4
That's right, you're correct about your external IP. It used to begin with 73, which might explain why it wasn't obvious. Securing access could mean reserving that IP and setting up a port forward, though it does feel like sharing a door with the world.
Reply
Reply
M
MiMiaw
10-03-2016, 12:45 AM #4

That's right, you're correct about your external IP. It used to begin with 73, which might explain why it wasn't obvious. Securing access could mean reserving that IP and setting up a port forward, though it does feel like sharing a door with the world.

Reply
Reply
J
Johan098
Junior Member
Find
5
10-10-2016, 11:02 AM
#5
The top image captures a screenshot of your Linksys routers application. The lower image shows a screenshot of the RF blaster inside the app.
Reply
Reply
J
Johan098
10-10-2016, 11:02 AM #5

The top image captures a screenshot of your Linksys routers application. The lower image shows a screenshot of the RF blaster inside the app.

Reply
Reply
M
macitom
Member
Find
170
10-19-2016, 09:23 PM
#6
The best approach is to resolve the FQDN locally within your network for internal use and point it to an external IP when accessing from outside. If your firewall allows, you can implement a workaround by redirecting traffic destined for public IP addresses back to the correct local address, though this requires careful management without a static IP. You may already have set this up, or it would fail if you're not connected via Wi-Fi, possibly using an UPNP method. If remote control is needed, consider using a key-based SSH session so that visibility remains clear while access is restricted.
Reply
Reply
M
macitom
10-19-2016, 09:23 PM #6

The best approach is to resolve the FQDN locally within your network for internal use and point it to an external IP when accessing from outside. If your firewall allows, you can implement a workaround by redirecting traffic destined for public IP addresses back to the correct local address, though this requires careful management without a static IP. You may already have set this up, or it would fail if you're not connected via Wi-Fi, possibly using an UPNP method. If remote control is needed, consider using a key-based SSH session so that visibility remains clear while access is restricted.

Reply
Reply