From: Joe Menola <menola@sbcglobal.net>
To: qemu-devel@nongnu.org
Subject: Re: /dev/tun Was: Re: [Qemu-devel] Win98: how to exchange data with Linux
Date: Thu, 15 Jul 2004 20:01:23 -0500 [thread overview]
Message-ID: <200407152001.23559.menola@sbcglobal.net> (raw)
In-Reply-To: <20040715024939.GA23838@jbrown.mylinuxbox.org>
On Wed July 14 2004 9:49 pm, Jim C. Brown wrote:
> On Wed, Jul 14, 2004 at 09:10:01PM -0500, Joe Menola wrote:
> > I'm baaaaaaaaaack. :)
> >
> > I started playing with vbe, I think I've made some progress but can't
> > seem to get things working. It's possible that I'm in over my head....
> > I'll let you be the judge.
> > Here's where I'm at:
> >
> > As root:
> > [root@joe vde-1.5.3]# ./vde_switch -tap tap0 -daemon
> > [root@joe vde-1.5.3]# ifconfig tap0 192.168.0.254
> > [root@joe vde-1.5.3]# chmod 777 /tmp/vde.ctl
> > [root@joe vde-1.5.3]# echo "1" > /proc/sys/net/ipv4/ip_forward
> > [root@joe vde-1.5.3]# iptables -t nat -A POSTROUTING -o eth0 -j
> > MASQUERADE
> >
> > I assume that at this point vde is set and ready.... or have I already
> > fallen off the edge?
>
> The tap0 device should have its own subnet. E.g. below, it appears that
> your LAN already uses the 192.168.0.* subnet. I'd recommend that you use
> this
>
> ifconfig instead:
> > [root@joe vde-1.5.3]# ifconfig tap0 192.168.254.254 netmask 255.255.255.0
Done
>
> I don't know iptables very well, but to the best of my knowledge that looks
> correct. You can try adding this line as well, not sure if it will help or
>
> not however:
> > [root@joe vde-1.5.3]# iptables -t nat -A POSTROUTING -o tap0 -j
> > MASQUERADE
Tried both tap0 and eth0, also each seperately, no difference seen.
>
> (note to self: add iptables guru to vde team)
>
> > As user I start qemu with
> >
> > [joe@joe qemu]$ vdeq qemu -hda /mymnt/qemu/qdrive.img -boot c -m 256
> > -enable-audio -pci -cirrusvga
> >
> > Monitor output
> >
> > QEMU 0.5.5 monitor - type 'help' for more information
> > (qemu) qemu exited: vdeq quits
> > [joe@joe qemu]$
>
> That looks right, unless you are saying that qemu quits prematurely.
No, that was output from a completed and closed Qemu session.
> > I'm somewhat confused about network settings for Win98, my "real" network
> > consists of my linux host (eth0) connected to a dsl router (192.168.0.1).
> > I tried dchp (my router supports it but it's not installed on my linux
> > host), tried static ip's 192.168.0.254 (address assinged to tap0?) and
> > 192.168.0.135 (unused address on my lan) . As gateway's I have both my
> > routers address and eth0's address on my Linux host. Same for dns.
> > No internet, and cannot ping anything.
> >
> > Is there hope? lol
>
> DHCP from the router will not work. Assuming that you've made the above
> change and are using the 192.168.254.* subnet, the router/gateway for Win98
> is 192.168.254.254 and you can assign it any ip address you want in the
> subnet, for example 192.168.254.135 should work. You can also do
>
> /sbin/dhcpd tap0
>
> after you set up vde and install a DHCPd server. That works great for me.
> (I can give you my dhcpd.conf file if you decide to go this route.)
Please do. I've installed a DHCPd server, I doubt that I have dhcpd.conf setup
properly.
Thanks again for all your help. I've been keeping a log of my efforts, if I
get this up and going I could easily put together a cut n paste trail of all
my steps. You might be able to use it as a rough draft for your up coming
"VBE For Dumbies" book?
-jm
next prev parent reply other threads:[~2004-07-16 1:04 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-12 21:56 [Qemu-devel] Win98: how to exchange data with Linux Mario Cazorzi
2004-07-12 22:12 ` Joe Menola
2004-07-13 1:23 ` Jim C. Brown
2004-07-13 2:03 ` Joe Menola
2004-07-13 2:51 ` /dev/tun Was: " Jim C. Brown
2004-07-13 3:15 ` Joe Menola
2004-07-15 2:10 ` Joe Menola
2004-07-15 2:49 ` Jim C. Brown
2004-07-16 1:01 ` Joe Menola [this message]
2004-07-16 1:39 ` Jim C. Brown
2004-07-18 23:12 ` Joe Menola
2004-07-12 22:25 ` John R. Hogerhuis
2004-07-13 7:24 ` vaise
2004-07-13 14:08 ` Sebastien Bechet
2004-07-13 14:18 ` Adrian Smarzewski
2004-07-13 14:46 ` Adrian Smarzewski
2004-07-13 17:22 ` Filip Navara
2004-07-13 17:45 ` John R. Hogerhuis
2004-07-13 17:58 ` Adrian Smarzewski
2004-07-13 18:11 ` John R. Hogerhuis
2004-07-13 18:31 ` Adrian Smarzewski
2004-07-14 2:42 ` Jim C. Brown
2004-07-14 9:50 ` Adrian Smarzewski
2004-07-14 10:04 ` Antony T Curtis
2004-07-14 11:11 ` Fabrice Bellard
2004-07-14 11:58 ` Adrian Smarzewski
2004-07-14 14:01 ` Adrian Smarzewski
2004-07-14 12:28 ` Brad Watson
2004-07-14 12:46 ` Adrian Smarzewski
2004-07-14 16:44 ` John R. Hogerhuis
2004-07-15 0:38 ` Leigh Dyer
2004-07-15 5:25 ` John R. Hogerhuis
2004-07-15 5:38 ` Leigh Dyer
2004-07-14 2:34 ` Jim C. Brown
2004-07-14 6:02 ` Jim C. Brown
2004-07-14 6:15 ` Johannes Martin
2004-07-13 17:50 ` Adrian Smarzewski
2004-07-13 22:31 ` Sebastien Bechet
2004-07-14 2:26 ` Jim C. Brown
2004-07-14 3:15 ` Filip Navara
2004-07-14 9:54 ` Adrian Smarzewski
2004-07-14 9:55 ` Adrian Smarzewski
2004-07-14 10:14 ` J. Mayer
2004-07-14 2:21 ` Jim C. Brown
2004-07-12 22:50 ` [Qemu-devel] " Robert Wittams
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=200407152001.23559.menola@sbcglobal.net \
--to=menola@sbcglobal.net \
--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).