From rtgwg-bounces@ietf.org Wed Jan 10 09:29:37 2007 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1H4eRX-0003dr-1r; Wed, 10 Jan 2007 09:28:43 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1H4eRV-0003di-Np for rtgwg@ietf.org; Wed, 10 Jan 2007 09:28:41 -0500 Received: from mailgw3.ericsson.se ([193.180.251.60]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H4eRM-0008BL-Ob for rtgwg@ietf.org; Wed, 10 Jan 2007 09:28:41 -0500 Received: from esealmw129.eemea.ericsson.se (unknown [153.88.254.120]) by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id EB4BB179 for ; Wed, 10 Jan 2007 15:28:25 +0100 (CET) Received: from esealmw114.eemea.ericsson.se ([153.88.200.5]) by esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Wed, 10 Jan 2007 15:28:25 +0100 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Date: Wed, 10 Jan 2007 15:28:24 +0100 Message-ID: <63A23507A6F0C344BE6D60303E9441D994FD00@esealmw114.eemea.ericsson.se> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Ways to add a static route entry to a router? Thread-Index: Acc0w5Ykk0iODShpTrqLLZC3UhGBlA== From: =?iso-8859-1?Q?Andr=E1s_Cs=E1sz=E1r_=28IJ/ETH=29?= To: X-OriginalArrivalTime: 10 Jan 2007 14:28:25.0521 (UTC) FILETIME=[96B74A10:01C734C3] X-Brightmail-Tracker: AAAAAA== X-Spam-Score: 0.0 (/) X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab Subject: Ways to add a static route entry to a router? X-BeenThere: rtgwg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: rtgwg.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: rtgwg-bounces@ietf.org Dear All, After hours of struggling to find different ways of installing static = route entries to routers, it seems that the only way of doing this is by = CLI. I can hardly believe that. I thought of SNMP and it seems to be able to = read the routing tables, modify routes and even invalidate/remove routes = but it seems not be capable of adding a new static route entry to a = router. Do I miss something? Is there some other protocol or any other way? Any answers would be = higly appreciated! In addition, do you know of any limitations/constraints how frequently = one can add/remove static route entries from Cisco/Juniper routers? Sorry for the somewhat offtopic questions but many thanks for any = answers. Kind regards, Andras _______________________________________________ rtgwg mailing list rtgwg@ietf.org https://www1.ietf.org/mailman/listinfo/rtgwg From rtgwg-bounces@ietf.org Wed Jan 31 15:51:57 2007 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HCMPg-0003jA-GN; Wed, 31 Jan 2007 15:50:40 -0500 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HCMPZ-0003cF-Ce; Wed, 31 Jan 2007 15:50:33 -0500 Received: from ns3.neustar.com ([156.154.24.138]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1HCMPZ-0004vi-26; Wed, 31 Jan 2007 15:50:33 -0500 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns3.neustar.com (Postfix) with ESMTP id BF9CB175F1; Wed, 31 Jan 2007 20:50:02 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1HCMP4-0004xs-Bm; Wed, 31 Jan 2007 15:50:02 -0500 Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Message-Id: Date: Wed, 31 Jan 2007 15:50:02 -0500 X-Spam-Score: -2.5 (--) X-Scan-Signature: 31247fb3be228bb596db9127becad0bc Cc: rtgwg@ietf.org Subject: I-D ACTION:draft-ietf-rtgwg-rfc3682bis-09.txt X-BeenThere: rtgwg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: rtgwg.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: rtgwg-bounces@ietf.org --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Routing Area Working Group Working Group of the IETF. Title : The Generalized TTL Security Mechanism (GTSM) Author(s) : V. Gill, et al. Filename : draft-ietf-rtgwg-rfc3682bis-09.txt Pages : 18 Date : 2007-1-31 The use of a packet's Time to Live (TTL) (IPv4) or Hop Limit (IPv6) to verify whether the packet was originated by an adjacent node on a connected link has been used in many recent protocols. This document generalizes this technique. This document obsoletes RFC 3682. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-rtgwg-rfc3682bis-09.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-rtgwg-rfc3682bis-09.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-rtgwg-rfc3682bis-09.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2007-1-31121526.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-rtgwg-rfc3682bis-09.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-rtgwg-rfc3682bis-09.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2007-1-31121526.I-D@ietf.org> --OtherAccess-- --NextPart Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ rtgwg mailing list rtgwg@ietf.org https://www1.ietf.org/mailman/listinfo/rtgwg --NextPart--