From: Bernhard Thaler <bernhard.thaler@wvnet.at>
To: zh99998@gmail.com
Cc: netfilter@vger.kernel.org
Subject: Re: set route LSRR/SSRR option by iptables or nftables
Date: Sat, 28 May 2016 00:46:35 +0200 [thread overview]
Message-ID: <5748CE4B.60804@wvnet.at> (raw)
In-Reply-To: CAP8bwDWMZ5fkxuX1T5rF-Xbe4Zn8gU0kUWqz93c=5otN2woXag@mail.gmail.com
depending on your setup/requirements, you could use NFQUEUE and e.g.
python nfqueue bindings and scapy to add source routing ip options
-> use NFQUEUE target in OUTPUT or POSTROUTING chain to send packets of
your choosing to a queue
-> write a python program
-> use nfqueue bindings to receive packets from queue
(https://www.wzdftpd.net/blog/nfqueue-bindings.html)
-> use scapy (http://www.secdev.org/projects/scapy/) to add IP Options
and LSRR/SSRR and update the packet
have a look here for some examples:
-> https://5d4a.wordpress.com/2011/08/25/having-fun-with-nfqueue-and-scapy/
-> http://allievi.sssup.it/techblog/archives/631
next reply other threads:[~2016-05-27 22:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-27 22:46 Bernhard Thaler [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-05-13 0:55 set route LSRR/SSRR option by iptables or nftables 神楽坂玲奈
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=5748CE4B.60804@wvnet.at \
--to=bernhard.thaler@wvnet.at \
--cc=netfilter@vger.kernel.org \
--cc=zh99998@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