We are making some progress, you now know how to enable your ethernet card, and set a static IP address.
NAT. I don't think as a user you have any control over NAT. You see addresses in the range of 192.168.x.y are class C private addresses. What this means is they are not routable over the internet. If a router running a subnet in this address range is requested to route a packett to the ISP over a sub net that is a routable IP address ( not private ) then NAT kicks in, and does address translation. Your 192.168.x.y addresses are never forwarded to the internet.
At this point the IP addresses you are using (on your side local lan) are fine. Understand routers have at least two subnet sides. One side connects to your ISP, that side has its own sub-net, its own IP address, it can be static, or assigned by DHCP. That is usually configurable, and your ISP should be telling you what to do here. Your lan side is a private sub-net.
Quote:
|
I set the default route using "route add 0.0.0.0 eth0"
|
This won't work. Your router has an IP address set for your side of the router. It will be something like 192.168.0.1 ( just a guess on my part, you can verify this ), that IP address is what you want to set in linux with a route add command. Here is what my wroking route table looks like. ( as an example ).
Code:
route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.1.0 * 255.255.255.0 U 2 0 0 eth0
127.0.0.0 * 255.0.0.0 U 0 0 0 lo
default 192.168.1.1 0.0.0.0 UG 2 0 0 eth0
My side of my router's IP addr is 192.168.1.1 so set the default route to match. How this works in a nut shell, the system looks in the /etc/hosts file to look for the IP address to send a packett to. This is good because you can add names of each machine on your local lan, and it will equate a name to IP addr of any local machine you add. If the system can not find the destination, in the /etc/hosts file, then it will forward it to the "default" route. This is why you want it pointed to your router. From here the packett is sent by your router.
Quote:
# Generated by dhcpcd for interface eth0
search
nameserver 192.168.0.1
|
This won't work either. You need the DNS addresses from your ISP. Your router is not a DNS server. So your router can not give a IP address for a name. ( URL ).
Many routers can pass the using systems the DNS information, once they have it. Probably some do not. Your ISP will know the DNS addresses for his network. You can call and ask. If you have a windoze machine that works, you can look at the network setup there. You can also look at the router configuration and see if you can find it in there. Mine shows it, I don't know if yours does or not.
Once you have those addresses, edit the /etc/resolv.conf file as root, and add them. Here is what mine looks like. Note the addresses are not private addresses, like your lan side.
Code:
cat /etc/resolv.conf
# search cliffshome.org
nameserver 206.47.244.52
nameserver 206.47.244.108
These addresses are good for Symaptico.ca, they won't work for any other network.
Hope this gets you going.
