static IP configuration problem

Greg Rundlett greg.rundlett at gmail.com
Tue Oct 18 19:57:01 EDT 2005


On 9/23/05, Frank DiPrete <fdiprete at comcast.net> wrote:
>
>
> It looks like the network the machine is on is 192.168.1.0/24<http://192.168.1.0/24>with a
> default route 192.168.1.15 <http://192.168.1.15>. www will depend on DNS
> working properly and
> I suspect that your primary dns server would be 192.168.1.15<http://192.168.1.15>depending
> on what you are using for a router and your setup.
>
> Check the /etc/resolv.conf file


Here is the resolv.conf file, and the values are all correct...however they
would only be obtained via the router at 192.168.1.15 <http://192.168.1.15>,
when obtaining a DHCP lease.

# cat /etc/resolv.conf
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by
resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver 24.34.241.8 <http://24.34.241.8>
nameserver 24.34.240.8 <http://24.34.240.8>
nameserver 68.87.64.196 <http://68.87.64.196>
search hsd1.ma.comcast.net <http://hsd1.ma.comcast.net>.

fwiw, the inability to assign the static IP seems to have gone away after
upgrading my kernel to 2.6 from 2.4. There is still some strangeness b/c
network-admin says it doesn't recognize my network configuration format and
presents a list of various distros (I'm running Debian Sarge, and it's on
the list of choices). I can edit and save the configuration, and it will
later still insist that it doesn't recognize the configuration; but the
configuration works.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.gnhlug.org/mailman/private/gnhlug-discuss/attachments/20051018/5ae97b74/attachment.html


More information about the gnhlug-discuss mailing list