Skip to content
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

Doesn't send UDP messages #158

Open
Achivai opened this issue Jul 15, 2019 · 15 comments

Comments

@Achivai
Copy link

commented Jul 15, 2019

What OS?

  • [ x] Windows
  • Mac
  • Linux (Which distro?)

Description of issue

I am trying to send UDP-packets to ip adress X and port Y. I'm sending them, but not receiving, and when I'm monitoring data with wireshark I am not seeing any packets being sent. I already unblocked the program in the firewall.

@dannagle

This comment has been minimized.

Copy link
Owner

commented Jul 15, 2019

Will you post a screenshot? Maybe there is something odd with your settings.

@gpgp72

This comment has been minimized.

Copy link

commented Jul 30, 2019

I came here to say the same thing. The normal send packet does not work in udp mode. Sending UDP via send intense traffic does however work. I observed this by reading the packets through wireshark. No traffic is generated when pushing send on a saved packet that is set for udp.

@dannagle

This comment has been minimized.

Copy link
Owner

commented Jul 30, 2019

@gpgp72 Will you post a screenshot?

@dannagle dannagle self-assigned this Jul 30, 2019

@gpgp72

This comment has been minimized.

Copy link

commented Jul 30, 2019

Screenshot (1)
Screenshot (3)
Screenshot (4)
Screenshot (5)

@gpgp72

This comment has been minimized.

Copy link

commented Jul 30, 2019

Sorry, I am learning my way around this forum. Above please see a few screenshots, first was a previous connection with intense traffic. So working. Second is showing that tcp is working, traffic is generated (but my listening device is not set for tcp), third shows no traffic generated by the send button with the identical command in UDP mode, fourth is working again in intense traffic mode.
This version of packet sender was downloaded inside of the last week. There is nothing abnormal about the network setup to my knowledge. Thank you Dan for you attention to this matter.
Me : slinks off to the donate page .....

Greg Peeler

@dannagle

This comment has been minimized.

Copy link
Owner

commented Jul 30, 2019

@gpgp72 Under File --> Settings, there is a place where you can assign a bind address. What happens if you select "Bind This" and put in your current IP? (I believe to be 10.32.2.8)

@dannagle

This comment has been minimized.

Copy link
Owner

commented Jul 30, 2019

@gpgp72 two other things to try...

  • Does the main send button work (at the top, used while drafting the packet)?

  • Is it the send button attached to the packet itself that does not work (the saved packet table) ?

@gpgp72

This comment has been minimized.

Copy link

commented Jul 30, 2019

Packet sender says it is sending, but wireshark shows it is not. Behavior is the same as the send next to the saved packet.

@gpgp72

This comment has been minimized.

Copy link

commented Jul 30, 2019

that makes it work.
so maybe a service order thing on the windows side. You cannot see the ip that is in the range i am testing, thats the wireless adapter at 10.32.

@dannagle

This comment has been minimized.

Copy link
Owner

commented Jul 30, 2019

Which one made it work? Was it setting a bind address?

Please let me know so I can try to detect the problem in the software and alert the user.

@gpgp72

This comment has been minimized.

Copy link

commented Jul 30, 2019

Sorry I wasn’t clear. Binding the address made the send button on a saved udp packet work.

@dannagle

This comment has been minimized.

Copy link
Owner

commented Jul 30, 2019

This has been an on-going problem when using the general bind address of "0.0.0.0" (the standard for IPv4) with multiple NICs. The OS may not know which NIC to send the packet out, so it picks one at random and hopes your gateway re-routes it to the correct path, which it usually does. For the times it doesn't... that's why I added that IP-bind feature. It forces the use of the NIC you want.

Anyway, there is no good solution to this, but I can perhaps detect when the problem may manifest and prompt the user (once per session) about the potential issue and fix.

I'm glad yours is now working. I'm going to leave this ticket open to remind me to dig further.

@gpgp72

This comment has been minimized.

Copy link

commented Jul 30, 2019

@gpgp72

This comment has been minimized.

Copy link

commented Jul 31, 2019

@dannagle

This comment has been minimized.

Copy link
Owner

commented Jul 31, 2019

Packet Sender can simultaneously listen on any number of UDP, TCP, or SSL ports. It is comma-separated list under File->Settings. Then Network tab. See screenshot.

image

The port icons then changes to reflect it...

image

Note that UDP sending only uses the first port that is bounded. Packet Sender is simply listening on all the others. TCP and SSL sending is always dynamic. Those can be force-bound if you use the command line interface.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants
You can’t perform that action at this time.