# mangOH Red lost 192.168.2.2 IP & MT7697 Setup **URL:** \ **Category:** mangOH Red\ **Created:** [July 31, 2018, 5:35am UTC](https://mangoh.discourse.group/t/mangoh-red-lost-192-168-2-2-ip-mt7697-setup/1774 "2018-07-31T05:35:22Z")\ **Posts on this page:** 1\ **Showing post:** 51
**Author:** ![Madan](https://avatars.discourse-cdn.com/v4/letter/m/6a8cbe/32.png) [@Madan](https://mangoh.discourse.group/u/Madan)\ **Post date:** [October 24, 2018, 5:23pm UTC](https://mangoh.discourse.group/t/mangoh-red-lost-192-168-2-2-ip-mt7697-setup/1774/51 "2018-10-24T17:23:39Z")
@asyal, @davidc I went through the sample code (WiFiClientTest) and observed that it also uses a shell script to initialize `wlan1` and WiFi router connectivity. So, I continued to test my logic again. I figured that there is an issue with GPIO2 - activating this one, causing the PING and any other TCP/HTTP transactions fail from the app and even the overall system (mangOH red). IP configuration is all good. I posted the case as new thread. Please suggest how to resolve this. > [@TCP transactions fail when GPIO2 activated (MT7697 WiFi)](https://mangoh.discourse.group/t/tcp-transactions-fail-when-gpio2-activated-mt7697-wifi/2049): > > Hi All, There is a peculiar behavior observed in our application. I have been investigating the WiFi initiation and connectivity issues during bootup with a legato app initializing WLAN1. Issue under discussion is at [https://mangoh.discourse.group/t/mangoh-red-lost-192-168-2-2-ip-mt7697-setup/1774/46](https://mangoh.discourse.group/t/mangoh-red-lost-192-168-2-2-ip-mt7697-setup/1774/46) Once the Application starts, connectivity to external IPs is lost (ex. a ping command to GoogleDNS, etc). Our app is expected to send a file to an external host. After a step-by-step review a… --- _[View the full topic](https://mangoh.discourse.group/t/mangoh-red-lost-192-168-2-2-ip-mt7697-setup/1774)._