Claudio,
I think NAT is already configured from what was posted, AFAIK he was
expecting to exit his network by broadcast instead of specifying the IP
address of the DG explicitly
Tony
On Jul 25, 2013 9:17 AM, "Claudio Kuenzler" <c...@claudiokuenzler.com> wrote:
> Ok, I just figured out what's going on.. The network 192.168.1.0 doesn't
>> have a route to known the hosts in the network 192.168.5.0.
>>
>> Is it possible to NAT all the lxc network to route to the 192.168.1.0?
>>
>
> You can create iptables NAT postrouting for the internal (192.168.5.0)
> addresses to use the "public" address of the physical host (192.168.1.x).
> See
> http://www.centos.org/docs/4/4.5/System_Administration_Guide/postrouting-ipmasquerading.html
>
> - sorry, forgot to CC lxc-users
>
>
> ------------------------------------------------------------------------------
> See everything from the browser to the database with AppDynamics
> Get end-to-end visibility with application monitoring from AppDynamics
> Isolate bottlenecks and diagnose root cause in seconds.
> Start your free trial of AppDynamics Pro today!
> http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
> _______________________________________________
> Lxc-users mailing list
> Lxc-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/lxc-users
>
>
------------------------------------------------------------------------------
See everything from the browser to the database with AppDynamics
Get end-to-end visibility with application monitoring from AppDynamics
Isolate bottlenecks and diagnose root cause in seconds.
Start your free trial of AppDynamics Pro today!
http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
_______________________________________________
Lxc-users mailing list
Lxc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lxc-users
