{"action":"created","issue":{"url":"https://api.github.com/repos/docker/docker/issues/21926","repository_url":"https://api.github.com/repos/docker/docker","labels_url":"https://api.github.com/repos/docker/docker/issues/21926/labels{/name}","comments_url":"https://api.github.com/repos/docker/docker/issues/21926/comments","events_url":"https://api.github.com/repos/docker/docker/issues/21926/events","html_url":"https://github.com/docker/docker/issues/21926","id":147384904,"number":21926,"title":"Strange behaviour with overlay network and AWS","user":{"login":"adamlc","id":809944,"avatar_url":"https://avatars.githubusercontent.com/u/809944?v=3","gravatar_id":"","url":"https://api.github.com/users/adamlc","html_url":"https://github.com/adamlc","followers_url":"https://api.github.com/users/adamlc/followers","following_url":"https://api.github.com/users/adamlc/following{/other_user}","gists_url":"https://api.github.com/users/adamlc/gists{/gist_id}","starred_url":"https://api.github.com/users/adamlc/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/adamlc/subscriptions","organizations_url":"https://api.github.com/users/adamlc/orgs","repos_url":"https://api.github.com/users/adamlc/repos","events_url":"https://api.github.com/users/adamlc/events{/privacy}","received_events_url":"https://api.github.com/users/adamlc/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/docker/docker/labels/group/networking","name":"group/networking","color":"F6FBFF"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":4,"created_at":"2016-04-11T10:32:40Z","updated_at":"2016-04-12T07:18:42Z","closed_at":null,"body":"I seem to be having a weird issue with my overlay network on AWS. I created an overlay network with the range 192.168.0.0/16, which is working great! But for some reason when a container gets assigned the IP ```192.168.0.21``` nothing can communicate with it, it doesn't seem to make a difference what server its on in the docker swarm. I'll be honest I don't really know here to begin debugging this or how to replicate this. Can anyone help? This could be fixed on 1.10 but AWS are still on 1.9.1 😢 \r\n\r\n**Output of `docker version`:**\r\n\r\n```\r\nClient:\r\n Version:      1.9.1\r\n API version:  1.21\r\n Go version:   go1.4.2\r\n Git commit:   a34a1d5/1.9.1\r\n Built:\r\n OS/Arch:      linux/amd64\r\n\r\nServer:\r\n Version:      1.9.1\r\n API version:  1.21\r\n Go version:   go1.4.2\r\n Git commit:   a34a1d5/1.9.1\r\n Built:\r\n OS/Arch:      linux/amd64\r\n```\r\n\r\n\r\n**Output of `docker info`:**\r\n\r\n```\r\nContainers: 6\r\nImages: 112\r\nServer Version: 1.9.1\r\nStorage Driver: devicemapper\r\n Pool Name: docker-202:1-263652-pool\r\n Pool Blocksize: 65.54 kB\r\n Base Device Size: 107.4 GB\r\n Backing Filesystem:\r\n Data file: /dev/loop0\r\n Metadata file: /dev/loop1\r\n Data Space Used: 5.876 GB\r\n Data Space Total: 107.4 GB\r\n Data Space Available: 44.78 GB\r\n Metadata Space Used: 8.409 MB\r\n Metadata Space Total: 2.147 GB\r\n Metadata Space Available: 2.139 GB\r\n Udev Sync Supported: true\r\n Deferred Removal Enabled: false\r\n Deferred Deletion Enabled: false\r\n Deferred Deleted Device Count: 0\r\n Data loop file: /var/lib/docker/devicemapper/devicemapper/data\r\n Metadata loop file: /var/lib/docker/devicemapper/devicemapper/metadata\r\n Library Version: 1.02.93-RHEL7 (2015-01-28)\r\nExecution Driver: native-0.2\r\nLogging Driver: json-file\r\nKernel Version: 4.1.17-22.30.amzn1.x86_64\r\nOperating System: Amazon Linux AMI 2016.03\r\nCPUs: 2\r\nTotal Memory: 3.862 GiB\r\nName: swarm-node-eu-west1-1c-1\r\nID: F5EH:BZNO:6HR5:MSTB:EYE3:MPBD:GKRX:RM7J:OSIB:ALF7:C4YU:C3RR\r\nCluster store: consul://127.0.0.1:8500\r\nCluster advertise: 10.0.2.26:2375\r\n```\r\n\r\n**Additional environment details (AWS, VirtualBox, physical, etc.):**\r\nWe're on an AWS VPC in EU-West1"},"comment":{"url":"https://api.github.com/repos/docker/docker/issues/comments/208750524","html_url":"https://github.com/docker/docker/issues/21926#issuecomment-208750524","issue_url":"https://api.github.com/repos/docker/docker/issues/21926","id":208750524,"user":{"login":"adamlc","id":809944,"avatar_url":"https://avatars.githubusercontent.com/u/809944?v=3","gravatar_id":"","url":"https://api.github.com/users/adamlc","html_url":"https://github.com/adamlc","followers_url":"https://api.github.com/users/adamlc/followers","following_url":"https://api.github.com/users/adamlc/following{/other_user}","gists_url":"https://api.github.com/users/adamlc/gists{/gist_id}","starred_url":"https://api.github.com/users/adamlc/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/adamlc/subscriptions","organizations_url":"https://api.github.com/users/adamlc/orgs","repos_url":"https://api.github.com/users/adamlc/repos","events_url":"https://api.github.com/users/adamlc/events{/privacy}","received_events_url":"https://api.github.com/users/adamlc/received_events","type":"User","site_admin":false},"created_at":"2016-04-12T07:18:42Z","updated_at":"2016-04-12T07:18:42Z","body":"Thanks for the suggest, unfortunately there doesn't seem to be anything in iptables. If I have some time later I'll go through some of the logs and see if I can figure it out. This is on a production cluster so I don't want to tinker too much!\r\n\r\n```\r\n[ec2-user@swarm-node-eu-west1-1a-1 ~]$ sudo iptables -L -n\r\nChain INPUT (policy ACCEPT)\r\ntarget     prot opt source               destination\r\n\r\nChain FORWARD (policy ACCEPT)\r\ntarget     prot opt source               destination\r\n\r\nChain OUTPUT (policy ACCEPT)\r\ntarget     prot opt source               destination\r\n```"}}