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.
New problem: When I reboot plugged into the router, evrything goes back to not working. I have to do what I mentioned above in order to get everything to work. That's a hassel. Is there anything I can change to avoid doing this?
Is this a dialup connection or always on? Do you use ppp to connect? The only time I've none /etc/resolv.conf to change
is when ppp-go adds tempary entrys to it?
Please post the output from:
ifconfig -a
/etc/resolv.conf
The 192 numbers are the ones I posted at the beginning of the thread. Whenever I change the resolv.conf file, it creates resolv.conf.sv and the regular resolv.conf stays the same. How can I change this and have it stick?
I know it's not kicking me off after a certain amount of time because it's broadband--it's supposed to be on all the time. It worked fine inder Suse 7.3 so I know it's possible, I just need to know where to go and what to fix.
Originally posted by busbarn I know it's not kicking me off after a certain amount of time because it's broadband--it's supposed to be on all the time.
Correct me if I'm wrong, you're using ATT Broadband services?
Now quoting from AT & T Broadbroad Internet page:
Configure Computer Settings with DHCP What is DHCP?
Once assigned, the address stays with that computer for a certain time period and then returns to the pool if not used. This means that more users can be supported with fewer addresses, thus assisting in the implementation of uniform equipment and service requirements for the latest cable Internet service industry.
This falls under the RTFP ... Read the fine print
Now what YOU can do about it?
1. Don't worry about /etc/resolv.conf
2. Once the ip address is lost, then what:
Login in with your user account:
$ su - root
# ifconfig eth0
Check the ip address
# ifconfig eth0 down
# ifconfig eth0 up
Count to 10
# ifconfig eth0
Did you ip address changes? If so your "in like flint"
if no:
# tail -f /var/log/messages
Look for messages about DHCP, ip adress being assigned.
3. What can you do to try to "beat the sytsem"
You could try running script that sends at ping say every 30 minutes the script might look something like this:
(ping -i 1800 $5 &) >/dev/null 2>&1
If you want to getting a little trickier, you could write that script so that if the ping fails it run the ifconfig comands
for you. [/b] See the BASH scripting howto]/b] at http://tldp.org for details.
You might also want to put that ping script in a file called:
/etc/rc.d/rc.pingme and call it from rc.local. so that when ever your system reboots it starts the ping for you.
Correct me if I'm wrong, you're using ATT Broadband services?
Now quoting from AT & T Broadbroad Internet page:
Configure Computer Settings with DHCP What is DHCP?
Once assigned, the address stays with that computer for a certain time period and then returns to the pool if not used. This means that more users can be supported with fewer addresses, thus assisting in the implementation of uniform equipment and service requirements for the latest cable Internet service industry.
This falls under the RTFP ... Read the fine print
That's misleading..... and doesn't really clarify the DHCP.
When its not in use, like if they have their cable modem off or computer off, is when it will return the IP not in use. If you have a computer on or router connected, its always being used. AT&T and most other cable modem ISP's set a release time after they assigned an IP, usually 24 hours. When that time is up and the computer or router are still connected, they renew their IP address automatically.
busbarn,
You shouldn't be losing your connection at all, but don't worry, its not kicking you off like that, your just losing your IP or connections in other ways.
Also, they didn't happen to give you the option of a static IP did they ? When I had AT&T broadband, I got a static IP, but also could use DHCP if I wanted...
Your could well be right?
But once again RTFP, read the fine print on you service contract. If it was me I would be on the phone asking
for a clarification before I ruled it out.
If YOU rule out ATT, what does that leave you with, flakey
hardware?
Tricky --
What do you think about the PLAN A +B As listed above?
Originally posted by pickledbeans Your could well be right?
But once again RTFP, read the fine print on you service contract. If it was me I would be on the phone asking
for a clarification before I ruled it out.
If YOU rule out ATT, what does that leave you with, flakey
hardware?
Tricky --
What do you think about the PLAN A +B As listed above?
Not sure what your asking pickled ?
And I could be right, I know I'm right.. cause I have had AT&T and I currently work for the Cable Company.. The only one that drops you that I know of due to inactivity is AOL Broadband, since they require you to login to connect. Which I have no idea why anyone would want that on a boradband connection
What ever dude ------
Since you missed it the first time.
Question to orginal poster? How low between disconnects? Look in /var/log/messges there should be
messges when connection starts and when it ends.
Here is PLAN B:
Quote:
Originally posted by pickledbeans
Now what YOU can do about it?
1. Don't worry about /etc/resolv.conf
2. Once the ip address is lost, then what:
Login in with your user account:
$ su - root
# ifconfig eth0
Check the ip address
# ifconfig eth0 down
# ifconfig eth0 up
Count to 10
# ifconfig eth0
Did you ip address changes? If so your "in like flint"
if no:
# tail -f /var/log/messages
Look for messages about DHCP, ip adress being assigned.
3. What can you do to try to "beat the sytsem"
You could try running script that sends at ping say every 30 minutes the script might look something like this:
(ping -i 1800 $5 &) >/dev/null 2>&1
If you want to getting a little trickier, you could write that script so that if the ping fails it run the ifc
onfig comands
for you. See the BASH scripting howto]/b] at http://tldp.org for details.
You might also want to put that ping script in a file called:
/etc/rc.d/rc.pingme and call it from rc.local. so that when ever your system reboots it starts the ping for you.
You can connect to the internet only if you bypass the router?
A friend have a broadband connection (no cable but ADSL), he uses a Cisco 677 ADSL router. In the operation guide it say that the router have a DHCP server and client.
when you connect without the router you are assigned a ip address of 12.x.x.x
But when you are connected through the router you are assigned a number of the type 192.168.x.x . This range of address is reserved for use only in private Lans, so i think that the DHCP client in the slackware computer is receiving the ip address from the router and not from the ISP.
If this is correct you can check the configuration of the DHCP client in the Suse and Slackware boxs and compare.
Also if the clients are different you can try using in the slackware box the same that in the Suse.
Wow, lots of intructions that I have no clue of the meaning. As long as I leave my computer on I'm fine. BUt X crashed and I couldn't use any of the terminals (tty1-5). Keyboard locked. I tried alt-ctrl-del and the computer rebooted. When it rebooted, the ip adress changed from 12 to 192. So as long as I don't reboot. It's all cool.
I would have compared suse and slack but I only have one box and I wiped out suse. I would mount zip and suddenly all of my devices (floppy, cdrw, dvd, and zip) were busy and I couldn't save or load anything from them. Great--perfect time to try slack.
Lesson Learned: print out config files before total reboot for comparison sake.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
