Code:
sudo echo "nameserver 10.1.1.254" >> /etc/resolv.conf
My only petpeeve about using sudo is the difficulty in redirecting output as root.
Use a text editor (as root) and add the line manually. That would be easiest.
Is this the address of the wireless router? Not all routers function as nameservers. If you can run "ipconfig /all" on a windows machine on the wireless network, you can learn which DNS servers it uses. Maybe 10.1.1.254 is OK.
I think that your LAN is in the 192.168.0.0 address space and the wireless network is in the 10. address space. They may be two totally different networks, without any connection. Perhaps they don't want computers to access the LAN via a wireless connection, but have a wireless router to enable you access to the internet. At work, in our conference room, we have a wireless router for guests, who need to have a wireless connection to the internet for demonstrations. Our work laptops have wireless disabled. And by the way, these are both private address ranges. Such addresses do not exist on the Internet.
Code:
Yes all i was given by the IP person was to use the setting :
IP address 10.1.1.(and any range 60 to 69 hear)
Subnet Mask 255.255.255.0
DNS 10.1.1.254
Assuming that 10.1.1.254 is a router, this should be the address you use for the default gateway.
Three things you need to know (if not using DHCP) are
1). The IP address your network device should have.
2). The default gateway IP address. This will be the address of a router.
3). The nameserver (DNS) address. There are sometimes 2 of them if you use your ISPs DNS server.
If using 10.1.1.254 doesn't work as the nameserver address, you could: find out what the IP addresses of the ISP are; use OpenDNS or google's DNS service 8.8.8.8.
Before running "sudo route ..." to configure the default gateway, run "sudo route" without options so we can see what the settings were before. After configuring the default gateway, run "sudo route" again. Post your commands and output in [ code ] ... [ /code ] blocks so they are easier to read. Look at Schniedz's posts above to see what I mean.
Lastly, since there is no DHCP server on the wireless network, stop running "sudo dhclient eth1". You will configure your device manually.
Good Luck!