v1.9.14908. Fragmented UDP packets to/from zero port

[i4u1]

I got fragmented outgoing UDP packets blocked by my firewall.

Characteristix: their size 60 bytes only(!). Their port numbers in/out are zero (0). The direction is: from local address under NAT (manual port forwarding on router) to WAN address (inet).

What's happening? Why uTorrent sends these 60-byte fragmented(!) UDPs to peers? Is it possible to unfagment them in code?

[Firon]

It's probably your own firewall just being dumb about UDP. Make it blanket-allow UDP.

[i4u1]

I'm sure FW is quite decent. No cause to not believe.

Why not uTorrent? zero ports in/out? and 60 byte fragmented data? Maybe some bad code in there?

Btw i have tweaked MTU. Does uTorrent check MTU size in registry to send correctly?

I think it's uTorrent bug not FW.

[DreadWingKnight]

What firewall do you use?

[i4u1]

Outpost Firewall Pro версия 6.5.3 (2518.381.0686).

Check extra send/sendto outgoing udp calls to uninit port of peers. maybe wrong setsockopt params. maybe lack of IP_DONTFRAGMENT.

[Saribro]

Have you checked the traffic with wireshark or similar to make sure your firewall isn't confusing itself?

Might provide more data on the issue aswell if it's not a misreport.