You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Specified interface is not being taken into account when using send method.
Scapy version
2.5.0
Python version
3.11
Operating system
Debian 12
Additional environment information
No response
How to reproduce
When trying to send a packet over a specific interface, the interface specified is being ignored in the send method in scapy/arch/linux.py. For example:
Upon opening Wireshark, I noticed that packets were being sent over my eth0 interface rather than the specified eth1. After further inspecting the code and debugging, I found this function in scapy:
As you can see in iff = x.route()[0], the interface is being determined by the route method, and the one I specified is completely ignored throughout the function.
Actual result
No response
Expected result
No response
Related resources
No response
The text was updated successfully, but these errors were encountered:
fernandoenzo
changed the title
Bug in send method. Interface is not being taked into account
Bug in send method. Interface is not being taken into account
Aug 22, 2024
Brief description
Specified interface is not being taken into account when using
send
method.Scapy version
2.5.0
Python version
3.11
Operating system
Debian 12
Additional environment information
No response
How to reproduce
When trying to send a packet over a specific interface, the interface specified is being ignored in the
send
method inscapy/arch/linux.py
. For example:Upon opening Wireshark, I noticed that packets were being sent over my
eth0
interface rather than the specifiedeth1
. After further inspecting the code and debugging, I found this function in scapy:As you can see in
iff = x.route()[0]
, the interface is being determined by theroute
method, and the one I specified is completely ignored throughout the function.Actual result
No response
Expected result
No response
Related resources
No response
The text was updated successfully, but these errors were encountered: