On Tue, Jun 25, 2019 at 11:03 PM He Zhe wrote:
>
>
>
> 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,
> >
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
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
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