dns trouble
I just set up a wireless pci card (Conceptronic C54i) on a Suse 9.1.
Everything seems to work fine (afer much pain)... by everything I mean: I connect to my wireless network with a fixed IP (no DHCP) I can ping my DSL router I can ping my DNS server but now I'm stuck in what I thought would be the easiest step, which is setting up access to DNS. Like I said, I can ping the DNS server of my ISP... I know it works, because dig @<DNS IP> www.google.com works.... I can even get to Google on my browser using the IP I get from dig... but just running dig www.google.com doesn't work.... and of course my browser can't resolve any names..... I thought all I would have to do was set up /etc/resolv.conf with my DNS Ips... here is what I have: domain local nameserver 83.58.0.33 nameserver 83.58.32.97 I am not running any firewall (even though I know I should....).... Anyway, I spent a couple of weeks figuring out the wireless setup, and now that I'm almost there I'm really frustrated to be stuck at this point.... so any help would be much appreciated... Thanks! |
Do you get an error or just no result? Do you have DNS set correctly in /etc/resolv.conf?
|
Well, I seem to be going backwards.... after reboot I cant even ping the DNS server.... so dig says it cant access the DNS...
Heres all the network stuff I can think of... youll notice I have two cards... one is wired to 192.168.2.* the wireless is on the network 192.168.1.*... my access point has IP 192.168.1.1 linux:~ # ifconfig eth0 Link encap:Ethernet HWaddr 00:A0:C5:B2:DD:9B inet addr:192.168.2.2 Bcast:192.168.2.255 Mask:255.255.255.0 inet6 addr: fe80::2a0:c5ff:feb2:dd9b/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:358 errors:0 dropped:0 overruns:0 frame:0 TX packets:55 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 RX bytes:34175 (33.3 Kb) TX bytes:6113 (5.9 Kb) Interrupt:11 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) wlan0 Link encap:Ethernet HWaddr 00:80:5A:22:03:1E inet addr:192.168.1.33 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::280:5aff:fe22:31e/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:233 errors:0 dropped:0 overruns:0 frame:0 TX packets:4 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 RX bytes:21430 (20.9 Kb) TX bytes:288 (288.0 b) linux:~ # iwconfig lo no wireless extensions. eth0 no wireless extensions. wlan0 IEEE 802.11-DS ESSID:"Wireless" Nickname:"unknown" Mode:Managed Frequency:2.412GHz Access Point: 00:A0:C5:82:CE:69 Bit Rate=11Mb/s Encryption key:off Power Management:off Link Quality:100/100 Signal level:-79 dBm Noise level:-154 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 sit0 no wireless extensions. linux:~ # route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.2.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 wlan0 0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 wlan0 linux:~ # cat /etc/resolv.conf domain local nameserver 83.58.0.33 nameserver 83.58.32.97 ......... Like I said, at this point I cant ping the DNS servers... but I can ping my access point.... |
Your routing table looks OK. DNSes are outside your network so you need to have Internet access to be able to get to them. Are you able to check if your AP has Internet access and that it's forwarding the connections (or natting etc)?
|
I'm gonna make a guess here and say that your internet service is not provided to you via you wireless card, but via your wired ethernet interface which is connected to a DSL modem.
Your wireless interface (192.168.1.33/24) is set STATICALLY? Your wired interface (192.168.2.2/24) is set DYNAMICALLY (via DHCP)? Your access point (192.168.1.1) is not really your gateway, but your DSL modem (192.168.2.1 ??? I'm guessing here) IS your gateway? If that is the case, then your default route is set wrong. It should be the IP address of your real gateway, which would be your DSL router (192.168.2.1 maybe?). Hope this helps. Bill Jennings |
Quote:
Say I am connected to a lan but I also have a ppp interface that connects me to the internet. what should be my correct default route and how do i set it up? thanks |
Your default route is for everything that's not covered in the rest of your routing table. It's usually listed last and it's really just a shortcut for "none of the above". So...
Without a default route, what IP addresses are not listed in your routing table? Whatever they are, if they are all routed in the same direction, then just set a default in that direction. If not, then you will have to add routes for some (usually the smallest set) and set the default to point to the others. Routing is really very simple, once you get how it's done. Hope this helps. Bill Jennings |
All times are GMT -5. The time now is 04:13 AM. |