Linux-Networking Digest #2, Volume #10 Tue, 26 Jan 99 03:13:38 EST
Contents:
Re: Why Does Linux Networking Suck So Badly ? (Edmund)
Re: PPP Setup for Uswest.net Dial in (Mike Horwath)
Re: diald won't connect ("[EMAIL PROTECTED]")
Newbie wants to install networking. Help! (Brian Barjenbruch)
Re: TULIP CHIPSET: 10/100 Nic Anywhere? (Bill McCall)
Re: Need help with stumper re: RedHat 5.2 / diald-0.16-1 / pppd (Scott Harvey)
----------------------------------------------------------------------------
From: Edmund <[EMAIL PROTECTED]>
Subject: Re: Why Does Linux Networking Suck So Badly ?
Date: Tue, 26 Jan 1999 07:24:58 GMT
j wrote:
> The sheer number of messages posted here - usually half going
> unanswered - tells the tale ... Linux networking sucks.
Actually, I kinda think it shows how many people are really becoming
interested in Linux and really taking advantage of it's power.
>
>
> Now you can take your Winders, add in file-sharing in just a
> couple of minutes, bring up your Winders workstations and
> locate and link in within just another few minutes. Easy.
> Quick. Relatively painless. Not the Linux way ...
Wrong, you obviously haven't really used Linux much. To get a Samba
share going on a RedHat distribution takes about 30 seconds. All you do
is modify a few parameters in smb.conf and you're up and running without
even having to reboot your system..
>
>
> Now you may try to defend Linux by saying that it has more
> "flexibility" - but quite frankly we could do with a lot
> less "flexibility" and a lot more simplicity. I'll bet
> that 95% of users just want to tie into a local NT server
> or use Linux AS a file/print server for Winders PCs.
> I think that "flexibility" is just an excuse - a euphamism
> for "a bunch of really unsophisticated little utilities
> written with no real plan in mind by people with a fetish
> for cryptic poorly-documented command-line parameters and
> well-hidden config files". As is, Linux is a user-UNfriendly
> mirror of MSDOS - and that goes double for "connectivity" issues.
See my statement above again.
>
>
> Want cheap PC networking & connectivity ? One "L" word comes
> to mind and it's NOT "Linux" - try "LanTastic" instead.
Linux is EXACTLY what comes to my mind.
>
>
> Now Linux IS relatively compact and fast and DOES get past
> some of the old buggaboos inherent to DOS-derived systems,
> but Linux just isn't "ripe" yet.
Depends on what your definition of "just isn't "ripe" yet" is.
If your definition of "just isn't "ripe" yet" means - Will run for
months on end without a glitch and without having to be rebooted due to
some app crashing it or eating memory, then your entirely wrong once
again.
If your definition of "just isn't "ripe" yet" means - Any bozo can turn
it on and think they can become an ISP or claim they are a Network
Administrator then you are right.
> It needs DUN boxes and
> "Network" panels which HELP you with things and show all
> the pertinent options and conflicts right there.
Like I said before, you obviously haven't looked around. RedHat's
networking configuration tools are pretty easy these days.
>
>
> Someone could make a LOT of money if they could put together
> a turn-key Linux-based file/print server package which could
> autoconfigure most things and be really easy and helpful on
> the rest. Something you take out of the box and 20 minutes
> later you have a good working server. You can do that with
> Winders, but not with Linux unless you apparently have put
> in a tremendous number of obsessive hours.
>
Damn... I can't stand when people talk without knowing what they are
talking about. Once again See RedHat!
>
> Now you thought I was just gonna flame ... nope. I've been
> relatively polite and realistic here. There are MANY issues
> to address, MANY refinements to be made before Linux becomes
> a really good option for administrators of small/medium networks.
Well, I wonder if you are one of those "administrators of small/medium
networks". From your message so far, it doesn't relaly seem like you
have the knowledge to be one. Also, if you are and you knew what you
were talking about and what you were really doing, you'ld probably be
getting paid a hell of a lot more by being an administrator of a large
network.
>
> As much as I dislike Winders, it's a positive relief to boot
> back into it after fooling around for hours in vain with Linux.
> Preferring Winders to ANYTHING ... IMHO that's a pretty severe
> indictment. Linux has been badly over-sold. If it weren't so
> cheap it would be a rip-off ... a hobby OS masquerading as
> the "real deal".
The one thing I'll grant you is that just like with any sophisticated OS
or program for that matter, there is a learning curve, and when you are
someone out of the Windows world, of course Linux is totally alien to
you. But once you get the hang of it, you will really appreciate all
that you can do with it.
C'ya,
Edmund
[EMAIL PROTECTED]
------------------------------
From: [EMAIL PROTECTED] (Mike Horwath)
Subject: Re: PPP Setup for Uswest.net Dial in
Crossposted-To: mn.online-service
Date: Tue, 26 Jan 1999 07:21:33 GMT
In mn.online-service Clayton Haapala <[EMAIL PROTECTED]> wrote:
: I've had some success! Here's an /etc/ppp/peers file that has worked for me,
: though not as reliably as I'd hoped:
: crtscts
: idle 600
: ipcp-accept-local
: ipcp-accept-remote
: ipcp-max-terminate 10
: lcp-max-failure 20
: lcp-max-terminate 10
: debug
: defaultroute
: asyncmap 0
: (I've left out the call to chat and baudrate lines....)
: No need for CHAP or PAP here.
If I were you I would just use PAP and be done with it.
CHAP won't work for you at all as it is an exchange of passwords, and
you don't know theirs :)
: Next bit of fun is the on-demand stuff, as I'm using pppd 2.3.5. :-)
: I also have to figure out the static routes I'll need to make my
: dedicated link work, but at least I control that part.
No rocket science - just plod along and it will all work.
Nice seeing a message from you Clay.
--
Mike Horwath Admin & Manager @ VISI.com WORK: [EMAIL PROTECTED]
IRC: Drechsau http://www.visi.com/ HOME: [EMAIL PROTECTED]
The only Minnesota ISP with public statistics: http://noc.visi.com/
Garbage In -- Gospel Out. - berkeley fortune(6)
------------------------------
From: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
Subject: Re: diald won't connect
Date: Mon, 25 Jan 1999 22:52:59 -0800
maybe, maybe not -- but the stable kernel been something like 2.0.36 for
quite awhile now, so why not upgrade?
[EMAIL PROTECTED] wrote:
>
I am using kernel 2.0.29 is this possibly the problem?
------------------------------
From: Brian Barjenbruch <[EMAIL PROTECTED]>
Crossposted-To:
athome.users-unix,comp.os.linux.help,comp.os.linux.questions,comp.os.linux.setup
Subject: Newbie wants to install networking. Help!
Date: Tue, 26 Jan 1999 06:10:44 GMT
Okay, here's the deal:
I have a Power Macintosh G3 with a *built-in* Ethernet port. How do I
get Linux to recognize this? What are the steps I need to go through
to install networking with this (I have a cable modem connected to the
Ethernet port)?
Again: It's not on a card, it is a built-in Enet port. Does this make
a difference, Linux-wise? (LinuxPPC)
--
"Its origin and purpose...still a total mystery."
- Dr. Heywood Floyd, "2001: A Space Odyssey"
------------------------------
From: [EMAIL PROTECTED] (Bill McCall)
Subject: Re: TULIP CHIPSET: 10/100 Nic Anywhere?
Date: Tue, 26 Jan 1999 07:31:18 GMT
Try the Samsung SC1200-TX, it uses the Digital 21110 chip.
On Mon, 25 Jan 1999 11:01:33 -0500, "Will Lyster" <[EMAIL PROTECTED]>
wrote:
>Looking for a 10/100 NIC that uses the Tulip chipset.
>
>Please respond to [EMAIL PROTECTED]
>
>Thanks
------------------------------
From: Scott Harvey <[EMAIL PROTECTED]>
Subject: Re: Need help with stumper re: RedHat 5.2 / diald-0.16-1 / pppd
Date: Tue, 26 Jan 1999 05:34:31 +0000
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.
==============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==
------------------------------
** 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
******************************
