[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
backtracking forged packets?
- Subject: backtracking forged packets?
- From: ahebert at pubnix.net (Alain Hebert)
- Date: Mon, 16 Mar 2020 11:08:47 -0400
- In-reply-to: <[email protected]>
- References: <CAP-guGVJ6onnkWmLCg60_c5C_X0CNU4Nm=262yMrKLgXXrChtQ@mail.gmail.com> <[email protected]> <[email protected]>
   In my opinion you can, just that the participants are not willing
to do so due, in part, to the lack of acceptance of BCP38.
-----
Alain Hebert ahebert at pubnix.net
PubNIX Inc.
50 boul. St-Charles
P.O. Box 26770 Beaconsfield, Quebec H9W 6G7
Tel: 514-990-5911 http://www.pubnix.net Fax: 514-990-9443
On 2020-03-14 07:35, nanog at jack.fr.eu.org wrote:
> This is the issue (and the leitmotiv) of forged packets: you cannot
> trace their origin in real world situation
>
>
> On 3/14/20 12:03 PM, Jean | ddostest.me via NANOG wrote:
>> Hi Bill,
>>
>> can you post some forged packets please? You can send them offlist if
>> you prefer.
>>
>> It seems to be similar to what Octopus experience few weeks ago on this
>> list.
>>
>> Thanks
>>
>> Jean St-Laurent | CISSP #634103
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nanog.org/pipermail/nanog/attachments/20200316/8ca86f86/attachment.html>