Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I have a version of slackware installed as a virtual machine and am not able to ping hosts or otherwise receive data from any IP addresses external to the LAN. I think this problem is due to the hostname of the vm not being recognized by the gateway (ddwrt); the vm receives an IP via dhcp but the gateway does not seem to recognize its hostname (registers as *).
Will readily respond with whatever conf file is needed.
First thing to know is what Virtualization product are you using. Another thing to consider is if your Virtual Machine is setup to use a NAT network card or a Bridged network card. NAT will give out a private IP to communicate with the Host machine only. Bridged will obtain an IP from your network DHCP server.
It makes Sense that it will work via NAT. When you use NAT vmware will give a private IP address to access the Host machine and other NAT machines. It will then do any external traffic via the Host machine's network configuration.
When you use Bridged, the VM acts as if it is a separate machine and not a VM on the Host machine. Therefore all network traffic is done on it's own with your Physical Network. check your settings in /etc/network/interfaces. You may need to specify a gateway on dns servers.
The file you listed is not present; instead I have listed my rc.inet1.conf and hosts files:
# 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]=""
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"
## Example config information for wlan0. Uncomment the lines you need and fill
## in your info. (You may not need all of these for your wireless network)
#IFNAME[4]="wlan0"
#IPADDR[4]=""
#NETMASK[4]=""
#USE_DHCP[4]="yes"
#DHCP_HOSTNAME[4]="icculus-wireless"
#DHCP_KEEPRESOLV[4]="yes"
#DHCP_KEEPNTP[4]="yes"
#DHCP_KEEPGW[4]="yes"
#DHCP_IPADDR[4]=""
#WLAN_ESSID[4]=BARRIER05
#WLAN_MODE[4]=Managed
##WLAN_RATE[4]="54M auto"
##WLAN_CHANNEL[4]="auto"
##WLAN_KEY[4]="D5AD1F04ACF048EC2D0B1C80C7"
##WLAN_IWPRIV[4]="AuthMode=WPAPSK EncrypType=TKIP WPAPSK=7B1ABEEB5D197741923ED26727569C365E31212096A0EAFAD563B268BAD01CAF TxRate=0"
#WLAN_WPA[4]="wpa_supplicant"
#WLAN_WPADRIVER[4]="ndiswrapper"
## Some examples of additional network parameters that you can use.
## Config information for wlan0:
#IFNAME[4]="wlan0" # Use a different interface name nstead of
# the default 'eth4'
#HWADDR[4]="00:01:23:45:67:89" # Overrule the card's hardware MAC address
#MTU[4]="" # The default MTU is 1500, but you might need
# 1360 when you use NAT'ed IPSec traffic.
#DHCP_KEEPRESOLV[4]="yes" # If you dont want /etc/resolv.conf overwritten
#DHCP_KEEPNTP[4]="yes" # If you don't want ntp.conf overwritten
#DHCP_KEEPGW[4]="yes" # If you don't want the DHCP server to change
# your default gateway
#DHCP_IPADDR[4]="" # Request a specific IP address from the DHCP
# server
#WLAN_ESSID[4]=DARKSTAR # Here, you can override _any_ parameter
# defined in rc.wireless.conf, by prepending
# 'WLAN_' to the parameter's name. Useful for
# those with multiple wireless interfaces.
#WLAN_IWPRIV[4]="AuthMode=WPAPSK EncrypType=TKIP WPAPSK=thekey TxRate=0"
# Some drivers require a private ioctl to be
# set through the iwpriv command. If more than
# one is required, you can place them in the
# IWPRIV parameter (space-separated, see the
# example).
All of your wireless config settings are commented out. Deleted the leading # on the following lines to make them look like this
Code:
## Example config information for wlan0. Uncomment the lines you need and fill
## in your info. (You may not need all of these for your wireless network)
IFNAME[4]="wlan0"
IPADDR[4]=""
NETMASK[4]=""
USE_DHCP[4]="yes"
DHCP_HOSTNAME[4]="icculus-wireless"
DHCP_KEEPRESOLV[4]="yes"
DHCP_KEEPNTP[4]="yes"
DHCP_KEEPGW[4]="yes"
DHCP_IPADDR[4]=""
WLAN_ESSID[4]=BARRIER05
WLAN_MODE[4]=Managed
WLAN_RATE[4]="54M auto"
LAN_CHANNEL[4]="auto"
WLAN_KEY[4]="D5AD1F04ACF048EC2D0B1C80C7"
WLAN_IWPRIV[4]="AuthMode=WPAPSK EncrypType=TKIP WPAPSK=7B1ABEEB5D197741923ED26727569C365E31212096A0EAFAD563B268BAD01CAF TxRate=0"
WLAN_WPA[4]="wpa_supplicant"
WLAN_WPADRIVER[4]="ndiswrapper"
Try running ifconfig and see what your IP address is. Looks like to me you are not actually pulling an IP because your network settings are commented out. Interesting thing is that it knows what IP matches google.com even though it can not connect. Do you have a local DNS server?
Hmmm ... if resolv.conf looks like that you're most likely getting a lease
from a router. Funny that it shouldn't set-up a default route via the
DHCP response, though.
What does 'route' - executed w/o parameters - tell you?
OK, that's all wrong ... 0.0.0.0 is not a valid IP address,
if your router announces itself as that I'm not surprised
you're not getting anywhere. Looks to me like the router
is misconfigured.
All of the other devices on the LAN receive IPs successfully, including two windows boxes and a debian distro..... I'm considering giving up on Slackware altogether...
OK, that's all wrong ... 0.0.0.0 is not a valid IP address,
if your router announces itself as that I'm not surprised
you're not getting anywhere. Looks to me like the router
is misconfigured.
Yes. Might be informative to set DEBUG_ETH_UP="yes" in /etc/rc.d/rc.inet1.conf and see what shows in the logs after reboot or
Code:
/etc/rc.d/rc.inet1 eth0_restart
Isn't there a config file to control which parameters are accepted from the DHCP server? Might be possible to prevent accepting the default route using that and configure the desired one in /etc/rc.d/rc.inet1.conf using GATEWAY.
Are "all the other boxes" virtualised, too? What's the host OS?
Pardon me. The "other boxes" are actual physical devices.
The host OS for the VM that I am troubleshooting is XP 64.
If the router is announcing an incorrect IP? How can I correct this?
I know this is getting off topic, but I am using a Buffalo WHR-HP-G54 with DDWRT v24. I have just created another vm and the router is announcing itself as 0.0.0.0 there as well...
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.