My apologies, I removed the broadcast address line from the /etc/network/interfaces file below, and I added this to my etc/hosts file: 192.168.1.9 [your computer's name here]
I rebooted and that seemed to do the trick. on 12/10/00 3:10 PM, Eirik Dentz at [EMAIL PROTECTED] wrote: > Nevermind, I just fixed it. > > eirik > > > on 12/10/00 3:04 PM, Eirik Dentz at [EMAIL PROTECTED] wrote: > >> I just did a fresh install of Debian 2.2.18. I'm using a Intel 10/100 Pro >> PCI >> ethernet card on an i386 system. I'm hooked up to the Internet through a >> Linksys router that connects to a DSL modem. I actually installed Debian >> through this connection to the Internet without any problems. Debian set my >> /etc/network/interfaces file eth0 setting to dhcp. And I didn't have any >> problems reaching the internet with it configured this way. In order to >> serve >> web pages from my linux box though I have to set it to a fixed IP address. >> On >> my last install of Debian, I was able to switch the /etc/network/interfaces >> eth0 setting to static and assign an IP address to my linux box like so: >> >> iface eth0 inet static >> address 192.168.1.9 >> netmask 255.255.255.0 >> broadcast address: 192.168.1.255 >> network address 192.168.1.0 >> gateway 192.168.1.1 >> >> And I had no problems reaching the Internet. >> >> After applying these same settings to my fresh install, I can no longer reach >> internet. >> >> Let me clarify this a litte: >> >> I am able to pull up my router's browser based configuration interface, so I >> know that my http requests are getting as far as the router, but for some >> reason they aren't getting passed through the router to the DNS servers. I >> checked the DNS addresses in my /etc/resolv.conf file and they are correct. >> I >> also tried typing in an IP address rather that a domain name and I'm getting >> a >> "TCP error: Network is unreachable" I know that it is a problem with the >> network configuration on my Linux box, because I'm not having any problems on >> my other computer using the same network settings. Is there another >> configuration file that I've missed, or is there some security mechanism that >> could be causing this? Any help or advice would be appreciated. >> >> eirik >
