qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Lonnie Cumberland <lonnie@neenet.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] eth0 problems
Date: Sat, 28 Aug 2004 20:55:49 -0400	[thread overview]
Message-ID: <41312995.4080900@neenet.com> (raw)
In-Reply-To: <20040829010306.GA15763@jbrown.mylinuxbox.org>

Hello All,

I just looked at  the kernel sources for my 2.6.3-7mdk kernel and 
TUN/TAP has already been compiled in as a module.

Although there is no /dev/net/tun0 listed or /dev/tun0 as well

Actually, on I do not even see the /dev/eth0 even though it is now 
working on my  cable modem and the ifconfig show that it is there.

Any other ideas?

Thanks for the help,
Lonnie

Jim C. Brown wrote:

>On Sat, Aug 28, 2004 at 07:43:55PM -0500, Joe Menola wrote:
>  
>
>>>Technically, tun doesn't provide eth0 for the host either. In fact, the
>>>kernel documentation says you need to have eth0 first, or else you cant use
>>>tuntap (that may no longer be true though, remember this is from the
>>>offical kernel docs :). tuntap provides a tun0/tap0 device in the host and
>>>an eth0 device in the guest. user net should provide an eth0 as well, but
>>>it won't add anything to the host.
>>>
>>>If eth0 doesn't show, that may be due to lack of hardware support. Be sure
>>>your kernel has support for the ne2k-pci module.
>>>
>>>user net isn't just for internet access .. the guest can still access the
>>>LAN or the WAN/intranet .. they just can't initiate a talk to it.
>>>
>>>      
>>>
>>You're correct...nor can network shares be accesed?
>>
>>    
>>
>
>Not sure. A node on the lan can't access shares on the user net guest, but
>the guest may be able to access shares on the node ... this depends on the
>protocol in question.
>
>Windows shares have the additional complication that they have to be on the
>same subnet, although I am not familar with Windows XP and above so they may
>have removed this limitation (Samba removes this limitation if you set an option
>in its config file).
>
>  
>
>>Thanks for the correction.
>>
>>
>>    
>>

  reply	other threads:[~2004-08-29  1:56 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-28 21:54 [Qemu-devel] eth0 problems Lonnie Cumberland
2004-08-28 23:13 ` Joe Menola
2004-08-28 23:04   ` Lonnie Cumberland
2004-08-29  0:18     ` Joe Menola
2004-08-29  0:33       ` Jim C. Brown
2004-08-29  0:43         ` Joe Menola
2004-08-29  1:03           ` Jim C. Brown
2004-08-29  0:55             ` Lonnie Cumberland [this message]
2004-08-29  1:54               ` Mark Williamson
2004-08-29  2:53               ` Joe Menola
2004-08-29  2:33                 ` Lonnie Cumberland
2004-08-29  5:39                   ` Joe Menola

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=41312995.4080900@neenet.com \
    --to=lonnie@neenet.com \
    --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).