Interface names must start with tun or tap on BSD and Darwin
#4049
Labels
Comments
|
That’s indeed a bug. Do you feel like submitting a PR?Sent from my iPhoneOn 28 Jun 2023, at 07:38, Matt Bolognani ***@***.***> wrote:
Brief description
The tun interfaces on my Mac are all named "utun".
How can I make scapy work with that?
Scapy version
2.5
Python version
3.10
Operating system
MacOS Ventura
Additional environment information
No response
How to reproduce
from scapy.layers.tuntap import TunTapInterface
if name == "main":
t = TunTapInterface("utun3", mode_tun=True)
Actual result
ValueError: Interface names must start with tun or tap on BSD and Darwin
Expected result
No error
Related resources
No response
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>
|
|
@guedou I looked at the code today. Unfortunately it's not just a naming issue; the socket type and ioctl are different. I'll give it a try later this summer. Any suggestions are welcome :) |
|
Hi @guedou, Sorry about the radio silence. I opened a draft pull request with the changes that I made. There is still a lot of work to be done before it can be merged (adding tests, refactoring, etc.). |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Brief description
The tun interfaces on my Mac are all named "utun0", "utun1", etc.
How can I make scapy work with that?
Scapy version
2.5
Python version
3.10
Operating system
MacOS Ventura
Additional environment information
No response
How to reproduce
Actual result
ValueError: Interface names must start with
tunortapon BSD and DarwinExpected result
No error
Related resources
No response
The text was updated successfully, but these errors were encountered: