# Cellular Modem connectivity issues on boot

**URL:** <https://forums.balena.io/t/cellular-modem-connectivity-issues-on-boot/711>\
**Category:** Product support\
**Created:** [March 28, 2017, 9:24pm UTC](https://forums.balena.io/t/cellular-modem-connectivity-issues-on-boot/711 "2017-03-28T21:24:46Z")\
**Posts on this page:** 1\
**Showing post:** 22

<div class="post-metadata">

**Author:** ![shaunmulligan](https://sea2.discourse-cdn.com/balena/user_avatar/forums.balena.io/shaunmulligan/32/34_2.png) [@shaunmulligan](https://forums.balena.io/u/shaunmulligan)\
**Post date:** [April 5, 2017, 1:44pm UTC](https://forums.balena.io/t/cellular-modem-connectivity-issues-on-boot/711/22 "2017-04-05T13:44:26Z")

</div>

@liammonahan, yeah my modem doesn’t seem to ever get released. This is really strange. Could you try a really simple base image, not one of the [resin.io](http://resin.io) ones (we add some additional udevd stuff in the container), perhaps if you can try push a simple Dockerfile like:

```auto
FROM armhf/busybox

CMD ["echo", "hello"]

```

That container shouldn’t do anything with udev or anything at all really. if it still disconnect with this, then we will know its an issue in the hostOS, but if this container works fine, then we will know its some weird interaction within the entry point of the [resin.io](http://resin.io) base images.

---

_[View the full topic](https://forums.balena.io/t/cellular-modem-connectivity-issues-on-boot/711)._
