qemu and -net tap networking
Ritesh Raj Sarraf
Hash: SHA1
Hi,
I'm using two instances of qemu (0.8.1) at a time.
I'm also using kqemu 1.3.0.pre7
One runs GNU/Hurd and the other runs FreeBSD.
Here are the configs I'm using for both.
Hurd:
rrs@learner:~ $ cat `which hurd-boot`
#!/bin/sh
qemu -M isapc -m
128 -hda /mnt/windows/qemu-debian-gnuhurd.img -hdb /mnt/windows/swap-qemu.img -fda /home/rrs/virtualization/qemu/hurd-floppy -net
nic -net
tap,vlan=0,ifname=tap1,script=/home/rrs/virtualization/qemu/qemu-net-script-hurd.sh -boot
a
FreeBSD:
#!/bin/sh
qemu -hda /home/rrs/virtualization/qemu/qemu-debian-freebsd -m 128 -boot
c -net nic -net
tap,vlan=0,ifname=tap2,script=/home/rrs/virtualization/qemu/qemu-net-script-freeBSD.sh
The scripts just do the work of assigning both of the tap interfaces
separate ip addresses and accordingly sets up ip_forwarding settings.
The problem is that when both are running, the one that boots second cannot
ping its gateway. If I halt the first qemu process and restart the second
qemu process, it works fine.
Is this a known behavior ?
I thought separating them with separate virtual networks would allow me to
run multiple qemu instances with full networking support.
TIA,
Ritesh
- --
Ritesh Raj Sarraf
RESEARCHUT -- http://www.researchut.com
"Necessity is the mother of invention."
"Stealing logic from one person is plagiarism, stealing from many is
research."
"The great are those who achieve the impossible, the petty are those who
cannot - rrs"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
iD8DBQFEd2tL4Rhi6gTxMLwRAuvNAKCeYmR3ZYbe1aTDcSPEQlyvXwnMhQCffpHY
CyRZsfyoUExBJoKE5CVipUg=
=1TyQ
-----END PGP SIGNATURE-----
Ritesh Raj Sarraf
Hash: SHA1
ba...@gmx.net on Friday 02 Jun 2006 11:43 wrote:
> Dear Ritesh Sir,
>
> Your message comes with the pgp signed message and ends with some code.
> would you mind describing what is it and why and how is it important to
> sign a message. Is it a digital signeture? does this tells that this
> message is origineted from you and not from other? what about if I copied
> it alongwith my message and send it?
Good you asked this question.
It'd be good to see more people using gpg keys.
PGP - Pretty Good Privacy
GPG - GNU Privacy Guard.
GPG is a the default Digital Key Management software used on more Linux
distributions today.
Basically, you use gpg keys to sign and encrypt your messages. These confirm
the authenticity of the messages.
You can't rely on any XYZ message on the internet just because it shows
someone's name, say mine as <rrs -AT- researchut -DOT- com>. Forging email
is very easy.
These applications are also used to distribute software. Most packages these
days are signed by their vendors to validate that your downloaded package
wasn't tampered.
So now, how does it work ?
There basically are 2 keys you generate, public and private.
The private key is very important and you should keep it securely making
sure you don't lose it or other access it.
The public key is what you put up on your website, or upload it to the Key
servers, or share in Key Signing Parties.
Key Signing parties are one of the best methods of sharing your digital keys
with others as in such cases you first physically verify yourself to the
other person.
So say, Me and You meet. I give you my Public Key i.e. 0x04F130BC and take
your key. You are sure that 0x04F130BC is my key because I met you in
person and gave it to you.
Next, you import my key to your key database.
Next time when I send you a message, I sing my message.
When you receive a message from my email address, you find that it is a
signed message. You email client program asks GPG to look into your key
database to see if it has my public key in it. If yes, it then verifies the
message. If verification goes correct, it confirms that the message indeed
is from me only.
If on the way, any other person tried to tamper the message (say by adding a
SPAM footer) into it, GPG on your machine would complain that the message
is not correct. This way you can verify if I sent you a message or not.
Another part is encryption.
I need to send you a message but it's secret. I need to send you an
encrypted message. For this, both parties need to have each other's keys in
their database. When I send a message to you and select Encrypt, GPG looks
into my key database to see for your public key. It finds your public key
there. Then it encrypts the message using your public key in my database.
This message can _only_ be decrypted by your private key. That's why I said
that your private key should be kept secure.
Encryption is a long topic. GnuPG has made life a lot easier for people
(atleast for me :-). You can get details about GnuPG at
http://www.gnupg.org
HTH,
Ritesh
- --
Ritesh Raj Sarraf | RESEARCHUT - http://www.researchut.com
"Necessity is the mother of invention."
"Stealing logic from one person is plagiarism, stealing from many is
research."
"The great are those who achieve the impossible, the petty are those who
cannot - rrs"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
iD8DBQFEgYoS4Rhi6gTxMLwRAtDeAJ4zCpygvno41B8UB52GJpoRaeTYZACeLFRk
tpqugmzU+43kL7PPfzO+9dg=
=ONp7
-----END PGP SIGNATURE-----
Ritesh Raj Sarraf
Hash: SHA1
It'd be great if we could have a key signing party.
The only problem is I'm not aware how many people are there actively using
Linux/Free Software and in which places they are.
For me, if enough people can meet some time at Birganj, Nepal we can have a
key signing party.
Ritesh
iD8DBQFEgYyJ4Rhi6gTxMLwRAkVfAJ49yBHTD6UgM0CHde7W5cXIJj5KMQCggAoe
+tXIVCT1Z5mMMGV/0y5weiY=
=2COB
-----END PGP SIGNATURE-----