# 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:** 16

<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 2, 2017, 4:52pm UTC](https://forums.balena.io/t/cellular-modem-connectivity-issues-on-boot/711/16 "2017-04-02T16:52:37Z")

</div>

Hey Liam, I spent some time trying to reproduce this today, but haven’t been able to get the same behaviour with any of the modems I have here. It’s pretty strange, I am wondering if perhaps its something to do with the `cdma` modems as I am based in Europe, so have only ever tested GSM modems. Perhaps @mccollam has had some success with his CDMA based modems.

It’s also interesting to see these two lines:

```auto
Mar 06 12:08:13 e5882e6 pppd[856]: Terminating on signal 15
Mar 06 12:08:13 e5882e6 NetworkManager[723]: Terminating on signal 15

```

Which seem like something is sending SIGTERM to the pppd and NM. This I suspect is the systemd process in your container when it shutdown during a application stop while updating. So perhaps having `INITSYSTEM=off` will stop the issue from happening?

---

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