Linux-Networking Digest #955, Volume #9 Thu, 21 Jan 99 00:13:33 EST
Contents:
Re: Machine denys telnet and FTP ([EMAIL PROTECTED])
Re: DHCP Client not working with ADSL and Bellsouth.net (Russell Senior)
Remote Printing (Larry Rivera)
Re: This is Linux, not Windows, so why not superior flexibility AND idiot-friendly?
(Peter McDermott)
Olicom OC-2325 Driver (Thane Bellomo)
Re: Mgetty not working (Bill Unruh)
Re: eth0: The transmission stopped! (David Kirkpatrick)
Real Audio Proxy though Linux; How? (Crewden)
Re: Linux, Samba and Windows (Mark Roberts)
Re: Documentation for SAMBA? ("Scott Brause")
Re: Linux/Win98 Network Problem ("Ed Shea")
Re: Logging into Netware server. ([EMAIL PROTECTED])
Re: Why Does Linux Networking Suck So Badly ? (j)
Re: PCMCIA Network card (J. Scott Berg)
Mgetty not working ([EMAIL PROTECTED])
Re: Macintosh network (Matt Kressel)
Re: demand dialling not supported in kernel driver... (Clifford Kite)
----------------------------------------------------------------------------
From: [EMAIL PROTECTED]
Subject: Re: Machine denys telnet and FTP
Date: Thu, 21 Jan 1999 01:02:49 GMT
Is it just root that you are having problems logging in with?
If so this is the solution:
for FTP: Remove root from the /etc/ftpusers file
for Telnet: Add all of the ttyp{n} device names listed in /dev to
/etc/securetty, where n=0,1,2,...
In article <[EMAIL PROTECTED]>,
[EMAIL PROTECTED] (Scallica) wrote:
> >> I am using Redhat 5.2 with a 3c509 card. The system is online. However,
> >> when I try to telnet or ftp to it, it finds the host, but keeps denying my
> >> connection
> >> and closes the telnet window. What could be wrong? Thanx.
> >>
> >Chech your /etc/hosts.allow and /etc/hosts.deny files.
> >--
> >Luca Filipozzi <[EMAIL PROTECTED]>
> >
>
> I did...hosts.deny is empty, and hosts.allow sez
> ALL: ALL....any other suggestions?
>
============= Posted via Deja News, The Discussion Network ============
http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own
------------------------------
Crossposted-To: uswest.dsl
Subject: Re: DHCP Client not working with ADSL and Bellsouth.net
From: Russell Senior <[EMAIL PROTECTED]>
Date: 20 Jan 1999 17:51:24 -0800
>>>>> "Tom" == Tom Reinertson <[EMAIL PROTECTED]> writes:
Tom> If you are getting a reasonable Ethernet hardware address, then
Tom> try this. We use DSL from US West and some folks had a problem
Tom> with the dhcp client timing out before US West returned an IP
Tom> address. If you think this is a possibility, then boot under
Tom> Windoze, time how long your system `hangs' before it gets an IP
Tom> address, and then check that time when you boot up under Linux.
Tom> If the `no dchp offer' error messages appears in less time, then
Tom> your script may be timing out before you get an IP address back
Tom> from Bellsouth.
I am trying to get ADSL setup with US West and have been having
trouble getting things to work. I have tried the ISC dhclient
software and also the dhcpcd-1.3.17-pl2. I've tried with the linux
kernel version 2.1.115 and 2.2.0-pre8. In the case of dhcpcd, I am
seeing the following errors in the dhcpcd.log file.
Jan 19 10:10:03 dalles dhcpcd[1181]: broadcasting DHCP_DISCOVER
Jan 19 10:10:04 dalles dhcpcd[1181]: corrupted UDP msg with uh_ulen=321 in_cksum=-2
discarded
Jan 19 10:10:41 dalles last message repeated 5 times
Jan 19 10:11:03 dalles dhcpcd[1181]: timed out waiting for a valid DHCP server
response
The tcpdump output seems to indicate that the dhcp server is
responding, but dhcpcd doesn't seem to like what it is hearing for
some reason.
Any ideas?
Please CC: me on followups. Thanks.
--
Russell Senior
[EMAIL PROTECTED]
------------------------------
From: Larry Rivera <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
Subject: Remote Printing
Date: Wed, 20 Jan 1999 11:02:26 -0400
Hello:
I've set up linux box for remote printing accross platforms:
1. Samba users (via Win95) can print to laser printer connected to linux
box with no problem.
2. Netware users can print remotely as well as ipx has been enabled on
the linux NIC and ncpfs software has been loaded.
3. Linux users get the following messages when trying to access the same
remote printer:
mer: /usr/sbin/lpd: remote: Your host does not have line printer access
My local printcap which has attached laser printer is as follows:
#
# Laser Printer directly connected to mer.UUCP.com
laser:lp=/dev/lp1:sd=/var/spool/lpd/laser:of=/var/spool/filters/ljet4-fi
lter:lf=/usr/adm/lpd-errs:mx#0:sh:rw:
My remote machine's printcap is as follows:
# Remote at mer.UUCP.com
remote:lp=/dev/null:rm=mer:rp=laser:sd=/var/spool/lpd/remote:
My /etc/hosts.lpd includes remote machines ip # and host name.
When I try do read the queue with lpq -Premote, I get:
merdist: waiting for queue to be enabled on mer
Rank Owner Job Files Total Size
1st root 0 hosts 654 bytes
2nd root 1 hosts 654 bytes
mer: lpd: laser: Your host does not have line printer access
Jobs are waiting at the remote machine's queue, to gain access to the
local queue for processing. I've tried lpc enable/start to restart lpd
but to no avail. Has anyone out there seen this situation??
------------------------------
From: Peter McDermott <[EMAIL PROTECTED]>
Crossposted-To:
comp.os.linux.misc,comp.os.linux.portable,comp.os.linux.powerpc,comp.os.linux.setup
Subject: Re: This is Linux, not Windows, so why not superior flexibility AND
idiot-friendly?
Date: 19 Jan 1999 12:31:28 -0000
Gregory Loren Hansen <[EMAIL PROTECTED]> wrote:
> In article <77ofit$h87$[EMAIL PROTECTED]>, rob <[EMAIL PROTECTED]> wrote:
>>
>>So true - what you use is what you like. A foreign graduate student here
>>was all frustrated with windows because he was used to UNIX and coudn't
>>figure out how to grep in windows.
> Can you?
Sure. Just run BBEdit. :-)
--
[EMAIL PROTECTED]
------------------------------
From: Thane Bellomo <[EMAIL PROTECTED]>
Subject: Olicom OC-2325 Driver
Date: Thu, 21 Jan 1999 01:57:50 GMT
I am looking for a driver for an Olicom PCI 10/100 Ethernet Card
OC-2325. Any help would leave me in your debt.
Thane.
------------------------------
From: [EMAIL PROTECTED] (Bill Unruh)
Crossposted-To: comp.os.linux.misc
Subject: Re: Mgetty not working
Date: 21 Jan 1999 03:48:49 GMT
In <7865bi$gv1$[EMAIL PROTECTED]> [EMAIL PROTECTED] writes:
>My mgetty simply stopped working one day. I am not sure what caused this. This
>is what I did:
Stopped working how? Do
ps aux|grep mgetty
Is there a listing for the mgetty program?
Look in /var/log/mgetty.ttyS1
Any clue there?
Look in /var/log/messages-- any statement that S1 is respawning too
fast?
>- I checked my modem. Seems to be communicating fine. - Tried typing
>"/sbin/mgetty ttyS1" at the command prompt. I then called. Works fine there
>too. - I checked my inittab to see if everything was ok. This is what is
>listed: "S1:345:respawn:/sbin/mgetty ttyS1" [no quotes] Looks fine to me.
Check in in the mgetty setup files to see if the init string is right.
------------------------------
From: David Kirkpatrick <[EMAIL PROTECTED]>
Subject: Re: eth0: The transmission stopped!
Date: Wed, 20 Jan 1999 22:45:41 +0000
Reply-To: [EMAIL PROTECTED]
Bill,
It looks like the error message was -> transmitter <- not
transmission. Could you verify that?
The status register CSR5 is compared to TxDied (2) and found
true
causing the code to go into the warning code you see. It goes
into
this code if the debug switch TULIP_DEBUG was used on
compilation.
I don't know what the default is passed in.
I think the rest of the CSR5 word is meaningless. You can
verify this by looking at the meaning of the bits in the tulip.c
driver in /usr/src/linux/drivers/net/tulip.c. The only one I
found
meaningful was the 2 which is TxDied. So the transmitter died.
??
Why? Are there any log messages or other info?
There is some other checks that do not get executed in
this code path i.e. "major error", "out of sync pointer" and an
"abnormal error summary bit"? Open up console logging if its not
on with /etc/syslog.conf to a file in /var/log and monitor it
with
tail -r /var/log/the_file_you_specify. See what error messages
come out. Also review the other log files in /var/log.
So it may be that CSR5 is set out of lower load code on
the board and is reporting a non-critical problem - "transmittor
died". A board manual would be helpful. Cables ok - cables
clear from any radio frequency source etc - guesses?
David Kirkpatrick
[EMAIL PROTECTED]
>
> The whole message is"eth0: The transmission stopped! CSR5 is 20a812,
> CSR6 816e0002". This occurs as my machine boots up.
> I'm using a NetGear ethernet card and the tulip.c driver version .90.
> My kernel is a Red Hat based 2.0.33.
> I've seen quit a few posts regarding this card/driver, but none
> seem to address the "transmission stopped" problem. I can also see
> that quite a few people seem to be able to run just fine using the
> same kernel/card/driver combination. Can soemone give me a hint about
> what this message means?
> Just in case it's meaningful as a clue, once the machine is up,
> the ethernet connection works a little, but very erratically, based
> on the results of ping.
>
> Thanks for the help,
> Bill Cripe
--
[EMAIL PROTECTED]
[EMAIL PROTECTED]
[EMAIL PROTECTED]
------------------------------
From: [EMAIL PROTECTED] (Crewden)
Subject: Real Audio Proxy though Linux; How?
Date: Wed, 20 Jan 1999 15:23:34 GMT
HTTP transport works just fine. Those realaudio sites whose .ram file
contains a reference to a pnm:// URL don't.
Is there a real audio PNA proxy for linux similar to what the wingate
Real Audio proxy service provides?
Or can masquerading accomplish this?
Provided there is enough information availabl,e I am prepared to write
my own.
------------------------------
From: Mark Roberts <[EMAIL PROTECTED]>
Subject: Re: Linux, Samba and Windows
Date: Wed, 20 Jan 1999 15:01:35 +0000
Yep - your Windows'98 machine sends encrypted passwords.
There is a security hole in SAMBA and Win'95 where passwords were sent
in clear form across the network so anyone could intercept them.
There are several solutions:
a) setup Win'98 to send passwords in clear form
[you can do this using regedit, this means you accept the resulting
security hole]
b) get SAMBA to use encrypted passwords and either
get the patch to update your Win'95 box to encrypt passwords
or
upgrade your Win'95 box to Win'98
There is a web site for SAMBA detailing the problems - can't remember
the link though.
B Rasmusson wrote:
>
> Hello!
>
> I recently installed Linux (RedHat 5.2) and Samba on one machine in my small
> network (3 computers, no dedicated server, Ethernet-hub). Both my
> Windows-machines finds my Linux-computer when I run Samba. On one of them I
> run Windows 95 and on the other I run Windows 98. But it is only on my
> Windows 95-machine I actually can log in with a password. In Windows 98 I
> can't get it to accept the password (the same password as in 95). On both
> computers I log in with the same username. What is the problem? Any
> suggestions?
>
> Bengt
> [EMAIL PROTECTED]
------------------------------
From: "Scott Brause" <[EMAIL PROTECTED]>
Subject: Re: Documentation for SAMBA?
Date: Wed, 20 Jan 1999 09:49:37 -0500
Bill,
Have you tried installing the just released SAMBA 2.0. I had some
itegration problems with earlier versions of samba, however, SAMBA 2.0 works
great. In addition, it has the new web based administration tool which may
take some of your headaches away.
Scott
------------------------------
From: "Ed Shea" <[EMAIL PROTECTED]>
Subject: Re: Linux/Win98 Network Problem
Date: Wed, 20 Jan 1999 15:24:44 GMT
Probably encrypted passwords. There's a registry hack for the Win98 machine
to have it send plain text password - better yet, set the Samba config to
use encrypted passwords.
autodata wrote in message <783b3a$[EMAIL PROTECTED]>...
>I'm pulling my hair out over a little networking problem.
>
>I have a Linux box (running RH 5.2 / Samba) running as a server, with a
>Win95
>machine and a Win98 machine on the LAN. The Windows 95 machine logs into
>the
>Linux server fine, but the Win98 box can't log in! At first, I thought
>it
>was the user account, but I've tried every user account on both machines
>and
>all get in on the Win95 box ... none on the Win98.
>
>When you browse the network on either Windows machine, Linux shows up.
>
>TCP/IP is set up the same on both machines (only difference is the
>computer
>name, host, and IP address).
>
>I doubt the problem is in my smb.conf, but here it is just in case ...
>
>
>[global]
> workgroup = HOME
> server string = Linux Samba Server
> printcap name = /etc/printcap
> load printers = yes
> guest account = guest
> null passwords = yes
> log file = /var/log/samba/log.%m
> max log size = 50
> socket options = TCP_NODELAY
>
>[homes]
> comment = Home Directories
> browseable = yes
> writable = yes
>
>[printers]
> comment = All Printers
> path = /var/spool/samba
> browseable = yes
> guest ok = yes
> writable = no
> public = yes
> printable = yes
>
>[public]
> path = /opt/public
> public = yes
> only guest = no
> writable = yes
> printable = no
>
------------------------------
From: [EMAIL PROTECTED]
Subject: Re: Logging into Netware server.
Date: Wed, 20 Jan 1999 14:51:38 GMT
[posted and mailed]
The ncpfs filesystem will allow you to mount Netware drives.
insmod ipx
ipx_configure --auto_primary=on --auto_interface=on
insmod ncpfs
and
ncpmount -S yourserver -U yourusername -P yourpassword /mountpoint
[if you are lucky and the stars are aligned]
will do the trick.
In article <[EMAIL PROTECTED]>,
[EMAIL PROTECTED] (Allen Beddingfield) wrote:
> Could someone please explain the procedures for connecting a Linux
> machine to a Netware server?
> Linux version: Redhat 5.1
> Server: Netware 3.12
============= Posted via Deja News, The Discussion Network ============
http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own
------------------------------
From: [EMAIL PROTECTED] (j)
Subject: Re: Why Does Linux Networking Suck So Badly ?
Date: Wed, 20 Jan 1999 14:34:02 GMT
On Wed, 20 Jan 1999 16:06:50 +1100, [EMAIL PROTECTED] (Iain
Chalmers) wrote:
>At least thats my perspective - comments welcomed, platform wars
>>/dev/null, or dragged to the trash can, or something :-)
Thanks for a NON-inflammatory response to my critique.
I didn't post to trash Linux, I posted to try and FOCUS
people on what Linux seems to be lacking. Perhaps if
they get peeved, some of these brilliant programmers
will be inspired to DO something to make Linux a better
option for the larger networking universe. Gigantic GUIs
are not needed - I always perfered "text windows" instead -
but strides DO need to be made in terms of autoconfiguration,
hardware detection, conflict detection & resolution and
bringing all the parts of Linux networking together into
one comprehensive utility.
What's the point in having a powerful computer if you have
to do all the hard stuff by yourself ? The learning curve
is steep enough for Linux - and most new users are coming
from the Winders world, having never specified a command-
line parameter in their lives. At least I got into PCs
back when a VIC-20 was a "hot" computer :-)
On Linux networking, perhaps those most interested developers
need to gather around a nice chat room, compare notes about
what good things they've seen in other OSs and come to some
agreement about a standard approach and user interface.
Linux will never be for everyone nor serve every purpose,
but it CAN fit a variety of niche applications if tamed
just a bit. Those apps will generate money and attention,
and those will help and encourage further development.
Those who learned Unix in college are now using Linux for
file/web servers and gateways - and that attention alone
changed "How do you pronounce that ?" into a number of
good commercial releases and a stack of good press.
-anon
------------------------------
From: [EMAIL PROTECTED] (J. Scott Berg)
Crossposted-To: comp.os.linux.hardware
Subject: Re: PCMCIA Network card
Date: 21 Jan 1999 03:11:44 GMT
In article <[EMAIL PROTECTED]>,
David Moulton <[EMAIL PROTECTED]> wrote:
>I have everything up and running on my Dell lattitude CPi except
>networking. It came with a 3Com LAN CardBus PC Card. This apparently has
>a 3c575 in it. I have gotten the card manager to recognize this, but
>then the kernel bags later in the boot. Here is the sequence in the
>messages file:
>
>Jan 19 21:34:33 localhost kernel: Linux PCMCIA Card Services 3.0.5
Get version 3.0.7 of pcmcia-cs; see http://hyper.stanford.edu/~dhinds/pcmcia/
It works (3.0.5 did not); I have one.
-Scott Berg
------------------------------
From: [EMAIL PROTECTED]
Crossposted-To: comp.os.linux.misc
Subject: Mgetty not working
Date: Thu, 21 Jan 1999 03:02:15 GMT
My mgetty simply stopped working one day. I am not sure what caused this. This
is what I did:
- I checked my modem. Seems to be communicating fine. - Tried typing
"/sbin/mgetty ttyS1" at the command prompt. I then called. Works fine there
too. - I checked my inittab to see if everything was ok. This is what is
listed: "S1:345:respawn:/sbin/mgetty ttyS1" [no quotes] Looks fine to me.
And yes,I am running at runlevel 3. Anyone have any ideas about what is going
wrong?
============= Posted via Deja News, The Discussion Network ============
http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own
------------------------------
From: Matt Kressel <[EMAIL PROTECTED]>
Subject: Re: Macintosh network
Date: Wed, 20 Jan 1999 15:34:10 GMT
Robert wrote:
>
> I need some help with the administration of a mac network. General
> information required at first.
> Robert
Without specific information, most people will not be able to help you.
What particular toruble are you having?
How does Linux relate, etc?
-Matt
--
Matthew O. Kressel | INTERNET: [EMAIL PROTECTED]
+--------- Northrop Grumman Corporation, Bethpage, NY ---------+
+--------- TEL: (516) 346-9101 FAX: (516) 346-9740 ------------+
------------------------------
From: [EMAIL PROTECTED] (Clifford Kite)
Subject: Re: demand dialling not supported in kernel driver...
Date: 14 Jan 1999 13:48:28 -0600
Mark Giesbrecht ([EMAIL PROTECTED]) wrote:
: Hey all,
: I'm trying to get demand dialling going on my RH5.1. (2.0.34 installed
: kernel) I followed the howto from http://www.nic.com/~cannon/Linux and
: am having one problem. Within my options file as:
: demand
: idle 60
: ipcp-accept-remote
: ipcp-accept-local
: lock
: noauth
: defaultroute
: user giesbrej
: remotename cadvision.com
: modem 115200 crtscts
: connect '/usr/sbin/chat -v -f /etc/ppp/call-isp'
: Once I try /usr/sbin/pppd :10.0.0.2, I get an error stating:
: /usr/sbin/pppd : demand dialling not supported in kernel driver 2.2.0.
The kernel ppp 2.2.0 driver is the driver that comes with the kernel and
doesn't support demand dialing. The ppp.c that comes with ppp-2.3.5
supports demand dialing and is supposed to be copied to the kernel
source tree during the ppp-2.3.5 "make install" phase. This sometimes
doesn't happen even with a pristine ppp package because of a install
configuration problem. I don't do RedHat but it looks like their
repackaged ppp has a similar problem.
The solution to this is manually copy the file ppp-2.3.5/linux/ppp.c to
/usr/src/linux/drivers/net . There then may be kernel compile problems
due to another configuration error in that is in ppp.c code. This has
caused many a lot of pain and agony so here's the fix:
With a pristine ppp-2.3.5 source tree, starting at line 3079 in
ppp-2.3.5/linux/ppp.c you have:
#if LINUX_VERSION_CODE < VERSION(2,1,86)
#define FREE_SKB(skb) dev_kfree_skb(skb)
#else
#define FREE_SKB(skb) dev_kfree_skb(skb, FREE_WRITE)
#endif
Change the "<" to ">=" . Then copy the modified file to the kernel
source directory /usr/src/linux/drivers/net, replacing the old ppp.c
there, and recompile the kernel.
If the particular Linux distribution you use has chosen to modify the
ppp.c code, you still should be able to use this as a guide to find
and change this code near line 3079.
Unfortunately there may be still other errors that are contributed
by RedHat.
: I'm confused, as I'm using ppp-2.3.5 (upgraded rpm from 2.3.3-4).
--
Clifford Kite <[EMAIL PROTECTED]> Not a guru. (tm)
/* Editing with vi is a lot better than using a huge swiss army knife. */
------------------------------
** 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
******************************
