Connected means defined directly on an interface on your router.
because 117.120.0.0/21 is defined directly on a router interface
(eth1) your static route will never work. A connected route takes
preference over a static one. because of this, the route is not
installed in the routing table
Hi,
Thanks! It works now!
Basically it is really now a simple setup where my eth0 is connected to my
upstream and my eth1 will eventually be connected to a layer3 switch which
are able to do IP VLAN and the rest of my servers will be connected to a
layer2 switch. So will my config works in this
On Fri, Feb 29, 2008 at 1:15 PM, Poh Yong Hwang [EMAIL PROTECTED] wrote:
So the docs talking about Originating a route to eBGP Neighbours where it
uses static instead of connected is not really correct? Sorry, trying to
understand the difference between using a static route compared to using a
Hi,
I have problem sending prefixes to my upstream provider based on the docs on
Originating route to eBGP neighbours. My prefixes is as follows
117.120.0.0/21 and here is my detail configuration:
protocols {
bgp {
bgp-id: 203.192.163.146
local-as: 7595
