Skip Menu |

This queue is for tickets about the Net-Ping CPAN distribution.

Report information
The Basics
Id: 17409
Status: resolved
Priority: 0/
Queue: Net-Ping
People
Owner: Nobody in particular
Requestors: bergonz [...] labs.it
Cc:
AdminCc:
Bug Information
Severity: Unimportant
Broken in: 2.31
Fixed in: (no value)

History Show all quoted text
  Wed Feb 01 05:13:19 2006 Guest - Ticket created
Subject: Trivial improvement: size > 1024
Sometimes, in complex networks (tunnels, GRE, IPsec, etc.), it happens that big packets are dropped and small packets go through. For this reason, I enjoy pinging with packets of size equal to the MTU, that is 1500 for ethernet, which leads to a ICMP data size of 1472. Currently Net::Ping limits icmp data size to 1024. I trivially expand it to 2048 by changing the definition of $max_datasize (and the corresponding number in the POD). Please note that you can very well ping with sizes > MTU: the packet will simply be fragmented. Real problems arise at about 65535. Since this trivial improvement is very useful for me and works in my situation, I suggest to include it in the next release. The POD should probably mention the fact that not all network devices answer ping of any size: there are devices for which I have to use 1400 o 1000. Having created two tickets in a day, I promise not to open any more for at least a month. Best regards, Bergonz
  Fri Sep 04 07:36:45 2009 PJNEWMAN [...] cpan.org - Correspondence added
On Wed Feb 01 05:13:19 2006, guest wrote: Show quoted text
> Currently Net::Ping limits icmp data size to 1024. I trivially
expand it Show quoted text
> to 2048 by changing the definition of $max_datasize (and the > corresponding number in the POD).
A plus one/bump for this please, I'd also like to be able to do it for the same reasons Bergonz mentioned, I can't really see any reason for it to be limited to that, and it would be nice if it would work natively for me on any machine without me needing to remember to patch it. Thanks, PN
  Fri Sep 04 07:36:47 2009 The RT System itself - Status changed from 'new' to 'open'
  Fri Sep 04 08:19:45 2009 PJNEWMAN [...] cpan.org - Correspondence added
Actually I've just noticed you can't set the don't fragment flag, so this still wouldn't really do what I want, even with that potential bug fix. Thanks anyway, PN
  Sat Apr 16 10:55:29 2016 RURBAN [...] cpan.org - Correspondence added
On Fri Sep 04 08:19:45 2009, PJNEWMAN wrote: Show quoted text
> Actually I've just noticed you can't set the don't fragment flag, so > this still wouldn't really do what I want, even with that potential > bug fix.
I've added that feature to RURBAN/Net-Ping-2.49_04.tar.gz but could not test it, since none of my systems have IP_DONTFRAG. the new dontfrag option to new is ignored if Socket::P_DONTFRAG is undefined. on linux I also set IP_MTU_DISCOVER to IP_PMTUDISC_DO -- Reini Urban
  Sat Apr 16 10:55:37 2016 RURBAN [...] cpan.org - Correspondence added
On Fri Sep 04 08:19:45 2009, PJNEWMAN wrote: Show quoted text
> Actually I've just noticed you can't set the don't fragment flag, so > this still wouldn't really do what I want, even with that potential > bug fix.
I've added that feature to RURBAN/Net-Ping-2.49_04.tar.gz but could not test it, since none of my systems have IP_DONTFRAG. the new dontfrag option to new is ignored if Socket::P_DONTFRAG is undefined. on linux I also set IP_MTU_DISCOVER to IP_PMTUDISC_DO -- Reini Urban
  Fri Aug 17 04:19:15 2018 RURBAN [...] cpan.org - Correspondence added
I've added this feature to the test release 1.70_90 which will be 1.71. The allowed max_datasize is now 65535, though staying below the MTU is recommended. -- Reini Urban
  Fri Aug 17 04:19:16 2018 RURBAN [...] cpan.org - Status changed from 'open' to 'resolved'