# Cross host container linking doesn't work (AWS)
**URL:** https://forums.suse.com/t/cross-host-container-linking-doesnt-work-aws/1396
**Category:** Rancher 1.x
**Created:** [January 6, 2016, 10:32am UTC](https://forums.suse.com/t/cross-host-container-linking-doesnt-work-aws/1396 "2016-01-06T10:32:59Z")
**Posts on this page:** 4
**Page:** 1
### Author:  [@dmetzler](https://forums.suse.com/u/dmetzler)
#### Post date: [January 6, 2016, 10:32am UTC](https://forums.suse.com/t/cross-host-container-linking-doesnt-work-aws/1396/1 "2016-01-06T10:32:59Z")
Hello
I’m trying to setup rancher on AWS.
My current setup is the following :
- 1 host with rancher/server:0.51.0 provisioned with docker-machine
- 3 hosts with rancher/agent provisioned via the rancher UI.
The hosts live in a VPC, in the same subnet and can communicate (SG allows all traffic inside the SG)
When everything is up, the cross host networking doesn’t seems to work. When two containers in a network are on the same host, they can communicate whether when they are on different ones they can’t.
Here is the infrastructure page :
[ ](https://dl.dropboxusercontent.com/s/mwkbg1p0y5u6cuq/Screenshot%202016-01-06%2011.18.12.png?dl=0)
I don’t know where the 172.31.25.41 ip address comes from : it’s not a private or public ip… Sometimes, two hosts have the same IP !
I tryed to re-register the agent by forcing the CATTLE\_IP to the private’s VPC IP but it doesn’t work either.
Where can I try to have some logs about the IPSec networking to try to guess what’s going wrong ? Any advice ?
---
### Author:  [@denise](https://forums.suse.com/u/denise)
#### Post date: [January 8, 2016, 7:07pm UTC](https://forums.suse.com/t/cross-host-container-linking-doesnt-work-aws/1396/2 "2016-01-08T19:07:08Z")
You should be able to re-register the agent and force the `-e CATTLE_AGENT_IP` to the private VPC ID.
What happens when you try to do that?
Is the `172.31.25.41` IP the docker0 bridge IP?
---
### Author:  [@dmetzler](https://forums.suse.com/u/dmetzler)
#### Post date: [January 9, 2016, 6:23am UTC](https://forums.suse.com/t/cross-host-container-linking-doesnt-work-aws/1396/3 "2016-01-09T06:23:37Z")
By forcing to the private VPC ID it works, thx. I tried with the public address, tried to separate the rancher server from the VPC, and a lot of other things… but not this one.
Thx for the answer and kudos to your product it’s awesome !
---
### Author:  [@denise](https://forums.suse.com/u/denise)
#### Post date: [January 11, 2016, 7:27pm UTC](https://forums.suse.com/t/cross-host-container-linking-doesnt-work-aws/1396/4 "2016-01-11T19:27:57Z")