Hi Troopy,
You want to look at netperf...
http://www.netperf.org/
Cheers,
Robert.
Troopy . wrote:
Hello,
i have a question not directy related to Vyatta but more to networking.
I am looking for a tool that is able to measure the (one-way) latency or
delay.
From what i know ping or
Are there any plans to build NetFlow support into Vyatta?
___
Vyatta-users mailing list
Vyatta-users@mailman.vyatta.com
http://mailman.vyatta.com/mailman/listinfo/vyatta-users
Wooo! Very nice! Man Vyatta sure is going to be one power house of a
router here soon :D
On Jan 17, 2008 1:23 PM, Dave Roberts [EMAIL PROTECTED] wrote:
Are there any plans to build NetFlow support into Vyatta?
Yup. It's something we're looking at over the next three releases or so.
Don't
If you aren't all that worried about microsecond accuracy, then NTP can
be made reasonably accurate, somewhere around +/- 10ms if yoou use
multiple clock sources. See http://www.ijs.si/time/ for more info.
A latency measurement tool that might be useful is D-ITG from
I am using Vyatta as a gateway to the internet and have noticed that it
passes un-NATed private addresses out the public interface. Is there a
way to turn this feature off or should I make a firewall rule?
Thanks,
Ben
___
Vyatta-users mailing list
netflow == nice
sflow == better (imho, at least)
sflow is open, and gives L2 info as well as full bgp path stats rather
than just srcAS and peerAS info. Or you could totally blow our socks off
and do both ;)
But then again, you don't *really* wanna be writing royalty checks to
crisco now, do
Max,
Are you looking for an x-flow collector or are you looking for the
Vyatta to be a flow exporter?
Cheers,
Robert.
Peter Wohlers wrote:
netflow == nice
sflow == better (imho, at least)
sflow is open, and gives L2 info as well as full bgp path stats rather
than just srcAS and peerAS
You'll want to create a firewall rule. By default, a router just
forwards the traffic
it's sent (assuming it can find a route to use for forwarding . . .)
Best,
Justin
On Jan 17, 2008 11:39 AM, Ben Speckien [EMAIL PROTECTED] wrote:
I am using Vyatta as a gateway to the internet and have
You'll also want to edit /etc/syslog.conf and change *.warning to *.*
to record all
log messages; otherwise, lower-level messages will be discared
You can check startup by hand by running /etc/init.d/vyatta-rtrmgr
start which will
save you the physical reboot --
Justin
On Jan 17, 2008 12:54 PM,
There are methods for doing this in kernel using ip_conntrack_netlink
and ulogd2, but last time I looked they weren't incredibly mature. I
should probably browse the code again and see what the current state of
the state is.
Until then, you can add userspace applications that use libpcap to
(SIDE NOTE: (No offense meant) Why should changing interface
notations and static routes cause anything to crash?)
It shouldn't. That's one of the big things we're fixing in Glendale. The
Routermanager process did not handle errors well at all. It has been
eliminated entirely in Glendale.
--
I've used D-ITG also, great for simulation of VOIP/SIP traffic.
One other tools that has a longer history Mgen/Drec. Just like ITG you
will need sync clocks between sender ( mgen ) and receiver ( drec ).
Both pkgs allows for creation by
src/dst/port/ttl/pps/kbps/etc...
Mgen
I commented out all static routes and enabled each one by one. The rtrmgr will
not start will these specific static routes entered. When they are commented
out, rtrmgr starts fine.
Shane McKinley
Habersham EMC
-Original Message-
From: Ken Felix (C) [mailto:[EMAIL PROTECTED]
Sent: Thu
None of these next-hop addresses are assigned to an interface on the router.
Shane
-Original Message-
From: Justin Fletcher [mailto:[EMAIL PROTECTED]
Sent: Thu 1/17/2008 6:46 PM
To: Shane McKinley
Cc: vyatta-users@mailman.vyatta.com
Subject: Re: [Vyatta-users] Waiting for xorp_rtrmgr...
Are they all assigned to a system that's on a network that's directly
connected to the router?
On Jan 17, 2008 3:59 PM, Shane McKinley [EMAIL PROTECTED] wrote:
None of these next-hop addresses are assigned to an interface on the router.
Shane
-Original Message-
From: Justin
Are the next hops directly connected? There was an issue with
recursive route lookup --
On Jan 17, 2008 2:56 PM, Shane McKinley [EMAIL PROTECTED] wrote:
I have found the static routes causing the issue:
route XZ.85.142.64/26 {
next-hop: XX.128.129.18
metric:
I cannot get the live cd to successfully boot up it tries to but
fails any suggestions
--
Rick Mitchell
___
Vyatta-users mailing list
Vyatta-users@mailman.vyatta.com
http://mailman.vyatta.com/mailman/listinfo/vyatta-users
#1 - No, but I do have a static interface-route with XX.128.128.0/20 - the
actual interface is XX.128.128.0/24 -- the reason I have this is for proper BGP
exporting
#2 - Invalid, my mistake
#3 - Dido to #1
My interface-routes are last on my static routes list in the config -- could
this be
Can you provide just a bit more information?
Justin
On Jan 17, 2008 4:41 PM, Rick Mitchell [EMAIL PROTECTED] wrote:
I cannot get the live cd to successfully boot up it tries to but
fails any suggestions
--
Rick Mitchell
___
Vyatta-users
I think you've hit bug 2390: RIB: xorp_rib crashed after a static
route with a nextop through an unxisted interface or a route being
configured and committed
See https://bugzilla.vyatta.com/show_bug.cgi?id=2390 ; it's fixed in
the supported version.
Best,
Justin
On Jan 17, 2008 5:19 PM, Shane
For those of you trying to image computers with Clonezilla and have any
(*dare I say the name*) Cisco switches, you will have timeout issues.
I've recently figured out a resolution and I'd like to share it with
everyone so that in the future someone else does not have to work as hard to
get it
Hello Dave, Ken, Jonathon
Many many thanks for your answers
Very interesting
Thanks
Troopy
-- Original Message --
From: Ken Felix (C) [EMAIL PROTECTED]
Date: Thu, 17 Jan 2008 18:24:17 -0500
I've used D-ITG also, great for simulation of VOIP/SIP
22 matches
Mail list logo
