Re: Re.: Modem Problem.
From: Moe Trin (ibuprofin_at_painkiller.example.tld)
Date: 03/05/05
- Next message: Michael Heiming: "Re: Find Linux OS Brand and Version"
- Previous message: bi-weekly: "A new reader? Welcome to comp.os.linux.misc, read this first if you're new here (FAQ)"
- In reply to: nospam_at_st.com: "Re.: Modem Problem."
- Next in thread: nospam_at_st.com: "Re: Re.: Modem Problem."
- Reply: nospam_at_st.com: "Re: Re.: Modem Problem."
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Fri, 04 Mar 2005 18:54:01 -0600
In article <20050303200757.67e613e3.nospam@st.com>, nospam@st.com wrote:
>And the final one that I was looking for why ppp hangs.
Would be nice to know what you were referring to - your article does
not have a 'References:' header.
>Here is an entire section of a manual that I found on this one:
>http://tinyurl.com/5hfkq
Well, if I read this correctly, they're talking about putting your
hostname into /etc/hosts. Actually, there would be a LOT of other
symptoms of this, starting when the systems tries to boot. Depending on
your distribution, there is some section of the boot scripts that looks
for a file that tells what your hostname is (in Red Hat and clones, this
is /etc/sysconfig/network). The hang occurs when the system tries to
resolve this name to an address. The correct solution is to make sure
your system knows it's FULL name from this boot file - meaning that the
name has a host and domain section, separated by dots. An example would
be 'localhost.localdomain' or 'www.microsoft.com' (though using a real
name like that could lead to problems if you are not authorized by
the real domain to use it). Then, in /etc/hosts this FULL name should
refer to an IP address. The exception to this is 'localhost.localdomain'
as all resolvers know that localhost really refers to that name. Make sure
that there is only one line per IP address, and that a given hostname only
appears on one line. If you so not have a fixed name (DHCP, or no local
network for example), you can point your hostname at other addresses in
the 127.0.0.0/8 network. All computers know that any host on the
127.x.y.z network refers to itself.
If your system can not resolve the FULL hostname from the /etc/hosts file,
it will attempt to look elsewhere as defined in the /etc/nsswitch.conf and
/etc/host.conf files. If there is one or more nameserver declarations in the
/etc/resolv.conf file, the system will attempt to contact these hosts, and
that is often where the delay occurs. The nameserver has to be reachable NOW
in the boot sequence, not later. Also understand that the resolver will
believe the FIRST answer it gets - even if that answer is "I don't know".
Thus, if you depend on using a nameserver to resolve your name to an address,
EVERY NAMESERVER LISTED must return the "correct" answer.
>Incidentally it came from FreeBSD.
While not wishing to knock the FreeBSD manual, most of it is not applicable
to Linux. They have been using a different type of ppp application since
about 1997 when they stopped using the ANU version at ppp-2.3.6. Many of
the commands and options they use do not exist, or are named differently
from the ANU version used in Linux. In the same way, the version used in
Linux has a fairly large number of options that FreeBSD never heard of.
>This seems to be a very well known, long term existing problem as this
>section seems quite detailed and exists for atleast a few years.
Yes, the problem goes back to the introduction of DNS in the late 1980s.
Old guy
- Next message: Michael Heiming: "Re: Find Linux OS Brand and Version"
- Previous message: bi-weekly: "A new reader? Welcome to comp.os.linux.misc, read this first if you're new here (FAQ)"
- In reply to: nospam_at_st.com: "Re.: Modem Problem."
- Next in thread: nospam_at_st.com: "Re: Re.: Modem Problem."
- Reply: nospam_at_st.com: "Re: Re.: Modem Problem."
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
