# Perspective Wifi LAN - Host Invalid General advices

**URL:** <https://forum.inductiveautomation.com/t/perspective-wifi-lan-host-invalid-general-advices/32078>\
**Category:** General Discussion\
**Created:** [February 10, 2020, 1:16am UTC](https://forum.inductiveautomation.com/t/perspective-wifi-lan-host-invalid-general-advices/32078 "2020-02-10T01:16:28Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![jespinmartin1](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/jespinmartin1/32/57175_2.png) [@jespinmartin1](https://forum.inductiveautomation.com/u/jespinmartin1)\
**Post date:** [February 10, 2020, 1:16am UTC](https://forum.inductiveautomation.com/t/perspective-wifi-lan-host-invalid-general-advices/32078/1 "2020-02-10T01:16:28Z")

</div>

I know there’s a lot of information about this but I must be missing something. I want to make sure that my problem is regarding my router.

I’m using the perspective app from app store v 0.93 and Ignition 8.0.8 and I want to reach the gateway from my mobile device.

In my LAN network  
-My router is using 192.168.1.1 model HG8245H, with port forwarding 8088 enable

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/2X/1/19d277ce2b05d22386a0806e477debfd497e8115.png)  
 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/2X/7/76222eca4cc503006f11501110034e9ba97867f8.png)

-My gateway is runing in a W10 PC on 192.168.1.9:8088 static IP. I’ve disabled the firewall and even add a port 8088 into firewall configurations. I also tried turning off antivurus and firewall.  
 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/2X/f/fbd2fefb53a378d8918bb1dddb90609264cc2c0a.png)  
 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/2X/d/d74cc23973b4d10a28944180d7ae13846c19d9dc.png)

-iOS 13.3.1 iPhoneX device with static IP 192.168.1.8  
 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/2X/d/de266f1a7b70b6b794faa3fbb01e29c0f1da5782.png)  
On the perspective app I’m trying to add the gateway in this way:  
 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/2X/e/e2257229b3502265ecf4dc31e9ecdeaecd89b271.png)  
Is that the correct typing to add a gateway?

Even my PC has some reply from my mobile device  
 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/2X/9/95d4384e8c024ffe395877ad1ac545499bda9256.png)

What am I missing? please some help!!

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [February 10, 2020, 1:31am UTC](https://forum.inductiveautomation.com/t/perspective-wifi-lan-host-invalid-general-advices/32078/2 "2020-02-10T01:31:02Z")

</div>

I don’t know what the problem is, but your pinhole rule is not applicable. Traffic from 192.168.1.8 to 192.168.1.9 doesn’t go through the router’s NAT, since they are in the same subnet. However, many newer combo wired/wireless routers set up WiFi/LAN isolation by default. That allows “guests” in a household to access the internet, but not interfere with anything else in the house. Look for such a feature in the router’s firmware.

You almost certainly don’t want a NAT pinhole, especially without SSL.

---

<div class="post-metadata">

**Author:** ![jespinmartin1](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/jespinmartin1/32/57175_2.png) [@jespinmartin1](https://forum.inductiveautomation.com/u/jespinmartin1)\
**Post date:** [February 10, 2020, 1:35am UTC](https://forum.inductiveautomation.com/t/perspective-wifi-lan-host-invalid-general-advices/32078/3 "2020-02-10T01:35:58Z")

</div>

I consider this and I made a bridge connection from my Wifi card to my Ethernet card like:

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/2X/4/4bd2257095e49a25c53ef7f8f6b8501281f893ec.png)  
In “Puente de red”  
 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/2X/5/51684e8759551142ad7d8d8b6e0e52049e1159af.png)

So my problem must be with my router right??? something is security or firewall, because I disabled the firewall in the router and everything, but nothing happens.

Thanks about SSL advice, but I don’t see how port 8043 would make a difference.

---

<div class="post-metadata">

**Author:** ![jespinmartin1](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/jespinmartin1/32/57175_2.png) [@jespinmartin1](https://forum.inductiveautomation.com/u/jespinmartin1)\
**Post date:** [February 10, 2020, 2:06am UTC](https://forum.inductiveautomation.com/t/perspective-wifi-lan-host-invalid-general-advices/32078/4 "2020-02-10T02:06:25Z")

</div>

> [@pturmel](#):
>
> pinhole rule

Sir what you mean by Pinhole? I'm not to used to english terms

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [February 10, 2020, 3:27am UTC](https://forum.inductiveautomation.com/t/perspective-wifi-lan-host-invalid-general-advices/32078/5 "2020-02-10T03:27:09Z")

</div>

> [@jespinmartin1](#):
>
> Pinhole

It is the common name for a firewall rule that performs Destination Network Address Translation (DNAT) inwards from a WAN to a LAN. An external client connection to the router public address and a specific port has its destination address munged to the private address of the rule target as the packets travel into the LAN.

Generic NAT is more properly known as Source Network Address Translation, outwards from LAN to WAN. An internal client connection to an address on the WAN side has the LAN source address munged to the routers WAN address on the way out so replies are routeable. This requires the router to maintain a state table so replies can be forwarded to the correct internal client.

Source NAT outbound is generally not port-specific (though it can be)--any port numbers may be used--so is conceptually a "wide-open window" view out to the world. Destination NAT inbound is almost always port-specific (though there are 1:1 NAT applications), so is conceptually a "tiny pinhole" view into the local network.

---

<div class="post-metadata">

**Author:** ![jespinmartin1](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/jespinmartin1/32/57175_2.png) [@jespinmartin1](https://forum.inductiveautomation.com/u/jespinmartin1)\
**Post date:** [March 6, 2020, 1:28am UTC](https://forum.inductiveautomation.com/t/perspective-wifi-lan-host-invalid-general-advices/32078/6 "2020-03-06T01:28:36Z")

</div>

The problem was in the firmware version installed on a modem of my ISP. I just updated the firmware and it was solved
