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 am having a Slack trouble. It can't detect my universities DHCP Server, and thuse give me a domain name, or an IP address so I can connect to the internet.
This is puzzeling to me, as SuSe and Red Hat were able to find the thing just fine, and when I was running this slack box back at my house, it found my router just fine.
And if the DHCP server has no name? Or at least, not one we have access to?
I work for an ISP, unfortunately a different one then I use, and we don't have the information, nor can we get it.
I've taking many phone calls from irate customers who use linux who call us flat out liars when we tell them we don't have that information, nor is it required. From everything I know about DHCP, networks, and TCP/IP, it isn't required. The initial request is a general broadcast.
I've seen a bunch of posts on here saying keep hounding your ISP....Sad fact is, even if you find someone who knows linux, they aren't going to have domain names, DNS addresses, DHCP addresses to give you in most cases. They just aren't available.
My cable internet ISP was the same way, they wouldn't give me the dhcp server name--said it wasn't needed and they don't have it. I simply told them that I run Linux and it IS required and it IS needed. They said they don't have the information. I told them that for the $90 per month I'm paying for their package, they needed to get me someone who DOES know the answer as there is no such thing as a DHCP server without a name or IP address. After about 15 minutes of being put on hold and getting transferred around, I got my answer. I also got a job offer because there was only one other guy who knew Linux there. (I applied and got no response though. )
Whether it's actually required or not, I've got no idea, but I know that with the information, you'll get your system online quickly.
As for them not being available, it's incorrect. SOMEONE knows the answer, and if you're paying for your internet connection, then you should be given the answer you need to get online.
It was not necessary for me on Slackware 9. I didn't have any clue what I was doing. I found the config file, turned the "use dhcp" to yes and it connected just fine without any DHCP address. I'm not sure what I did or didn't do, as I am used to SuSE and the yast configuration utility, but if I can work with another slack user to figure out why it's needed sometimes and not others, I'll help however I can.
Well I asked my schools, tech support for help, of which they were none. Anyways, I asked them for the information about DHCP for my linux box, the girl paused and said something to the effect of, "We don't support Linux, and thus i can't give you that information."
Maybe it's really just something silly like a
unpatched jack, or a cross-over cable? :)
if you do
ifconfig eth0 172.163.51.0
(just a bogus address), does it work?
Which network module are you using?
Another possibility is that the server is
trying to assign you a lease that matches
your MAC address (you've been there
before) but someone else has that IP at
the moment? (I've seen setups like that).
My cable internet ISP was the same way, they wouldn't give me the dhcp server name--said it wasn't needed and they don't have it. I simply told them that I run Linux and it IS required and it IS needed. They said they don't have the information. I told them that for the $90 per month I'm paying for their package, they needed to get me someone who DOES know the answer as there is no such thing as a DHCP server without a name or IP address. After about 15 minutes of being put on hold and getting transferred around, I got my answer. I also got a job offer because there was only one other guy who knew Linux there. (I applied and got no response though. )
Whether it's actually required or not, I've got no idea, but I know that with the information, you'll get your system online quickly.
As for them not being available, it's incorrect. SOMEONE knows the answer, and if you're paying for your internet connection, then you should be given the answer you need to get online.
Well, everything has an IP address, certainly. If it didn't, it wouldn't be able to get online. They all also have a name in most cases. However, take for example the ISP I work for......we have hundreds of DHCP servers throughout the network. When you attempt to renew your IP, a broadcast is made to everything in the network. Every DHCP which receives that request replies, and the network device grabs the first set of IP, DNS, and gateway addresses it receives, and ignores the rest.
So you see...with our ISP, we don't have that information. In fact, the only way to get it, would be to find someone else with our service and get it from their DHCP information after they're retrieved a valid IP. However, that may not be the best server to use.
So really, the name isn't needed, and it's not very efficient to use one. There must be a way to make linux work without one, otherwise, someone will need to recode the way the protocol works in linux to take advantage of these newer technologies to their fullest potential.
The problem is that Slackware, can't autodetect the settings, and I didn't know what neede to be put in. Thankfully my SuSe Live-Eval came through for me again, and I simply looked at what it had the settings at.
On a side note, this topic is done. I have been working on this problem for 4 days now (it all started with a virus in windows that despit my best efforts i cannot delete or evade). I had Slackware running at one point in time, for some reason it isnt working here at school. I am switching to Suse. Why I ever left my slack install that i had a month ago, I will never know...
Well...my problem isn't fixed, and no one seems to be answering my thread, so I'll just hijack this one.
How can I get the insmod to run on boot? How can I bring my adapter up on boot?
I'm going to try and figure out DHCP without needing an IP, but I'm not overly concerned. When I get home tonight, I'm going to try getting my settings off of windows, then boot to slack and throw in all the static information.
Ok, here's the update. Setting everything statically STILL didn't work. I configured my domain name, gateway, IP, DNS's....still can't ping a url or any IP outside my network.
ifconfig still shows my adapter as eth0, drivers installed, and if I do an ifconfig eth0 xxx.xxx.x.x it shows my IP and subnet, althought my subnet is the first 2 octets of my IP then .255.255, instead of all 255's, I dunno if that makes a difference. 4AM is too late to be messing around.
Someone must know how to solve this. How come I get ping past my gateway, which is my router?
I have an ISP that uses DHCP for IP addressing, gateway, and DNS information. I also have managed to use some neat tools I've stumbled across to locate information like host name, domain name, and DNS and gateway information I retrieved from when my system is booted in WinXP.
The device is detected as seen in dmesg and all settings are correct. After running ifconfig eth0 the device does not get an IP address, nor can it be used. If I statically set my IP (which will only work when connected to my router as my ISP requires DHCP), DNS, gateway, host, and domain name, I can ping my router and other computers in my network, but cannot resolve hostnames or ping past the router.
So, we know the card is working, we know linux can detect it and work with it IF it's configured statically, but then I am unable to get past my router. If I disconnect the router and connect directly to the cable modem, I can't do anything, since static IP's won't work through my ISP and I can't seem to force my linux to renew it's address.
So if it isn't the router, and it isn't the NIC, and everything is installed, how come I can't connect?
Now, please, give's the output of
ifconfig
route
cat /etc/resolv.conf
cat /etc/host.conf
iptables -L
It would also be interesting to check whether
dhcpcd, dhclient, pump or whatever daemon
you're using is actually installed/running...
If you're worried about intrusions replace the actual
values for your internet presence with some consistent
bogus scheme....
Cheers,
Tink
ok. Will do, as soon as I get home. I haven't installed or ran any daemon's, so that could be the problem too. I don't want to run any servers, just connect, do I need a daemon running? If so...how do I go about that? I work until 1AM CST, so, it'll be awhile before I those outputs for you.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.