"James (Jim) Hatridge" wrote:
> 
> HI Jerry et al;
> 
> On Sun, 11 Apr 1999, Jerry Lynn Kreps wrote:
> 
> > In only one line:
> > KDE has a program, Kppp, that is almost identical in operation to
> > Windows "dial" program.
> > If you need help for the settings let us know...
> 
> YES!! I need too help with Kppp. When I try to connect I get "Serial line
> is looped back." Do you have any ideas? Or at least point me toward what
> could be wrong.

First, if you did a straight install of SuSE then things would have been
setup correctly.  So, during or after the install you have used YaST to
change some configuration, or have recompiled the kernel.  Let's
reconfigure.

There are two network address that are reserved: 0.0.0.0 and 127.0.0.0
The first is called the 'default route' and the second is called the
'loopback address'.  Network 127.0.0.0 is reserved by IP traffic local
to your host, so address 127.0.0.1 will be assigned to a special
interface on your host, the so-called 'loopback interface', which acts
like a closed circuit.  Any IP packet handed to it from TCP or UDP will
be returned to them (.0 and .1) as if it had just arrived from some
network.  This allows you to develop and test networking software
without ever using a "real" network.  Another useful application is when
you want to use networking software on a standalone host.

You can display your serial device configurations with:
        /sbin/setserial -bg /dev/cua* 
        /sbin/setserial -bg /dev/ttyS*
the second being more current...   A 'wild' interrupt detection command
would be:
        /sbin/setserial -W /dev/ttyS*

Your hostname, unless you changed it, is 'localhost'.
The following command will give you the status of all of all flags for a
give serial device:
        stty -a < /dev/ttyS1

Read the man pages for setserial to see how to read serial device
configurations and to force configure them.

You have mistakenly attached your serial port device to the loopback
address during installation.  Also, since you are probably not using DNS
or NIS for address resolution, you have to put all hostnames and
addresses in the /etc/hosts file.

My hosts file looks like this:
127.0.0.1       localhost
127.0.0.2       JLKreps.AtHome  JLKreps

(Note: some distros reverse the entry order:  localhost   127.0.0.1,
etc)

To make all applications use /etc/hosts exclusively when looking up the
IP address of a host, you have to edit /etc/hosts.conf and insert the
line 'order hosts bind',and another which says 'multi on' and comment
out with the '#" character any other lines starting with 'order'.

Then you can force the loopback to 127.0.0.1 with
        ifconfig lo localhost  (or 127.0.0.1)
To see if things setup ok use:
        ifconfig lo
It should show a netmask of 255.0.0.0 .
Now you can start playing with it.  What is still missing is an entry in
the routing table that tellws IP that it may use this interface as a
route to destination 127.0.0.1.  This is accomplished by typing: 
        route add 127.0.0.1
You can use localhost instead of 127.0.0.1.

Use ping to check that everything is fine.
        ping localhost
It should begin sending back messages and giving travel times in
milliseconds (ms).
PING localhost (127.0.0.1): 56 data bytes
64 bytes from 127.0.0.1: icmp_deq=0  ttl=32  time=1 ms
etc....
Use control-C to break out of ping.
If you don't get this message something is messed up.  Check that the
ifconfig and route binaries you use are compatible with the kernel
release you run, and, above all, that the kernel has been compiled with
networking enabled. You can tell this from the presence of the /proc/net
directory.  If you get a message saying "network unreachable" you
probably have got the route command wrong.  Make sure you use the same
address as you gave to ifconfig.

NOTE note NOTE note NOTE note NOTE note NOTE note NOTE

Usually, all these settings are done each time you boot because they are
in rc.config.
rc.config is set by using Yast --> 'System administration' -->'Nework
configuration' and following instructions on page 115 of the  SuSE
manual.  The instructions to install PPP begin on page 126.  Using YaST
is a lot easier than doing the manual things I described earlier. ;-) 
Don't activate 'diald' or 'SLIP', since you are going to be using pppd. 
Just make sure pppd is in /usr/sbin or install it if it is not.  If
diald is installed return YaST and disable it.  Once you have configured
your hostname and loopback correctly, and have installed pppd and
deactivated diald, then run Kppp and configure your modem and ISP name
and quad address.
-- 

JLK
Linux, because it's STABLE, the source code is included, the price is
right.
--
To get out of this list, please send email to [EMAIL PROTECTED] with
this text in its body: unsubscribe suse-linux-e
Check out the SuSE-FAQ at http://www.suse.com/Support/Doku/FAQ/ and the
archive at http://www.suse.com/Mailinglists/suse-linux-e/index.html

Reply via email to