LinuxQuestions.org
View the Most Wanted LQ Wiki articles.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Networking > Linux - Wireless Networking
User Name
Password
Linux - Wireless Networking This forum is for the discussion of wireless networking in Linux.

Notices



Reply
 
Search this Thread
Old 09-23-2005, 12:04 AM   #1
tbthorpe
LQ Newbie
 
Registered: Feb 2005
Distribution: Fedora Core 3
Posts: 13

Rep: Reputation: 0
Network dies almost immediately (FC3)


Hi everyone,

I'm trying to set up my linux box with wireless. So I ran iwconfig and got eth1 set up with my network name, and key and everything, and it seemed to be fine. I tried pinging google, didn't work. I figured maybe i have to "release/renew" so to speak (I'm coming from a longstanding windows background). Anyways, a dhclient -r followed by a dhclient seemed to do the trick. I was online. After the 'dhclient', I got this output:

Internet Systems Consortium DHCP Client V3.0.1
Copyright 2004 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/products/DHCP

Listening on LPF/eth1/00:02:2d:7d:3d:ec
Sending on LPF/eth1/00:02:2d:7d:3d:ec
Listening on LPF/eth0/00:08:0d:95:3e:60
Sending on LPF/eth0/00:08:0d:95:3e:60
Sending on Socket/fallback
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 6
DHCPOFFER from 192.168.0.1
DHCPREQUEST on eth1 to 255.255.255.255 port 67
DHCPACK from 192.168.0.1
bound to 192.168.0.104 -- renewal in 276481 seconds.

So I'm on my network, get on the internet just fine...for about one minute. After that, the only way to get back on is to do a 'dhclient -r' and release it, then renew. Then I'm back on for another minute or so.

Does anyone know what's going on? Thanks a ton for your help!

-Tim T
 
Old 09-23-2005, 10:03 AM   #2
six6
Member
 
Registered: Jun 2004
Location: In Adamantine Chains and penal Fire
Distribution: Debian Sarge & Ubuntu Breezy
Posts: 107

Rep: Reputation: 16
Maybe it's not the dchp lease, but the dns settings. After you lose the connection, try pinging something on the local network or by its IP. If that works, learn more with "man resolv.conf".

If not, well it could be many things. Check dmesg when the connection drops. See if ifconfig still reports you have an IP. Err, maybe your wireless card driver needs work. Etc...

Last edited by six6; 09-23-2005 at 10:05 AM.
 
Old 09-23-2005, 10:42 AM   #3
tbthorpe
LQ Newbie
 
Registered: Feb 2005
Distribution: Fedora Core 3
Posts: 13

Original Poster
Rep: Reputation: 0
Hey six,
So I tried pinging something else on the network, and it worked. The problem is, I really have a lack of network experience, so I'm not sure what that means at all. I read the man page, and didn't really understand. I'm not sure what setting in the dns configuration would make it die so quickly. Any more help would be fantastic. Thanks!
 
Old 09-23-2005, 06:09 PM   #4
six6
Member
 
Registered: Jun 2004
Location: In Adamantine Chains and penal Fire
Distribution: Debian Sarge & Ubuntu Breezy
Posts: 107

Rep: Reputation: 16
Well, resolv.conf must contain the information your system uses to resolve domain names to numerical IP addresses. Behind a router doing NAT (like on your home network for example, where you're sharing one "outside" IP address assigned to your modem among all your home computers) you typically have a private IP address like 192.168.0.104, for example. If this is your setup, your modem is acting as your nameserver, and you should reflect your modem's IP as a nameserver in /etc/resolv.conf:
Code:
# Maybe make your /etc/resolv.conf read just like this
nameserver 192.168.0.1 # use if your IP is 192.168.0.XXX
Though maybe you have are at work, and your IP address is something else, like 134.23.56.221. In that case, you must find out what nameservers to use from your network adminstrators.

An easier way around this problem is to install the resolvconf package (not sure if Fedora has a similar package, Ubuntu/Debian do), or the awesome NetworkManager package that Redhat employees developed. Either of these should manage dns for you.

Edit: Noticed your modem's address is 192.168.0.1, reflected the changes appropriately.

Last edited by six6; 09-23-2005 at 06:14 PM.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
MySQL server dies immediately upon startup... CrazyPilot Linux - Software 2 03-22-2005 08:14 PM
nForce3 network dies after 30 seconds in mandrake 10 antken Linux - Networking 1 10-09-2004 08:53 PM
Network dies after 25 minutes on FC2 virgos Linux - Networking 8 07-07-2004 11:34 AM
Network dies shortly after startup. Passive Linux - Wireless Networking 1 06-05-2004 03:19 PM
Network connection dies every 20 to 30 hours explorer Linux - Newbie 9 04-02-2003 12:39 PM


All times are GMT -5. The time now is 03:49 AM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration