summaryrefslogtreecommitdiffstats
path: root/sbin
Commit message (Collapse)AuthorAgeFilesLines
* o Fix usage(): remove '-l', add missed '-f', sort.maxim2003-07-261-1/+1
|
* Remove references to the '-l' option in synopsis. The rest of thesimon2003-07-261-2/+1
| | | | | | | | description of this option was removed in v. 1.22. PR: docs/54880 Submitted by: Lukas Ertl <l.ertl@univie.ac.at> Approved by: ceri (mentor)
* Minor mdoc(7) cleanup, based on the PR below.simon2003-07-261-2/+4
| | | | | | | PR: docs/54826 Submitted by: Lukas Ertl <l.ertl@univie.ac.at> Reviewed by: ru Approved by: ceri (mentor)
* When deciding whether to download the microcode or not look at the API ratherharti2003-07-251-1/+1
| | | | | | | | than at the vendor. We have three different Fore cards and only the PCA200 need the microcode. Look also at the RAM address and load the code only if it is not zero. A zero RAM address means either a bug in the driver or this is a interface created by harp(4) in which case fatm(4) handles the microcode issue.
* Due to a gcc bug, it doesn't like local variables with names like 'sin'.harti2003-07-251-3/+3
| | | | Rename this for the moment. Also fix a sparc64 alignment warning.
* Make ilmid WARNS=6 clean. The problem were a couple of unused functionharti2003-07-252-14/+14
| | | | arguments and missing consts.
* Build /sbin/gpt on amd64 for good luck as well.peter2003-07-241-1/+2
|
* Simplistic C comment re is wrong, use more correct oneimp2003-07-231-1/+1
|
* Remove old workaroundimp2003-07-231-3/+1
|
* Add a note that net.inet.ip.fw.autoinc_step is ipfw2-specificluigi2003-07-221-0/+4
|
* Quote from a Problem Report:maxim2003-07-211-1/+1
| | | | | | | | | | | | 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
* o Initialize do_pipe before command parsing.maxim2003-07-211-0/+1
| | | | | | PR: bin/54649 Submitted by: Andy Gilligan <andy@evo6.org> MFC after: 3 days
* Take advantage of the use of file system IDs to simplify umount(8)iedowse2003-07-201-298/+144
| | | | | | | | | | | | | | | | | and make it work more reliably in a number of cases that have traditionally been troublesome. The new behaviour is: 1) If the filesystem can be determined by the fsid or device, or uniquely identified by the mountpoint, then just go ahead and call unmount(2) using the file system ID. 2) Otherwise use fstatfs(2) to resolve the path into a file system ID (checking with stat(2) that it is a filesystem root directory). Case 2 can potentially block if an NFS server is down, but it can always be avoided by using an unambiguous specification. It handles all the hard cases such as symlinks and mismatches between the mount list and reality. For example, if a filesystem was mounted as /mnt inside a chroot, it will show up in the mount list as /mnt, but now you can unmount it from outside the chroot with "umount /chroot_path/mnt".
* When mount(8) is invoked with the `-v' flag, display the filesystemiedowse2003-07-183-17/+54
| | | | | | | | | | | | ID for each file system in addition to the normal information. In umount(8), accept filesystem IDs as well as the usual device and path names. This makes it possible to unambiguously specify which file system is to be unmounted even when two or more file systems share the same device and mountpoint names (e.g. NFS mounts from the same export into different chroots). Suggested by: Dan Nelson <dnelson@allantgroup.com>
* Don't call print_pdu() when we are not debugging. This would resultharti2003-07-181-1/+2
| | | | | | | in calling fprintf() with a NULL fp. Strange enough this didn't result in cores in stable, but results in cores now. MFC after: 2 weeks
* Since checkmntlist() and getmntentry() return a struct statfs thatiedowse2003-07-181-24/+17
| | | | includes the filesystem type name, remove the "type" output parameter.
* When the file system to unmount is specified by device name insteadiedowse2003-07-181-45/+7
| | | | | | | | of by mount point, umount had to take care not to unmount the wrong file system if another file system was covering the requested one. Now that the file system to unmount is specified to the kernel using the filesystem ID, this confusion cannot occur, so remove the code that checked for it.
* Userland side of:luigi2003-07-152-14/+22
| | | | | | | | | | | | | | Allow set 31 to be used for rules other than 65535. Set 31 is still special because rules belonging to it are not deleted by the "ipfw flush" command, but must be deleted explicitly with "ipfw delete set 31" or by individual rule numbers. This implement a flexible form of "persistent rules" which you might want to have available even after an "ipfw flush". Note that this change does not violate POLA, because you could not use set 31 in a ruleset before this change. Suggested by: Paul Richards
* Make sure that comments are printed at the end of a rule.luigi2003-07-151-2/+4
| | | | Reported by: Patrick Tracanelli <eksffa@freebsdbrasil.com.br>
* Fix one typo in help() string, remove whitespace at end of line andluigi2003-07-141-24/+23
| | | | | | other minor whitespace changes. Replace u_char with uint8_t in a few places.
* o Rename local variables, do not shadow global declarations.maxim2003-07-141-7/+7
|
* o Kill MINICMPLEN, there is ICMP_MINLEN already.maxim2003-07-141-7/+6
|
* o Be ready to get a reply with length up to IP_MAXPACKET.maxim2003-07-141-11/+18
| | | | | | | | o Warn when recieved packet length is not equal to length of the packet we sent out. Idea from NetBSD. o Fit the dump of packet with wrong data to 80 columns (from NetBSD). Comments from: bde
* ccept of empty lines when reading from a file (this fixes a bugluigi2003-07-141-25/+52
| | | | | | | | | | | | | | introduced in the latest commits). Also: * update the 'ipfw -h' output; * allow rules of the form "100 add allow ..." i.e. with the index first. (requested by Paul Richards). This was an undocumented ipfw1 behaviour, and it is left undocumented. and minor code cleanups.
* Remove reference to max block size. dump no longer limits the block size.grog2003-07-141-13/+1
|
* Add a '-T' flag to print the timestamp as numeric value insteadluigi2003-07-122-5/+14
| | | | | | | of converting it with ctime(). This is a lot more convenient for postprocessing. Submitted by: "Jacob S. Barrett" <jbarrett@amduat.net>
* Document the existence of comments in ipfw rules,luigi2003-07-121-4/+11
| | | | | | | the new flags handled when reading from a file, and clarify that only numeric values are allowed for icmptypes. MFC after: 3 days
* In random order:luigi2003-07-121-218/+277
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * make the code compile with WARNS=5 (at least on i386), mostly by adding 'const' specifier and replacing "void *" with "char *" in places where pointer arithmetic was used. This also spotted a few places where invalid tests (e.g. uint < 0) were used. * support ranges in "list" and "show" commands. Now you can say ipfw show 100-1000 4000-8000 which is very convenient when you have large rulesets. * implement comments in ipfw commands. These are implemented in the kernel as O_NOP commands (which always match) whose body contains the comment string. In userland, a comment is a C++-style comment: ipfw add allow ip from me to any // i can talk to everybody The choice of '//' versus '#' is somewhat arbitrary, but because the preprocessor/readfile part of ipfw used to strip away '#', I did not want to change this behaviour. If a rule only contains a comment ipfw add 1000 // this rule is just a comment then it is stored as a 'count' rule (this is also to remind the user that scanning through a rule is expensive). * improve handling of flags (still to be completed). ipfw_main() was written thinking of 'one rule per ipfw invocation', and so flags are set and never cleared. With readfile/preprocessor support, this changes and certain flags should be reset on each line. For the time being, only fix handling of '-a' which differentiates the "list" and "show" commands. * rework the preprocessor support -- ipfw_main() already had most of the parsing code, so i have moved in there the only missing bit (stripping away '#' and comments) and removed the parsing from ipfw_readfile(). Also, add some more options (such as -c, -N, -S) to the readfile section. MFC after: 3 days
* Do not compare unsigned int values with ULONG_MAX. The comparison iskan2003-07-112-5/+5
| | | | always false on 64bit platforms and GCC 3.3.1 issues warning there.
* Correct to match reality regarding interface names.dannyboy2003-07-081-3/+7
| | | | | | | PR: 51006 Submitted by: "Dmitry Pryanishnikov" <dmitry@atlantis.dp.ua> mdoc clue by: "Simon L. Nielsen" <simon@nitro.dk> MFC after: 10 days
* * introduce a section on SYNTAX to document the handlingluigi2003-07-081-44/+77
| | | | | | | | | | | | | | spaces and comma-separated lists of arguments; * reword the description of address specifications, to include previous and current changes for address sets and lists; * document the new '-n' flag. * update the section on differences between ipfw1 and ipfw2 (this is becoming boring!) MFC after: 3 days
* A bunch of changes (mostly syntactic sugar, all backward compatible):luigi2003-07-081-251/+383
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * Make the addr-set size optional (defaults to /24) You can now write 1.2.3.0/24{56-80} or 1.2.3.0{56-80} Also make the parser more strict. * Support a new format for the list of addresses: 1.2.3.4,5.6.7.8/30,9.10.11.12/22,12.12.12.13, ... which exploits the new capabilities of O_IP_SRC_MASK/O_IP_DST_MASK * Allow spaces after commas to make lists of addresses more readable. 1.2.3.4, 5.6.7.8/30, 9.10.11.12/22, 12.12.12.13, ... * ipfw will now accept full commands as a single argument and strip extra leading/trailing whitespace as below: ipfw "-q add allow ip from 1.2.3.4 to 5.6.7.8, 9.10.11.23 " This should help in moving the body of ipfw into a library that user programs can invoke. * Cleanup some comments and data structures. * Do not print rule counters for dynamic rules with ipfw -d list (PR 51182) * Improve 'ipfw -h' output (PR 46785) * Add a '-n' flag to test the syntax of commands without actually calling [gs]etsockopt() (PR 44238) * Support the '-n' flag also with the preprocessors; Manpage commit to follow. MFC after: 3 days
* Drop the pid file after we call the final daemon call. w/o -n wouldimp2003-07-051-2/+4
| | | | | | | give the wrong pid. Submitted by: ru and Lukas Ertl PR: 54113
* Implement the 'ipsec' option to match packets coming out of an ipsec tunnel.luigi2003-07-042-0/+22
| | | | | | | | | Should work with both regular and fast ipsec (mutually exclusive). See manpage for more details. Submitted by: Ari Suutari (ari.suutari@syncrontech.com) Revised by: sam MFC after: 1 week
* Remove smbfs, portalfs, and nwfs from sbin. The sources live in usr.sbingordon2003-07-0217-2370/+0
| | | | now.
* Move mount_portalfs, mount_smbfs, and mount_nwfs from sbin to usr.sbin.gordon2003-07-021-4/+1
| | | | | | | | They don't have alot of reason to be in sbin and contribute to library bloat in the dynamic case. If you are using any of these filesystem type to hold your /usr, please seek professional help. The actual code was repo-copied by joe.
* Add a new mount flag MNT_BYFSID that can be used to unmount a fileiedowse2003-07-011-70/+71
| | | | | | | | | | | | | | | | | | system by specifying the file system ID instead of a path. Use this by default in umount(8). This avoids the need to perform any vnode operations to look up the mount point, so it makes it possible to unmount a file system whose root vnode cannot be looked up (e.g. due to a dead NFS server, or a file system that has become detached from the hierarchy because an underlying file system was unmounted). It also provides an unambiguous way to specify which file system is to be unmunted. Since the ability to unmount using a path name is retained only for compatibility, that case now just uses a simple string comparison of the supplied path against f_mntonname of each mounted file system. Discussed on: freebsd-arch mdoc help from: ru
* Remove pathnames.h.gordon2003-06-291-2/+0
| | | | Pointed out by: Mathieu Arnold <mat@mat.cc>
* Tweak a couple of utilities so they compile cleanly for /rescue. Mostlygordon2003-06-292-2/+8
| | | | | | path fixes. Submitted by: Tim Kientzle <kientzle@acm.org>
* Move path definitions to include/paths.h. This makes it easier to overridegordon2003-06-292-14/+5
| | | | | | these definitions in the /rescue case. Submitted by: Tim Kientzle <kientzle@acm.org>
* Convert fsck and mount to using execvP to find fsck_foo and mount_foo.gordon2003-06-294-89/+13
| | | | | | | This simplifies the code path and makes the default path easy to override in the /rescue case. Submitted by: Tim Kientzle <kientzle@acm.org>
* o update for new 802.11 supportsam2003-06-281-2/+6
| | | | o fix channel command so channel - does what the man page says
* remove extra whitespace and blank linesluigi2003-06-271-5/+2
|
* o correct mode request handlingsam2003-06-251-3/+6
| | | | | o add 802.11 alias support o suppress display of the default "mode autoselect" when showing the "phy mode"
* The current recommended default time to live (TTL) for the Internetru2003-06-251-3/+3
| | | | | | | Protocol (IP) is 64 [RFC791, RFC1122]. Prodded by: Igor Kucherenko <kivvy@sunbay.com> Obtained from: http://www.iana.org/assignments/ip-parameters
* remove unused file (RELENG_5 and above use ipfw2, the old ipfw1luigi2003-06-241-2667/+0
| | | | has been unused and unmaintained for a long time).
* Split some long lines to fit 80 columns (the code in RELENG_4luigi2003-06-231-5/+10
| | | | was already correct).
* syntactic sugar: support range notation such asluigi2003-06-231-5/+32
| | | | | | | | | | | | | | | 1.2.3.4/24{5,6,7,10-20,60-90} for set of ip addresses. Previously you needed to specify every address in the range, which was unconvenient and lead to very long lines. Internally the set is still stored in the same way, just the input and output routines are modified. Manpage update still missing. Perhaps a similar preprocessing step would be useful for port ranges. MFC after: 3 days
* o Fix sets of rules usage example.maxim2003-06-231-4/+4
| | | | | | PR: docs/53625 Submitted by: Kostyuk Oleg <cub@cub.org.ua> MFC after: 1 week
* Add support for multiple values and ranges for the "iplen", "ipttl",luigi2003-06-222-29/+91
| | | | | | | | | | | | | | | | | | | | | | | | | | "ipid" options. This feature has been requested by several users. On passing, fix some minor bugs in the parser. This change is fully backward compatible so if you have an old /sbin/ipfw and a new kernel you are not in trouble (but you need to update /sbin/ipfw if you want to use the new features). Document the changes in the manpage. Now you can write things like ipfw add skipto 1000 iplen 0-500 which some people were asking to give preferential treatment to short packets. The 'MFC after' is just set as a reminder, because I still need to merge the Alpha/Sparc64 fixes for ipfw2 (which unfortunately change the size of certain kernel structures; not that it matters a lot since ipfw2 is entirely optional and not the default...) PR: bin/48015 MFC after: 1 week
OpenPOWER on IntegriCloud