<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	
	>
<channel>
	<title>
	Comments on: How to code Packet Sniffer in C with Sockets on Linux	</title>
	<atom:link href="https://www.binarytides.com/packet-sniffer-code-c-linux/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.binarytides.com/packet-sniffer-code-c-linux/</link>
	<description>News, Technology, Entertainment and more</description>
	<lastBuildDate>Sat, 18 Sep 2021 04:34:48 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.8.2</generator>
	<item>
		<title>
		By: Rohit Pradhan		</title>
		<link>https://www.binarytides.com/packet-sniffer-code-c-linux/comment-page-1/#comment-324274</link>

		<dc:creator><![CDATA[Rohit Pradhan]]></dc:creator>
		<pubDate>Sat, 18 Sep 2021 04:34:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.binarytides.com/blog/?p=48#comment-324274</guid>

					<description><![CDATA[Is there an equivalent code for this project in C++?]]></description>
			<content:encoded><![CDATA[<p>Is there an equivalent code for this project in C++?</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Khupmalsawm Singson		</title>
		<link>https://www.binarytides.com/packet-sniffer-code-c-linux/comment-page-1/#comment-288529</link>

		<dc:creator><![CDATA[Khupmalsawm Singson]]></dc:creator>
		<pubDate>Wed, 21 Oct 2020 21:30:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.binarytides.com/blog/?p=48#comment-288529</guid>

					<description><![CDATA[In reply to &lt;a href=&quot;https://www.binarytides.com/packet-sniffer-code-c-linux/comment-page-1/#comment-158869&quot;&gt;yifabao&lt;/a&gt;.

Its interesting and i would like to know more]]></description>
			<content:encoded><![CDATA[<p>In reply to <a href="https://www.binarytides.com/packet-sniffer-code-c-linux/comment-page-1/#comment-158869">yifabao</a>.</p>
<p>Its interesting and i would like to know more</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: yifabao		</title>
		<link>https://www.binarytides.com/packet-sniffer-code-c-linux/comment-page-1/#comment-158869</link>

		<dc:creator><![CDATA[yifabao]]></dc:creator>
		<pubDate>Sun, 27 May 2018 10:00:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.binarytides.com/blog/?p=48#comment-158869</guid>

					<description><![CDATA[Thank you for your code,it help me to understand TCP well!]]></description>
			<content:encoded><![CDATA[<p>Thank you for your code,it help me to understand TCP well!</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Juan Mamani		</title>
		<link>https://www.binarytides.com/packet-sniffer-code-c-linux/comment-page-1/#comment-154430</link>

		<dc:creator><![CDATA[Juan Mamani]]></dc:creator>
		<pubDate>Thu, 08 Feb 2018 18:44:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.binarytides.com/blog/?p=48#comment-154430</guid>

					<description><![CDATA[Really thanks for sharing source code!]]></description>
			<content:encoded><![CDATA[<p>Really thanks for sharing source code!</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Paulo		</title>
		<link>https://www.binarytides.com/packet-sniffer-code-c-linux/comment-page-1/#comment-133511</link>

		<dc:creator><![CDATA[Paulo]]></dc:creator>
		<pubDate>Wed, 04 Oct 2017 13:01:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.binarytides.com/blog/?p=48#comment-133511</guid>

					<description><![CDATA[I made some changes in order to fit into my needs. :)

It worked like a charm.

Thank you very much.]]></description>
			<content:encoded><![CDATA[<p>I made some changes in order to fit into my needs. :)</p>
<p>It worked like a charm.</p>
<p>Thank you very much.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: suraj kumar		</title>
		<link>https://www.binarytides.com/packet-sniffer-code-c-linux/comment-page-1/#comment-115800</link>

		<dc:creator><![CDATA[suraj kumar]]></dc:creator>
		<pubDate>Mon, 24 Apr 2017 08:00:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.binarytides.com/blog/?p=48#comment-115800</guid>

					<description><![CDATA[HOW TO EXTRACT THE WEBSITE ADDRESS FROM SOURCE AND DESTINATION ADDRESS??

i got the output as:


***********************TCP Packet*************************

IP Header
   &#124;-IP Version        : 4
   &#124;-IP Header Length  : 5 DWORDS or 20 Bytes
   &#124;-Type Of Service   : 40
   &#124;-IP Total Length   : 52  Bytes(Size of Packet)
   &#124;-Identification    : 19032
   &#124;-TTL      : 55
   &#124;-Protocol : 6
   &#124;-Checksum : 43676
   &#124;-Source IP        : 117.18.237.29
   &#124;-Destination IP   : 192.168.43.207

TCP Header
   &#124;-Source Port      : 80
   &#124;-Destination Port : 56273
   &#124;-Sequence Number    : 1092319184
   &#124;-Acknowledge Number : 1740369094
   &#124;-Header Length      : 8 DWORDS or 32 BYTES
   &#124;-Urgent Flag          : 0
   &#124;-Acknowledgement Flag : 1
   &#124;-Push Flag            : 0
   &#124;-Reset Flag           : 0
   &#124;-Synchronise Flag     : 0
   &#124;-Finish Flag          : 0
   &#124;-Window         : 287
   &#124;-Checksum       : 58902
   &#124;-Urgent Pointer : 0

                        DATA Dump                         
IP Header
    45 28 00 34 4A 58 40 00 37 06 AA 9C 75 12 ED 1D         E(.4JX@.7...u...
    C0 A8 2B CF                                             ..+.
TCP Header
    00 50 DB D1 41 1B 77 D0 67 BB EC C6 80 10 01 1F         .P..A.w.g...\80...
    E6 16 00 00 01 01 08 0A 0F 9D 5C DD 00 09 EA CC         ..........\.....
Data Payload]]></description>
			<content:encoded><![CDATA[<p>HOW TO EXTRACT THE WEBSITE ADDRESS FROM SOURCE AND DESTINATION ADDRESS??</p>
<p>i got the output as:</p>
<p>***********************TCP Packet*************************</p>
<p>IP Header<br />
   |-IP Version        : 4<br />
   |-IP Header Length  : 5 DWORDS or 20 Bytes<br />
   |-Type Of Service   : 40<br />
   |-IP Total Length   : 52  Bytes(Size of Packet)<br />
   |-Identification    : 19032<br />
   |-TTL      : 55<br />
   |-Protocol : 6<br />
   |-Checksum : 43676<br />
   |-Source IP        : 117.18.237.29<br />
   |-Destination IP   : 192.168.43.207</p>
<p>TCP Header<br />
   |-Source Port      : 80<br />
   |-Destination Port : 56273<br />
   |-Sequence Number    : 1092319184<br />
   |-Acknowledge Number : 1740369094<br />
   |-Header Length      : 8 DWORDS or 32 BYTES<br />
   |-Urgent Flag          : 0<br />
   |-Acknowledgement Flag : 1<br />
   |-Push Flag            : 0<br />
   |-Reset Flag           : 0<br />
   |-Synchronise Flag     : 0<br />
   |-Finish Flag          : 0<br />
   |-Window         : 287<br />
   |-Checksum       : 58902<br />
   |-Urgent Pointer : 0</p>
<p>                        DATA Dump<br />
IP Header<br />
    45 28 00 34 4A 58 40 00 37 06 AA 9C 75 12 ED 1D         E(.4JX@.7&#8230;u&#8230;<br />
    C0 A8 2B CF                                             ..+.<br />
TCP Header<br />
    00 50 DB D1 41 1B 77 D0 67 BB EC C6 80 10 01 1F         .P..A.w.g&#8230;\80&#8230;<br />
    E6 16 00 00 01 01 08 0A 0F 9D 5C DD 00 09 EA CC         &#8230;&#8230;&#8230;.\&#8230;..<br />
Data Payload</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Veerendra		</title>
		<link>https://www.binarytides.com/packet-sniffer-code-c-linux/comment-page-1/#comment-100362</link>

		<dc:creator><![CDATA[Veerendra]]></dc:creator>
		<pubDate>Fri, 16 Dec 2016 12:32:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.binarytides.com/blog/?p=48#comment-100362</guid>

					<description><![CDATA[In reply to &lt;a href=&quot;https://www.binarytides.com/packet-sniffer-code-c-linux/comment-page-1/#comment-47567&quot;&gt;Mayank&lt;/a&gt;.

this might helpful to you :)  written in python --&#062;https://github.com/veerendra2/wifi-deauth-attack]]></description>
			<content:encoded><![CDATA[<p>In reply to <a href="https://www.binarytides.com/packet-sniffer-code-c-linux/comment-page-1/#comment-47567">Mayank</a>.</p>
<p>this might helpful to you :)  written in python &#8211;&gt;<a href="https://github.com/veerendra2/wifi-deauth-attack" rel="nofollow ugc">https://github.com/veerendra2/wifi-deauth-attack</a></p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: fleur		</title>
		<link>https://www.binarytides.com/packet-sniffer-code-c-linux/comment-page-1/#comment-95708</link>

		<dc:creator><![CDATA[fleur]]></dc:creator>
		<pubDate>Mon, 10 Oct 2016 07:50:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.binarytides.com/blog/?p=48#comment-95708</guid>

					<description><![CDATA[In reply to &lt;a href=&quot;https://www.binarytides.com/packet-sniffer-code-c-linux/comment-page-1/#comment-66032&quot;&gt;aysh&lt;/a&gt;.

Hi 
do you have a report or conception of this sniffer!!
please help me]]></description>
			<content:encoded><![CDATA[<p>In reply to <a href="https://www.binarytides.com/packet-sniffer-code-c-linux/comment-page-1/#comment-66032">aysh</a>.</p>
<p>Hi<br />
do you have a report or conception of this sniffer!!<br />
please help me</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Anand KR		</title>
		<link>https://www.binarytides.com/packet-sniffer-code-c-linux/comment-page-1/#comment-90096</link>

		<dc:creator><![CDATA[Anand KR]]></dc:creator>
		<pubDate>Fri, 29 Jul 2016 07:28:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.binarytides.com/blog/?p=48#comment-90096</guid>

					<description><![CDATA[Hi,

How can we extract &quot;ethernet header&quot; information from the captured packets.
I am surprised to see that you are casting the buffer to iphdr struct directly, so in that case what about the ethernet header part of the frame.

Kindly explain the same. I am new to networking.

Thanks in advance.]]></description>
			<content:encoded><![CDATA[<p>Hi,</p>
<p>How can we extract &#8220;ethernet header&#8221; information from the captured packets.<br />
I am surprised to see that you are casting the buffer to iphdr struct directly, so in that case what about the ethernet header part of the frame.</p>
<p>Kindly explain the same. I am new to networking.</p>
<p>Thanks in advance.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: shalu		</title>
		<link>https://www.binarytides.com/packet-sniffer-code-c-linux/comment-page-1/#comment-74434</link>

		<dc:creator><![CDATA[shalu]]></dc:creator>
		<pubDate>Tue, 19 Apr 2016 04:54:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.binarytides.com/blog/?p=48#comment-74434</guid>

					<description><![CDATA[the code is working fine but the problem is nothing will display in log file. :(]]></description>
			<content:encoded><![CDATA[<p>the code is working fine but the problem is nothing will display in log file. :(</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Kate		</title>
		<link>https://www.binarytides.com/packet-sniffer-code-c-linux/comment-page-1/#comment-72588</link>

		<dc:creator><![CDATA[Kate]]></dc:creator>
		<pubDate>Sat, 02 Apr 2016 12:44:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.binarytides.com/blog/?p=48#comment-72588</guid>

					<description><![CDATA[Don&#039;t cast malloc :) And have your code handle the case where malloc returns NULL. I&#039;d probably use void * for the function&#039;s buffer argument on line 59 (leaving the array as unsigned char), and size_t for its size. Also if you re-order your source, you can avoid needing to write explicit prototypes. Line 218, unsigned int is the wrong type for %d. And unsigned short is the wrong type for iphdrlen; use size_t there, too.

Think of using the appropriate type as an example of abstraction; here you&#039;re abstracting the meaning of your variable from the implementation requirements for whatever type the struct used. Likewise for your buffer argument being void *.]]></description>
			<content:encoded><![CDATA[<p>Don&#8217;t cast malloc :) And have your code handle the case where malloc returns NULL. I&#8217;d probably use void * for the function&#8217;s buffer argument on line 59 (leaving the array as unsigned char), and size_t for its size. Also if you re-order your source, you can avoid needing to write explicit prototypes. Line 218, unsigned int is the wrong type for %d. And unsigned short is the wrong type for iphdrlen; use size_t there, too.</p>
<p>Think of using the appropriate type as an example of abstraction; here you&#8217;re abstracting the meaning of your variable from the implementation requirements for whatever type the struct used. Likewise for your buffer argument being void *.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Kutlan Turan		</title>
		<link>https://www.binarytides.com/packet-sniffer-code-c-linux/comment-page-1/#comment-67320</link>

		<dc:creator><![CDATA[Kutlan Turan]]></dc:creator>
		<pubDate>Tue, 19 Aug 2014 11:43:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.binarytides.com/blog/?p=48#comment-67320</guid>

					<description><![CDATA[how can ı decode this collected packets? have you got any suggession? ı mean for example ı got packets of sıp or text sended how can ı decode this?]]></description>
			<content:encoded><![CDATA[<p>how can ı decode this collected packets? have you got any suggession? ı mean for example ı got packets of sıp or text sended how can ı decode this?</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: aysh		</title>
		<link>https://www.binarytides.com/packet-sniffer-code-c-linux/comment-page-1/#comment-66032</link>

		<dc:creator><![CDATA[aysh]]></dc:creator>
		<pubDate>Wed, 19 Mar 2014 13:52:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.binarytides.com/blog/?p=48#comment-66032</guid>

					<description><![CDATA[Hi moon..I used ur coding for my project ...the coding was gud..the nly problem s aftr compiling I got nly starting..nd nthng was displayed in log.txt..its empty ..wt shld I do to get the right output...pls help me]]></description>
			<content:encoded><![CDATA[<p>Hi moon..I used ur coding for my project &#8230;the coding was gud..the nly problem s aftr compiling I got nly starting..nd nthng was displayed in log.txt..its empty ..wt shld I do to get the right output&#8230;pls help me</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Sovietmade		</title>
		<link>https://www.binarytides.com/packet-sniffer-code-c-linux/comment-page-1/#comment-65613</link>

		<dc:creator><![CDATA[Sovietmade]]></dc:creator>
		<pubDate>Fri, 19 Jul 2013 11:58:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.binarytides.com/blog/?p=48#comment-65613</guid>

					<description><![CDATA[Gr8 post,man,thanks a lot!!!]]></description>
			<content:encoded><![CDATA[<p>Gr8 post,man,thanks a lot!!!</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Anand		</title>
		<link>https://www.binarytides.com/packet-sniffer-code-c-linux/comment-page-1/#comment-65492</link>

		<dc:creator><![CDATA[Anand]]></dc:creator>
		<pubDate>Thu, 30 May 2013 08:45:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.binarytides.com/blog/?p=48#comment-65492</guid>

					<description><![CDATA[I tried to use the raw sockets to capture the packets from wlan0 and p2p0 (wireless interfaces) but I faced following issue:
1) The packet was of following format 
------.......
In the capture we used read option to get the packet being sent out and received at the wlan0 interface.


2) The issues happens when sending the packet out, the ethernet frame is not completely shown in the dump printed by using the read.
The first 8 bytes of the ethernet header (same as LLC+SNAP header size) are missing from the capture.


I also checked same packet at wireshark and it was properly captured.


3) On RX side the packet is properly received as per the dump.


Please let me know in which direction I can proceed to check the same.]]></description>
			<content:encoded><![CDATA[<p>I tried to use the raw sockets to capture the packets from wlan0 and p2p0 (wireless interfaces) but I faced following issue:<br />
1) The packet was of following format<br />
&#8212;&#8212;&#8230;&#8230;.<br />
In the capture we used read option to get the packet being sent out and received at the wlan0 interface.</p>
<p>2) The issues happens when sending the packet out, the ethernet frame is not completely shown in the dump printed by using the read.<br />
The first 8 bytes of the ethernet header (same as LLC+SNAP header size) are missing from the capture.</p>
<p>I also checked same packet at wireshark and it was properly captured.</p>
<p>3) On RX side the packet is properly received as per the dump.</p>
<p>Please let me know in which direction I can proceed to check the same.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Silver Moon		</title>
		<link>https://www.binarytides.com/packet-sniffer-code-c-linux/comment-page-1/#comment-64940</link>

		<dc:creator><![CDATA[Silver Moon]]></dc:creator>
		<pubDate>Fri, 15 Feb 2013 07:19:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.binarytides.com/blog/?p=48#comment-64940</guid>

					<description><![CDATA[In reply to &lt;a href=&quot;https://www.binarytides.com/packet-sniffer-code-c-linux/comment-page-1/#comment-3406&quot;&gt;Sumit&lt;/a&gt;.

what does the program output in the terminal ?]]></description>
			<content:encoded><![CDATA[<p>In reply to <a href="https://www.binarytides.com/packet-sniffer-code-c-linux/comment-page-1/#comment-3406">Sumit</a>.</p>
<p>what does the program output in the terminal ?</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Mayank		</title>
		<link>https://www.binarytides.com/packet-sniffer-code-c-linux/comment-page-1/#comment-47567</link>

		<dc:creator><![CDATA[Mayank]]></dc:creator>
		<pubDate>Wed, 22 Aug 2012 13:41:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.binarytides.com/blog/?p=48#comment-47567</guid>

					<description><![CDATA[Please provide a link for wireless sniffer in Linux for capturing 802.11 packets]]></description>
			<content:encoded><![CDATA[<p>Please provide a link for wireless sniffer in Linux for capturing 802.11 packets</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: M.USMAN		</title>
		<link>https://www.binarytides.com/packet-sniffer-code-c-linux/comment-page-1/#comment-34330</link>

		<dc:creator><![CDATA[M.USMAN]]></dc:creator>
		<pubDate>Thu, 26 Jul 2012 21:12:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.binarytides.com/blog/?p=48#comment-34330</guid>

					<description><![CDATA[In reply to &lt;a href=&quot;https://www.binarytides.com/packet-sniffer-code-c-linux/comment-page-1/#comment-32389&quot;&gt;Silver Moon&lt;/a&gt;.

HI,
i did make a sniffer with the help of signals, i am thinking way wrong about signals and my concepts are not clear that time when i post my question here any ways here it is...

http://dl.dropbox.com/u/63897671/sniffer.c]]></description>
			<content:encoded><![CDATA[<p>In reply to <a href="https://www.binarytides.com/packet-sniffer-code-c-linux/comment-page-1/#comment-32389">Silver Moon</a>.</p>
<p>HI,<br />
i did make a sniffer with the help of signals, i am thinking way wrong about signals and my concepts are not clear that time when i post my question here any ways here it is&#8230;</p>
<p><a href="http://dl.dropbox.com/u/63897671/sniffer.c" rel="nofollow ugc">http://dl.dropbox.com/u/63897671/sniffer.c</a></p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Silver Moon		</title>
		<link>https://www.binarytides.com/packet-sniffer-code-c-linux/comment-page-1/#comment-33840</link>

		<dc:creator><![CDATA[Silver Moon]]></dc:creator>
		<pubDate>Wed, 13 Jun 2012 11:51:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.binarytides.com/blog/?p=48#comment-33840</guid>

					<description><![CDATA[In reply to &lt;a href=&quot;https://www.binarytides.com/packet-sniffer-code-c-linux/comment-page-1/#comment-33830&quot;&gt;kostya&lt;/a&gt;.

you have to use either IPPROTO_TCP , IPPROTO_UDP or IPPROTO_ICMP
you cannot use IPPROTO_IP since its a dummy protocol (value is 0)

if you need to capture all types of packets then use the more generic sniffer as explained here :
http://www.binarytides.com/blog/packet-sniffer-code-in-c-using-linux-sockets-bsd-part-2/]]></description>
			<content:encoded><![CDATA[<p>In reply to <a href="https://www.binarytides.com/packet-sniffer-code-c-linux/comment-page-1/#comment-33830">kostya</a>.</p>
<p>you have to use either IPPROTO_TCP , IPPROTO_UDP or IPPROTO_ICMP<br />
you cannot use IPPROTO_IP since its a dummy protocol (value is 0)</p>
<p>if you need to capture all types of packets then use the more generic sniffer as explained here :<br />
<a href="http://www.binarytides.com/blog/packet-sniffer-code-in-c-using-linux-sockets-bsd-part-2/" rel="ugc">http://www.binarytides.com/blog/packet-sniffer-code-in-c-using-linux-sockets-bsd-part-2/</a></p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: kostya		</title>
		<link>https://www.binarytides.com/packet-sniffer-code-c-linux/comment-page-1/#comment-33830</link>

		<dc:creator><![CDATA[kostya]]></dc:creator>
		<pubDate>Sun, 03 Jun 2012 15:15:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.binarytides.com/blog/?p=48#comment-33830</guid>

					<description><![CDATA[great code! 
can you explain me some thing? I&#039;m just beginner in socket programming. 
You use construction as socket(AF_INET , SOCK_RAW , IPPROTO_TMP). i don&#039;t understand it. we get defferent packets (as UDP, TCP) which is above ip-level. Why you don&#039;t use parameter IPPROTO_IP?]]></description>
			<content:encoded><![CDATA[<p>great code!<br />
can you explain me some thing? I&#8217;m just beginner in socket programming.<br />
You use construction as socket(AF_INET , SOCK_RAW , IPPROTO_TMP). i don&#8217;t understand it. we get defferent packets (as UDP, TCP) which is above ip-level. Why you don&#8217;t use parameter IPPROTO_IP?</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
