SlackwareThis Forum is for the discussion of Slackware Linux.
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've asked this question before, but i'll ask agian in the hope someone can shed some new light on it.
im running slackware 10 and cant get an ip address from my isp for either one of my nic's via dhcp.
my rc.inet1.conf has the dhcp attribute set to 'yes', and when i ./rc.inet1 the dhcp client displays the mac address for both my card but does not manage to get an address from my isp.
i've also used the netconfig tool, but have not had any luck with that either. i dont need to pass any other information about my net connection.
my windows / redhat machine has no problem getting an address from my isp via dhcp. i have tried the nic from that machine in my slackware box with no luck . static address work fine.
is there something fundamental i'm missing? as i've run out of options
First, we kill any running instance of the dhcp client daemon.
Then, we bring eth0 down.
Next, we try manually running the dhcp client on your card, and we verify whether or not you got an IP through it.
If dhcpcd eth0 command hangs for a while, there's the rub...
Next, we run mii-tool to see how the link is on your card to your router/modem. Not all cards or drivers are mii enabled, so this may not work.
Finally, we ping google to see if our connection is up and running
i dunno if u have tried this or not, swap a different nic card out, and check<cat /proc/pci> it could be either a nic hardware failure or your disto did not detect the right nic card.
All fails install windows and trouble shoot from there.
i think its your nic gone bad.
i've tried 3 different nics, including one that i know it works fine on. i tried listing the pci cards that way before, and everything seems fine. lsmod seems right too.
both cards work fine with static address's though.
yeah, i looked for clues in redhat, but found nothing.
as a last gasp attempt i took the nic from my xp /redhat xo and put it in the slackware box and then put redhat 9 on it, so it was just the same setup as my main box, but this didnt work either.
I am having the same exact problem. My Setup was behind a wireless router and it worked fine.
I moved it and connected the cable modem connected directly to my NIC and now I cannot get internet via dhcp.
dmesg | grep eth0 shows and lspci show the hardware drivers are recongnized.
mii-tool shows that eth0 is on my card
But when I try to obtain an ip lease dhcpcd hangs and I cannot get an ip.
I am running Slackware 10 and I have tried all the above suggestions as well. netconfig, etc.
Any ideas why my wireless router would give me an ip via dhcp but not my cable modem directly?
I too am having the same problem, rc.inet1.conf is very bare except for DHCP=yes.
When i upgraded from 9.1 to 10.0, no problem. But when i used all the .new config files, shit started to break.
Distribution: SlackWare 10.1+, FreeBSD 4.4-5.2, Amiga 1.3,2.1,3.1, Windors XP Pro (makes a fair answering machine)
Posts: 287
Rep:
If you are plugging a machine with slack directly to an ISP PPOE install RoPPOE (roaring penguin) the ppoe client.
Other distros and windor use a WAN mini-port for these connections by default.....
Slack needs one thus RoPPoe....
I found out a while back that you just have to edit /etc/rc.d/rc.inet1.conf and add in some address. I have a comcast cable modem to connect to, this is mine:
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]="255.255.255.0"
USE_DHCP[0]="yes"
DHCP_HOSTNAME[0]="192.168.1.100"
# 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"
Sorry for the late reply, but I still this will help someone googlin away.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.