similar to: [Bug 1476] xtables-monitor --trace segfaults running inside a container

https://bugzilla.netfilter.org/show_bug.cgi?id=1476 Bug ID: 1476 Summary: xtables-monitor --trace segfaults running inside a container Product: bugzilla Version: other Hardware: x86_64 OS: All Status: NEW Severity: enhancement Priority: P5 Component: netfilter

https://bugzilla.netfilter.org/show_bug.cgi?id=1435 Bug ID: 1435 Summary: segfault when using iptables-nft and iptables-legacy inside a container Product: libnftnl Version: unspecified Hardware: x86_64 OS: All Status: NEW Severity: enhancement Priority: P5 Component:

https://bugzilla.netfilter.org/show_bug.cgi?id=1595 Antonio Ojea <antonio.ojea.garcia at gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |WORKSFORME --- Comment #2 from Antonio Ojea

https://bugzilla.netfilter.org/show_bug.cgi?id=1730 Bug ID: 1730 Summary: nft does not handle IPv6 addresses with embedded IPv4 addresses Product: nftables Version: 1.0.x Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 Component: nft

https://bugzilla.netfilter.org/show_bug.cgi?id=1742 Bug ID: 1742 Summary: using nfqueue breaks SCTP connection (tracking) Product: libnetfilter_queue Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 Component: libnetfilter_queue Assignee:

https://bugzilla.netfilter.org/show_bug.cgi?id=1766 Bug ID: 1766 Summary: nfqueue randomly drops packets with same tuple Product: netfilter/iptables Version: unspecified Hardware: x86_64 OS: All Status: NEW Severity: major Priority: P5 Component: netfilter hooks Assignee:

https://bugzilla.netfilter.org/show_bug.cgi?id=1427 Bug ID: 1427 Summary: can not reuse source port to a DNATed IP if it is being used by another connection Product: netfilter/iptables Version: unspecified Hardware: x86_64 OS: All Status: NEW Severity: normal Priority: P5

https://bugzilla.netfilter.org/show_bug.cgi?id=1728 Bug ID: 1728 Summary: Regression: iptables lock is now waited for without --wait Product: iptables Version: 1.8.x Hardware: x86_64 OS: All Status: NEW Severity: normal Priority: P5 Component: unknown

https://bugzilla.netfilter.org/show_bug.cgi?id=989 Bug ID: 989 Summary: Deprecated function gethostbyaddr used in xtables Product: iptables Version: 1.4.x Hardware: All OS: All Status: NEW Severity: normal Priority: P5 Component: iptables Assignee: netfilter-buglog at

https://bugzilla.netfilter.org/show_bug.cgi?id=1108 Bug ID: 1108 Summary: Need a new release to build nftables --with-xtables Product: iptables Version: CVS (please indicate timestamp) Hardware: All OS: All Status: NEW Severity: normal Priority: P5 Component: iptables

https://bugzilla.netfilter.org/show_bug.cgi?id=1149 Bug ID: 1149 Summary: xtables-eb.c:533: bad test ? Product: netfilter/iptables Version: unspecified Hardware: x86_64 OS: All Status: NEW Severity: enhancement Priority: P5 Component: ip_tables (kernel) Assignee:

https://bugzilla.netfilter.org/show_bug.cgi?id=1112 Bug ID: 1112 Summary: xtables-compat-multi fails to parse comments Product: iptables Version: CVS (please indicate timestamp) Hardware: x86_64 OS: Gentoo Status: NEW Severity: minor Priority: P5 Component: unknown Assignee:

https://bugzilla.netfilter.org/show_bug.cgi?id=982 Bug ID: 982 Summary: vfork() in xtables.c can corrupt stack Product: iptables Version: 1.4.x Hardware: x86_64 OS: other Status: NEW Severity: normal Priority: P5 Component: iptables-restore Assignee: netfilter-buglog at

On Tue, Jul 23, 2013 at 04:56:30PM +0800, hzguanqiang wrote: > Hi Guys, > When I created a lxc container by libvirt, I logged into the lxc > container and noticed that info under /proc/ dir did not match the > lxc container resource. Is the /proc dir in lxc container just > showing the same thing as the lxc host? If I want to monitor the > realtime resource usage inside the lxc

On 07/24/2013 10:28 AM, hzguanqiang wrote: > On 2013-07-23 18:14, "Daniel P. Berrange" <berrange@redhat.com> wrote: > >>> On Tue, Jul 23, 2013 at 04:56:30PM +0800, hzguanqiang wrote: >>> Hi Guys, >>> When I created a lxc container by libvirt, I logged into the lxc >>> container and noticed that info under /proc/ dir did not match the

https://bugzilla.netfilter.org/show_bug.cgi?id=943 Summary: Memory corruption in libxtables/xtables.c + fix Product: iptables Version: 1.4.x Platform: All OS/Version: All Status: NEW Severity: normal Priority: P5 Component: ip6tables AssignedTo: netfilter-buglog at lists.netfilter.org

Hi Guys, When I created a lxc container by libvirt, I logged into the lxc container and noticed that info under /proc/ dir did not match the lxc container resource. Is the /proc dir in lxc container just showing the same thing as the lxc host? If I want to monitor the realtime resource usage inside the lxc container, What should I do? -------------- Best regards! GuanQiang 2013-07-23

------------------------------------------------------------------ Doctoral Symposium of CISTI'2017 12th Iberian Conference on Information Systems and Technologies 14th and 17th of June 2017, ISCTE-IUL, Lisboa, Portugal http://www.cisti.eu/ --------------------------------------------------------------------------- The purpose of CISTI'2017?s Doctoral Symposium is to provide graduate

------------------------------------------------------------------ Doctoral Symposium of CISTI'2017 12th Iberian Conference on Information Systems and Technologies 14th and 17th of June 2017, ISCTE-IUL, Lisboa, Portugal http://www.cisti.eu/ --------------------------------------------------------------------------- The purpose of CISTI'2017?s Doctoral Symposium is to provide graduate

https://bugzilla.netfilter.org/show_bug.cgi?id=1110 Bug ID: 1110 Summary: Build failure if --with-xtables Product: nftables Version: unspecified Hardware: x86_64 OS: other Status: NEW Severity: normal Priority: P5 Component: iptables over nftable Assignee: pablo at