VectorLinux
October 25, 2014, 12:37:06 am *
Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
News: Visit our home page for VL info. To search the old message board go to http://vectorlinux.com/forum1. The first VL forum is temporarily offline until we can find a host for it. Thanks for your patience.
 
Now powered by KnowledgeDex.
   Home   Help Search Login Register  
Please support VectorLinux!
Pages: [1]
  Print  
Author Topic: Repairing Network connection in Virtualbox image of Vector Linux SOHO 7.0  (Read 1702 times)
jasa
Member
*
Posts: 1


« on: August 10, 2013, 09:55:30 am »

The image of VectorLinux 7.0 SOHO downloaded from http://virtualboximages.com/VectorLinux+7+SOHO+Virtual+Appliance has the network link broken (through the NAT interface of Vbox 4.2.16 installed in Windows 7). After a few hours, and without finding straightforward instructions in the net, I managed to solve the problem. The interface in the guest is eth1.

The following files shall be configured like shown below (many comments in the files are removed for brevity). Also, I used netconfig to give (irrelevant) username and domain (IMHO this is not relevant for solving the problem) and to order the use of DHCP (the default choice, check the netconfig manual). Hope this helps someone, because that VL image is quite nicely configured.

After this, reboot or re-init the network (by running /etc/rc.d/rc.inet1 restart).

UPDATE: the same exact recipe worked for another PC, also a Win7 host, with a cable link (instead of wifi). 
                                                                    
                                                                    
/etc/rc.d/rc.inet1                                                                    
                                            

Code:
#!/bin/sh
# This file is supposed to be created by vnetadd
# and modified by vnetset.
# You can modify it by hand, but be careful ;-)

## The settings
DEVICE='eth1'
DHCP='yes'
IPADDR='127.0.0.1'
NETMASK='255.255.255.0'
GATEWAY=''
PROBE='no'

. /etc/rc.d/functions-network "$@"

/etc/rc.d/rc.inet2        

Code:
#!/bin/sh

## The settings
DEVICE=eth1
DHCP=yes
IPADDR=
NETMASK=
GATEWAY=
PROBE=no

. /etc/rc.d/functions-network "$@"


/etc/rc.d/rc.inet1.conf

Code:
# /etc/rc.d/rc.inet1.conf
#
# This file contains the configuration settings for network interfaces.
# If USE_DHCP[interface] is set to "yes", this overrides any other settings.
# If you don't have an interface, leave the settings null ("").



# Config information for eth0:
IPADDR[0]=""
NETMASK[0]=""
USE_DHCP[0]="yes"
DHCP_HOSTNAME[0]=""

# Config information for eth1:
IPADDR[1]=""
NETMASK[1]=""
USE_DHCP[1]="yes"
DHCP_HOSTNAME[1]=""

# Config information for eth2:
IPADDR[2]=""
NETMASK[2]=""
USE_DHCP[2]=""
DHCP_HOSTNAME[2]=""

# Config information for eth3:
IPADDR[3]=""
NETMASK[3]=""
USE_DHCP[3]=""
DHCP_HOSTNAME[3]=""

# Default gateway IP address:
GATEWAY=""

# Change this to "yes" for debugging output to stdout.  Unfortunately,
# /sbin/hotplug seems to disable stdout so you'll only see debugging output
# when rc.inet1 is called directly.
DEBUG_ETH_UP="no"

« Last Edit: August 13, 2013, 05:26:06 am by jasa » Logged
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2013, Simple Machines Valid XHTML 1.0! Valid CSS!