<br><br><div class="gmail_quote">2012/6/12 Fajar A. Nugraha <span dir="ltr"><<a href="mailto:list@fajar.net" target="_blank">list@fajar.net</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>On Tue, Jun 12, 2012 at 12:23 PM, Sébastien Montagne<br>
<<a href="mailto:sebastien.montagne@gmail.com" target="_blank">sebastien.montagne@gmail.com</a>> wrote:<br>
><br>
> It seems that ARP reply is not seen in guest's eth0...<br>
<br>
<br>
</div>Well, fix that :)<br>
<div><br>
<br>
> Guest netstat -nr :<br>
><br>
> # netstat -nr<br>
> Kernel IP routing table<br>
> Destination Gateway Genmask Flags MSS Window irtt<br>
> Iface<br>
> 91.121.99.0 0.0.0.0 255.255.255.0 U 0 0 0<br>
> eth0<br>
><br>
><br>
> Running route add -host 91.121.99.254 eth0<br>
<br>
</div>You shouldn't need to execute that command. Ever.<br>
<div><br>
<br>
><br>
> Running route del -net <a href="http://91.121.99.0/24" target="_blank">91.121.99.0/24</a> gw 0.0.0.0 eth0<br>
<br>
</div>... and neither does that command. Ever.<br>
<div><br>
<br>
> Guest tcpdump -n -i eth0 host 91.121.99.254 :<br>
> # tcpdump -n -i eth0 host 91.121.99.254<br>
> tcpdump: verbose output suppressed, use -v or -vv for full protocol decode<br>
> listening on eth0, link-type EN10MB (Ethernet), capture size 65535 bytes<br>
> 07:13:35.725768 ARP, Request who-has 91.121.99.254 tell 91.121.99.167,<br>
> length 28<br>
> 07:13:36.741762 ARP, Request who-has 91.121.99.254 tell 91.121.99.167,<br>
> length 28<br>
<br>
><br>
</div><div>> Host tcpdump -n -i br0 host 91.121.99.254 :<br>
> # tcpdump -n -i br0 host 91.121.99.254<br>
> tcpdump: WARNING: br0: no IPv4 address assigned<br>
> tcpdump: verbose output suppressed, use -v or -vv for full protocol decode<br>
> listening on br0, link-type EN10MB (Ethernet), capture size 65535 bytes<br>
> 07:15:09.221773 ARP, Request who-has 91.121.99.254 tell 91.121.99.167,<br>
> length 28<br>
> 07:15:09.222176 ARP, Reply 91.121.99.254 is-at 00:00:0c:07:ac:01, length 46<br>
<br>
</div>Try tcpdump on your container's veth interface on host side (from your<br>
example, it was vethZkMxv3). This can help isolate whether the problem<br>
is in the host (e.g. host firewall) or veth pair (unlikely, but worth<br>
to try). </blockquote><div><br></div><div>Thank you.</div><div>I'll try it as soon as possible (server maintenance right now).</div><div><br> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Also:<br>
<br>
- disable firewall (e.g. iptables) in the host temporarily, if active<br></blockquote><div><br></div><div>No firewall on my system.</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
- try simple setup first, with IPv4 in both host and guest<br>
</blockquote><div><br></div><div>It is a hosted server ; I have only 1 available IPv4 address for now.</div><div><br></div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
- make sure the switch/router your server connected to supports<br>
multiple MAC on the same port<br></blockquote><div><br></div><div>I think I use only *one* MAC address : the one my provider gave for my host.</div><div><div>It is the same in </div><div><br></div><div>Here is the information the provider gave :</div>
<div><i>IP : <span style="white-space:pre-wrap"> </span>91.121.99.167</i></div><div><i>IPv6 : <span style="white-space:pre-wrap"> </span>2001:41d0:1:98a7::/64</i></div><div><i>MAC : <span style="white-space:pre-wrap"> </span>00:1C:C0:17:8B:44</i></div>
</div><div><br></div><div><br></div><div>Or, do you mean the host veth generated interface seems to have created one of its own ?</div><div><br></div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
If you're using a hosted server, the last one might be the source of<br>
problem as many provider doesn't allow that.</blockquote><div><br></div><div>Okay :(</div><div><br></div><div><br></div><div>Do you think it would be possible to solve the problem with e.g. information in /etc/ethers ?</div>
<div><br></div><div><br></div><div>Thank you Fajar ! </div></div>