From: Jeff White <jaw171@pitt.edu>
To: Paul Robert Marino <prmarino1@gmail.com>,
Phil Oester <kernel@linuxace.com>
Cc: Abogholo A <abogholo@gmail.com>, netfilter@vger.kernel.org
Subject: Re: why scapy packet no effected by ip tables
Date: Mon, 21 Jul 2014 08:38:26 -0400 [thread overview]
Message-ID: <53CD09C2.2090604@pitt.edu> (raw)
In-Reply-To: <CAPJdpdA7JGd6g9G99sxFUhMTX4-KWkYdnwLjcoxA26C47BPOrw@mail.gmail.com>
Obviously you are doing this for DNS, you need TCP too. If a DNS
request or response is larger than 512 bytes it will use TCP.
Jeff White - GNU+Linux Systems Administrator
University of Pittsburgh - CSSD
On 07/20/2014 12:27 PM, Paul Robert Marino wrote:
> look at ebtables instead.
>
>
> On Thu, Jul 17, 2014 at 11:23 AM, Phil Oester <kernel@linuxace.com> wrote:
>> On Wed, Jul 16, 2014 at 05:16:21PM +0430, Abogholo A wrote:
>>> i wrote this rule for change all udp destination ip address to 8.8.8.8
>>> when dport is 53:
>>>
>>> iptables -t nat -A OUTPUT -p udp -m udp --dport 53 -j DNAT
>>> --to-destination 8.8.8.8
>>>
>>> but when send this packet
>>>
>>> sr1(IP(dst="4.2.2.4")/UDP()/DNS(rd=1,qd=DNSQR(qname="iranled.com")))
>>>
>>> iptables no effected to them
>>>
>>> why?
>>
>> Scapy uses raw sockets, which don't go through iptables.
>>
>> Phil
>> --
>> To unsubscribe from this list: send the line "unsubscribe netfilter" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
> --
> To unsubscribe from this list: send the line "unsubscribe netfilter" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
prev parent reply other threads:[~2014-07-21 12:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-16 12:46 why scapy packet no effected by ip tables Abogholo A
2014-07-17 15:23 ` Phil Oester
2014-07-20 16:27 ` Paul Robert Marino
2014-07-21 12:38 ` Jeff White [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=53CD09C2.2090604@pitt.edu \
--to=jaw171@pitt.edu \
--cc=abogholo@gmail.com \
--cc=kernel@linuxace.com \
--cc=netfilter@vger.kernel.org \
--cc=prmarino1@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).