# Networking goes randomly down

**URL:** <https://forums.suse.com/t/networking-goes-randomly-down/6791>\
**Category:** Rancher 1.x\
**Created:** [July 4, 2017, 11:57am UTC](https://forums.suse.com/t/networking-goes-randomly-down/6791 "2017-07-04T11:57:48Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Dr\_No](https://avatars.discourse-cdn.com/v4/letter/d/9f8e36/32.png) [@Dr\_No](https://forums.suse.com/u/Dr_No)\
**Post date:** [July 4, 2017, 11:57am UTC](https://forums.suse.com/t/networking-goes-randomly-down/6791/1 "2017-07-04T11:57:48Z")

</div>

The Networking between the hosts goes randomly down for no reason. When I reboot the host where rancher server is located, everything goes back to normal and I can ping all other hosts.  
I use 3 hosts who are all on the same Subnet with Private IPs.

---

<div class="post-metadata">

**Author:** ![bacheson](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/bacheson/32/2881_2.png) [@bacheson](https://forums.suse.com/u/bacheson)\
**Post date:** [July 4, 2017, 3:50pm UTC](https://forums.suse.com/t/networking-goes-randomly-down/6791/2 "2017-07-04T15:50:33Z")

</div>

This has been an issue for years. I just stopped using the rancher managed network.

---

<div class="post-metadata">

**Author:** ![Dr\_No](https://avatars.discourse-cdn.com/v4/letter/d/9f8e36/32.png) [@Dr\_No](https://forums.suse.com/u/Dr_No)\
**Post date:** [July 4, 2017, 6:12pm UTC](https://forums.suse.com/t/networking-goes-randomly-down/6791/3 "2017-07-04T18:12:55Z")

</div>

What do you suggest, that I can use instead?

---

<div class="post-metadata">

**Author:** ![bacheson](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/bacheson/32/2881_2.png) [@bacheson](https://forums.suse.com/u/bacheson)\
**Post date:** [July 5, 2017, 1:29pm UTC](https://forums.suse.com/t/networking-goes-randomly-down/6791/4 "2017-07-05T13:29:31Z")

</div>

I’m on Google Cloud so I just use my own private network for internal services (redis, mysql, influxdb, beanstalk etc.)

I launch each internal service (network=host) with each container exposing the necessary port to the private network only.

I then launch my other containers (network=host) and hardcode all private ips using environment variables. This has allowed me to run hundreds of containers without the constant network failures I was getting with rancher’s managed network.

Regardless at the container velocity I’m dealing with you must use ips to sidestep DNS, it becomes another point of failure.

---

<div class="post-metadata">

**Author:** ![leodotcloud](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/leodotcloud/32/3103_2.png) [@leodotcloud](https://forums.suse.com/u/leodotcloud)\
**Post date:** [August 10, 2017, 7:01pm UTC](https://forums.suse.com/t/networking-goes-randomly-down/6791/5 "2017-08-10T19:01:59Z")

</div>

@Dr_No and @bacheson can you please check if you are hitting this: [https://github.com/rancher/rancher/issues/9377](https://github.com/rancher/rancher/issues/9377)

```auto
docker exec -it $(docker ps | grep ipsec-router | awk '{print $1}') bash
cat /proc/net/xfrm_stat

```

and check for `XfrmInStateSeqError`.