I have found that VC3 is very fussy about adding routes. Changing an
interface and deleting the node followed by recreating it with new
settings leads to no routing table entries for me.
I have found that the only way to get a correct table is to start from a
clean format
David
Aubrey Wells
Sounds like we have the same issue then. Do your routes show up
correctly in the system routing table? What kind of hardware are you
using? I'm running a dell 1950 with dual dual-core 3.0 Xeons and 8
gig of ram. No PCI cards, all onboard broadcom NICs.
--
Aubrey Wells
Thanks for the response - sorry for my impatience. :-)
I dont mind the viewing discrepancy, its the fact that vyatta doesn't
recognize the existance of the routes - so I can't do anything with
them. So you're saying load config.boot should fix the problem? Will
that cause any downtime
No problem - I know exactly how you feel some days!
And I'd missed the point that it didn't make into the system route table, so the
first question I'd ask is whether the next hop you're specifying is
directly connected?
If it isn't, try using the IP address of the directly connected next hop
