Re: PLIP setup?

1997-03-01 Thread Jim
On Thu, 27 Feb 1997, Steve Reid wrote:

 SIOCSIFADDR: No such device
 SIOCSIFDSTADDR: No such device

 It looks as if the PLIP device is not compiled into the kernel. I don't
 get any message regarding PLIP when I boot, but I _know_ I have PLIP
 compiled into the kernel. 

Compile both lp and plip as modules- lp otherwise takes priority and
since only one device per port is allowed, plip will not exist. You
can make an ugly hack to kernel sources if you wish.

With the 11 wire plip cable on port 0x278 (IRQ 5), I connect machines 
edp0 and edp1  (.1 and .2) as follows:

/sbin/insmod plip io=0x278 irq=5
/sbin/ifconfig plip0 arp 10.0.0.1 pointopoint 10.0.0.2 up
/sbin/route add -net 10.0.0.0 plip0
/sbin/route add -host 10.0.0.2 plip0

edp0 is the gateway machine (short.circuit.com) and the above is used
on edp1 with the difference of .1 and .2 being swapped around in the
command lines. In addition, edp0 is defined as the gateway on edp1:

/sbin/route add default gw 10.0.0.1 plip0

Slow machines like mine need klogd -c4 to stop plip errors from going to
the screen.

To take the network down:

/sbin/ifconfig plip0 down 
rmmod plip


-!-


Re: PLIP setup?

1997-03-01 Thread Jim
On Fri, 28 Feb 1997, Spineux Alain wrote:
 
 You can't include PLIP and the printer driver together

You can with separate ports and module support..

#/etc/conf.modules
#
[..]
options lp io=0x3bc,0x378
options plip io=0x278;irq=5

This puts a printer on your plip network.  


-!-


Re: PLIP setup?

1997-03-01 Thread Karl Ferguson
At 06:47 PM 2/28/97 -0800, Jim wrote:

Hmmm - how fast is PLIP?  Are you able to give me some stats on FTP's and
ping times?  I'm wondering if it's faster than 115200 serial...

Regards

Compile both lp and plip as modules- lp otherwise takes priority and
since only one device per port is allowed, plip will not exist. You
can make an ugly hack to kernel sources if you wish.

With the 11 wire plip cable on port 0x278 (IRQ 5), I connect machines 
edp0 and edp1  (.1 and .2) as follows:

/sbin/insmod plip io=0x278 irq=5
/sbin/ifconfig plip0 arp 10.0.0.1 pointopoint 10.0.0.2 up
/sbin/route add -net 10.0.0.0 plip0
/sbin/route add -host 10.0.0.2 plip0

edp0 is the gateway machine (short.circuit.com) and the above is used
on edp1 with the difference of .1 and .2 being swapped around in the
command lines. In addition, edp0 is defined as the gateway on edp1:

/sbin/route add default gw 10.0.0.1 plip0

Slow machines like mine need klogd -c4 to stop plip errors from going to
the screen.

To take the network down:

/sbin/ifconfig plip0 down 
rmmod plip


-!-



--
  ___

   Karl Ferguson,
   Tower Networking Pty Ltd [EMAIL PROTECTED]
   t/a STAR Online Services  [EMAIL PROTECTED]
   Tel: +61-9-455-3446  Fax: +61-9-455-2776   http://www.star.net.au
  ___


Re: PLIP setup?

1997-03-01 Thread Steve
 Hmmm - how fast is PLIP?  Are you able to give me some stats on FTP's and
 ping times?  I'm wondering if it's faster than 115200 serial...

It sure is! I haven't tried FTP yet, but `ping -s 8` times look good:

PLIP   3.6 ms
33.6k modem  100.3 ms
10base-T   0.5 ms

Jim pointed me to the mini-HOWTO in /usr/doc/HOWTO/mini/PLIP.gz which has
all the necessary instructions. I've currently got plip and lp compiled
into the kernel and working at the same time, thanks to simple
instructions in the mini-howto. 



Re: PLIP setup?

1997-03-01 Thread Jim


On Sat, 1 Mar 1997, Karl Ferguson wrote:

 Hmmm - how fast is PLIP?  Are you able to give me some stats on FTP's and
 ping times?  I'm wondering if it's faster than 115200 serial...

I don't do well with my slow machine (web crawler indeed) but even it manages 
15 KB/s using ncftp. Andrea tells me his setup does 40 KB/s or thereabouts. 
Curious as to how well this compares to a null-modem serial connection.. 

This weekend I was planning to look into nfsroot and try to get the other
machine to boot up over the PLIP connection. Just for kicks, you know.

Does anyone have any info on doing this? 


-!-


Re: PLIP setup?

1997-02-28 Thread J.H.M.Dassen
On Feb 27, Steve Reid wrote
 I'm trying to configure a PLIP connection between two machines, but I'm
 having some problems... 
[...]
 It looks as if the PLIP device is not compiled into the kernel. I don't
 get any message regarding PLIP when I boot, but I _know_ I have PLIP
 compiled into the kernel. I've tried building a new kernel a couple of
 times and made sure to compile PLIP in. A grep of my .config file shows
 the CONFIG_PLIP=y line. 
 
 The system does notice lp1 and lp2 at boot, but says (polling) instead of 
 using an IRQ.

If you want to use PLIP, you must make sure that lp is compiled as a module.

This is documented in the PLIP minihowto, /usr/doc/HOWTO/mini/PLIP.gz if you
have the doc-linux package installed; see also drivers/net/README[12].PLIP
in the kernel source.

I'm attaching my plip-connect script.

HTH,
Ray
-- 
LEADERSHIP  A form of self-preservation exhibited by people with auto-
destructive imaginations in order to ensure that when it comes to the crunch 
it'll be someone else's bones which go crack and not their own.   
- The Hipcrime Vocab by Chad C. Mulligan
#! /bin/sh
set -e

# This assumes that both local and remote agree on their /etc/hosts
# data for PLIP use (hosts one and two), 
# e.g. 10.0.0.23 one and 10.0.0.42 two

usage () {
  cat  2  'END'
Usage: plipconnect [one|two] [up|down]
[one|two]: hostname
[up|down]: desired connection state
END
  exit 1
}

if test $1 = one ; then
  local=one
  remote=two
else if test $1 = two ; then
  local=two
  remote=one
  else
usage 
  fi
fi

if test $2 = up ; then
  insmod /lib/modules/`uname -r`/net/plip.o || true
  sleep 1
  ifconfig plip1 $local pointopoint $remote up
  route add $remote
  # Don't mess up the console with timeouts
  start-stop-daemon --stop --verbose --pidfile /var/run/klogd.pid || true
  sleep 2
  start-stop-daemon --start --verbose --pidfile /var/run/klogd.pid \
--exec /sbin/klogd -- -c 3 || true
  route add $remote
  ifconfig
  echo 
  route
  echo up done
  if grep -q '^/' /etc/exports ; then
echo You have entries in /etc/exports; assuming NFS daemons are active
  else 
echo You have no entries in /etc/exports; you have to start NFS daemons 
manually
  fi
else
  if test $2 = down ; then
ifconfig plip1 down || true
/etc/init.d/sysklogd restart || true
#route del $remote
ifconfig
echo 
route
echo down done.
  else
usage
  fi
fi


Re: PLIP setup?

1997-02-28 Thread D M-L
 
 I'm trying to configure a PLIP connection between two machines, but I'm
 having some problems... 
 
 I get a pair or error messages when I try to configure the plip interface
 using ifconfig: 
 
 SIOCSIFADDR: No such device
 SIOCSIFDSTADDR: No such device
 
 The two machines are both running Debian. Both produce the same error
 messages. I've tried plip and plip[0-2] for interface names. No luck.

I used 'plip1' for the normal printer port (lpt1 for dos)

 
 It looks as if the PLIP device is not compiled into the kernel. I don't
 get any message regarding PLIP when I boot, but I _know_ I have PLIP
 compiled into the kernel. I've tried building a new kernel a couple of
 times and made sure to compile PLIP in. A grep of my .config file shows
 the CONFIG_PLIP=y line. 
 
 The system does notice lp1 and lp2 at boot, but says (polling) instead of 
 using an IRQ.

You can't include PLIP and the printer driver together

 
 Any ideas???
 


-- 

Spineux Alain

==
  Spineux Alain E-MAIL : [EMAIL PROTECTED]
  INSTITUT STEVIN
  Catholic University of LouvainFAX: 32-10-472501
  PLACE DU LEVANT 2 PHONE  : 32-10-472516
  B-1348 LOUVAIN-LA-NEUVE (BELGIUM)
===


Re: PLIP setup?

1997-02-28 Thread William Chow


On Fri, 28 Feb 1997, Spineux Alain wrote:

  
  I'm trying to configure a PLIP connection between two machines, but I'm
  having some problems... 
  
  I get a pair or error messages when I try to configure the plip interface
  using ifconfig: 
  
  SIOCSIFADDR: No such device
  SIOCSIFDSTADDR: No such device
  
  The two machines are both running Debian. Both produce the same error
  messages. I've tried plip and plip[0-2] for interface names. No luck.
 
 I used 'plip1' for the normal printer port (lpt1 for dos)
 
 
 You can't include PLIP and the printer driver together
 
Hmmm... I'm not too sure if this will work, but I've been examining a
module that allows resource sharing of the parrallel port between devices.
The name is called parbus and it supposedly allows sharing between Zip
drives and the printer. I've never gotten it to work, but perhaps if you
look at their home page (do an altavista for parbus) they may have
something about sharing resources between the parralel for printing and
PLIP, perhaps an alpha driver or something for the PLIP part. 
Also, I've heard rumors that the 2.1.x kernels are eventually going to
have methods to resolve resource sharing problems, but I don't know how
far that has gotten.

Will
(The above was not intended to be a flame, if people are offended by above
comments, I sincerely apologize beforehand :) )