RE: PLIP Connection to Win95
Lindsay:
Thanks for taking the time to answer my question. I think you missed an
important detail; This is a PLIP connection (parallel port IP); there is no
network card. The network "adapters" are drivers. Anyhow, I was able to
set up "lin" with the following:
#ifconfig plip1 192.168.0.5 pointopoint 192.168.0.1
#route add default dev plip1
and was then able to ping 192.168.0.5 (lin pinging its own plip adapter),
but when lin pinged 192.168.0.1 (win's network adapter) it timed out.
Similarly, when I did c:\windows>ping 192.168.0.5 (win pinging lin) it also
timed out. I'm guessing it could be one of two things:
1) I am using an incorrect windows driver
2) Lin is too slow and I need to change the timing (I read about that
somewhere).
I'm using the dialup networking adapter #2 (DUN#2)in windows (upgraded
version 1.2); this is the same driver that does direct-cable connection. IP
addresses and netmasks seem to have been set appropriately; win can ping
itself and its network adapter (driver). The features of this driver,
however, seem to be poorly documented. A few nights ago, before upgrading
the dialup networking adapter in win, I had been able to ping lin-->win
(using the Ndis2 driver). The new DUN#2 supposedly has 32bit NDIS support
(Ndis2 is 16) , so I have a feeling I might be on the right track here. I
tried asking around in the Windows chat rooms, but no one has a clue.
My Linux box is quite slow; it was built from spare parts (some of which
came from the trash).
It is an AMD '386 w/5MB RAM (very slow, indeed). Perhaps the slowness of
lin is responsible for the ping time-out.
Any ideas?
Thanks again for answering.
--David
P.S. In case you are wondering: PLIP is compiled into my kernel; LP support
is not.
> -----Original Message-----
> From: Lindsay Allen [mailto:allen@cbcfreo.wa.edu.au]
> Sent: Sunday, August 02, 1998 5:50 AM
> To: David Karlin
> Subject: Re: PLIP Connection to Win95
>
>
>
>
> On Sat, 1 Aug 1998, David Karlin wrote:
>
> > I have two boxes; call them lin and win.
> >
> > hostname ip address netmask
> > lin 192.168.0.5 255.255.255.0
> > win 192.168.0.1 255.255.255.0
> >
> > I believe that win's network adapter has been properly
> configured; It can
> > ping it's loopback and its network adapter.
>
> Neither of these means that things are correct.
>
> > After reading the NAG manual
> > section on PLIP connections, I booted lin and did the following:
> >
> > #ifconfig
> > (info on "lo" displayed; all looked good.)
> > #route add default gw 192.168.0.1
> > SIOCADDRT: Network is unreachable.
>
> You don't need the default route command unless you have a gateway.
> Try route add -n 192.168.0.0 Oh, I see below that you did this.
>
> > I also tried:
>
> > #route add 192.168.0.5 and
> > #route add -net 192.168.0.0
> >
> > Both of these commands yielded the same error msg. This is especially
> > annoying since, while fooling with configuration a few nights
> ago, lin was
> > able to successfully ping win (although, at that point win was unable to
> > ping lin).
> >
> > Can anyone figure out how to fix this?
> >
> > Thanks for taking the time to read this (yes, I'm a Linux newbie).
>
> All this assumes that your ethernet card is loaded correctly. If you need
> more help send the output of
> ifconfig and
> route -n
> commands.
>
> If the card is not loaded check /etc/conf.modules and do a "depmod -a" as
> root.
>
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Lindsay Allen <allen@cleo.murdoch.edu.au> Perth, Western Australia
> voice +61 8 316 2486 modem +61 8 364-9832 32S, 116E vk6lj
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
>
--
Unsubscribe? mail -s unsubscribe debian-user-request@lists.debian.org < /dev/null
Reply to: