# Changing to DHCP

**URL:** <https://forums.balena.io/t/changing-to-dhcp/535>\
**Category:** Product support\
**Created:** [January 26, 2017, 8:08pm UTC](https://forums.balena.io/t/changing-to-dhcp/535 "2017-01-26T20:08:38Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![imrehg](https://sea2.discourse-cdn.com/balena/user_avatar/forums.balena.io/imrehg/32/36_2.png) [@imrehg](https://forums.balena.io/u/imrehg)\
**Post date:** [January 26, 2017, 11:46pm UTC](https://forums.balena.io/t/changing-to-dhcp/535/2 "2017-01-26T23:46:55Z")

</div>

You should try to use `dbus` interface to interact with the host OS, including networking (see in the docs about [Container Runtime](https://docs.resin.io/runtime/runtime/) for some overview, and the [dbus communication section in particular](https://docs.resin.io/runtime/runtime/#dbus-communication-with-hostos)).

There are some other posts in the forum that have examples on how to do this (controlling the network interface from within the container), for example [this post](https://forums.balena.io/t/raspberry-pi-3-and-additional-network-dongle/438/5?u=imrehg). Either Connman (the network manager in resinOS 1.x) and NetworkManager (the one used in resinOS 2.x) can be controlled over `dbus`.

In general, network configuration within the container is precarious and have a lot of edge cases. What sort of use case you have in mind for this, if you don’t mind my asking?

---

_[View the full topic](https://forums.balena.io/t/changing-to-dhcp/535)._