Quantcast
Channel: All Routing posts
Viewing all articles
Browse latest Browse all 8688

BGP Discard on default route

$
0
0

Hi all,

 

I'm sure you know the set up by now but just in case here is a quick refresh of the basic topology:

 

laptop --> Cust router --> CPE --> LNS --> Core --> BGP peer --> Laptop

 

I have the radius assigning an address now to the CPE from a range we are stipulating for the customer. In this test case it is 10.10.10.0/29. The cust router facing the customer laptop is assigned 10.10.10.2/29 and the laptop 10.10.10.3/29. The CPE is allocated 10.10.10.1/29. 

I have configured static NAT on the cust router and I can ping 10.10.10.1 from the customer laptop. Okay so far.

Now, on the LNS I can see the route for the 10.10.10.0/29 network as private access (as it should be as it is inside the L2TP tunnel) so I can ping that address from the LNS.

On the core, I have eBGP running to the BGP peer (simulating an upstream ISP) and on the BGP Peer I have configured several loopback interfaces to simulate upstream internet addresses to test ping to.

On the core, I also have iBGP running from loopback to the other core (setup topology replicated to this one). When I look at the routing table on the core I see the following:

 

 

Clive@THW-CORE-01# run show route 10.10.10.3

inet.0: 37 destinations, 41 routes (36 active, 0 holddown, 1 hidden)
+ = Active Route, - = Last Active, * = Both

0.0.0.0/0 *[Static/5] 2w1d 05:29:59
Discard

 

The route 10.10.10.0/29 network will be in the default route as it is a subscriber. Can anyone please tell me why this would show up as Discard please? This is stopping any testing that we can achieve....

 

Thanks


Viewing all articles
Browse latest Browse all 8688

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>