SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
At home dhcp worked great, assigned me an IP, and I could access places on the network and the internet. However, on campus DHCP doesn't work at all. I tried running dhcpcd with combinations of -r and -S to no success. What should I do to get dhcp working on my campus network?
yes - spoofing the mac may work, and will rule it out. Registering the other mac is better - not good idea going to sysadmin with a tale of all the cracker tricks you've tried. Talking to sysadmin will be definitive... and solve the issue even if it ain't the mac address.
Shot in the dark:
Are you running 2.6.24.x where x < 4 ?
If so, is this a new problem since upgrading to 2.6.24.x?
If so, then upgrade to 18.104.22.168 - there was a fix in there relating to how the kernel sends DHCP DISCOVER, and it caused some dhcp servers to not hand out ip addresses.
Why would spoofing my MAC address be considered cracking?
I din't say that - I said that the sysadmin may frown upon it.
Spoofing a mac address is a cracking technique. It is used to gain you access where you would not otherwise be allowed.
I mean I'm supposed to have access to my campus network and I'm not being malicious.
From what was discussed, you are supposed to have access to your campus network from a registered computer. We may disagree with, even despise, that policy, but it is the one in place. At least, that was the speculation in previous posts.
While intent counts for a lot, the sysadmin may feel that you are circumventing campus IT security. You will probably find you have some contractual obligations concerning that and there are usually quite stiff penalties involved with breaking them.
Much better to let the sysadmin know what you want to do - it is certain that the issue has been considered.
I had sent an email to my sysadmin
Don't e-mail - do you have any idea how many emails these guys get each day? Go to that worthies office and bang on the door.
I felt optimistic, ran dhclient and it worked.
Perhaps the lease on the old machine's access expired. (Try the old machine.) Perhaps sysadmin got your email and did something after all? May be worth clearing up.
I had emailed him before and had gotten a timely response so I didn't see a reason to see him in person. I know he made at least one change, the instructions to register for linux is now a bash script instead of a .exe... Note that to register you first need to be connected to the LAN i.e. dhcp needs to be working.
So last night cable (tv + broadband) crashed for everyone in the area. Internet is currently up, and it works in my room (tested on friend's computer), but I can't connect on my slackware computer. The only thing I've changed in the interim is I commented out everything in /etc/inetd.conf. dhclient gives an error saying I'm already registered/have an address, so I don't think the problem is with that.
Grr, I'm really not sure what's wrong with my network connection. It intermittently stops working. When I try to ping I get an unknown hostname. When I run dhclient it tells me can't bind to dhcp address, address already in use. Ideas?