: PLIP start up doesn't report problems but also doesn't work?

: PLIP start up doesn't report problems but also doesn't work?

Post by Jeffrey Wiegl » Wed, 23 Feb 1994 15:21:11



Well, I solved my original problem that was preventing me from adding the
plip interface 'pl0' with ifconfig, turns out I don't have 'pl0' as the
NET-2 faq suggests but instead I use 'plip0'  this seemed to work without
any problems.

some background.  I have two linux machines enigma.robo.com and
arcadia.robo.com.  they are to compose a two machine isolated network with
IP address of 192.63.31.27 and 192.63.31.23 respectively.

I have recompiled my kernel.

my hosts files are
--begin file--
127.0.0.1       localhost
192.63.31.27    enigma.robo.com enigma
192.63.31.23    arcadia.robo.com arcadia
--end file--

my reolve.conf and host.conf files are the bare minimum without nameservers
and other than that the only files I think will be of interest is rc.inet1

--begin file--
HOSTNAME=enigma

# Attach the loopback device.
/sbin/ifconfig lo 127.0.0.1
/sbin/route add 127.0.0.1

# attach the plip device
/sbin/ifconfig plip0 192.63.31.27 pointopoint 192.63.31.23 up
/sbin/route add 192.63.31.23 plip0
--end file--

(the rc.inet1 file on arcadia is similarly configured but with ip address
swapped around and configured from arcadia's point of view.)

now when I boot my two machines they come up fine, run the rc.inet1 file
without error messahes or problems and then they startup all the net
daemons except for named since I don't want this hassle.

so there are no errors during the boot up.

if I then log in as root I can do the following:

--begin command--
enigma:/etc/rc.d# ifconfig
lo        IP ADDR 127.0.0.1  BCAST 127.255.255.255  NETMASK 255.0.0.0
          MTU 2000  METRIC 0  POINT-TO-POINT ADDR 0.0.0.0
          FLAGS: 0x0049 ( UP LOOPBACK RUNNING )

plip0     IP ADDR 192.63.31.27  BCAST 192.63.31.255  NETMASK 255.255.255.0
          MTU 1600  METRIC 0  POINT-TO-POINT ADDR 192.63.31.23
          FLAGS: 0x0053 ( UP BROADCAST POINTOPOINT RUNNING )

--end command--
(again similarly for arcadia but with appropriate ip addreses.)

I can also show the routing being done:

-begin command--
enigma:/etc/rc.d# route
Kernel routing table
Destination net/address   Gateway address           Flags RefCnt    Use
Iface
localhost                 *                         UH         0     38 lo
arcadia.robo.com          enigma.robo.com           UGH        0      2 plip0
--end command--

and for arcadia I get:

--begin command--
arcadia:/etc/rc.d# route
Kernel routing table
Destination net/address   Gateway address           Flags RefCnt    Use
Iface
localhost                 *                         UH         0     38 lo
enigma.robo.com           *                         UH         0      2 plip0
--end command--

I CAN'T SEEM TO FIGURE OUT WHY enigma adds that Gateway address and arcadia
doesn't.  do you know why?

anyways the bigger problem is this...

from enigma I can ping enigma and I can telnet/rlogin to enigma but
whenever I try to ping/telnet/rlogin to arcadia (the only other remote
machine I can ping) the command will just hang indefinetly.  if I ctrl-C a
ping operation it tells me how many packets sent, 0 received, 100% packet
loss.

this behavior is also similar on the other machine arcadia, in that it
seems to hang on commands to remote hosts.

Do you know why?  do I have some sort of routing information screwed up?  I
would have thought I would get "network unreachable" errors if the routing
was botched.

Well, hopefully you guru's out there will be able to help me with my
problem since I feel I am sooooo close to getting this plip stuff working
between the two computers.

also can somebody tell me how to configure plip so it will use IRQ 7
instead of the default 5? I have a soundcard at 5 and for now I just
hardcoded dev->irq=7; in plip_init() and plip_open().  I don't think this
is the best and most elegant way to do this though and if you have a better
solution please let me know.

Also please let me know if you have a solution to my overall network
configure/routing problem described above.  If you need more information
please let me know.

Thanks in advance for all your help,

- Jeff Wiegley

 
 
 

: PLIP start up doesn't report problems but also doesn't work?

Post by Brian Switz » Fri, 25 Feb 1994 01:44:11


: Well, I solved my original problem that was preventing me from adding the
: plip interface 'pl0' with ifconfig, turns out I don't have 'pl0' as the
: NET-2 faq suggests but instead I use 'plip0'  this seemed to work without
: any problems.

: some background.  I have two linux machines enigma.robo.com and
: arcadia.robo.com.  they are to compose a two machine isolated network with
: IP address of 192.63.31.27 and 192.63.31.23 respectively.

[setup deleted]

I just installed Slackware over my old SLS system (what a difference!) and
found that my PLIP connection didn't work any more :-( - my setup looks
just like yours.

: I CAN'T SEEM TO FIGURE OUT WHY enigma adds that Gateway address and arcadia
: doesn't.  do you know why?

Just offhand - did you tell enigma its gateway was arcadia when you
installed the network disks?  I remember I did, and the gateway route was
set up for me.

: anyways the bigger problem is this...

: from enigma I can ping enigma and I can telnet/rlogin to enigma but
: whenever I try to ping/telnet/rlogin to arcadia (the only other remote
: machine I can ping) the command will just hang indefinetly.  if I ctrl-C a
: ping operation it tells me how many packets sent, 0 received, 100% packet
: loss.

: this behavior is also similar on the other machine arcadia, in that it
: seems to hang on commands to remote hosts.

: Do you know why?  do I have some sort of routing information screwed up?  I
: would have thought I would get "network unreachable" errors if the routing
: was botched.

: Well, hopefully you guru's out there will be able to help me with my
: problem since I feel I am sooooo close to getting this plip stuff working
: between the two computers.

: also can somebody tell me how to configure plip so it will use IRQ 7
: instead of the default 5? I have a soundcard at 5 and for now I just
: hardcoded dev->irq=7; in plip_init() and plip_open().  I don't think this
: is the best and most elegant way to do this though and if you have a better
: solution please let me know.

edit drivers/net/Space.c and search for PLIP.  You should see a table
with the parameters for all the PLIP lines, just change the appropriate
entry from 5 to 7.  (BTW, reading your question reminded me that I had to
do exactly this on my old SLS distribution to get PLIP to work.
Everything seems fine now - I get 25K per sec FTP transfers... thanks!)

: Also please let me know if you have a solution to my overall network
: configure/routing problem described above.  If you need more information
: please let me know.

: Thanks in advance for all your help,

: - Jeff Wiegley


 
 
 

1. Re. bffcreate -X doesn't work Re: bffcreate -X Doesn't Work

bffcreate first restores all images from the tape to /tmp (default)
and than does a 'restore -p' to pack them in big files and place these
files in /usr/sys/inst.images. It's much more easier to use 'dd' to
copy the files directly from the tape to disk. The only thing you have
to take care about it the naming. If all images are copied run 'inutoc'
on the directory were you placed your files this will create the
table of contents files '.toc'.

frank ;-)

.----------------------------------------------------------------------.
| E-Mail: FRANVM3(KRAEMERF)                 - IBM VNET  "Yes, I'm one  |
| ======  IBMMAIL(DEIBM27S)                 - IBM-Mail   of those      |
|         DE.IBMX400.IBMMAIL.KRAEMER.KRAEME - X.400      stupid IBM    |

| Voice : +49-(0)611/776-364                                           |
| Mail  : Abraham-Lincoln Street 26, 6200 Wiesbaden, Germany           |
'----------------------------------------------------------------------'

2. OS5 Problems - CAN SOMEONE HELP!

3. PPP doesn't die, it just doesn't work anymore

4. KDE flashes, won't start

5. ping -g 'gateway-IP' 'host-IP' DOESN'T work!

6. Possible Bug: 2.4.14 USB Keyboard

7. 'ppp-on' Works, 'ifup ppp0' Doesn't

8. Access Win Through Telnet

9. PLIP doesn't work anymore with 2.4.18

10. PLIP doesn't work...

11. It Doesn't Matter (much) If Sun Doesn't "Support" Dataless

12. plip in 1.1.92 doesn't work...

13. Oh, fooey -- drivers don't work, rpm doesn't work