From 48e842cc98b1436da57c8682c6c8414ba379ed7c Mon Sep 17 00:00:00 2001
From: Martin Mares <mj@ucw.cz>
Date: Mon, 10 Apr 2000 11:21:40 +0000
Subject: Use neighbor cache to track direct route to the peer or multihop
 destination.

Calculate next_hop properly based on the local address we get from the
neighbor entry.
---
 proto/bgp/config.Y | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

(limited to 'proto/bgp/config.Y')

diff --git a/proto/bgp/config.Y b/proto/bgp/config.Y
index f83191a..f18f2bd 100644
--- a/proto/bgp/config.Y
+++ b/proto/bgp/config.Y
@@ -15,7 +15,7 @@ CF_HDR
 CF_DECLS
 
 CF_KEYWORDS(BGP, LOCAL, NEIGHBOR, AS, HOLD, TIME, CONNECT, RETRY, KEEPALIVE,
-	MULTIHOP, STARTUP, VIA)
+	MULTIHOP, STARTUP, VIA, NEXT, HOP, SELF)
 
 CF_GRAMMAR
 
@@ -47,6 +47,7 @@ bgp_proto:
  | bgp_proto CONNECT RETRY TIME NUM ';' { BGP_CFG->connect_retry_time = $5; }
  | bgp_proto KEEPALIVE TIME NUM ';' { BGP_CFG->connect_retry_time = $4; }
  | bgp_proto MULTIHOP NUM VIA IPA ';' { BGP_CFG->multihop = $3; BGP_CFG->multihop_via = $5; }
+ | bgp_proto NEXT HOP SELF ';' { BGP_CFG->next_hop_self = 1; }
  ;
 
 CF_CODE
-- 
cgit v1.2.3