New addon "fping" in testing tree

Post Reply
ummeegge
Community Developer
Community Developer
Posts: 5001
Joined: October 9th, 2010, 10:00 am

New addon "fping" in testing tree

Post by ummeegge » September 11th, 2012, 3:25 pm

Hi all,
there is a new network tool --> http://fping.org/ in the testing tree available. It works similar then ping but brings also some specials with.

The wiki is also close to be ready  ;):

english:
http://wiki.ipfire.org/en/addons/fping/start

german:
http://wiki.ipfire.org/de/addons/fping/start

How to change to testing tree can be read in here --> http://wiki.ipfire.org/de/configuration ... re/testing .

Greetings

UE
Image
Image

Lorenco
Posts: 127
Joined: September 13th, 2012, 4:02 pm

Re: New addon "fping" in testing tree

Post by Lorenco » November 8th, 2013, 1:18 pm

Hi, wie kann man denn so was auf der Ipfire laufen lassen:

ping -c 4 -M do -s 1465 www.t-online.de

Das funktioniert nicht mit der ping Version von Ipfire.

Gruß

ummeegge
Community Developer
Community Developer
Posts: 5001
Joined: October 9th, 2010, 10:00 am

Re: New addon "fping" in testing tree

Post by ummeegge » November 8th, 2013, 7:37 pm

Ja da hast du recht,
was geht wäre

Code: Select all

ping -c 5 -s 1400 www.t-online.de

aber -M (leider) und do kennt ping auf dem Fire nicht.

fping auch nicht
Usage: fping [options] [targets...]
  -a        show targets that are alive
  -A        show targets by address
  -b n      amount of ping data to send, in bytes (default 56)
  -B f      set exponential backoff factor to f
  -c n      count of pings to send to each target (default 1)
  -C n      same as -c, report results in verbose format
  -e        show elapsed time on return packets
  -f file    read list of targets from a file ( - means stdin) (only if no -g specified)
  -g        generate target list (only if no -f specified)
                (specify the start and end IP in the target list, or supply a IP netmask)
                (ex. fping -g 192.168.1.0 192.168.1.255 or fping -g 192.168.1.0/24)
  -H n      Set the IP TTL value (Time To Live hops)
  -i n      interval between sending ping packets (in millisec) (default 25)
  -l        loop sending pings forever
  -m        ping multiple interfaces on target host
  -n        show targets by name (-d is equivalent)
  -p n      interval between ping packets to one target (in millisec)
                (in looping and counting modes, default 1000)
  -q        quiet (don't show per-target/per-ping results)
  -Q n      same as -q, but show summary every n seconds
  -r n      number of retries (default 3)
  -s        print final stats
  -I if      bind to a particular interface
  -S addr    set source address
  -t n      individual target initial timeout (in millisec) (default 500)
  -T n      ignored (for compatibility with fping 2.4)
  -u        show targets that are unreachable
  -O n      set the type of service (tos) flag on the ICMP packets
  -v        show version
  targets    list of targets to check (if no -f specified)


tracepath und hping können pmtud setzen soviel ich weiss.

Hab gerade mal die iputils auf den neuesten Stand gebracht und tracepath mit kompiliert (liegt unter /usr/bin mit 755). Findest du im Anhang.

UE
Image
Image

Lorenco
Posts: 127
Joined: September 13th, 2012, 4:02 pm

Re: New addon "fping" in testing tree

Post by Lorenco » November 12th, 2013, 2:59 pm

Danke. Hatte allerdings übersehen, das ping standardmäßig schon mit "don't Fragment" läuft.
Also braucht man kein -M ....

ummeegge
Community Developer
Community Developer
Posts: 5001
Joined: October 9th, 2010, 10:00 am

Re: New addon "fping" in testing tree

Post by ummeegge » November 13th, 2013, 6:38 am

In der Manpage taucht -M schon noch auf --> http://linux.die.net/man/8/ping und im Sourcecode (ping.c) ist es auch noch zu finden?

Code: Select all

}

case 'M':
      
   if (strcmp(optarg, "do") == 0)
         
   pmtudisc = IP_PMTUDISC_DO;

else if (strcmp(optarg, "dont") == 0)
         
   pmtudisc = IP_PMTUDISC_DONT;

else if (strcmp(optarg, "want") == 0)
      
      pmtudisc = IP_PMTUDISC_WANT;

else {
         
   fprintf(stderr, "ping: wrong value for -M: do, dont, want are valid ones.\n");
         
   exit(2);

}


Das sind jetzt die "iputils ss020927". Wie kommst du drauf ?

Grüsse

UE
Image
Image

Lorenco
Posts: 127
Joined: September 13th, 2012, 4:02 pm

Re: New addon "fping" in testing tree

Post by Lorenco » July 30th, 2014, 10:13 am

Ist ja schon eine Weile her, aber besser spät als nie...

Hatte mal so etwas wie hier gefunden:
http://wiki.jokeru.ro/df-mtu

Also drin ist es wohl, aber was ist Standard...

User avatar
Arne.F
Core Developer
Core Developer
Posts: 8522
Joined: May 7th, 2006, 8:57 am
Location: BS <-> NDH
Contact:

Re: New addon "fping" in testing tree

Post by Arne.F » July 30th, 2014, 10:24 am

Auf dem IPFire gab is bis core78 zwei verschiedene ping binaries. (eins in /bin und eins in /usr/bin) Das eine kennt -M und das andere nicht. Dieser Fehler wurde in core79 behoben. http://www.ipfire.org/news/ipfire-2-15- ... 9-released
Jetzt gibt es nur noch eine Version die den parameter kennt.

Danke. Hatte allerdings übersehen, das ping standardmäßig schon mit "don't Fragment" läuft.
Also braucht man kein -M ....

Das wär mit neu. Bei mir fragmemtiert ping standardmäßig. Evtl. ist die alte version ohne -M da anders.
Last edited by Arne.F on July 30th, 2014, 10:29 am, edited 1 time in total.
Arne

Support the project on the donation!

Image

Image

Image
PS: I will not answer support questions via email and ignore IPFire related messages on my non IPFire.org mail addresses.

Post Reply