Linux-Networking Digest #15, Volume #10 Wed, 27 Jan 99 03:14:09 EST
Contents:
Re: PPP Setup for Uswest.net Dial in (Clayton Haapala)
Re: ypserv problem (Ken Roberts)
Re: How to compile with SOCK_PACKET support? (Russell Senior)
Re: PCMCIA Network and RedHat 5.1 help! (Michael Benedict)
win98 and diald problem ("Jim Rainville")
Re: realaudio heavy CPU loading (Daniel R Creveling)
Re: realaudio heavy CPU loading (Daniel R Creveling)
Re: Need help with stumper re: RedHat 5.2 / diald-0.16-1 / pppd
([EMAIL PROTECTED])
Re: realaudio heavy CPU loading (Daniel R Creveling)
two ip addresses / two gateways / one machine? (Adam K Kirchhoff)
Re: PPP problem (no kidding) (David Kirkpatrick)
----------------------------------------------------------------------------
Crossposted-To: mn.online-service
From: [EMAIL PROTECTED] (Clayton Haapala)
Subject: Re: PPP Setup for Uswest.net Dial in
Date: Tue, 26 Jan 1999 20:58:29 GMT
In article <78kk21$qtt$[EMAIL PROTECTED]>,
Werner <[EMAIL PROTECTED]> wrote:
>Clayton Haapala <[EMAIL PROTECTED]> wrote:
>> Here's the "blow-off" email I got from uswest when I asked about
>> connecting linux. I have followed up with them to ask specifically
>> about "Tell me what I am dialing -- I'll take care of the rest, but
>> haven't gotten that answer yet.
>
>
>Why on earth would you pick an ISP run by people thousands of miles away whos
>tech support people have expert training on reading flow charts?
>
>
>
>I'm sure there are many local ISPs whos tech support people actually use Linux
>and could help you off the top of their heads.
Free 56K modem, free installation, if I hang on for two months.
That's about it. I'm NOT depending on them for my email delivery or
anything vital. Oh, and I'd like to swing a little weight getting DSL
to my area (I'm currently 18000 feet out from the CO). The only other
reason I can think of is that I was drunk at the time I sent in the
card, because you are right -- there are many good local ISPs around
where Linux connectivity wouldn't even have been an issue.
I have gotten it working, though.
--
Clay Haapala "Woe to he who fears change more than disaster! For
[EMAIL PROTECTED] how can he then avoid disaster?" -- from "the Firebugs"
------------------------------
From: Ken Roberts <[EMAIL PROTECTED]>
Subject: Re: ypserv problem
Date: Tue, 26 Jan 1999 17:04:52 -0600
sorry, forgot to mention /var/yp/securenets
# localhost
host 127.0.0.1
# local net
255.255.255.0 192.160.1.1
> Which libc are you using ?
/libc-2.0.7.so
/lib/libc.so.4.7.6
/lib/libc.so.5.4.46
- Ken
------------------------------
Subject: Re: How to compile with SOCK_PACKET support?
From: Russell Senior <[EMAIL PROTECTED]>
Date: 26 Jan 1999 15:06:47 -0800
>>>>> "Jeffrey" == Jeffrey T Kowalczyk <[EMAIL PROTECTED]> writes:
Jeffrey> I'm trying my first kernel recompile (third day of using
Jeffrey> linux). This is with RH5.2, I ran xconfig and went through
Jeffrey> all the options, but I saw nothing on SOCK_PACKET
Jeffrey> support. I'm supposed to add SOCK_PACKET to use
Jeffrey> dhcpcd-1.3.17, so I can use my cablemodem (hopefully).
Jeffrey> I took a look at the generated makefile (that is what xconfig
Jeffrey> does, right?), but saw nothing related to SOCK_PACKET. In
Jeffrey> fact, I've never been able to find anything to read about it.
Jeffrey> Help, I'm waiting for someone to lend a tip before starting
Jeffrey> this compile...
I agree that this is a little confusing. Try grep'ing the linux
sources for it. One of the config options does turn it on indirectly,
but I don't recall which one it is.
Ah, here it is: your .config should have the line:
CONFIG_PACKET=y
--
Russell Senior
[EMAIL PROTECTED]
------------------------------
From: Michael Benedict <[EMAIL PROTECTED]>
Subject: Re: PCMCIA Network and RedHat 5.1 help!
Date: Wed, 27 Jan 1999 00:36:59 -0500
I am no great Linux expert, but the only thing that I can think of is
that your routing table may not be set up right. Try running 'route' and
seeing if there is an entry for eth0 and if it is correctly
configured. If not, well. . .'man route' :). The other thing is, and
I don't know if you left this out, but ifconfig should also contain an
entry for 'lo' the loopback device which I believe to be very important
for any networking. My loopback ip is 127.0.0.0 and I am fairly certain
that this is a Linux-standard. If that isn't there, maybe try 'ifup lo'
(I am not positive that that will work right, or even not mess something
up, but it sounds right, but I must put a big caveat on it). Hope that
helps.
Michael Benedict
[EMAIL PROTECTED]
------------------------------
From: "Jim Rainville" <[EMAIL PROTECTED]>
Subject: win98 and diald problem
Date: Tue, 26 Jan 1999 21:12:40 -0800
I'm using diald-config 2.2 on a Redhat 5.1 system. It has been working great
until I upgraded my windows machines to win98. After the upgrade diald dials
my ISP about every 10 minutes. I've tracked it down to the udp netbios-ns
request so I have to tell diald to ignore it. The problem is I don't know
where to put this rule. I know in the plain diald package it would go in the
/etc/diald.conf file but in with diald-config the configuration files seem
to be scattered all over the system. I tried putting it in
/usr/local/lib/diald/standard.filter.m4 but that didn't help. Can you point
me in the direction of where I might get more information on this?
Thanks,
Jim
------------------------------
From: [EMAIL PROTECTED] (Daniel R Creveling)
Crossposted-To: comp.os.linux.misc,comp.os.linux.setup,comp.os.linux.hardware
Subject: Re: realaudio heavy CPU loading
Date: 27 Jan 1999 07:11:48 GMT
I don't think it's your hardware. I had the same problem
with RealAudio on my K6-233 and on some Dell's at school.
When the machines are running Windows everything is fine,
but when you play the same .rm file in Linux the machine just
about crashes. I think the Linux version of RealAudio is
just not up to speed with the other (Mac & Windows) versions.
Of course, if anyone knows how to fix this problem then
please help me too!
Dan
Kelvin Leung ([EMAIL PROTECTED]) wrote:
: Hello,
: I got my RH 5.2 running with Ensoniq PCI sound card. I have the alsa
: sound driver works fine. Both X11amp and Realaudio can produce sound
: out. But the RealAudio heavily load my CPU (K6-166 overclocked to 200).
: The audio is interrupted everytime I change to another window , or
: browsing within Netscape. I got the CPU load monitor fire up and it
: seems the CPU is fully occupied! I don't think it's the CPU problem 'cos
: I don't have problem with X11amp, also the Realaudio (not G2) in Windows
: in the same machine. Is that a fact or just my system doing weird!?
: Kelvin
------------------------------
From: [EMAIL PROTECTED] (Daniel R Creveling)
Crossposted-To: comp.os.linux.misc,comp.os.linux.setup,comp.os.linux.hardware
Subject: Re: realaudio heavy CPU loading
Date: 27 Jan 1999 07:19:09 GMT
I don't think it's your hardware. I have the same problem
on my K6-233 and on some dell's at school. When the
machines are running Windows everything is fine, but when
I play the same .rm file on Linux and the machine just about
crashes. I have only used RealPlayer on RedHat though, so
maybe it's a problem specific to RH. I'll have to try it on
a different distribution. I really think that the Linux
version of RealPlayer is just not up to speed with the rest
of the versions (Win and Mac).
Just my $0.02,
Dan
Kelvin Leung ([EMAIL PROTECTED]) wrote:
: Hello,
: I got my RH 5.2 running with Ensoniq PCI sound card. I have the alsa
: sound driver works fine. Both X11amp and Realaudio can produce sound
: out. But the RealAudio heavily load my CPU (K6-166 overclocked to 200).
: The audio is interrupted everytime I change to another window , or
: browsing within Netscape. I got the CPU load monitor fire up and it
: seems the CPU is fully occupied! I don't think it's the CPU problem 'cos
: I don't have problem with X11amp, also the Realaudio (not G2) in Windows
: in the same machine. Is that a fact or just my system doing weird!?
: Kelvin
------------------------------
From: [EMAIL PROTECTED]
Subject: Re: Need help with stumper re: RedHat 5.2 / diald-0.16-1 / pppd
Date: Tue, 26 Jan 1999 23:10:59 GMT
In article <[EMAIL PROTECTED]>,
Scott Harvey <[EMAIL PROTECTED]> wrote:
> This is a multi-part message in MIME format.
> --------------9E2D026243784761890898BF
> Content-Type: text/plain; charset=us-ascii
> Content-Transfer-Encoding: 7bit
>
> Joseph Morrison wrote:
>
> > Hello folks,
> >
> > I've been using diald-0.16-1 (with a couple of patches) with RedHat 5.1
> > for months with no problems whatsoever. Recently I installed RedHat 5.2
> > on a friend's machine, and cannot get diald to work properly. I
> > installed the same version of diald (0.16-1 with patches), but when I
> > couldn't get that to work, I tried a newer version (I think it was
> > 0.16-5). In both cases, the same problem occurred. The symptoms are
> > *very* weird:
> >
> > 1. During boot, diald starts with no apparent problems. After boot,
> > diald correctly waits for network requests, and when one is made, diald
> > calls the chat script, which calls the ISP and connects successfully.
> > Then diald reports that it is starting pppd, which hangs. A minute later
> > pppd gives up and diald hangs up. A minute later, diald tries again, and
> > the whole sequence repeats. pppd never starts up properly.
> >
> > 2. If I kill diald (or reboot without starting diald), I can use the
> > RedHat control panel to start ppp manually ("activate ppp device"),
> > which works fine and establishes a connection normally (although for
> > some reason there is a long delay before it actually dials the phone).
> >
> > So far, one would think that my pppd options are wrong in my diald.conf
> > file or something. However....
> >
> > 3. After I start ppp manually and then disconnect manually, here's the
> > weird part: I can restart diald, and it works perfectly.
> >
> > 4. If I reboot the machine, I'm back to square one - diald doesn't work
> > again, until I manually connect and disconnect once.
> >
> > So it appears that starting ppp manually and then disconnecting does
> > something which makes diald work, but I can't figure out what it is.
> >
> > I'm a pretty seasoned Linux user and I'm at a loss on this one. My
> > guesses have been that the problem is related to stale lock files
> > somewhere, but I can't find evidence to support that theory. I've
> > downloaded source RPMs and read the code for pppd, diald, ifup-ppp, etc.
> > The only lock file that seems like a candidate for explaining this
> > problem is /var/lock/LCK..modem. However, that file seems to be there
> > when it's supposed to be, and it seems to not be there when it's not
> > supposed to be... so it doesn't seem like it can be the problem.
> >
> > I've tried reading up on "uucp style locks", but I'm still not sure what
> > they are. I've checked permissions of the serial devices, done "find"
> > commands to see what files are touched after manually connecting and
> > disconnecting the ppp device - and can still not come up with a good
> > theory to explain this diald problem.
> >
> > I'm wondering if my ppp options are wrong in the /etc/diald.conf file
> > (shown below) but that seems unlikely, since it does work fine once I do
> > the manual connect/disconnect.
> >
> > Any ideas would be very much appreciated! I've been singing the praises
> > of RedHat Linux to my friend, who is getting less and less impressed ;-)
> >
> > Thanks,
> > - Joe Morrison
> >
> > ------------ /etc/diald.conf -------------
> > mode ppp
> > connect "/usr/sbin/chat -v -f /etc/sysconfig/network-scripts/chat-ppp0"
> > device /dev/modem
> > speed 115200
> > modem
> > lock
> > crtscts
> > local 192.168.1.1
> > remote 0.0.0.0
> > dynamic
> > defaultroute
> > include /usr/lib/diald/standard.filter
> >
> > -------------------------------------------
>
> The set up looks right but ,I have just goten my set up to work on 5.2 and
> I documented what I did to the set up files in order for things to work. I
> have included a text file which contains all of the set up details I had to
> change in order for diald to work on my system. A diagnostic aid: use
> tail -f /var/log/messages to look at the system log as you try to bring up
> diald.
If you have syslogd running you can also look at /var/log/syslog
this has other, sometimes useful, information in it.
HTH
norm
>
> --------------9E2D026243784761890898BF
> Content-Type: text/plain; charset=us-ascii;
> name="RH5.2-notes.txt"
> Content-Transfer-Encoding: 7bit
> Content-Disposition: inline;
> filename="RH5.2-notes.txt"
>
> Notes of tweaks you need to perform to the diald-0.16.5a-1 scripts and
> set up files to run in RH5.0 RH5.1 or RH5.2 systems after installing the
> RPM file.
> 1.) copy diald.conf file to /etc/diald.conf from /usr/lib/diald directory.
> create the directory /etc/diald. Copy diald.ctl and standard.filter to
> /etc/diald/ directory.
> Important assumption: You have a working dial up set up working.
> If you do not have that working yet. It is strongly re that you
> get this working first before you attempt to get diald functioning.
> Change the diald.conf file to reference a working chat script file
> as shown from the excerpt from a working diald.conf file below.
>
> 2.) The --> is where you must provide the information based on your set up
> 3.) To test the diald set up you can type diald at a terminal window.
> 4.) To view the system log real time open an xterm window and type the command
> tail -f /var/log/messages. This will display the last view lines of the
> messages file.
> 5.) When you are happy with the set up and you want to run diald whenever you
> system boots you will need to copy diald.init to /etc/rc.d/init.d/diald
> Note: To little bash scripts that start diald come with the installation
> one is called diald-on contents:
> ***********************************************
> #! /bin/sh
>
> /etc/rc.d/init.d/diald.init start
> The other is called diald-off contents:
> **********************************************
> #!/bin/bash
> /etc/rc.d/init.d/diald.init stop
> Modify both scripts change the name of the diald.init to diald
> **********************************************
> for example
> diald-off /etc/rc.d/init.d/diald stop
>
> diald-on /etc/rc.d/init.d/diald start
> 5.a) The /etc/rc.d/init.d/diald initialization script should look like:
> *******************************************************
> #!/bin/sh
> #
> # diald The on demand TCP/IP networking program
> #
> #
> # chkconfig: 2345 57 5
> # description: Diald is the smart demand-dial PPP/SLIP networking daemon. \
> # It selectively activates the SLIP/PPP link to the Internet when \
> # traffic is detected that is considered important.
> #
>
> # Source function library.
> . /etc/rc.d/init.d/functions
>
> # Source networking configuration.
> . /etc/sysconfig/network
>
> # Check that networking is up.
> if [ ${NETWORKING} = "no" ]
> then
> exit 0
> fi
>
> [ -f /usr/sbin/diald ] || exit 0
> # Changed 1/24/99 Scott Harvey
> [ -f /etc/diald.conf ] || exit 0
>
> # See how we were called.
> case "$1" in
> start)
> # Start daemons.
> echo -n "Starting diald: "
> daemon /usr/sbin/diald
> echo
> touch /var/lock/subsys/diald
> ;;
> stop)
> # Stop daemons.
> echo -n "Shutting down diald: "
> killproc diald -TERM
> echo
> rm -f /var/lock/subsys/diald
> ;;
> restart)
> $0 stop
> $0 start
> ;;
> status)
> status diald
> ;;
> *)
> echo "Usage: diald {start|stop|restart|status}"
> exit 1
> esac
>
> exit 0
> ********************end of /etc/rc.d/init.d/diald script*******
> 5.b) To install diald into the system V initialization boot up scheme you need
> to run the ntsysv program. Diald will be one of the choices.
> make sure it has an "*" in the checked field. This means it will be
> started whenever your system is booted.
> ******cut from a working diald.conf set up file**********************
> include /etc/diald/standard.filter
> # or use the filter that brings the link up for use on a line shared with
> # a phone
> # as you lean more about diald you can modify phone.filter to suit your needs
> # include /etc/diald/phone.filter
> # stuff to set up the diald connection
> # the device information can be found in the file
> # /etc/sysconfig/network-scripts/ifcfg-ppp0 or
> # ifcfg-pppX where X is the designation of your ppp interface.
> -->device /dev/cua1 # determine from your set up
> speed 115200
> lock
> mode ppp
> # We may get another terminal server, thus use
> # 'dynamic' and do not tell PPP the IP number of the other end
> # For use with gated, comment out the 'dynamic' option, and
> # set remote to be the same as local
> dynamic
> local 10.0.0.1
> remote 10.0.0.2
> # Red hat sets up ppp to use PAP "Personal Authorization Protocol" This means
> # your password information to your ISP is in the /etc/ppp directory.
> --> pppd-options name your-username-at-your-ISP :
> # Delay sending packets for 5 seconds after PPP device opens -
> # this allows routes to be established back to the appropriate dialup server.
> up-delay 5
> defaultroute
> modem
> crtscts
> # note:If you have selected another ppp device use that name in place of
> # ppp0. For example if your interfaces name is ppp1 your would refer
> # to the script chat-ppp1. These script files can be found in the
> # /etc/sysconfig/network-scripts directory.
> --> connect "/usr/sbin/chat -v -f /etc/sysconfig/network-scripts/chat-ppp0"
> # this is all you have to do provided that you currently have a working ppp
> # set up
> radial-timeout 10
> fife /etc/diald/diald.ctl
> # restrict 9:00:00 17:45:00 1 * *
> # or-restrict 9:00:00 17:45:00 2 * *
> # or-restrict 9:00:00 17:45:00 3 * *
> # or-restrict 9:00:00 17:45:00 4 * *
> # or-restrict 9:00:00 17:45:00 5 * *
> # up
>
> --------------9E2D026243784761890898BF--
>
>
============= Posted via Deja News, The Discussion Network ============
http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own
------------------------------
From: [EMAIL PROTECTED] (Daniel R Creveling)
Crossposted-To: comp.os.linux.misc,comp.os.linux.setup,comp.os.linux.hardware
Subject: Re: realaudio heavy CPU loading
Date: 27 Jan 1999 07:21:05 GMT
Sorry about the multiple posts. It seemed to me at first
that my first one didn't go through. Sorry.
Dan
Daniel R Creveling ([EMAIL PROTECTED]) wrote:
: I don't think it's your hardware. I have the same problem
: on my K6-233 and on some dell's at school. When the
: machines are running Windows everything is fine, but when
: I play the same .rm file on Linux and the machine just about
: crashes. I have only used RealPlayer on RedHat though, so
: maybe it's a problem specific to RH. I'll have to try it on
: a different distribution. I really think that the Linux
: version of RealPlayer is just not up to speed with the rest
: of the versions (Win and Mac).
: Just my $0.02,
: Dan
------------------------------
From: Adam K Kirchhoff <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
Subject: two ip addresses / two gateways / one machine?
Date: Tue, 26 Jan 1999 18:12:20 -0500
Can someone please help me out. I have a linux box at work with one
network card. The computer resides on two networks, the internal
network for the business (at 10.200.3.18) and the Internet (at
209.107.24.146). I have no problem getting the computer to connect to
either network individually through their respective gateways (at
10.200.3.1 and 209.107.3.129), but I'd like to be able to configure eth0
to claim both IP addresses at the same time (I've been able to set up
IP-aliasing without any problems) and use both gateways at the same
time, chooing the appropriate one to connect to either network.
It's setting up route to use both gateways that I've been unable to
do, yet. Is there someway to do this? I've been throught the manpages,
the how-tos, and have even visited the LDP, but I haven't found what I'm
looking for.
This is what I've got so far:
ifconfig lo 127.0.0.1
ifconfig eth0 up
ifconfig eth0 209.107.24.146
ifconfig eth0:0 10.200.3.18
route add -net 127.0.0.0
route add -net 209.107.24.128 dev eth0
route add -host 209.107.24.146 dev eth0
route add default gw 209.107.24.129
No problems so far... My computer sees the Internet with no problems.
Now how do I go about setting it up so it can see the internal network?
I've tried:
route add -net 10.200.3.0 dev eth0:0 but I get the error "SIOCADDRT:
Invalid argument"
Anyway, I'm stumped. Any help would be apprecated.
Adam K
[EMAIL PROTECTED]
------------------------------
From: David Kirkpatrick <[EMAIL PROTECTED]>
Subject: Re: PPP problem (no kidding)
Date: Tue, 26 Jan 1999 20:16:48 +0000
Reply-To: [EMAIL PROTECTED]
Generic info for RH 5.2. Assumption: you installed PPP.
===================================================================
RH puts ppp scripts in /usr/doc/ppp-2.3.5
Copy ppp-on, ppp-on-dialer, options to /etc/ppp.
===================================================================
Modify ppp-on:
TELEPHONE, ACCOUNT, PASSWORD
==================================================================
For exec command. put in correct device probably
cua1, modem speed
===================================================================
Edit /etc/resolv.conf and put in ISP nameserver
nameserver xxx.xxx.xxx.xxx
nameserver xxx.xxx.xxx.xxx
You usually get two from your isp.
====================================================================
execute ppp-on & and monitor logs with
tail -f /var/log/messages.
+++++++++++++++++++++++++++++++++++++++
OR:
Control Pannel: Modem configuration. Select
correct device. (used in ppp-on script)
===================================================================
Network Configurator: Routing: Defaults blank
PPP0 will use this:
===================================================================
Network Configurator: Names: insert ISP
nameserver addresses.
===================================================================
System Configurator: PPP/SLIP/PLIP: Configurations, Add
Fill in Hardware, Communication. Assumes PAP not
required - If things do not work check with ISP.
==================================================================
Save quit. Verify /etc/resolv.conf has your ISP
addresses.
==================================================================
The linuxconf sets up most things but does not
setup the ppp-on script - that must be done by hand.
==================================================================
David wrote:
>
> Config: Suse 5.3 Compaq Presario 1220 3com pcmcia modem/ethernet card
> KDE with KPPP.
>
> Modem dials, connects, authenticates,pppd doesn't die.
>
> Here is the problem. I can't ping ppp0, loopback anything in the
> world. The only thing that it will ping is the router at the isp.
>
> Any ideas?
>
> davidmac
--
[EMAIL PROTECTED]
[EMAIL PROTECTED]
[EMAIL PROTECTED]
------------------------------
** FOR YOUR REFERENCE **
The service address, to which questions about the list itself and requests
to be added to or deleted from it should be directed, is:
Internet: [EMAIL PROTECTED]
You can send mail to the entire list (and comp.os.linux.networking) via:
Internet: [EMAIL PROTECTED]
Linux may be obtained via one of these FTP sites:
ftp.funet.fi pub/Linux
tsx-11.mit.edu pub/linux
sunsite.unc.edu pub/Linux
End of Linux-Networking Digest
******************************
