Robert Bays wrote:
> Komal,
>
> Vyatta doesn't integrate Julian's patchset by default right now. Was
> there a specific function/patch in there you needed support for?
>
> Cheers,
> Robert.
>
Hi Robert,
I would like to see patch applied for dual routing i.e alternate routing
and better dead
Aubrey,
Using tc outside the scope of Vyatta should be ok as long as you don't
harm your routing protocol updates. You can use tc on a vif, the parent
interface or both.
Cheers,
Robert.
Aubrey Wells wrote:
> Until native traffic policing is built in to vyatta, is it safe for me
> to use tc f
Hmm. I've never seen this with interfaces, but maybe it's a VIF issue.
Try setting the global log level to debug; maybe there's more information below
warning level.
And, of course, that's what support is for - they're GOOD with puzzles
like this!!
Justin
On Nov 5, 2007 9:43 PM, Aubrey Wells <
Komal,
Vyatta doesn't integrate Julian's patchset by default right now. Was
there a specific function/patch in there you needed support for?
Cheers,
Robert.
Komal Shah wrote:
> Hello,
>
> Does stock Vyatta kernel implement Julian's patch form
> http://www.ssi.bg/~ja for advance routing,load
It is the next hop. To give you one of the scenarios:
Added 8.17.X.253 /30 to eth0 vif 1180
subnet doesnt show up in vyatta's routing table (show route) but does
show up in the system table (route -n) and I can ping the other side
(8.17.X.254) both from within xorp and from the unix shell.
S
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 rout
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 while
Good questions - I think you're just seeing a synchronization issue.
If you see it in the system route table ("route -n" from the Linux
shell or "show route system forward" from the CLI) it's really in the
system RIB as the forwarding information base is updated from the RIB.
However, "show route"
Anyone? :-(
--
Aubrey Wells
Senior Engineer
Shelton | Johns Technology Group
404.478.2790
www.sheltonjohns.com
On Nov 3, 2007, at 10:16 PM, Aubrey Wells wrote:
Hi,
I'm having this really frustrating problem where occasionally I
will add an ip/network to vyatta, or delete a
I have two PCs linked by an E1 link wit Sangoma A101 cards
PC1
eth0 10.0.0.0/24
wan0
local 192.168.0.1
remote 192.168.0.2
prefix-length 24
PC2
eth0 10.9.1.0/24
wan0
local 192.168.0.2
remote 192.168.0.1
prefix-length 24
show route does not show the wan ports and I cannot ping them locally
Looki
Eric,
You can boot the system off of the livecd, mount your root disk and edit
the /etc/passwd file. You might also want to run fsck on the disk to
see if your file system has become corrupted somehow.
Cheers,
Robert.
Eric Basham wrote:
> Greetings, our Vyatta in our lab is running 2.0. It h
exactly! When it comes to something like that, you are much better
off spending the time to rebuild the router than trying to muk around
with a possibly compromised one.
On 11/5/07, Joey Kelly <[EMAIL PROTECTED]> wrote:
> On Monday 05 November 2007 04:48:56 pm Eric Basham wrote:
> > Greetings, ou
Thanks
I changed to serial i/f to ppp encapsulation and now the link comes up
and packets are flowing
I already have one end internal clock and the other external.
Now to learn how to set up routing so that I can use it
David
Robyn Orosz wrote:
> Hi David,
>
> PPP or HDLC will work back to back
On Monday 05 November 2007 04:48:56 pm Eric Basham wrote:
> Greetings, our Vyatta in our lab is running 2.0. It had been acting
> strangely of late (snmp not working at all) and then I became unable to
> login to it via telnet/ssh/http - would never get a prompt for
> ssh/telnet, and http would ne
Added a static route rule did the trick for me:
rule 4 {
type: "source"
translation-type: "static"
outbound-interface: "eth0"
protocols: "all"
source {
address: 10.10.5.20
}
destination {
Greetings, our Vyatta in our lab is running 2.0. It had been acting
strangely of late (snmp not working at all) and then I became unable to
login to it via telnet/ssh/http - would never get a prompt for
ssh/telnet, and http would never let me login. Went to the console and
could not load up xorps
Hello,
I have a mail server behind Vyatta on a private subnet. I forward SMTP traffic
to it with:
rule 34 {
type: "destination"
translation-type: "static"
inbound-interface: "eth0"
protocols: "tcp"
source {
netwo
Hi David,
PPP or HDLC will work back to back with a cross-over cable as you have
it. You may need to set one side of the connection for internal
clocking as Paul has stated.
For frame-relay, you need to set one side as the DCE which can't
currently be done via the CLI. You'll need to edit th
David,
Years ago when I used to do these back-to-back configs on Cisco gear, I
had to apply internal clock source to bring the T1/E1 up. I think by
default, these facilities rely on external clock (the telco) to bring
the link up.
Is there an option for internal clock source?
Paul
-Origin
I am a Vyatta beginner trying to set up a very simple static network
with two pcs and a E1 link between them using Sangoma A101 cards.
I have set up the frame relay encapsulation and local and remote
addresses with vif 16.
The wan cards are linked by a E1 pins 1,2 to 4,5 crossover cable that I
h
Hello everybody!
I'm new with Vyatta, and I'm using VC3, and I have a problem with
static routes and qualified-next-hop which is very important for my
network implementation.
I've got a static route to 10.100.153.0/24 through 10.100.153.100 (Wan
interface) and a qualified-next-hop throug (10.100.
21 matches
Mail list logo
