-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Select the network interface in send() #2356
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Codecov Report
@@ Coverage Diff @@
## master #2356 +/- ##
==========================================
+ Coverage 87.5% 87.79% +0.28%
==========================================
Files 243 243
Lines 50727 50728 +1
==========================================
+ Hits 44390 44537 +147
+ Misses 6337 6191 -146
|
Please don't merge yet. I have some doubts about this PR when multiple packets are sent. |
I do not agree with this PR. In my mind, Specifying an interface in An option would be to allow specifying an alternative routing table object (or a route). What do you think? |
The current implementation of |
OK I misunderstood your PR then, I'll have to read again. Anyway, having |
But I really don't think that |
The root issue might be related to this line https://github.com/secdev/scapy/blob/master/scapy/arch/linux.py#L478 |
Can this PR be merged? |
As I said, I don't like the idea of |
This PR aligns sr1() and send() behavior. I think that it is ok to merge it.
Bypassing the routing table with these functions is indeed useful for protocols such as IPv6 with link-local addresses when the same prefix exists on different interfaces.
|
This PR fixes #2355.