On Sun, Mar 17, 2013 at 8:49 PM, Roberto Aloi <prof...@gmail.com> wrote:
> Hi Fajar,
>
> thanks for your reply.
>
> I'm pretty sure EC2 only allows one IP address, so you can't arbitrarily
>> use another one, even on the same segment.
>>
>
> The idea is to expose a number of ports, which the clients can use to
> establish TCP connections with the individual containers. So, having
> individual IP addresses exposed to the outer world shouldn't represent a
> problem.
>
>
>> In your case however, I'd examine the output of "netstat -nr" and "brctl
>> show". The ping packets should've been sent from 10.0.3.1 (the bridge), so
>> it's odd that 10.0.67.72 complains about "Destination Host Unreachable". At
>> first glance that indicates routing or interface setup error on your bridge.
>>
>
> Output from `netstat`:
>
> $ netstat -nr
> Kernel IP routing table
> Destination Gateway Genmask Flags MSS Window irtt
> Iface
> 0.0.0.0 10.0.0.1 0.0.0.0 UG 0 0 0
> eth0
> 10.0.0.0 0.0.0.0 255.255.0.0 U 0 0 0
> eth0
> 10.0.0.0 0.0.0.0 255.255.0.0 U 0 0 0
> br0
>
>
>
I'd say it's netmask problem.
At the very least, your br0 should use 255.255.255.0 instead of 255.255.0.0.
--
Fajar
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_mar
_______________________________________________
Lxc-users mailing list
Lxc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lxc-users
