title: Pod accepting socket connection cannot see initiating pod's IP, if located on different kubernetes nodes
body: <p>System: kubernetes cluster running on vagrant using virtualbox <br>
  Pod A: 10.246.79.2 on minion 2 <br>
  Pod B: 10.246.61.3 on minion 3 <br>
  Pod C: 10.246.61.2 on minion 3 </p>
  
  <p>When a container in Pod C accepts a socket connection from Pod A, it sees the peer socket IP as 10.246.79.0, which happens to be the IP address of the flannel0 interface on minion 2.</p>
  
  <p>Is there something wrong with my network configuration? I used the defaults that came with vagrant.</p>
  
  <p>UPDATE:
  Actually, I found that the problem is due to IP Masquerading.  I found this in iptables: <br> </p>
  
  <p>Chain POSTROUTING (policy ACCEPT)  <br>
  num  target     prot opt source               destination          <br>
  1    MASQUERADE  all  --  10.246.79.0/24       0.0.0.0/0    <br> </p>
  
  <p>However, I thought flannel was set up with masquerading turned off: <br>
  [vagrant@kubernetes-minion-2 ~]$ cat /run/flannel/subnet.env  <br>
  FLANNEL_SUBNET=10.246.79.1/24  <br>
  FLANNEL_MTU=1472  <br>
  FLANNEL_IPMASQ=false  <br></p>
  
  <p>So I'm still confused...</p>