From owner-freebsd-doc@FreeBSD.ORG Wed Aug 7 07:54:20 2013 Return-Path: Delivered-To: freebsd-doc@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id B11EC7B4 for ; Wed, 7 Aug 2013 07:54:20 +0000 (UTC) (envelope-from andydj@icritical.com) Received: from mail3.icritical.com (mail3.icritical.com [212.57.248.143]) by mx1.freebsd.org (Postfix) with SMTP id 1B90E215B for ; Wed, 7 Aug 2013 07:54:19 +0000 (UTC) Received: (qmail 25278 invoked from network); 7 Aug 2013 07:47:36 -0000 Received: from localhost (127.0.0.1) by mail3.icritical.com with SMTP; 7 Aug 2013 07:47:36 -0000 Received: (qmail 25270 invoked by uid 599); 7 Aug 2013 07:47:31 -0000 Received: from unknown (HELO PDC002.icritical.int) (195.62.218.2) by mail3.icritical.com (qpsmtpd/0.28) with ESMTP; Wed, 07 Aug 2013 08:47:31 +0100 Date: Wed, 7 Aug 2013 08:47:31 +0100 From: Andy D'Arcy Jewell To: Subject: Documentation bug on http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/ipsec.html Message-ID: <20130807084731.7dea6a56@hyperion> Organization: iCritical X-Mailer: Claws Mail 3.8.1 (GTK+ 2.24.10; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Originating-IP: [10.78.99.2] X-TLS-Incoming: YES X-Virus-Scanned: by iCritical at mail3.icritical.com X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Aug 2013 07:54:20 -0000 Hi BSD guys, I'm working through the IPSEC tutorial at: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/ipsec.html After the tunnel creation incantations, there are some route add commands that seem to be in error, syntactically: """ As expected, both sides have the ability to send and receive ICMP packets from the privately configured addresses. Next, both gateways must be told how to route packets in order to correctly send traffic from either network. The following command will achieve this goal: # corp-net# route add 10.0.0.0 10.0.0.5 255.255.255.0 # corp-net# route add net 10.0.0.0: gateway 10.0.0.5 # priv-net# route add 10.246.38.0 10.246.38.1 255.255.255.0 # priv-net# route add host 10.246.38.0: gateway 10.246.38.1 """ The "route add {net,host}" commands both return errors "route: bad address: {net,host}". From the manpage, I see it should probably be "-net" or "-host", but fixing that then gives the error "route: bad address: 10.78.200.0:" which I guess is complaining about the trailing colon. In the manpage, under the DIAGNOSTICS section, it hints at something resembling the format used above, but I think it means "error output format": add [host | network ] %s: gateway %s flags %x The specified route is being added to the tables. The values printed are from the routing table entry supplied in the ioctl(2) call. If the gateway address used was not the primary address of the gateway (the first one returned by gethostbyname(3)), the gateway address is printed numerically as well as symbolically. iCritical is a brand of Critical Software Ltd. Registered in England & Wales: 04909220. Registered Office: IC2, Keele Science Park, Keele, Staffordshire, ST5 5NH. This message has been scanned for security threats by iCritical. The information contained in this message is confidential and intended for the addressee only. If you have received this message in error, or there are any problems with its content, please contact the sender.