Linux-Networking Digest #78, Volume #10 Mon, 1 Feb 99 15:13:42 EST
Contents:
Re: Configuring Linux on a permanent (not PPP) Connection to Internet (David
Kirkpatrick)
Re: IP aliases ("Glen Winn")
Re: Telnet & FTP time out (Linux <--> Win98) ("Quiney, Philip (EXCHANGE:HAL02:HM10)")
Re: ppp dial-on-demand or Diald ??? (Villy Kruse)
Help Needed!! PPP server setup (Bill Nash)
FS:new Cisco 2505 B/O Must Sell (GbyTheSea)
linux error ("Roberto")
Re: rpc errors and kernel 2.2.1 (Jorg B/)
Re: Red_Hat setup problems (Jeremy Randall)
Netatalk with Copstalk (douglasf)
Re: Red_Hat setup problems (Jim Roberts)
Re: Weird 3COM Card Problem - Help Please (David Hinds)
Re: ppp dial-on-demand or Diald ??? ("Nicola� Kisselhoff")
It might be stupid... but another NT and Linux prob (Martin Adler)
problem with cardmgr not recognizing card ([EMAIL PROTECTED])
Re: PPP no longer working (Clifford Kite)
----------------------------------------------------------------------------
From: David Kirkpatrick <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.questions
Subject: Re: Configuring Linux on a permanent (not PPP) Connection to Internet
Date: Mon, 01 Feb 1999 10:38:43 +0000
Reply-To: [EMAIL PROTECTED]
http://metalab.unc.edu/ select ftp archive
http://metalab.unc.edu/pub/Linux/docs/HOWTO/
Get NET-3-HOWTO and more.
dgap wrote:
>
> Hi, there...
>
> I need some info on how to configure Linux to stay connected to the Internet
> via a permanent connection (not PPP).
>
> My target is to provide a web server, mail exchange and news reading through
> the LAN of my organization... Where can I find info on this subject??
>
> Thanks in advance
>
> Paulo Ferreira
--
[EMAIL PROTECTED]
[EMAIL PROTECTED]
[EMAIL PROTECTED]
------------------------------
From: "Glen Winn" <[EMAIL PROTECTED]>
Subject: Re: IP aliases
Date: Mon, 1 Feb 1999 11:53:49 -0600
Make sure you added a route for the aliased IP address -
/sbin/route add -host 192.168.100.2 dev eth0:1
For more information look at the mini how-to:
ftp://metalab.unc.edu/pub/Linux/docs/HOWTO/mini/IP-Alias
Joerg Klaas wrote in message <[EMAIL PROTECTED]>...
>Is it usual that I am not able to ping a aliased IP Address from the
>machine where I configured IP-Aliasing ?
>
>e.g.
>
>eth0 192.168.100.1
>eth0:1 192.168.100.2
>
>While I'm logged in to "192.168.100.1" I can ping "192.168.100.1",
>but am unable to do so for "192.168.100.2".
>Pinging from another host to "192.168.100.2" works, so aliasing itself
>works fine.
>
>strange....
>
>
>Joerg
>
>
------------------------------
From: "Quiney, Philip (EXCHANGE:HAL02:HM10)" <[EMAIL PROTECTED]>
Subject: Re: Telnet & FTP time out (Linux <--> Win98)
Date: Mon, 01 Feb 1999 08:52:04 +0000
Steven Parker wrote:
>
> I have a Linux box with a 3Com 3c905B NIC and a Win98 box as the only
> two machines on my 10BaseT LAN (right now); they're connected with a
> little 8 port hub. I can ping back and forth fine... But, telneting to
> the Linux box takes a very long time (sometimes so long that it times
> out). Does anyone have any clues as to why this could be occurring?
Does your linux box have an entry in /etc/hosts for the Win98 box (check
by pinging the Win98 box with its name from the linux box)
> What should the gateway be set to? (I've tried setting it to the linux
> box...). Could it be the telnet daemon configured badly?
You don't need a gateway entry with your set up.
Try telneting to the linux box from itself. You will not be able to log
is as root unless you move the file /etc/securetty to a safe place (say
/root/etc). This will check that the telnet connection is being handled
by inetd correctly.
>
> Any help is greatly appreciated -steve
Watch the terminal emulation mode of the Windows Telnet client. Using
VT100 will allow such programs as 'vi' to work properly over the network
link. (check the environment variable TERM once logged in it should be
'vt100' - it sets itself from what your client is set to automatically
IIRC.
HTH
Regards
Phil Q
--
Phil Quiney Digital PowerLine,
[EMAIL PROTECTED] Nortel Networks,
Telephone: +44 (1279) 402363 London Rd, Harlow,
Fax: +44 (1279) 402885 Essex CM17 9NA,
United Kingdom.
"This message may contain information proprietary to Northern
Telecom so any unauthorised disclosure, copying or distribution
of its contents is strictly prohibited."
------------------------------
From: [EMAIL PROTECTED] (Villy Kruse)
Subject: Re: ppp dial-on-demand or Diald ???
Date: 1 Feb 1999 19:03:54 +0100
In article <794cf8$m36$[EMAIL PROTECTED]>,
Beno�t Cousson <[EMAIL PROTECTED]> wrote:
>Hi,
>
>
>So, is demand dialing not supported anymore with last kernel version, or is
>there a version problem with the ppp module???
>
Rather: demaind dialing is net quite yet supported by the kernel, but
it should be there "real soon now".
Diald is still working, though.
Try experiment with this parameter in /etc/diald.conf. Some times you need
to turn this option off.
buffer-packets or -buffer-packets
The explanation is that when you are waiting for the dial to complete the
tcp layer will generate several 'syn' requests which is buffered up in the
diald program. When the connection is established, all these 'syn' requests
get sent to the remote all at once, and some ppp/tcp servers simply cannot
cope with this, and the first connection attempt will then always fail.
Turning off buffer-packets, will discards all those 'syn' packets and
you may be alright.
Villy
------------------------------
Date: Mon, 01 Feb 1999 10:57:26 -0500
From: Bill Nash <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
Crossposted-To: linux.redhat.ppp
Subject: Help Needed!! PPP server setup
I am a 4 month old newbie currently running RedHat 5.2 with KDE desktop.
I have an external USR Sporster modem connected and is working fine
using kppp dialup into my ISP. I am trying to setup this system so I can
also dialup into it from a Win95 pc using PPP and PAP. I have read many
documents posted, and reviewed many web pages.
I am confused.
Why can't I dial into and out of the system once the changes below were
made? I think it has ing to do with the way the serial port is being
locked by mgetty, but I do not know how to fix it.
Why doesn't PPP dialup into the server work?
Below are the steps I followed.
1) verified mgetty was installed(did not know how to tell if it was
compiled with AutoPPP)
2)place the following line in /etc/inittab
s0:2345:respawn:/sbin/mgetty ttys0 -D /dev/ttys0
3)place the following lin in /etc/mgetty+sendfax/login.config
/AutoPPP/ - - /usr/sbin/pppd file /etc/ppp/options.server
4)place the following lines in /etc/ppp/options.server
-detach
asyncmap 0
modem
crtscts
lock
require-pap
refuse-chap
login
x.x.x.x:y.y.y.y
(Note x=server's ip address y=ip address to be assigned to serial port)
5)issued #kill -1 1 (to force initd to re-read inittab)
When I change the /etc/inittab file to include the following line:
s0:2345:respawn:/sbin/mgetty ttys0 -D /dev/ttys0
and issue the "kill -1 1" command, I can dial into the system using
Hyperterm on a Win95 system and can login(VT100 type connection) with no
problems. Once I disconnect, I try to dial my ISP (using kppp) and the
connection panel just hangs stating "Initializing Modem". I can see the
modem lights blinking like it is receiving commands, but it does not
dial out.
I edit /etc/inittab file and comment out the new line and my kppp dialup
into my ISP works fine.
# s0:2345:respawn:/sbin/mgetty ttys0 -D /dev/ttys0
Can anyone help me? I would greatly appreciate it.
Thanks,
Bill Nash
[EMAIL PROTECTED]
------------------------------
From: [EMAIL PROTECTED] (GbyTheSea)
Subject: FS:new Cisco 2505 B/O Must Sell
Date: 1 Feb 1999 18:09:14 GMT
Qty 1 Cisco 2505 8 ethernet ports
Version 11.0 software, documentation, and registration in shrinkwrap
No cables
condition:new in the box
Price:Best Offer
-Buy/Sell/Trade-Sun/SGI/Next/Mac/Cisco/Bay-
-For more GREAT DEALS follow the link below-
http://members.aol.com/GbyTheSea/index.html
------------------------------
From: "Roberto" <[EMAIL PROTECTED]>
Subject: linux error
Date: Mon, 1 Feb 1999 18:55:12 +0100
Dear people,
I have a little problem incontered trying install Red Hat Linux 5.2 on my HD
Western Digital AC26400 6GB.
After partition disk appear . . . Fdisk Error - an error occurred reading
the partition table for the block device /tmp/hdd. The error was::
inmput/output error.
Then if I skip this step after file systemm creation when the system trying
to install packages, appear . . . Error - mount failed: oparation not
supported by device.
Does anybody say me what can I do to complete installation of Linux on my
computer ?
Thaks everybody answer me !!!
Roberto
------------------------------
From: Jorg B/ <[EMAIL PROTECTED]>
Crossposted-To: alt.os.linux.slackware,alt.linux,alt.os.linux.slackware
Subject: Re: rpc errors and kernel 2.2.1
Date: Mon, 01 Feb 1999 18:27:12 GMT
Here is what I have found out in regards to my original problem (see below).
Using Kernel 2.2.x we need to start portmap BEFORE mounting nfs file systems
- the extra NFS facilities, like locking, want to talk to the portmapper.
So, looking at the /etc/rc.d/rc.inet2 file in Slackware 3.6 we need to do
some minor changes:
First move "rpc.portmap" from /usr/sbin/ to /sbin/.
Test is by using the "which" command:
which rpc.portmap
should come back with:
/sbin/rpc.portmap
Next you need to change your /etc/rc.d/rc.inet2 file to look like this:
#!/bin/sh
#
# rc.inet2 This shell script boots up the entire INET system.
# Note, that when this script is used to also fire
# up any important remote NFS disks (like the /usr
# distribution), care must be taken to actually
# have all the needed binaries online _now_ ...
#
# Author: Fred N. van Kempen, <[EMAIL PROTECTED]>
#
# Constants.
NET="/usr/sbin"
IN_SERV="lpd"
LPSPOOL="/var/spool/lpd"
# Start the SUN RPC Portmapper.
if [ -f /sbin/rpc.portmap ]; then
echo -n " portmap"
/sbin/rpc.portmap
fi
# At this point, we are ready to talk to The World...
echo "Mounting remote file systems..."
/sbin/mount -a -t nfs # This may be our /usr runtime!!!
echo -n "Starting daemons:"
... more stuff
[snip]
Make sure that you are chaging ALL lines that refer to rpc.portmap from:
if [ -f ${NET}/rpc.portmap ]; then
to
if [ -f /sbin/rpc.portmap ]; then
otherwise you next boot may not be what you expect...
Thats it...
Note: The above example worked fine for me unsing Slackware 3.6, other
versions or distributions maybe different.
Jorg B.
My original post:
Jorg B/ wrote:
> I'm using Slackware 3.6 with kernel 2.2.1 and I'm getting the following
> error messages during the boot-up:
>
> portmap: RPC call returned error 111
> RPC: task of released request still queued!
> RPC: (task is on xprt_pending)
> portmap: RPC call returned error 111
> RPC: task of released request still queued!
> RPC: (task is on xprt_pending)
> lockd_up: makesock failed, error=-111
> portmap: RPC call returned error 111
> RPC: task of released request still queued!
> RPC: (task is on xprt_pending)
>
> I have been running kernel 2.0.36 since it was released on the same
> machine without any problem... NFS worked without any problems. Even
> though I'm receiving the errors (see errors above) NFS seems to work
> fine... I can mount to other machines and other machines can mount the
> this machine. The 2.2.1 kernel IS configured to use nfs but not to use
> the automount feature.
>
> As far as I know and checked, Slackware 3.6 (out of the box) is ready to
> run kernel 2.2.1 for what we are doing here.
> Slackware 3.6 uses "nfsd 2.2beta37" ...
>
> Any Ideas what causes the rpc errors ?
>
> Thanks for your help...
>
> Jorg
>
> Ps: below is a printout from "dmesg"
>
> Linux version 2.2.1 (root@mail) (gcc version 2.7.2.3) #1 Fri Jan 29
> 08:00:56 PST 1999
> Detected 451028373 Hz processor.
> Console: colour VGA+ 80x25
> Calibrating delay loop... 448.92 BogoMIPS
> Memory: 257904k/262080k available (940k kernel code, 412k reserved,
> 2792k data, 32k init)
> CPU: Intel Pentium II (Deschutes) stepping 02
> Checking 386/387 coupling... OK, FPU using exception 16 error reporting.
>
> Checking 'hlt' instruction... OK.
> POSIX conformance testing by UNIFIX
> mtrr: v1.26 (19981001) Richard Gooch ([EMAIL PROTECTED])
> PCI: PCI BIOS revision 2.10 entry at 0xf0770
> PCI: Using configuration type 1
> PCI: Probing PCI hardware
> Linux NET4.0 for Linux 2.2
> Based upon Swansea University Computer Society NET3.039
> NET4: Unix domain sockets 1.0 for Linux NET4.0.
> NET4: Linux TCP/IP 1.0 for NET4.0
> IP Protocols: ICMP, UDP, TCP
> Starting kswapd v 1.5
> Serial driver version 4.27 with no serial options enabled
> ttyS00 at 0x03f8 (irq = 4) is a 16550A
> ttyS01 at 0x02f8 (irq = 3) is a 16550A
> pty: 256 Unix98 ptys configured
> Floppy drive(s): fd0 is 1.44M
> FDC 0 is a post-1991 82077
> (scsi0) <Adaptec AHA-294X Ultra SCSI host adapter> found at PCI 11/0
> (scsi0) Wide Channel, SCSI ID=7, 16/255 SCBs
> (scsi0) Warning - detected auto-termination
> (scsi0) Please verify driver detected settings are correct.
> (scsi0) If not, then please properly set the device termination
> (scsi0) in the Adaptec SCSI BIOS by hitting CTRL-A when prompted
> (scsi0) during machine bootup.
> (scsi0) Cables present (Int-50 NO, Int-68 YES, Ext-68 NO)
> (scsi0) Downloading sequencer code... 419 instructions downloaded
> scsi0 : Adaptec AHA274x/284x/294x (EISA/VLB/PCI-Fast SCSI) 5.1.10/3.2.4
> <Adaptec AHA-294X Ultra SCSI host adapter>
> scsi : 1 host.
> Vendor: SEAGATE Model: ST34501W Rev: 0018
> Type: Direct-Access ANSI SCSI revision: 02
> Detected scsi disk sda at scsi0, channel 0, id 0, lun 0
> Vendor: SEAGATE Model: ST34572W Rev: 0718
> Type: Direct-Access ANSI SCSI revision: 02
> Detected scsi disk sdb at scsi0, channel 0, id 1, lun 0
> scsi : detected 2 SCSI disks total.
> (scsi0:0:0:0) Synchronous at 40.0 Mbyte/sec, offset 8.
> SCSI device sda: hdwr sector= 512 bytes. Sectors= 8887200 [4339 MB] [4.3
> GB]
> (scsi0:0:1:0) Synchronous at 40.0 Mbyte/sec, offset 8.
> SCSI device sdb: hdwr sector= 512 bytes. Sectors= 8888924 [4340 MB] [4.3
> GB]
> tulip.c:v0.90f 12/17/98 [EMAIL PROTECTED]
> eth0: Digital DS21140 Tulip at 0xd000, 00 40 05 a3 44 81, IRQ 10.
> eth0: EEPROM default media type Autosense.
> eth0: Index #0 - Media MII (#11) described by a 21140 MII PHY (1) block.
>
> eth0: MII transceiver #0 config 1000 status 782d advertising 01e1.
> eth0: Advertising 0101 on PHY 0, previously advertising 01e1.
> Partition check:
> sda: sda1 sda2 sda3
> sdb: sdb1
> VFS: Mounted root (ext2 filesystem) readonly.
> Freeing unused kernel memory: 32k freed
> Adding Swap: 130748k swap-space (priority -1)
> eth0: Using user-specified media MII 100baseTx-FD.
> portmap: RPC call returned error 111
> RPC: task of released request still queued!
> RPC: (task is on xprt_pending)
> portmap: RPC call returned error 111
> RPC: task of released request still queued!
> RPC: (task is on xprt_pending)
> lockd_up: makesock failed, error=-111
> portmap: RPC call returned error 111
> RPC: task of released request still queued!
> RPC: (task is on xprt_pending)
------------------------------
From: Jeremy Randall <[EMAIL PROTECTED]>
Crossposted-To: alt.linux,comp.os.linux
Subject: Re: Red_Hat setup problems
Date: Mon, 01 Feb 1999 10:34:02 -0800
Please let me know what you find out! I'm having a similar problem on my home
LAN... it's terribly slow to telnet or FTP in to my 486, and P120! The weird
thing is, one of the 486's worked much faster on a corporate LAN... ugh...
Jeremy
Aidan Gillis wrote:
> Having major problems with telneting into a new linux box. Its really
> really slow.
>
> Spec of the machine
> Pentium 75
> 110 Mb ram
> 4.3 gig hard drive
> 3com fast etherlink
>
> when working on the box itself everything seems fine, even telneting to
> other boxes, but when trying to telnet in it takes forever. Any suggestions
> on what I should look for.
>
> Thanks
------------------------------
From: [EMAIL PROTECTED] (douglasf)
Subject: Netatalk with Copstalk
Date: Mon, 1 Feb 1999 10:40:18 -0800
I have a linux server running netatalk + samba sharing a 'public junk'
volume on a mixed Macintosh and Win/NT network. I had set the system up
to allow both platforms to read and write to the server. Everything
seemed to be working rather well, much better then I had expected, given
my rather limited knowledge of networks and linux.
So along comes a new Windows user who has CopsTalk installed on his
machine. When he logs in he sees the entire Macintosh network (Apple
printers and other AppleServers) along with the linux netatalk box. He
can login through the netatalk side and mount the 'junk' volume, but if
he tries to copy anything from or to the volume he gets a 'can't find
file pathname' error. If he logs in through the Windows Network, samba
handles everything just fine.
Has anyone seen this behavior? Any help is much appreciated.
Douglas
------------------------------
From: [EMAIL PROTECTED] (Jim Roberts)
Subject: Re: Red_Hat setup problems
Crossposted-To: alt.linux,comp.os.linux
Date: Mon, 01 Feb 1999 19:22:21 GMT
In article <[EMAIL PROTECTED]>,
Jeremy Randall <[EMAIL PROTECTED]> writes:
> Please let me know what you find out! I'm having a similar problem on my home
> LAN... it's terribly slow to telnet or FTP in to my 486, and P120! The weird
> thing is, one of the 486's worked much faster on a corporate LAN... ugh...
>
> Jeremy
>
>
> Aidan Gillis wrote:
>
>> Having major problems with telneting into a new linux box. Its really
>> really slow.
>>
>> Spec of the machine
>> Pentium 75
>> 110 Mb ram
>> 4.3 gig hard drive
>> 3com fast etherlink
>>
>> when working on the box itself everything seems fine, even telneting to
>> other boxes, but when trying to telnet in it takes forever. Any suggestions
>> on what I should look for.
>>
>> Thanks
>
--
Jim Roberts Never enough time!
[EMAIL PROTECTED]
------------------------------
From: [EMAIL PROTECTED] (David Hinds)
Crossposted-To: comp.os.linux.portable,linux.redhat.install
Subject: Re: Weird 3COM Card Problem - Help Please
Date: 1 Feb 1999 19:39:31 GMT
dave dufeau ([EMAIL PROTECTED]) wrote:
:
: I am experiencing almost the same ordeal with the 3ccfem656 card (I
: don't know the difference between this card and the 556), except that I
: cannot get the card to be recognized. Can you tell me which driver you
: used?
The FEM656 is a new card, and is also Cardbus. It is not supported at
this time. I haven't tried to get one from 3Com yet: I first heard
that it existed last week.
As for the original problem with the FEM556, my advice is to find a
different way to do the installation. It is basically impossible to
debug problems with install disks, and you can't easily patch those
disks anyway. After installing, then you can use the PCMCIA-HOWTO to
troubleshoot problems, or install new drivers, etc.
The 3CCFEM556 and 3C574 driver is still fundamentally flawed, and we
(me and Donald Becker) haven't been able to track down the problem.
-- Dave Hinds
------------------------------
From: "Nicola� Kisselhoff" <[EMAIL PROTECTED]>
Subject: Re: ppp dial-on-demand or Diald ???
Date: Mon, 01 Feb 1999 17:31:40 +0100
Si j'ai bien compris ce qu tu veux faire :
acc�der � l'internet � parti de n'importe laquelle de tes machines en
passant par celle qui � un modem et un seul compte chez ton provider.
Cel� s'appelle IPmasqurade et il y a un howto en fran�ais qui explique
cel�. Un bonne lecture pour tout ce qui concerne le r�seau est :
Administration r�seau sous linux de chez O'Reilly.
Tiens-moi au courant.
Amicalement, Nicolas.
Beno�t Cousson a �crit:
>
> Hi,
>
> I want to use my linux box (Dell PowerEdge 2300 + Redhat5.2) as a gateway to
> the internet for my local network (about 25 PC with NT/95/98). I've tried
...
------------------------------
From: [EMAIL PROTECTED] (Martin Adler)
Subject: It might be stupid... but another NT and Linux prob
Date: Mon, 01 Feb 1999 19:43:18 GMT
This one might be a little tough.... How do I make samba get the
Usernames from an NT server and use the encrypted passwords that NT
uses??
Thanks for the help,
Martin Adler
[EMAIL PROTECTED]
------------------------------
From: [EMAIL PROTECTED]
Subject: problem with cardmgr not recognizing card
Date: Mon, 01 Feb 1999 16:52:18 GMT
Hi. I've just recompiled my Red Hat 5.2 kernel to support PCMCIA. My card, a
3Com 589D, is not being detected. When I ran cardctl status, it reported that
that no cards were installed, and there is no indication of network activity
( a green light on the card cable). I have a Thinkpad 390. The system log
entries for cardmgr are: cardmgr[220]: starting, version is 3.0.5
cardmgr[220]: watching 2 sockets
nothing more about card mgr in the system log.
Any help would be greatly appreciated, thanks in advance.
Paul Misner
============= Posted via Deja News, The Discussion Network ============
http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own
------------------------------
From: [EMAIL PROTECTED] (Clifford Kite)
Subject: Re: PPP no longer working
Date: 1 Feb 1999 09:05:26 -0600
Nigel Sim ([EMAIL PROTECTED]) wrote:
: I originally installed RedHat 5.0 with pretty much all the extra's, and I
: managed to get it to connect to the net through PPP using the network
: manager in X. Today I upgraded the kernel to 2.2.1 and I made sure I added
: all the PPP and IP related bits. But now when I try to activate the PPP1
: device it dials, the lights flash a bit, but it then hangs up. When I boot
: to Win95 I can still connect (as you can see).
: What could be the problem here? Is there any known errors in 2.2.1 that I
: should know about?
My guess would be that you have ppp-2.2.0 and you need ppp-2.3.5 . You
also should read the linux/Documentation/Changes file.
--
Clifford Kite <[EMAIL PROTECTED]> Not a guru. (tm)
/* I gave up on politics when no matter who I voted for, I regretted it.
* -- Pepper...and Salt, WSJ */
------------------------------
** 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
******************************
