Operating Systems > Linux and UNIX

setting up internet

<< < (3/3)

Master of Reality:
did you add
route add default gw 192.168.1.1
to your client machines?

shuiend:
client machine means the computer i am trying to connect to the router correct? if that is yes then i do put that command in but it is after i have already staticaly made my ip so it does not get an ip from my dhcp server in the router

shuiend:
voidman to your reply on the netstat thing i have set my default gateway to the router and when i do netstat -rn this is what i get
Kernel IP routing table
Destination     Gateway         Genmask         Flags   MSS Window  irtt Iface
192.168.1.0     0.0.0.0         255.255.255.0   U        40 0          0 wlan0
0.0.0.0         192.168.1.1     0.0.0.0         UG       40 0          0 wlan0
that looks the same as you had but it still doe snot allow me to get outside of the network

voidmain:

quote:Originally posted by wild_jester / BOB:
voidman to your reply on the netstat thing i have set my default gateway to the router and when i do netstat -rn this is what i get
Kernel IP routing table
Destination     Gateway         Genmask         Flags   MSS Window  irtt Iface
192.168.1.0     0.0.0.0         255.255.255.0   U        40 0          0 wlan0
0.0.0.0         192.168.1.1     0.0.0.0         UG       40 0          0 wlan0
that looks the same as you had but it still doe snot allow me to get outside of the network
--- End quote ---


Now what is the error message you get when you type:

$ ping www.google.com

and can you successfully:

$ ping 216.239.51.101

If the first one fails and the second one is successful the you have a DNS resolver issue and your network is working. Then all you should have to do is configure the "/etc/resolv.conf" file with the proper domain/search domains and DNS servers.

If you can not ping the second address above but you can ping your gateway address then I will be a little confused as it should work. The only other thing I can think of at that point is possible firewall configuration on your SuSe box may be getting in the way. You might also try a:

$ /usr/sbin/traceroute -n 216.239.51.101

and see how far you get. Also I do not see a route for your loopback device (127.0.0.1).

Also, don't know if you've seen this or if it would be of any help:
http://talk.trekweb.com/~jasonb/articles/linux_wireless2.shtml

[ August 29, 2002: Message edited by: VoidMain ]

Navigation

[0] Message Index

[*] Previous page