Linux Blog

VMWare: “Unable to build the vmnet module”

Filed under: General Linux,Linux Software — at 10:49 am on Monday, July 21, 2008

If you run into the following problem:

VMware Server is installed, but it has not been (correctly) configured
for the running kernel. To (re-)configure it, invoke the
following command: /usr/local/bin/

and then try to issue the command and get something similar to the following:

/tmp/vmware-config1/vmnet-only/bridge.c: In function ‘VNetBridgeUp’:
/tmp/vmware-config1/vmnet-only/bridge.c:949: error: implicit declaration of function ‘sock_valbool_flag’
make[2]: *** [/tmp/vmware-config1/vmnet-only/bridge.o] Error 1
make[1]: *** [_module_/tmp/vmware-config1/vmnet-only] Error 2
make[1]: Leaving directory `/usr/src/kernels/'
make: *** [vmnet.ko] Error 2
make: Leaving directory `/tmp/vmware-config1/vmnet-only'
Unable to build the vmnet module.

Then try to use the VMWare any patch from:
I had used the patch before to get my VMWare Server up and running but did not realize that you had to use the patch after kernel upgrade or your VMWare server will no longer work.

Who knew?

Linux Wireless Morals

Filed under: General Linux — at 2:40 pm on Monday, April 7, 2008

Is it moral for some one who uses Linux to borrow some ones Wireless?

Lets say you are at a hot spot and you need to jump online really quickly but some the internet house your are at charges for wireless. Is it moral to connect to some one else’s wifi?

Maybe you just moved and the internet has not arrived at your house yet. Is it moral to use a neighbors for an undefined amount of time before you are settled in and have the internet set up?

If you answered yes to any of these questions then you may either be cheap (like me) or have low morals. Either way, there are ways to protect your identity and information while borrowing wireless by using Linux.

A good way to protect your self while borrowing some one else’s wireless is to tunnel with SSH. You can use a squid proxy on a port and set up your SSH to forward a local port to the squid server. Once this is done your unencrypted http traffic is now tunneled through an encrypted SSH session. If the person who owns the wireless network (or any one else) were to sniff the packets they would just see the destination address and not the full traffic information.

Use SSH for everything that is unencrypted. SSH to a known host and use these protocols here. FTP and POP are good examples of protocols that can be used by SSH. Don’t use an instant messenger through the internet, it is very easy to sniff the packets. Some times a friend may give out incriminating information which could get you in trouble.

A good device to help with protecting your information while using some one else’s wireless is DD-WRT. Once installed on a supported device it has many functions that can be used. Bridging mode, VPN passthru, advanced routing can all be used to protect your information. DD-WRT would be especially good if set up as a bridge to the other persons wireless. You could use a NAT firewall to hid how many devices you really have connected and change the mac addresses of the clients.

In the future I’ll be showing you more ways to hide your privacy while using wireless technologies so stay tuned!