From: Gregory Carter <gcarter@aesgi.com>
To: Mulyadi Santosa <mulyadi.santosa@gmail.com>
Cc: "Leena M." <kernmonk@gmail.com>, Kent Tu <kachin2@gmail.com>,
"kernelnewbies@nl.linux.org" <kernelnewbies@nl.linux.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: TESTING ROUTING CODE !!
Date: Thu, 16 Jul 2009 14:16:07 -0500 [thread overview]
Message-ID: <4A5F7C77.3090806@aesgi.com> (raw)
In-Reply-To: <f284c33d0907161134q20d01fc2wf63f484b63bb52d@mail.gmail.com>
I am currently using KVM.
Works very well for creating virtual networks, and testing iptable and
marking of packets for different routing code tests.
I use KVM because it keeps all of the machines seperate, and of course,
some of my machines are BSD.
So if you have different code bases you want to try your modifications
with, KVM is a good choice IMHO.
-Gregory Carter
-Applied Engineering Software Group
-gcarter@aesgi.com
On 07/16/2009 01:34 PM, Mulyadi Santosa wrote:
> On Fri, Jul 17, 2009 at 1:13 AM, Leena M.<kernmonk@gmail.com> wrote:
>> Any specific VM do you recommend , How about Xen ?
>>
>> Regards,
>> Leena
>
> Please don't top post...
>
> Since you talked about routing protocol, I think User Mode Linux would
> do just fine. It runs completely in user space and can be easily
> hooked with gdb.
>
>
next prev parent reply other threads:[~2009-07-16 20:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <e49baca60907161039s7ceb493bje3b1a5c943ce5f33@mail.gmail.com>
2009-07-16 17:56 ` TESTING ROUTING CODE !! Mulyadi Santosa
2009-07-16 18:06 ` Kent Tu
2009-07-16 18:13 ` Leena M.
2009-07-16 18:34 ` Mulyadi Santosa
2009-07-16 19:16 ` Gregory Carter [this message]
2009-07-16 18:36 ` Deepak Shah
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4A5F7C77.3090806@aesgi.com \
--to=gcarter@aesgi.com \
--cc=kachin2@gmail.com \
--cc=kernelnewbies@nl.linux.org \
--cc=kernmonk@gmail.com \
--cc=mulyadi.santosa@gmail.com \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).