-
Notifications
You must be signed in to change notification settings - Fork 266
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
Cannot send tcp packet larger than 1500 #21
Comments
@russianbullet MTU? |
abdullah I've modified the mtu of the ethernet card in windows but no luck , anything to do in sharppcap |
SharpPcap doesn't contain any limits to the packet size you can send. That of course doesn't mean that there aren't limits due to wincap or npcap. Now that npcap is supported by the latest git master would you mind trying npcap (instead of winpcap) and the latest git master to see if it works? If it doesn't then at least we can reach out to the npcap developer to discuss, winpcap is a dead project so we have no path for support there. |
Dear @chmorgan I've uninstalled winpcap and installed npcap , the result is the same , I get this exception when SendPacket **> An unhandled exception of type 'SharpPcap.PcapException' occurred in SharpPcap.dll
|
Hi Yang.
I looked but there doesn't look to be an 'issues' tab on the github npcap
project.
It looks like this person is having trouble sending a large packet. I had
them switch to using npcap so we had some option to reach out to you to see
if this is an issue with npcap, the usage of the function call or what.
SharpPcap isn't doing anything with the data but forwarding it on to the
underlying library.
Chris
…On Fri, Apr 21, 2017 at 12:38 PM, russianbullet ***@***.***> wrote:
Dear @chmorgan <https://github.com/chmorgan> I've unisntalled winpcap and
installed npcap , the result is the same , I get this error when SendPacket
**> An unhandled exception of type 'SharpPcap.PcapException' occurred in
SharpPcap.dll
Additional information: Can't send packet: send error: PacketSendPacket
failed**
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#21 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABJ-AHyFIt_7_uxDsPDIElyPwtWJcRf0ks5ryNuDgaJpZM4NDSeq>
.
|
Thank you Chris |
The issues page is at Nmap repo here: https://github.com/nmap/nmap/issues BTW, can you provide an example to reproduce this issue? It only needs to contain the sending packet call with 1600 bytes. And I will test whether it works. And please provide your DiagReport described in Npcap README. So I can see your adapter info. |
Hello @hsluoyz
|
Where is And BTW, I found you are running Win8. It's an outdated system and not supported by Microsoft any more. And I don't even have a Win8 VM to reproduce any bugs. (I only have Vista SP1, Win7 SP1, Win8.1, Win10). Please update to at least Win8.1 to avoid potential problems if possible. |
Hello @hsluoyz , I'm so sorry to be late , I couldn't upload the project here, so I've uploaded it to google drive , this is the link: https://drive.google.com/file/d/0B6TQYhFg8n0mdXhubm5ESDdyYkE/view |
Hi, I reproduced your issue. It seems that Windows hardcoded the maximum of MTU for Ethernet adapters to be 1500. In fact I never googled out an article that said MTU can be larger than 1500. It's a de-facto standard and it seems that Windows implements this way. In fact, you can get a larger MTU for other type adapters. For example, Npcap Loopback Adapter supports a MTU of 65536. |
Thank you @hsluoyz , It seems that am going to fragment the ip packet , thank you for your efforts guys , regards |
@hsluoyz @russianbullet i am quite sure you can change the MTU in windows. Using netsh tool... |
You can change the MTU |
@abdullah2993 I've already changed it , but no luck still the same error |
Closing this as it is a limitation of the OS and/or npcap. @hsluoyz thanks for your help. |
Hello
I'm trying to send 1600 bytes packet size , but no luck
I'll be delighted to hear from you soon
regards
The text was updated successfully, but these errors were encountered: