| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
Revert changes in r269180. It could cause -c N option to enter an
infinite loop if no reply packet is received.
|
|
|
|
|
|
|
|
|
|
|
| |
When interval is set to very small value with limited amount of packets,
ping6(8) would quit before the remote side gets a chance to respond.
Solve this by resetting the itimer when we have reached the maximum packet
number have reached, but let the other handling to continue.
PR: bin/151023
Submitted by: tjmao at tjmao.net
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Address. Although KAME implementation used FF02:0:0:0:0:2::/96 based on
older versions of draft-ietf-ipngwg-icmp-name-lookup, it has been changed
in RFC 4620.
The kernel always joins the /104-prefixed address, and additionally does
/96-prefixed one only when net.inet6.icmp6.nodeinfo_oldmcprefix=1.
The default value of the sysctl is 1.
ping6(8) -N flag now uses /104-prefixed one. When this flag is specified
twice, it uses /96-prefixed one instead.
Reviewed by: ume
Based on work by: Thomas Scheffler
PR: conf/174957
MFC after: 2 weeks
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
current version of FreeBSD, this isn't guarenteed by the API. Custom
security modules, or future implementations of the setuid and setgid
may fail.
PR: bin/172289
PR: bin/172290
PR: bin/172291
Submittud by: Erik Cederstrand <erik@cederstrand.dk>
Discussed by: freebsd-security
Approved by: cperciva
MFC after: 1 week
|
|
|
|
|
|
|
| |
Disussed with: gavin
No objection from: doc
Approved by: joel
MFC after: 3 days
|
|
|
|
|
|
|
| |
error: variable 'origextlen' set but not used
Approved by: dim
MFC after: 3 days
|
| |
|
| |
|
|
|
|
|
| |
is in accordance with the information at
ftp://ftp.cs.berkeley.edu/pub/4bsd/README.Impt.License.Change
|
| |
|
|
|
|
|
|
|
|
| |
PR: bin/144730
PR: bin/144974
Submitted by: Earl R. Lapus <earl.lapus at gmail.com>
Approved by: rrs (mentor)
MFC after: 1 month
|
|
|
|
|
|
| |
PR: bin/145759
Submitted by: pluknet
MFC after: 1 month
|
|
|
|
|
|
|
|
|
|
| |
ping(8)'s -a was mapped to -e, but -E was already taken in ping6 (old
option) so rename -e to -r.
Now:
ping -a => ping6 -r
ping -A => ping6 -R
MFC after: 2 days
|
|
|
|
| |
MFC after: 2 days
|
|
|
|
|
|
|
| |
taken, I chose -e (no real argument for this) but I'm willing to change to a different character if needed/desired.
PR: bin/123752 (inspired by)
MFC after: 2 days
|
|
|
|
|
|
|
|
|
|
| |
and be usable in scripts, etc.
This also changes the semantics in case when we lose one of n packets.
In that case, before we exited by SIG, now we exit with return(0).
Submitted by: Gert Doering (gert space.net)
MFC after: 10 days
|
|
|
|
|
|
|
|
|
|
| |
from .01 to .000001.
Note that due to the architecture of ping6,
you are still limited to kern.hz pings per
second.
MFC after: 2 weeks
|
|
|
|
|
| |
Reviewed by: dwmalone, maxim
MFC after: 2 weeks
|
|
|
|
|
|
|
|
|
| |
This was needed during the IPSEC->FAST_IPSEC->IPSEC transition
period to not break the build after picking up netipsec header
files. Now that the FAST_IPSEC kernel option is gone and the
default is IPSEC again those defines are superfluous.
Approved by: re (rwatson)
|
|
|
|
|
|
|
|
| |
This commit includes all remaining changes for the time being including
user space updates.
Submitted by: bz
Approved by: re
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
1. The static buffer that ping6(8) uses to hold the control data
it gets from recvmsg(2) is too small in some cases.
2. When it prints the extra header information it doesn't do
any checking to make sure the data it's printing is within
the bounds of the supplied buffer.
Fix this by:
o Increasing the buffer to hold extra headers to 10240 bytes (the minimum
according to RFC3542 sec. 20.1) and allocate it dynamically.
o In verbose mode, specify a warning if any control data from recvmsg(2)
was truncated because the buffer was too small.
o When printing the extra headers make sure not to overrun the buffer
boundaries.
Reviewed By: mlaier
PR: kern/99425
MFC After: 1 month
|
|
|
|
| |
Tested with: cmp(1)
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Noticed by: tinderbox
Tested on: panther
|
| |
|
|
|
|
| |
Obtained from: KAME
|
|
|
|
| |
Fixed some more markup.
|
|
|
|
| |
Use WARNS?= instead of WARNS=.
|
|
|
|
|
|
|
|
|
|
| |
(aka RFC2292bis). Though I believe this commit doesn't break
backward compatibility againt existing binaries, it breaks
backward compatibility of API.
Now, the applications which use Advanced Sockets API such as
telnet, ping6, mld6query and traceroute6 use RFC3542 API.
Obtained from: KAME
|
|
|
|
| |
Obtained from: KAME
|
|
|
|
|
|
|
|
|
|
|
|
| |
The output format specifier for the round-trip time in ping6 should be
changed to %.3f instead of %g since %g doesn't accurately represent the
precision of the number being output. In particular, %g truncates trailing
zeroes. 0.01 ms does not mean the same thing as 0.010 ms. Although they
are numerically identical, they do not have the same precision.
PR: bin/52324, bin/52750
Submitted by: dg
MFC after: 1 week
|
|
|
|
|
| |
obtained from: KAME
MFC after: 3 days
|
|
|
|
| |
calculated dynamically here.
|
| |
|
|
|
|
|
|
| |
PR: bin/38862
Submitted by: Martin Faxer <gmh003532@brfmasthugget.se> with some modification
MFC after: 1 week
|
| |
|
|
|
|
| |
o remove main prototype
|
|
|
|
|
|
| |
It does not help modern compilers, and some may take some hit from it.
(I also found several functions that listed *every* of its 10 local vars with
"register" -- just how many free registers do people think machines have?)
|
|
|
|
|
|
|
| |
PR: bin/35433
Submitted by: Morten Rodal <morten@rodal.no>,
Maxim Konovalov <maxim@macomnet.ru>
MFC after: 1 week
|
|
|
|
|
|
|
| |
PR: doc/33639
Reviewed by: ru
Approved by: ru
MFC after: 1 week
|
|
|
|
|
| |
PR: bin/32354
Obtained from: ping.c,v 1.61
|
|
|
|
|
|
| |
move some err() calls to errx() when message explains the pb enough
do not set errno just before exiting the program
lowercase errx() strings
|
|
|
|
|
|
| |
Binary builds that cannot handle this must explicitly set WARNS=0.
Reviewed by: mike
|
|
|
|
|
|
| |
This is not "useless", as one may have non-default
setting for BINOWN in make.conf, and we still want
these to be installed setuid root in this case.
|
|
|
|
| |
MFC after: 2 weeks
|
|
|
|
| |
MFC after: 2 weeks
|
|
|
|
|
|
| |
is the wrong value on FreeBSD).
MFC after: 1 week
|