> Von: Tomasz Chmielewski [mailto:man...@wpkg.org]
>
> On 2015-11-10 01:22, Fiedler Roman wrote:
>
> >> # iptables -A INPUT -p tcp --dport 22 -j ACCEPT
> >
> > Yes, also here.
> >
> > Compare
> >
> > iptables-save
> >
> > with
> >
> > iptables-save -t filter
> >
> > Later should work. I think, th
On 2015-11-10 01:22, Fiedler Roman wrote:
# iptables -A INPUT -p tcp --dport 22 -j ACCEPT
Yes, also here.
Compare
iptables-save
with
iptables-save -t filter
Later should work. I think, that some special tables cannot be read in
unpiv
(mangle perhaps).
It seems to behave just like "ipt
> Von: lxc-users [mailto:lxc-users-boun...@lists.linuxcontainers.org] Im
> Auftrag
>
> For some, reason, iptables-save does not seem to be working in
> unprivileged containers.
>
> To reproduce:
>
> - this adds a sample iptables rule:
>
> # iptables -A INPUT -p tcp --dport 22 -j ACCEPT
Yes, also
For some, reason, iptables-save does not seem to be working in
unprivileged containers.
To reproduce:
- this adds a sample iptables rule:
# iptables -A INPUT -p tcp --dport 22 -j ACCEPT
- this lists the rule:
# iptables -L -v -n
Chain INPUT (policy ACCEPT 13166 packets, 5194K bytes)
pkts b
