ipsec.py CANT FIND THE attribute IPPROTO_ESP and socket.IPPROTO_AH

23,445

I think I have it...it's not a clean solution, but it will do the trick... I've seen it in other scapy files...
All you need to do is edit ipsec.py and look for the line import socket just under it, add these conditionals:

if not hasattr(socket, "IPPROTO_ESP"):
    socket.IPPROTO_ESP = 50
if not hasattr(socket, "IPPROTO_AH"):
    socket.IPPROTO_AH = 51

As I mentioned in one of the comments, I tested using Python 2.7.10 on a variety of OSes (Lnx, Sol, AIX, HPUX, OSX) and the values seem to be consistent, while on Win they don't exist. Seems like MS removed them from WinSock2.h between (VStudio) 2005 and 2010.

Share:
23,445
yosi doran
Author by

yosi doran

Updated on July 09, 2022

Comments

  • yosi doran
    yosi doran almost 2 years

    I install the module scapy for python 2.6 and when I import this module I get this warning:

    WARNING: can't import layer ipsec: 'module' object has no attribute 'IPPROTO_AH'

    I looked in the socket attributes and i didnt find the 'IPPROTO_AH' attribute In addition, i tried to edit the module ipsec.py and find way to replace IPPROTO_AH with something else but then i got WARNING WITH IPPROTO_ESP !

    I tried edit lines in ipsec.py such as:

        overload_fields = {
        IP: {'proto': IPTest},
        IPv6: {'nh': IPTest},
        IPv6ExtHdrHopByHop: {'nh': socket.IPPROTO_AH},
        IPv6ExtHdrDestOpt: {'nh': socket.IPPROTO_AH},
        IPv6ExtHdrRouting: {'nh': socket.IPPROTO_AH},}
    
    bind_layers(IP, AH, proto=socket.IPPROTO_AH)
    bind_layers(IPv6, AH, nh=socket.IPPROTO_AH)
    

    how can i fix this ?

  • yosi doran
    yosi doran almost 9 years
    lol I rewrite all this module .. and this works (replace all the "socket.IPPROTO_AH" and "socket.IPPROTO_ESP" with their value)!! Thank you !!
  • CristiFati
    CristiFati almost 9 years
    I'd still recommend to check first if socket has them and if not then define them instead of replacing their occurrences with their values, because if you would like to run the code with another python installed on another machine with a different Windows version where those constant might have different values (although this wouldn't be very likely) the code won't work.
  • CristiFati
    CristiFati over 8 years
    I also did a test using Python2.7.10 on a variety of OSes (Linux, Solaris, AIX, HP-UX, OSX) and the values seem to be consistent, while on Win they don't exist. Seems like MS removed them from WinSock2.h between (VStudio) 2k5 and 2k10.