From: He Zhe
Since v5.1-rc1, some types of packets do not get unreachable reply with the
following iptables setting. Fox example,
$ iptables -A INPUT -p icmp --icmp-type 8 -j REJECT
$ ping 127.0.0.1 -c 1
PING 127.0.0.1 (127.0.0.1) 56(84) bytes of data.
— 127.0.0.1 ping statistics —
1 packets
Hi Bruce,
Have you ever met the following error with features/security/security.scc, when
running qemux86?
...
[ **] A start job is running for Load Kernel Modules (7min 26s / 7min 31s)
* systemd-modules-load.service - Load Kernel Modules
Loaded: loaded
On 6/26/19 10:49 AM, Bruce Ashfield wrote:
> On Tue, Jun 25, 2019 at 10:25 AM He Zhe wrote:
>> Hi Bruce,
>>
>> Have you ever met the following error with features/security/security.scc,
>> when running qemux86?
> Hmm. No, I haven't seen that.
>
> My old builds were using sysvinit, so I didn't
On Tue, Jun 25, 2019 at 11:00 PM Bruce Ashfield
wrote:
>
> On Tue, Jun 25, 2019 at 6:15 AM wrote:
> >
> > From: He Zhe
> >
> > Since v5.1-rc1, some types of packets do not get unreachable reply with the
> > following iptables setting. Fox example,
>
> So what's the upstream status of this ? (I
On Tue, Jun 25, 2019 at 6:15 AM wrote:
>
> From: He Zhe
>
> Since v5.1-rc1, some types of packets do not get unreachable reply with the
> following iptables setting. Fox example,
So what's the upstream status of this ? (I haven't checked netdev yet).
Bruce
>
> $ iptables -A INPUT -p icmp
On Tue, Jun 25, 2019 at 10:25 AM He Zhe wrote:
>
> Hi Bruce,
>
> Have you ever met the following error with features/security/security.scc,
> when running qemux86?
Hmm. No, I haven't seen that.
My old builds were using sysvinit, so I didn't have a recent build
ready to go. But I just started a
On 6/26/19 11:00 AM, Bruce Ashfield wrote:
> On Tue, Jun 25, 2019 at 6:15 AM wrote:
>> From: He Zhe
>>
>> Since v5.1-rc1, some types of packets do not get unreachable reply with the
>> following iptables setting. Fox example,
> So what's the upstream status of this ? (I haven't checked netdev