# Cannot Resolve Host with libcurl

**URL:** <https://forum.legato.io/t/cannot-resolve-host-with-libcurl/2897>\
**Category:** Legato Application Framework\
**Created:** [December 18, 2017, 7:58pm UTC](https://forum.legato.io/t/cannot-resolve-host-with-libcurl/2897 "2017-12-18T19:58:15Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![coffeebean](https://avatars.discourse-cdn.com/v4/letter/c/8e8cbc/32.png) [@coffeebean](https://forum.legato.io/u/coffeebean)\
**Post date:** [December 20, 2017, 6:34pm UTC](https://forum.legato.io/t/cannot-resolve-host-with-libcurl/2897/4 "2017-12-20T18:34:19Z")

</div>

I’ve been diagnosing this problem the past few days, and I’ve found the source of the issue (albeit not a solution). For some reason, when I establish a data connection through my application, the routing table fails to populate correctly.

Here’s the routing table (via `"route -n"`) when I connect to data via `"cm data connect"` in SSH:  
 ![routing_ssh](https://us1.discourse-cdn.com/flex019/uploads/legato1/original/1X/3a03c7eb1c34ef8ee5c572915b1ec527dee5575c.png)

Meanwhile, here it is when I connect through my application:  
 ![routing_app](https://us1.discourse-cdn.com/flex019/uploads/legato1/original/1X/64f1f6f3c775bb53268eaf4ad0c5ab0cdf76621f.png)

Notice how the entry for the gateway is completely missing. Interestingly enough, however, if I run `cm data info` on both instances, a gateway IP is provided.

Is this some sort of permissions issues? Or perhaps something wrong with my Legato installation? I’ve tried resetting the userspace and reinstalling the platform to no avail. Any insight would be greatly appreciated.

---

_[View the full topic](https://forum.legato.io/t/cannot-resolve-host-with-libcurl/2897)._