scapy fail to start

Bug #106768 reported by airbat
4
Affects Status Importance Assigned to Milestone
scapy (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: scapy

$ sudo scapy
/usr/bin/scapy:3101: Warning: 'with' will become a reserved keyword in Python 2.6
/usr/bin/scapy:3103: Warning: 'with' will become a reserved keyword in Python 2.6
Traceback (most recent call last):
  File "/usr/bin/scapy", line 10647, in <module>
    class Conf(ConfClass):
  File "/usr/bin/scapy", line 10693, in Conf
    route = Route()
  File "/usr/bin/scapy", line 1911, in __init__
    self.resync()
  File "/usr/bin/scapy", line 1915, in resync
    self.routes = read_routes()
  File "/usr/bin/scapy", line 2234, in read_routes
    ifreq = ioctl(s, SIOCGIFADDR,struct.pack("16s16x",iff))
IOError: [Errno 99] Cannot assign requested address

Version:
# aptitude show scapy
Paquet : scapy
État: installé
Automatiquement installé: non
Version : 1.0.4-1
Priorité : optionnel
Section : universe/net
Responsable : David Villa Alises <email address hidden>

Python version:
Paquet : python
État: installé
Automatiquement installé: non
Version : 2.5.1~rc1-0ubuntu3
Priorité : important
Section : python
Responsable : Ubuntu Core Developers <email address hidden>

It seems to be the same problem reported in #96753.
As pointed in #96753, an update have fixed it, but I get the same error now. Maybe the recent Python update ?

Revision history for this message
Scott Kitterman (kitterman) wrote :

I reopened Bug #96753 so we can keep the discussion together.

Revision history for this message
braddeshong (brad-deshong) wrote :

I fixed this problem by disabling an unused ethernet adapter after I started using wireless on my laptop. The old routes were still in /proc/net/route and the gateway addresses were conflicting.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.