[Solved] Virtual Box and wicd issue ?

Mac Tzu · 2009-06-27 00:24:58

Hey guys,

I have been using arch for like about a year now. I have slowing converting my family members across by install on their machines. But I have experience a new problem the other day. My brother has two computers a laptop that I have put arch & kdemod 4 in January. His also has a desktop with a windows which has just craped itself, so I said time to arch it !.

He needs xp for some programs (that don't like wine) so i have install virtualbox on his laptop no problems. But after successfully installing arch & kdemod 4 on the desktop I have tried 3 times to install virtualbox. The Problem I have is after installing the binaries as per wiki wicd stops working completly.

wicd cannot get ip address, when I trying connect via wireless error message is "bad password"

So something is going wrong with the bridging.

below listed rc.conf

#
# /etc/rc.conf - Main Configuration for Arch Linux
#

# -----------------------------------------------------------------------
# LOCALIZATION
# -----------------------------------------------------------------------
#
# LOCALE: available languages can be listed with the 'locale -a' command
# HARDWARECLOCK: set to "UTC" or "localtime"
# USEDIRECTISA: use direct I/O requests instead of /dev/rtc for hwclock
# TIMEZONE: timezones are found in /usr/share/zoneinfo
# KEYMAP: keymaps are found in /usr/share/kbd/keymaps
# CONSOLEFONT: found in /usr/share/kbd/consolefonts (only needed for non-US)
# CONSOLEMAP: found in /usr/share/kbd/consoletrans
# USECOLOR: use ANSI color sequences in startup messages
#
LOCALE="en_US.utf8"
HARDWARECLOCK="local"
USEDIRECTISA="no"
TIMEZONE="Australia/Melbourne"
KEYMAP="us"
CONSOLEFONT=
CONSOLEMAP=
USECOLOR="yes"

# -----------------------------------------------------------------------
# HARDWARE
# -----------------------------------------------------------------------
#
# MOD_AUTOLOAD: Allow autoloading of modules at boot and when needed
# MOD_BLACKLIST: Prevent udev from loading these modules
# MODULES: Modules to load at boot-up. Prefix with a ! to blacklist.
#
# NOTE: Use of 'MOD_BLACKLIST' is deprecated. Please use ! in the MODULES array.
#
MOD_AUTOLOAD="yes"
#MOD_BLACKLIST=() #deprecated
MODULES=(fuse vboxdrv vboxnetflt bridge)

# Scan for LVM volume groups at startup, required if you use LVM
USELVM="no"

# -----------------------------------------------------------------------
# NETWORKING
# -----------------------------------------------------------------------
#
# HOSTNAME: Hostname of machine. Should also be put in /etc/hosts
#
HOSTNAME="machine1"

# Use 'ifconfig -a' or 'ls /sys/class/net/' to see all available interfaces.
#
# Interfaces to start at boot-up (in this order)
# Declare each interface then list in INTERFACES
# - prefix an entry in INTERFACES with a ! to disable it
# - no hyphens in your interface names - Bash doesn't like it
#
# DHCP: Set your interface to "dhcp" (eth0="dhcp")
# Wireless: See network profiles below
#
eth1="dhcp"
eth0="dhcp"
wlan="dhcp"
br0="dhcp"
INTERFACES=(lo !eth0 !eth1 !wlan0 !br0)

# Routes to start at boot-up (in this order)
# Declare each route then list in ROUTES
# - prefix an entry in ROUTES with a ! to disable it
#
gateway="default gw 192.168.0.1"
ROUTES=(!gateway)

# Enable these network profiles at boot-up. These are only useful
# if you happen to need multiple network configurations (ie, laptop users)
# - set to 'menu' to present a menu during boot-up (dialog package required)
# - prefix an entry with a ! to disable it
#
# Network profiles are found in /etc/network.d
#
# This now requires the netcfg package
#
#NETWORKS=(main)

# -----------------------------------------------------------------------
# DAEMONS
# -----------------------------------------------------------------------
#
# Daemons to start at boot-up (in this order)
# - prefix a daemon with a ! to disable it
# - prefix a daemon with a @ to start it up in the background
#
DAEMONS=(syslog-ng network dbus wicd hal dhcpcd netfs @crond kdm)

Last edited by Mac Tzu (2009-06-27 22:37:07)

ngoonee · 2009-06-27 00:58:23

In the latest VirtualBox I believe you no longer need bridging, it can directly attach itself to a wireless or wired connection. That's how I'm using it.

Mac Tzu · 2009-06-27 11:19:59

Kewl,

So you saying that I just need to install virtualbox_bin from AUR. and that is it ? What about sharing usb ?

Cheers for the reply by the way

Ashren · 2009-06-27 11:34:36

And you have to chose bridging and your wireless interface (wlan0 etc ..) before firing up your VBox.

Mac Tzu · 2009-06-27 13:09:23

Yeah

bridge_br0="eth0 eth1 wlan0 vbox0" # Put any interfaces you need.
BRIDGE_INTERFACES=(br0)

is what /etc/conf.d/bridges looks like

Ashren · 2009-06-27 13:38:34

Mac Tzu: No, you don't need to bridge networks in rc.conf/conf.d anymore. You just need to chose the setting in VirtualBox.

See: vMXcxNA

Mac Tzu · 2009-06-27 22:35:03

Arrhh !

Awesome,

So I have pulling my hair out for no reason.

Cheers so much for your time

Last edited by Mac Tzu (2009-06-27 22:35:35)

Arch Linux

#1 2009-06-27 00:24:58

[Solved] Virtual Box and wicd issue ?

#2 2009-06-27 00:58:23

Re: [Solved] Virtual Box and wicd issue ?

#3 2009-06-27 11:19:59

Re: [Solved] Virtual Box and wicd issue ?

#4 2009-06-27 11:34:36

Re: [Solved] Virtual Box and wicd issue ?

#5 2009-06-27 13:09:23

Re: [Solved] Virtual Box and wicd issue ?

#6 2009-06-27 13:38:34

Re: [Solved] Virtual Box and wicd issue ?

#7 2009-06-27 22:35:03

Re: [Solved] Virtual Box and wicd issue ?

Board footer