| Fedora This forum is for the discussion of the Fedora Project. |
| 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.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
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.
 |
GNU/Linux Basic Guide
This 255-page guide will provide you with the keys to understand the philosophy of free software, teach you how to use and handle it, and give you the tools required to move easily in the world of GNU/Linux. Many users and administrators will be taking their first steps with this GNU/Linux Basic guide and it will show you how to approach and solve the problems you encounter.
Click Here to receive this Complete Guide absolutely free. |
|
 |
12-25-2004, 07:08 PM
|
#1
|
|
Member
Registered: Oct 2004
Location: /usr/home
Distribution: Fedora, Mint, FreeBSD, Android
Posts: 337
Rep:
|
FC2: DNS network settings for wireless
Hi all,
I am having trouble determining the correct settings for connecting to the Net via my laptop' s wireless card. system-config-network recognizes the card, seeing it as eth1. If I configure the device profile to automatically obtain the IP number using DHCP (with the " automatically obtain DNS information from provider" option turned on) and try to activate the network interface, the program spends a minute or so saying
Code:
Determining IP information for eth1...
and then ends with failure.
However, if I supply an IP number manually, say 192.168.1.2, the connection comes up almost instantly, but DNS lookup doesn't work, hence I can't browse or do anything.
I have several DNS servers listed on the DNS page and I tried deleting them, leaving everything empty, but then the RJ45 wired connection doesn' t work either.
Suggestions anyone?
|
|
|
|
12-25-2004, 07:40 PM
|
#2
|
|
Senior Member
Registered: Apr 2003
Distribution: Red Hat + Fedora
Posts: 1,074
Rep:
|
You didn't say anything about the DHCP server. Why?
Regarding DNS servers, what does /etc/resolv.conf contain currently?
|
|
|
|
12-25-2004, 08:03 PM
|
#3
|
|
Member
Registered: Oct 2004
Location: /usr/home
Distribution: Fedora, Mint, FreeBSD, Android
Posts: 337
Original Poster
Rep:
|
Quote:
Originally posted by misc
You didn't say anything about the DHCP server. Why?
|
Well, I assume that is running on the router, right? And I am trying to connect in public spaces, like cafes with hotspots, so I don't always have specific configuration information.
Quote:
|
Regarding DNS servers, what does /etc/resolv.conf contain currently?
|
Code:
; generated by /sbin/dhclient-script
nameserver 199.181.164.1
nameserver 199.181.164.2
This was generated by the LAN login. For some reason, the WLAN doesn't do the same.
|
|
|
|
12-26-2004, 06:34 AM
|
#4
|
|
Senior Member
Registered: Apr 2003
Distribution: Red Hat + Fedora
Posts: 1,074
Rep:
|
DHCP client access failed as you've seen already. You would see in the system's log files that no DHCP server answered or no DHCP server could be reached.
Quote:
|
However, if I supply an IP number manually, say 192.168.1.2, the connection comes up almost instantly, but DNS lookup doesn't work, hence I can't browse or do anything.
|
If a manually added nameserver entry makes it work completely, that's something where to start trouble-shooting.
|
|
|
|
12-29-2004, 07:07 PM
|
#5
|
|
Member
Registered: Oct 2004
Location: /usr/home
Distribution: Fedora, Mint, FreeBSD, Android
Posts: 337
Original Poster
Rep:
|
Quote:
Originally posted by misc
If a manually added nameserver entry makes it work completely, that's something where to start trouble-shooting.
|
Actually, I was entering an IP number for the local host (ie, my laptop), not a remote nameserver.
FWIW, here is the contents of /etc/sysconfig/network-scripts/ifcfg-eth1
Code:
DEVICE=eth1
BOOTPROTO=none
ONBOOT=yes
TYPE=Wireless
NETMASK=
DHCP_HOSTNAME=
IPADDR=192.168.1.4
DOMAIN=
HWADDR=[snip]
USERCTL=yes
PEERDNS=yes
GATEWAY=
IPV6INIT=no
ESSID=
CHANNEL=6
MODE=Auto
RATE=Auto
Nothing seems to work [sigh].
|
|
|
|
12-29-2004, 07:37 PM
|
#6
|
|
Senior Member
Registered: Apr 2003
Distribution: Red Hat + Fedora
Posts: 1,074
Rep:
|
That doesn't work for statically assigned IP addresses anyway. I'm no longer sure what you're trying to achieve. For DNS lookups to work you need to set up name servers with e.g. system-config-network, so they appear in /etc/resolv.conf
|
|
|
|
12-29-2004, 07:59 PM
|
#7
|
|
Member
Registered: Oct 2004
Location: /usr/home
Distribution: Fedora, Mint, FreeBSD, Android
Posts: 337
Original Poster
Rep:
|
Quote:
Originally posted by misc
That doesn't work for statically assigned IP addresses anyway. I'm no longer sure what you're trying to achieve.
|
I am trying to connect to WiFi hotspots in public places like cafés and hotels where I have no control over or even access to the server configuration. I can't manually enter a nameserver in this context because I have no idea to which network I am connecting.
Quote:
|
For DNS lookups to work you need to set up name servers with e.g. system-config-network, so they appear in /etc/resolv.conf
|
This is, in my experience, not entirely correct. For eth0, my LAN connection, I can leave the DNS page of system-config-network empty. I have automatically obtain IP address and automatically obtain DNS information selected in the device profile, and I can simply connect an RJ45 cable from the laptop to an ADSL modem/router and activate the interface; the connection comes up almost instantaneously and the program itself creates the appropriate nameserver entries in /etc/resolv.conf. I assume that the same settings should work for a WLAN connection, because I see Windows and Mac laptop users doing this all the time in the above-mentioned locations, but with Fedora Core 2 on my laptop I have been unable to do so up until now.
Thanks for your feedback.
|
|
|
|
12-29-2004, 08:10 PM
|
#8
|
|
Senior Member
Registered: Apr 2003
Distribution: Red Hat + Fedora
Posts: 1,074
Rep:
|
You misunderstand me. The ifcfg-eth1 file you quoted is not set up for DHCP-based WLAN access. I try to make sense of the two things you mix all the time: 1) statically assigned private IP with no DNS servers , 2) dynamic DHCP-based retrieval of IP and DNS servers. And then we're back at the beginning and the initial questions.
|
|
|
|
12-29-2004, 08:44 PM
|
#9
|
|
Member
Registered: Oct 2004
Location: /usr/home
Distribution: Fedora, Mint, FreeBSD, Android
Posts: 337
Original Poster
Rep:
|
I am sorry if I appear to mix statically-assigned and DHCP-assigned IP numbers, but I do understand the difference. I only mention static IP numbers because in my experiments I have noticed that when I assign a static IP number the system, the WLAN connection does work -- only DNS lookups don't work.
In any event, what are the correct settings for a WLAN interface? I have searched the net and posted queries in several forums, and up to now the only thing I have found is someone with the same problem: https://www.redhat.com/archives/fedo.../msg06956.html. Alas, I couldn't get his solution -- manually running dhclient -- to work for me.
Last edited by Kropotkin; 12-29-2004 at 08:45 PM.
|
|
|
|
| Thread Tools |
Search this Thread |
|
|
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
All times are GMT -5. The time now is 01:16 AM.
|
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|