summaryrefslogtreecommitdiffstats
path: root/sbin/route
Commit message (Collapse)AuthorAgeFilesLines
* link-local multicast address must be converted to KAME specificume2003-12-071-1/+1
| | | | | | | embeded scopeid form. Reported by: dwmalone MFC after: 3 days
* Add a describtion for the '-d' flagbrueffer2003-11-101-1/+3
| | | | | | | | While I'm here, add a missing comma PR: 41787 Obtained from: OpenBSD MFC after: 5 days
* Add the -xresolve flag to the route(8) man page.bms2003-09-261-0/+9
| | | | Reviewed by: ru
* LANG->LC_ALLache2003-08-041-1/+1
| | | | Pointed by: ru
* Fix problem differently, use ache2003-08-041-1/+1
| | | | | LANG=C tr 'a-z' 'A-Z'  for hypotetical case that script may generate non-ascii characters
* Use tr '[:lower:]' '[:upper:]' to work with any localeache2003-08-041-1/+1
|
* There is an undocument feature that ``route -vnd flush'' printsru2003-04-161-1/+1
| | | | | a nice dump of the entire routing table. Allow non-root users to see it too.
* Kill #ifdef NS codepeter2003-03-051-110/+0
|
* Since route(8) itself is no longer setuid, we can get a meaningfulkbyanc2003-01-251-1/+1
| | | | | | | | answer for the euid. As a result, fix it such that setuid scripts or programs may call route(8) to do work on their behalf. Reviewed by: ru MFC after: 3 days
* The .Nm utility.charnier2002-07-061-5/+7
|
* Don't have -prefixlen 128 on host routes.ume2002-06-081-8/+5
| | | | Obtained from: KAME
* Avoid construction which results in label at end of block.wollman2002-05-301-2/+6
|
* Respect -q with "add" and "delete". Document who respects -q.ru2002-05-252-31/+36
| | | | PR: bin/38531
* Allow prefix/prefixlen syntax for IPv6 to have consistencyume2002-05-211-15/+22
| | | | with IPv4.
* Have RTF_HOST for /128 destionation.ume2002-05-211-4/+9
|
* Try to guess prefixlen for guessable cases.ume2002-05-201-0/+33
| | | | | | | | - /0 if matches ::/128 - /64 if matches 2000::/3 and lowermost 64 bit is all 0 - /128 if matches 2000::/3 and lowermost 64 bit is non-zero 0 Obtained from: KAME/NetBSD
* Removed the cruft that became cruft after rev. 1.4.ru2002-04-121-5/+1
| | | | Fixed CLEANFILES.
* o remove __Pimp2002-03-211-3/+3
| | | | o remove main prototype
* Remove 'register' keyword.obrien2002-03-201-30/+30
| | | | | | 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?)
* Introduce an interface announcement message for the routingru2002-01-181-1/+24
| | | | | | | | | socket so that routing daemons and other interested parties know when an interface is attached/detached. PR: kern/33747 Obtained from: NetBSD MFC after: 2 weeks
* Default to WARNS=2.obrien2001-12-041-0/+1
| | | | | | Binary builds that cannot handle this must explicitly set WARNS=0. Reviewed by: mike
* Bring in latest CSRG revisions to this file.ru2001-10-171-11/+11
|
* Synch with NetBSD and OpenBSD.ru2001-08-312-3/+2
| | | | | | | | | | Allow non-superuser to open, listen to, and send safe commands on the routing socket. Superuser priviledge is required for all commands but RTM_GET. Lose `setuid root' bit of route(8). Reviewed by: wollman, dd
* Handle snprintf() returning < 0 (not just -1)brian2001-08-201-0/+4
| | | | MFC after: 2 weeks
* Handle snprintf() returning -1.brian2001-08-201-4/+6
| | | | MFC after: 2 weeks
* mdoc(7) police: utilize the new .Ex macro.ru2001-08-151-3/+1
|
* mdoc(7) police:ru2001-08-071-1/+1
| | | | | | | Avoid using parenthesis enclosure macros (.Pq and .Po/.Pc) with plain text. Not only this slows down the mdoc(7) processing significantly, but it also has an undesired (in this case) effect of disabling hyphenation within the entire enclosed block.
* Remove whitespace at EOL.dd2001-07-151-14/+14
|
* Due to the documented bug in inet_aton(3), it wasn't possibleru2001-07-111-2/+3
| | | | | | | | | | | to use 0xffffffff (INADDR_NONE) as a netmask value. The fix is to use inet_addr(3) which doesn't suffer from this problem. PR: bin/28873 Also, while here, fixed the bug when netmask value was ignored (RTF_HOST flag was set) if the "destination gateway netmask" syntax is used, e.g. ``route add 1.2.3.4 127.1 255.255.255.255''.
* mdoc(7) police: sort SEE ALSO xrefs (sort -b -f +2 -3 +1 -2).ru2001-07-061-3/+3
|
* Allow route(8) to create "proxy only" published ARP entries.ru2001-06-123-5/+24
| | | | | PR: bin/12357 Submitted by: Craig Leres <leres@ee.lbl.gov>
* Fixed the -iface breakage introduced with the latest KAME mergeru2001-06-121-2/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | in revision 1.48. It is pretty valid and often feasible to use a non-point-to-point interface as the gateway. One might, for example, use this to route some hosts through an ARP on a local interface, without having to assign an additional IP address: Script started on Tue Jun 12 16:16:09 2001 # ifconfig rl0 inet rl0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500 inet 192.168.4.115 netmask 0xffffff00 broadcast 192.168.4.255 # netstat -arn -finet | grep -w rl0 192.168.4 link#1 UC 3 0 rl0 => 192.168.4.65 0:d0:b7:16:9c:c6 UHLW 1 0 rl0 1197 # route add -net 192.168.100 -iface rl0 add net 192.168.100: gateway rl0 # ping 192.168.100.1 PING 192.168.100.1 (192.168.100.1): 56 data bytes 64 bytes from 192.168.100.1: icmp_seq=0 ttl=255 time=0.551 ms 64 bytes from 192.168.100.1: icmp_seq=1 ttl=255 time=0.268 ms ^C --- 192.168.100.1 ping statistics --- 2 packets transmitted, 2 packets received, 0% packet loss round-trip min/avg/max/stddev = 0.268/0.410/0.551/0.142 ms # netstat -arn -finet | grep -w rl0 192.168.4 link#1 UC 3 0 rl0 => 192.168.4.65 0:d0:b7:16:9c:c6 UHLW 1 0 rl0 1165 192.168.100 link#1 UCSc 1 0 rl0 => 192.168.100.1 0:d0:b7:16:9c:c6 UHLW 1 4 rl0 1192 Script done on Tue Jun 12 16:17:12 2001
* Sync with recent KAME.ume2001-06-111-120/+114
| | | | | | | | | | | | | | | | | | This work was based on kame-20010528-freebsd43-snap.tgz and some critical problem after the snap was out were fixed. There are many many changes since last KAME merge. TODO: - The definitions of SADB_* in sys/net/pfkeyv2.h are still different from RFC2407/IANA assignment because of binary compatibility issue. It should be fixed under 5-CURRENT. - ip6po_m member of struct ip6_pktopts is no longer used. But, it is still there because of binary compatibility issue. It should be removed under 5-CURRENT. Reviewed by: itojun Obtained from: KAME MFC after: 3 weeks
* When changing an indirect route, kernel routing code allocatesru2001-06-082-2/+11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | a route to the gateway and caches it in the route structure. It may happen (if the routing table is screwed) that the gateway route is the same route as the one being modified, in which case a kernel reports EDQUOT. Be more verbose about this: # route add -net 10 192.168.4.65 add net 10: gateway 192.168.4.65 # netstat -rn -finet Routing tables Internet: Destination Gateway Flags Refs Use Netif Expire default 192.168.4.65 UGSc 1 7 rl0 10 192.168.4.65 UGSc 0 0 rl0 127.0.0.1 127.0.0.1 UH 0 178 lo0 192.168.4 link#1 UC 2 0 rl0 => 192.168.4.65 0:d0:b7:16:9c:c6 UHLW 2 0 rl0 1123 Before: # route change -net 10 10.0.0.1 route: writing to routing socket: Disc quota exceeded change net 10: gateway 10.0.0.1: Disc quota exceeded After: # ./route change -net 10 10.0.0.1 route: writing to routing socket: Disc quota exceeded change net 10: gateway 10.0.0.1: gateway uses the same route PR: bin/1093, misc/26833
* Change the host/bits syntax introduced in route.c,v 1.24 to theru2001-06-082-9/+8
| | | | | | | net/bits syntax, for consistency with netstat(1) in particular. OK'ed by: phk MFC after: 1 week
* - Exit 1 if "add", "change", or "delete" operation fails.ru2001-06-072-10/+12
| | | | | | | | | | | | PR: bin/12489 - Use inet_ntoa(3) where it should have been used. This part of code simply wasn't converted to the "new" style after the routename() function was converted from the protocol-generic version to protocol-specific version in CSRG revision 5.6. MFC after: 1 week
* mdoc(7) police: properly use a -diag list in the DIAGNOSTICS section.dd2001-04-131-7/+7
| | | | Reviewed by: ru
* - Backout botched attempt to introduce MANSECT feature.ru2001-03-261-0/+1
| | | | - MAN[1-9] -> MAN.
* Set the default manual section for sbin/ to 8.ru2001-03-201-1/+0
|
* mdoc(7) police: Change -filled displays (which just happenru2001-02-071-3/+3
| | | | | | to be the same as -ragged in the current implementation) to -ragged. With mdocNG, -filled displays produce the correct output, formatted and justified to both margins.
* Add a couple of newlines in the output from route monitorphk2001-01-151-2/+4
|
* Add `_PATH_DEVZERO'.obrien2000-12-091-1/+2
| | | | Use _PATH_* where where possible.
* Typo fix: forgot -> forget.dannyboy2000-11-261-1/+1
| | | | | PR: 23113 Submitted by: Jimmy Olgeni <olgeni@uli.it>
* mdoc(7) police: use the new features of the Nm macro.ru2000-11-201-4/+7
|
* - Documented the host/bits syntax for destination argument.ru2000-09-291-3/+13
| | | | - Documented that netmask could be specified with third argument.
* Interpret the address argument as network-type address for `destination'ru2000-09-291-13/+12
| | | | | | argument only. Before that, the `route add default gateway' first tried the `gateway' as network address and passed its name to getnetbyname(3), which in the BIND resolution case does the T_PTR lookup on that name.
* Fixed the case where argument of 0.0.0.0/8 would match the default route.ru2000-09-291-4/+4
|
* Clear sin6_scope_id before passing routes into kernel, becaues kernelshin2000-03-111-0/+1
| | | | | | | | | | don't support routes with sin6_scope_id set. Without this fix, routes with IPv6 scoped addr won't work when it is assigned by "route" command. Approved by: jkh Reviewed by: ume
* Add an scope index embedded IPv6 link local addr creation support, by routeshin2000-02-231-0/+4
| | | | | | command. This is a workaround for some kernel interface which can't treat sin6_scope_id, yet.
* Support IPv6 scoped addr in ifconfig and routeshin2000-02-101-25/+71
| | | | | | | | | IPv6 scoped addr display is not yet supported by ifconfig and route. Now almost of IPv6 apps support it, so its support in ifconfig and route is important to keep consisetncy, and to avoid user confusion. Approved by: jkh
OpenPOWER on IntegriCloud