Hi there,
Thank you for your email. I am currently away on reservist and will only be
back on the 3rd March 2008.
My access to email during this period will be limited.
If there is any urgent matter that require attention, please contact Choon Kiat
([EMAIL PROTECTED]) during this period and cc
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
That's actually a harder problem - you can do it by changing where the system
looks for configuration on boot, install to disk and then modify the
files to change
what's mounted and where the system looks for the configuration, or build from
scratch and create your own LiveCD with the changes in
Thanks for the pointer to /etc/init.d/vyatta-ofr and /etc/default/vyatta.
What I would likely do is have a config file that has the equivalent of a
#include which tries a sequence of locations.
/mnt/usb/config/config.boot, /mnt/flash/config/config.boot,
That's a nice idea. You'll still have to have a default location from
which to start -
which is the challenge of diskless systems :-)
If
On Fri, Feb 29, 2008 at 4:07 PM, Christopher Johnson [EMAIL PROTECTED] wrote:
Thanks for the pointer to /etc/init.d/vyatta-ofr and /etc/default/vyatta.
