Ok, here's the deal.
I'm working on installing a wireless network in my home using an Orinoco RG 1000 to connect to the net with. My windows laptop is working fine with it and has no problems what so ever (using it to post this). My Linux box however I can not get online at all with. I have a wireless card installed in it and all the drivers in place, and I can ping it from my windows laptop, and I can ping my windows laptop from my Linux box.
The IPs are supposed to be assigned dynamically by the gateway as far as I can tell, but assigning a static IP doesn't solve this either.
Anyone tell me what I have wrong with my configuration under Linux for this to work?
heretic^ :
Checked the route table, it does include a default.
default 10.0.1.1 0.0.0.0 UG 0 0 0 eth0
(all correct as far as I can tell).
The contents of resolv.conf is
nameserver 10.0.1.1
Any further suggestions?
hmm, that is weird, is eth0 your wireless device, or do you have an actual NIC in that machine as well?
Also, does your windows box resolve to the same dns server, or does it point to other ones?
_________________ KOK - 011, Pullin rank on bitches since 2005
Here goes:
1 Eth0 is my wireless card, based on what iwconfig says.
2 The DNS server is the address of the gateway (I think) and I copied the
IP from the Windows box.
3 When I ping google.com I get the line "ping: unknown host google.com"
4 When I ping 216.239.37.99 I get a response.
Since the IP and google are the same computer do I need to fix something with the name resolution?
Joined: Wed 02-20-2002 11:27PM Posts: 867 Location: No one's really sure what became of Castorite after graduation
Source: Off Campus
Igenx wrote:
The IPs are supposed to be assigned dynamically by the gateway as far as I can tell, but assigning a static IP doesn't solve this either.
You are starting the DHCP client on the notebook, right? I prefer dhcpcd, but most distros use dhclient instead. Either one will automatically configure your routing tables and your DNS lookups properly, provided your wireless devices can "see" each other (it appears they can from what you've written).
Assigning a static IP won't give you proper DNS lookups, and may cause collisions when your router properly assigns that IP address to some other wireless device. Static IPs aren't reccomended unless you know what you're doing.
I've tried adding the IP for the nameserver into resolve.conf, no luck.
I've tried running dhclient, also no good. (Pinging google still doesn't work).
If I execute host google.com it resolves to the IP address. Any other help you guys can offer?
The exact output is
...
PHCPDISCOVER on eth0 to 255.255.255.255 port 67
DHCPACK from 10.0.1.1
bound to 10.0.1.4 -- renewal in xxxx seconds
where the value for xxxx varies per time I do it.
Joined: Wed 02-20-2002 11:27PM Posts: 867 Location: No one's really sure what became of Castorite after graduation
Source: Off Campus
Okay, I just re-read this thread. The laptop<==>router connectivity is fine. DHCP is working. Your problem is indeed with DNS.
Right now your DHCP configuration says that your router is also a DNS server, and points your laptop to it. Most routers, to my knowledge, aren't.
Possible scenarios:
1.) Your router does indeed support DNS name serving. Something's wrong with it's upstream connection. Double check to make sure your router is recieving DHCP information from the UMR DHCP servers. If the DNS field is statically assigned, set it to the UMR name servers.
2.) Your router does not support DNS name serving. For whatever reason, it's passing along a screwed-up value for name resolution. Hit the firmware reset button on the back of the router. It should "just work" after that.
In any case, you'll probably have to purge the dhclient's former address lease. This is to ensure that the connection-specific details are re-transmitted to the laptop. Do:
I figured out what the problem was.
The type of gateway I'm using (Orinoco RG 1000) uses a mask for the DHCP server, called 10.0.1.1 (when using the 10.x range). This functions fine under Windows, but for Linux it requires hard coding the IPs of the DNS servers on campus (for the campus network) into resolv.conf.
I added the lines
nameserver 131.151.254.243
nameserver 131.151.1.7
to resolv.conf
and edited the file /sbin/dhclient-script and commented out all if make_resolv_conf fi lines so that the changes I've made don't get over written. Everything works now, except that I need reinstall Gnome for my wife. :?
Users browsing this forum: No registered users and 9 guests
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum