<div dir="ltr"><div class="gmail_default" style="font-size:small">I understand how you see it. <br></div><div class="gmail_default" style="font-size:small">Maybe it was my mistake to get on the LXC bandwagon two years ago. I should not bet my business on a non-commercial, unsupported software.<br></div><div class="gmail_default" style="font-size:small">Now it is too late.<br><br><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Nov 8, 2016 at 1:26 PM, Serge E. Hallyn <span dir="ltr"><<a href="mailto:serge@hallyn.com" target="_blank">serge@hallyn.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Stéphane was helpfully pointing you in the direction of where the problem<br>
probably lies. Don't read it as "your problem isn't important so I'm<br>
closing it", read it as "your problem sounds like it could be x or y."<br>
<br>
<a href="http://github.com/lxc/lxc" rel="noreferrer" target="_blank">github.com/lxc/lxc</a> tracks upstream lxc. This is independent of Ubuntu.<br>
If you want to file an ubuntu bug, go to<br>
<a href="https://launchpad.net/ubuntu/+source/lxc" rel="noreferrer" target="_blank">https://launchpad.net/ubuntu/+<wbr>source/lxc</a> or<br>
<a href="https://launchpad.net/ubuntu/+source/linux" rel="noreferrer" target="_blank">https://launchpad.net/ubuntu/+<wbr>source/linux</a> for the kernel, and hit<br>
'Report a bug' on the right. (Or if you pay for support go through your<br>
support channel)<br>
<br>
<a href="http://github.com/lxc/lxc" rel="noreferrer" target="_blank">github.com/lxc/lxc</a> is also an independent volunteer project, so the entitlement<br>
in this message is unwarranted. If I show up to help move your couch in my<br>
free time, you can't complain that I didn't paint your walls. The message<br>
closing your issue was a very polite, respectful, and helpful one.<br>
<br>
I understand that as a user you don't really want to have to care about<br>
who's providing what software, but everyone will be able to do their jobs<br>
much better if they can focus on what they focus on.<br>
<span class="HOEnZb"><font color="#888888"><br>
-serge<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
Quoting Saint Michael (<a href="mailto:venefax@gmail.com">venefax@gmail.com</a>):<br>
> Stephane Grabber closed my report without investigating the evidence. He<br>
> says it is a firewall or a Kernel bug. If this a Kernel bug, he needs to<br>
> act, because I don't upgrade the Kernels, Ubuntu does it. And there is no<br>
> firewall in my LXC host.<br>
> I am complaining tomorrow to Canonical.<br>
><br>
> On Mon, Nov 7, 2016 at 1:49 PM, Saint Michael <<a href="mailto:venefax@gmail.com">venefax@gmail.com</a>> wrote:<br>
><br>
> > I already open a ticket<br>
> > <a href="https://github.com/lxc/lxc/issues/1284" rel="noreferrer" target="_blank">https://github.com/lxc/lxc/<wbr>issues/1284</a><br>
> ><br>
> > On Mon, Nov 7, 2016 at 1:43 PM, Saint Michael <<a href="mailto:venefax@gmail.com">venefax@gmail.com</a>> wrote:<br>
> ><br>
> >> The issue is very simple, and it started a few days ago, after an update.<br>
> >> You cannot communicate from the same network to a container, but from the<br>
> >> container you can initiate any connection just fine.<br>
> >> Also from outside my network I can ssh into a container and ping. From<br>
> >> the same network I cannot even ping a container.<br>
> >><br>
> >><br>
> >><br>
> >> On Mon, Nov 7, 2016 at 1:29 PM, Judd Meinders <<br>
> >> <a href="mailto:judd.meinders@rockwellcollins.com">judd.meinders@rockwellcollins.<wbr>com</a>> wrote:<br>
> >><br>
> >>> On Mon, Nov 7, 2016 at 12:10 PM, Saint Michael <<a href="mailto:venefax@gmail.com">venefax@gmail.com</a>><br>
> >>> wrote:<br>
> >>> ><br>
> >>> > Does anybody know how to open a bug with LXC?<br>
> >>> > I cannot figure it out. Ubuntu does point me to another site, but I<br>
> >>> cannot see how to open a new ticket.<br>
> >>> ><br>
> >>> ><br>
> >>> ><br>
> >>> > ______________________________<wbr>_________________<br>
> >>> > lxc-users mailing list<br>
> >>> > <a href="mailto:lxc-users@lists.linuxcontainers.org">lxc-users@lists.<wbr>linuxcontainers.org</a><br>
> >>> > <a href="http://lists.linuxcontainers.org/listinfo/lxc-users" rel="noreferrer" target="_blank">http://lists.linuxcontainers.<wbr>org/listinfo/lxc-users</a><br>
> >>><br>
> >>> <a href="https://github.com/lxc/lxc/issues" rel="noreferrer" target="_blank">https://github.com/lxc/lxc/<wbr>issues</a><br>
> >>><br>
> >>> If you can, include steps to reproduce the issue, software versions,<br>
> >>> configs, workarounds, etc. A well formed and organized issue will get<br>
> >>> more attention.<br>
> >>><br>
> >>> --<br>
> >>> Judd Meinders<br>
> >>> ______________________________<wbr>_________________<br>
> >>> lxc-users mailing list<br>
> >>> <a href="mailto:lxc-users@lists.linuxcontainers.org">lxc-users@lists.<wbr>linuxcontainers.org</a><br>
> >>> <a href="http://lists.linuxcontainers.org/listinfo/lxc-users" rel="noreferrer" target="_blank">http://lists.linuxcontainers.<wbr>org/listinfo/lxc-users</a><br>
> >><br>
> >><br>
> >><br>
> ><br>
<br>
> ______________________________<wbr>_________________<br>
> lxc-users mailing list<br>
> <a href="mailto:lxc-users@lists.linuxcontainers.org">lxc-users@lists.<wbr>linuxcontainers.org</a><br>
> <a href="http://lists.linuxcontainers.org/listinfo/lxc-users" rel="noreferrer" target="_blank">http://lists.linuxcontainers.<wbr>org/listinfo/lxc-users</a><br>
<br>
______________________________<wbr>_________________<br>
lxc-users mailing list<br>
<a href="mailto:lxc-users@lists.linuxcontainers.org">lxc-users@lists.<wbr>linuxcontainers.org</a><br>
<a href="http://lists.linuxcontainers.org/listinfo/lxc-users" rel="noreferrer" target="_blank">http://lists.linuxcontainers.<wbr>org/listinfo/lxc-users</a></div></div></blockquote></div><br></div>