You are in a root shell.
Verify the plip module is loaded:
$ lsmod Module Pages Used by plip 3 0
Find the exact name of the plip interface:
$ dmesg ... NET3 PLIP version 2.2 gniibe@mri.co.jp plip1: Parallel port at 0x378, using assigned IRQ 7
You can find the same information with
$ cat /proc/kmsg ... <4>NET3 PLIP version 2.2 gniibe@mri.co.jp <4>plip1: Parallel port at 0x378, using assigned IRQ 7 ... Cntrl-c
Configure the plip interface:
$ ifconfig plip1 192.168.0.1 pointopoint 192.168.0.2 netmask 255.255.255.255 up
Verify everything is ok:
$ ifconfig plip1 plip0 Link encap:Ethernet HWaddr FC:FC:C0:A8:00:01 inet addr:192.168.0.1 P-t-P:192.168.0.2 Mask:255.255.255.255 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
Verify the route to source exists:
$ route Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
If not, like in the previous example, add the route to 192.168.0.2, the source:
$ route add -host 192.168.0.2 dev plip1
Now the route is installed:
$ route Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.0.2 0.0.0.0 255.255.255.255 UH 0 0 0 plip1 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
Now you can perform a successful ping
from the
source server (ping
is not available on the Debian
install process):
$ ping target PING target (192.168.0.1): 56 data bytes 64 bytes from 192.168.0.1: icmp_seq=0 ttl=64 time=14.0 ms 64 bytes from 192.168.0.1: icmp_seq=1 ttl=64 time=4.3 ms --- target ping statistics --- 2 packets transmitted, 2 packets received, 0% packet loss round-trip min/avg/max = 4.3/9.1/14.0 ms
If it doesn't work, check the Null-Modem cable connection, rerun
dmesg
, ifconfig
, route
. Verify
everything. Take a rest. Restart.
When the ping is ok, return to the normal installation process:
On the target: Press Alt F1