Stephane Grabber closed my report without investigating the evidence. He says it is a firewall or a Kernel bug. If this a Kernel bug, he needs to act, because I don't upgrade the Kernels, Ubuntu does it. And there is no firewall in my LXC host. I am complaining tomorrow to Canonical.
On Mon, Nov 7, 2016 at 1:49 PM, Saint Michael <[email protected]> wrote: > I already open a ticket > https://github.com/lxc/lxc/issues/1284 > > On Mon, Nov 7, 2016 at 1:43 PM, Saint Michael <[email protected]> wrote: > >> The issue is very simple, and it started a few days ago, after an update. >> You cannot communicate from the same network to a container, but from the >> container you can initiate any connection just fine. >> Also from outside my network I can ssh into a container and ping. From >> the same network I cannot even ping a container. >> >> >> >> On Mon, Nov 7, 2016 at 1:29 PM, Judd Meinders < >> [email protected]> wrote: >> >>> On Mon, Nov 7, 2016 at 12:10 PM, Saint Michael <[email protected]> >>> wrote: >>> > >>> > Does anybody know how to open a bug with LXC? >>> > I cannot figure it out. Ubuntu does point me to another site, but I >>> cannot see how to open a new ticket. >>> > >>> > >>> > >>> > _______________________________________________ >>> > lxc-users mailing list >>> > [email protected] >>> > http://lists.linuxcontainers.org/listinfo/lxc-users >>> >>> https://github.com/lxc/lxc/issues >>> >>> If you can, include steps to reproduce the issue, software versions, >>> configs, workarounds, etc. A well formed and organized issue will get >>> more attention. >>> >>> -- >>> Judd Meinders >>> _______________________________________________ >>> lxc-users mailing list >>> [email protected] >>> http://lists.linuxcontainers.org/listinfo/lxc-users >> >> >> >
_______________________________________________ lxc-users mailing list [email protected] http://lists.linuxcontainers.org/listinfo/lxc-users
