From 7a45aa15901c0937bbcc9dd82c7e896f45948a27 Mon Sep 17 00:00:00 2001
From: Pyry Kovanen <pkova@users.noreply.github.com>
Date: Tue, 23 May 2017 18:09:28 +0300
Subject: [PATCH] Fix typo in troubleshooting.rst
(or its equivalent on other systems that Linux) => (or its equivalent on other systems than Linux)
---
doc/scapy/troubleshooting.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/doc/scapy/troubleshooting.rst b/doc/scapy/troubleshooting.rst
index 810eea84..3249c5c2 100644
--- a/doc/scapy/troubleshooting.rst
+++ b/doc/scapy/troubleshooting.rst
@@ -14,7 +14,7 @@ I can't ping 127.0.0.1. Scapy does not work with 127.0.0.1 or on the loopback in
The loopback interface is a very special interface. Packets going through it are not really assembled and disassembled. The kernel routes the packet to its destination while it is still stored an internal structure. What you see with tcpdump -i lo is only a fake to make you think everything is normal. The kernel is not aware of what Scapy is doing behind his back, so what you see on the loopback interface is also a fake. Except this one did not come from a local structure. Thus the kernel will never receive it.
-In order to speak to local applications, you need to build your packets one layer upper, using a PF_INET/SOCK_RAW socket instead of a PF_PACKET/SOCK_RAW (or its equivalent on other systems that Linux)::
+In order to speak to local applications, you need to build your packets one layer upper, using a PF_INET/SOCK_RAW socket instead of a PF_PACKET/SOCK_RAW (or its equivalent on other systems than Linux)::
>>> conf.L3socket
<class __main__.L3PacketSocket at 0xb7bdf5fc>
--
GitLab