From: "Hetz Ben Hamo" <hetz@witch.dyndns.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Win2003 and network - the saga continues
Date: Sat, 1 May 2004 18:07:21 +0200 [thread overview]
Message-ID: <20040501160102.M44620@witch.dyndns.org> (raw)
In-Reply-To: <1083425268.5552.22.camel@localhost>
Hi,
> I don't think it is a good idea if Fabrice starts publishing other
> people's software. I don't know what the licence is but perhaps
> just a hyper-link would suffice.
There are only 2 files inside this ISO. The README file which I wrote (do I
really need to declare GPL license for a README.TXT I wrote? :)
The other file is just an INF file which is a simple text file with a list of
vendors and their card names. Nothing secret or proprietary here. Heck, you
can erase 98% of it and can still use it. The actual file that INF file
installs (ne2000.sys) is actually an internal part of Windows 2000/XP/2003
and it's NOT inside the ISO image I provided.
> You added the host machine as a gateway within the guest? You also need
> to tell the host how to respond to the pings with something like:
>
> route add -host <guest IP address> tun0
>
> Personally I use the scripts published to the list earlier to set up
> NAT and DHCP for the guest machine. The post was by Nathan Hand on Thursday
> entitled "improved qemu-ifup script".
I already have a DHCPD server running at home and it seems that iptables with
kernel 2.6 causing some problems (but maybe my machine is wrong configured -
this machine is a big mix of Redhat 8 + 9 + Fedora, all in 1 partition, big
party ;)
Thanks,
Hetz
prev parent reply other threads:[~2004-05-01 16:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-01 14:39 [Qemu-devel] Win2003 and network - the saga continues Hetz Ben Hamo
2004-05-01 15:27 ` James Ascroft-Leigh
2004-05-01 16:07 ` Hetz Ben Hamo [this message]
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=20040501160102.M44620@witch.dyndns.org \
--to=hetz@witch.dyndns.org \
--cc=qemu-devel@nongnu.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).