Dave,
I've never tried using plip to connect Linux to Windows, so I don't know if any
of this will help or not.
I'm no expert on networking, but I do have plip working between two Debian 2.0
machines and, for reference, here's my config files. I have plip compiled as a
module:
/etc/hosts
127.0.0.1 localhost.pfeifer.home localhost
192.168.1.1 newdebian.pfeifer.home newdebian
192.168.1.2 olddebian.pfeifer.home olddebian
/etc/networks
localnet 127.0.0.0
pfeifer.home 192.168.1.0
/etc/init.d/network
ifconfig lo 127.0.0.1
route add -net 127.0.0.0
ifconfig plip1 192.168.1.1 pointopoint 192.168.1.2 up
route add -net 192.168.1.0 netmask 255.255.255.0 dev plip1
The last two lines in /etc/init.d/network can also just be entered manually from
the command line to bring up the interface.
When the plip interface is up, my ifconfig output for plip looks like this:
plip1 Link encap:Ethernet HWaddr FC:FC:C0:A8:01:01
inet addr:192.168.1.1 P-t-P:192.168.1.2 Mask:255.255.255.0
UP POINTOPOINT RUNNING NOARP MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
Collisions:0
Interrupt:7 Base address:0x378
the output of route -evn looks like this:
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
192.168.1.0 0.0.0.0 255.255.255.0 U 1500 0 0 plip1
127.0.0.0 0.0.0.0 255.0.0.0 U 3584 0 0 lo
and a ping to the other machine looks like this:
PING olddebian.pfeifer.home (192.168.1.2): 56 data bytes
64 bytes from 192.168.1.2: icmp_seq=0 ttl=64 time=4.6 ms
64 bytes from 192.168.1.2: icmp_seq=1 ttl=64 time=4.4 ms
Tom
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. 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.
>
> 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).
>
> --
> Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null
--
Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null
