# IP Routing to container

**URL:** <https://forums.docker.com/t/ip-routing-to-container/8424>\
**Category:** Docker Desktop\
**Tags:** macos\
**Created:** [April 5, 2016, 3:11pm UTC](https://forums.docker.com/t/ip-routing-to-container/8424 "2016-04-05T15:11:21Z")\
**Posts on this page:** 1\
**Showing post:** 14

<div class="post-metadata">

**Author:** ![almirkadric](https://sea3.discourse-cdn.com/docker/user_avatar/forums.docker.com/almirkadric/32/12451_2.png) [@almirkadric](https://forums.docker.com/u/almirkadric)\
**Post date:** [July 27, 2016, 10:10am UTC](https://forums.docker.com/t/ip-routing-to-container/8424/14 "2016-07-27T10:10:55Z")

</div>

This is the same as the following topic

> [@Support tap interface for direct container access (incl. multi-host)](https://forums.docker.com/t/support-tap-interface-for-direct-container-access-incl-multi-host/17835/4):
>
> +1 on this feature I thought this was a hyperkit limitation but it turned out to be a configuration ability issue (or lack there of) reference here: [https://github.com/docker/hyperkit/issues/45](https://github.com/docker/hyperkit/issues/45) Though it would be ideal that docker comes with tap interfaces installed similar to VirtualBox and VMWare. Worst case scenario we should be able to extend the feature set of Moby if the feature is available via third party software (brew install tuntap).

---

_[View the full topic](https://forums.docker.com/t/ip-routing-to-container/8424)._