Re: Ann : Capture & Ether1394
Brought to you by:
aeb,
bencollins
From: <fir...@se...> - 2000-05-23 17:42:31
|
On Tue, 23 May 2000, [iso-8859-1] Franck Bonin wrote: > You should insmod the IEEE 1394 subsystem modules > (ieee1394.o and > ohci1394.o) FIRST on ALL the machines. > > And then insmod eth1394.o and ifup interfaces on all > the machines. > > This will fix the problem with HW address. Ok, I did the following: Machine 1: insmod ieee1394.o insmod pcilynx.o insmod raw1394.o Machine 2: insmod ieee1394.o insmod pcilynx.o insmod raw1394.o Machine 1: insmod eth1394.o ifup eth3 Machine 2: insmod eth1394.o ifup eth3 Now when I do a ifconfig eth3 I get: Machine 1: eth3 Link encap:Ethernet HWaddr 00:00:69:65:65:00 inet addr:192.168.3.10 Bcast:192.168.3.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:186 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 txqueuelen:100 Machine 2: eth3 Link encap:Ethernet HWaddr 00:00:69:65:65:00 inet addr:192.168.3.11 Bcast:192.168.3.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:186 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 txqueuelen:100 This driver does not rely on any type of card does it? Judd Tracy jt...@is... |