Re: Kernel & VMware bridging - Whats the difference?

[Earl <unorlist () yahoo com>]

--- Rock Lobster <rocklobster () cheerful com> wrote:
> Lately, I've been attempting to setup a GenII
> honeypot on my laptop with vmware.
> I do have a couple of questions that I can't quite
> work out though.
>
> When I compiled my host o/s kernel I forgot to
> enable bridging and TUN/TAP support,  which
> according to the UML linux paper I read is required
> for the brctl package to work.  Now the things is, 
> because bridging wasnt enabled in my kernel
> intially,  why did the vmware guest o/s get an IP
> from my dhcp server and manage to sit happily on my
> network without any problem?  

I guess you enabled bridge networking w/in VMWare...

I'm not exactly sure what you objective is (Which
paper are you looking at?) but to answer your
question:

Kernel Bridging: primarily routes packets from one
physical interface to another physical interface on a
given system thus creating a layer2 device.

VMWare Bridging: route packets from one virtual
interface of one virtual [guest] machine to one
physical interface of the host system

Although CONFIG_BRIDGE (802.1d Ethernet Bridging) is a
required kernel option for establishing the bridge
with brctl, I don't believe TUN/TAP is.

> I'm also curious as to why I couldnt just install
> the brctl package and then have the product of
> vmnet0 placed into my iptables rules accordingly? 
> Why doesnt vmnet0 show up as another network device
> when I 'ifconfig -a'

Sorry, but I'm lost here...

Earl


                
__________________________________
Do you Yahoo!?
New and Improved Yahoo! Mail - Send 10MB messages!
http://promotions.yahoo.com/new_mail