[lug] network settings

Calvin Dodge caldodge at fpcc.net
Wed Sep 20 18:57:45 MDT 2000


KRITZBERG DAVID OWEN wrote:
> 
 
> I can ping colorado.edu but it really just pings 128.138.146.175--the
> IP I have taken for the linux box. I have used this IP successfully
> before on a Win98 machine.

And I can ping your computer from here in Lakewood, so routing isn't the issue.
 
> It doesn't make a difference (given my current settings) whether or
> not the  gateway 128.138.146.1 is allowed to route IP
> packets... I don't know if that provides extra information.

Ummm ... your computer has no control over whether that gateway can route
packets. If your looking at that setting on your computer, it's a reference to
YOUR computer's ability to forward packets. Again, routing isn't the issue
here.

Do you have nslookup installed? (it's part of bind-utils in Red Hat - I'm
guessing that Mandrake may use similar package names)

What happens if you try nslookup?  As in:

$ nslookup

set q=any
server 128.138.240.1
colorado.edu
exit

Hmmm ... when I did this, one of the response lines was 'text = "DNS problems
call UnixOps (303) 492-6096"'

> Is there a solution here, or what else should I try?

Well, I'd try a known good nameserver first - 24.1.11.7 is one such beast.

OTOH, 128.138.240.1 answered a request from me for an outside URL, so I _think_
it's working OK.

If you still can't resolve URLs, then the problem is with your computer
(perhaps an uninstalled package?).

If you CAN resolve URLs with a known good nameserver, then you can either 1)
call that phone number, 2) rely on another server, or 3) install bind and
caching-nameserver (those are Red Hat's names for the appropriate packages) on
your system, start named, and enter "nameserver 127.0.0.1" in /etc/resolv.conf.




PC Drew wrote:
> 
> You've gotta ask ITS to put your IP address in DNS for you.

Well, at least one part of their DNS knows about the computer in question - I
did a reverse DNS lookup to get the name gview146-175-dhcp.Colorado.EDU.

> Since you've posted your actual IP addresses to the list (and now
> they've been sent to a lot of people and accessible via the archive on
> the web) you may be more likely to be attacked.  I ran a portscan on

Well, PC, your mail header has "posted" _your_ IP address too.

Nmap shows some interesting ports on your system.  (no flame intended - just a
reminder that for most people, IP addresses CAN be extracted from the mail
headers)

Hmmm ... what service does "objcall" perform on your system?

> this box, I'd recommend installing SSH as an alternative to telnet and
> ftp.  I know this sounds like a pain, and you don't have to listen to
> me, but those are my recommendations.

Amen on SSH.

Calvin




More information about the LUG mailing list