From: Bob Barry <bobb@absamail.co.za>
To: Jason Gress <jasong@ccgr.org>
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] Win98 tun networking to host
Date: Tue, 11 May 2004 20:34:17 +0200 [thread overview]
Message-ID: <200405112034.17807.bobb@absamail.co.za> (raw)
Jason -
Thanks for the qemu CVS ebuild.
In another post you wrote:
> Also I was wondering if anyone has gotten a tun network connection to be able
> to see their local host PC's network connections (network neighborhood, etc.)
> to be accessable. Any tips would be appreciated!
I second the motion. I've been battling with ifconfig and route for two days, and
haven't found the magic combination. My qemu-0.5.5 w98se can ping itself, but says
the host's network is unreachable. I put w98 on 192.168.0.1; host is 192.168.1.1; made
host a gateway to w98 network; qemu_ifup works; ifconfig shows tun0 OK; host gets
ping return from w98 IP; kde net info shows eth0 and tun0 both "up"; w98 ipconfig /all
shows similar to two w98 boxes on the host's network. But w98 still says host network
unreachable. Please, you network boffins - give us a hint (or better, a tutorial).
Thanks,
Bob Barry
reply other threads:[~2004-05-11 18:27 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200405112034.17807.bobb@absamail.co.za \
--to=bobb@absamail.co.za \
--cc=jasong@ccgr.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).