# FX30S 3G, R17: cannot connect to Legato App through 127.0.0.1

**URL:** <https://forum.sierrawireless.com/t/fx30s-3g-r17-cannot-connect-to-legato-app-through-127-0-0-1/20647>\
**Category:** FX30\
**Created:** [June 17, 2020, 8:09am UTC](https://forum.sierrawireless.com/t/fx30s-3g-r17-cannot-connect-to-legato-app-through-127-0-0-1/20647 "2020-06-17T08:09:42Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![andris.pavenis](https://avatars.discourse-cdn.com/v4/letter/a/57b2e6/32.png) [@andris.pavenis](https://forum.sierrawireless.com/u/andris.pavenis)\
**Post date:** [June 17, 2020, 8:09am UTC](https://forum.sierrawireless.com/t/fx30s-3g-r17-cannot-connect-to-legato-app-through-127-0-0-1/20647/1 "2020-06-17T08:09:42Z")

</div>

Noticed following problem with FX30S 3G after update to firmware r17:

- I have legacy app wrapped as Legato app which additionally to other primary functionality (which works both in r14 and r17) listens to 2 network ports
- with firmware r14 and sandboxing connecting to these ports through 127.0.0.1 worked without problems. I could access them also through 192.168.2.2 when connected to USB (not available in production environment except for servicing). I do not want to expose them through rmnet0
- Connecting to these port no more works through 127.0.0.1 after upgrade to r17 both when sandboxed and not sandboxed

Additional information:

- custom built legato 18.06.5 with some additions and some unnecessary parts removed from build (no changes from version I used with firmware r14)

---

<div class="post-metadata">

**Author:** ![cchenry](https://avatars.discourse-cdn.com/v4/letter/c/a183cd/32.png) [@cchenry](https://forum.sierrawireless.com/u/cchenry)\
**Post date:** [June 17, 2020, 4:01pm UTC](https://forum.sierrawireless.com/t/fx30s-3g-r17-cannot-connect-to-legato-app-through-127-0-0-1/20647/2 "2020-06-17T16:01:33Z")

</div>

Hi there,  
I suspect the issue might be related to the firewall. Could you try flushing it and then run you application (do not reboot your FX30S)?  
iptables -F  
BR,  
Chris

---

<div class="post-metadata">

**Author:** ![andris.pavenis](https://avatars.discourse-cdn.com/v4/letter/a/57b2e6/32.png) [@andris.pavenis](https://forum.sierrawireless.com/u/andris.pavenis)\
**Post date:** [June 18, 2020, 5:56am UTC](https://forum.sierrawireless.com/t/fx30s-3g-r17-cannot-connect-to-legato-app-through-127-0-0-1/20647/3 "2020-06-18T05:56:21Z")

</div>

Small script helped:

```
#! /bin/sh
echo app.LegatoAppName >/proc/self/attr/current
telnet 127.0.0.1 9001

```

Is there really necessary to forbid access to localhost address by SMACK label even if app is not sandboxed. I did not have this problem also for sandboxed app with r14

---

<div class="post-metadata">

**Author:** ![andris.pavenis](https://avatars.discourse-cdn.com/v4/letter/a/57b2e6/32.png) [@andris.pavenis](https://forum.sierrawireless.com/u/andris.pavenis)\
**Post date:** [August 3, 2020, 4:49am UTC](https://forum.sierrawireless.com/t/fx30s-3g-r17-cannot-connect-to-legato-app-through-127-0-0-1/20647/4 "2020-08-03T04:49:54Z")

</div>

I’m using own Legato build anyway with some additional applications added and some unnecessary removed

So it would be no problem for me to disable SMACK use in liblegato.

From the other side only 127.0.0.1 is blocked in case of different SMACK labels. One can connect to any  
127.x.y.z (where x.y.z != 0.0.1) without any problems. Currently that solves my problem with localhost

From the other side blocking 127.0.01 as some security precaution is completely non effective as anything as it can easily avoided by using for example 127.0.1.1.