VMWare/Firestarter - was 2d chance at Unity

[NoOp]

Lets move this out of the Unity thread.

On 04/19/2011 09:52 PM, Lucio M Nicolosi wrote:
> On Wed, Apr 20, 2011 at 12:36 AM, NoOp <glgxg at sbcglobal.net> wrote:
>
> [huge snip]
>
> G.,
>
> - I have VMWare installed on my Maverick 64 with Network Type
configured as NAT.
>
> - I'm running Firestarter.
>
> - When WMWare is off (most of the time) and vmnet8 is up (as on
> startup) I keep receiving these messages, that clog my log files.

Configure Firestarter (or iptables) to allow or ignore the 172 traffic
(172.16.x.0/24). Check your ifconfig for the

http://www.fs-security.com/docs.php
or for iptables:
http://communities.vmware.com/thread/128134

>
> - According to the referred old link
>
http://communities.vmware.com/thread/49350;jsessionid=A905D175FC22F0D4EDEC2196D2D1B374
> it seems that something in the Ubuntu host is trying to contact the
> virtual net, in my case 172.16.88.1-255, but get no response since
> although the virtual board, and router and DHCP are all configured and
> running, VMWare is off.
>
> - The src/des ports are (at least) 137/138  (samba), 631 (internet
> printing, probably cups) and 17500 (dropbox), services installed in
> the host.

Dropbox polls
http://forums.dropbox.com/topic.php?id=21238
http://forums.dropbox.com/topic.php?id=16253
http://ubuntuforums.org/archive/index.php/t-1403920.htm

>
> - If I turn off Firestarter, the flow of messages, every few seconds,
> stops, but...
>
> - in this case, although unseen, shouldn't the requests still be
> alive, waking up each every few seconds to consume (not so) precious
> CPU cicles in my extremely underloaded Athlon X2, legacy, processor
> (and no, I won't give it to you) in such an inelegant way?

I'm not very familiar with Firestarter - I typically don't have it
installed & have only installed it a few times for testing. I'll install
it today & see what the effect is.

>
> - Thus, since I cannot shut off all these services, wouldn't my only
> option be to shut of the vmnet8 offender as I usually do? (But then,
> Linux never offers "only" options).

VMware is off - no guest running:

$ ps -e | grep vm
 1890 ?        00:00:01 vmware-converte
28437 ?        00:00:00 vmware-usbarbit
28506 ?        00:00:00 vmnet-bridge
28514 ?        00:00:00 vmnet-dhcpd
28517 ?        00:00:00 vmnet-netifup
28520 ?        00:00:00 vmnet-dhcpd
28523 ?        00:00:00 vmnet-natd
28526 ?        00:00:00 vmnet-netifup

$ sudo service vmware status
Module vmmon loaded
Module vmnet loaded

$ sudo vmware-networks --status
Bridge networking on vmnet0 is running
DHCP service on vmnet1 is running
Hostonly virtual adapter on vmnet1 is enabled
DHCP service on vmnet8 is running
NAT service on vmnet8 is running
Hostonly virtual adapter on vmnet8 is enabled
Network detection service is not running
All the services configured on all the networks are running

If you wish to conserve cycles:
$ sudo service vmware stop
You can verify by:
$ ifconfig and  $ ps -e | grep vm
you'll not longer have vmnet1 & vmnet8.

Just remember to turn it back on before you bring up vmware:
$ sudo service vmware start
...