Cheers Greg. That was interesting.  I decided to follow the SunRayOnUbuntu with 3.1 howto and actually got a little bit further.

The SR1 and my Ubuntu vmware server start talking to each other, but the SR1 seems to break down the link  on the firmware update.

Back to plan A. which I dropped as Solaris on a laptop vmware w/s host was a PITA. My new vmware setup should make it easier.

19:26:47.696921 rarp who-is 08:00:20:c3:17:64 (oui Unknown) tell Broadcast
19:26: 48.176140 rarp who-is 08:00:20:c3:17:64 (oui Unknown) tell Broadcast
19:26:48.176177 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 08:00:20:c3:17:64 (oui Unknown), length: 300
19:26:48.177406 IP mirror-i.bootps > 192.168.89.149.bootpc: BOOTP/DHCP, Reply, length: 350
19:26:48.180140 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 08:00:20:c3:17:64 (oui Unknown), length: 300
19:26: 48.191828 IP mirror-i.bootps > 192.168.89.149.bootpc: BOOTP/DHCP, Reply, length: 300
19:26:48.195644 arp who-has mirror-i (Broadcast) tell 192.168.89.149
19:26:48.195831 arp reply mirror-i is-at 00:0c:29:44:03:85 (oui Unknown)
19:26:48.199746 IP 192.168.89.149.4097 > mirror-i.tftp:  30 RRQ "CoronaP1.080020C31764" octet
19:26:49.140665 IP 192.168.89.149.4098 > mirror-i.tftp:  45 RRQ "CoronaP1-3.0_51,REV=2004.11.10.16.18 " octet
19:26:50.007687 IP 192.168.89.149.4099 > mirror-i.tftp:  17 RRQ "CoronaP1" octet
19:26:52.086506 IP 192.168.89.149.33527 > mirror-i.afs3-rmtsys: S 759:759(0) win 4096 <mss 1460,eol>
19:26:52.086550 IP mirror-i.afs3-rmtsys > 192.168.89.149.33527: R 0:0(0) ack 760 win 0
19:26:52.088934 IP 192.168.89.149.afs3-rmtsys > 255.255.255.255.afs3-rmtsys:  [|rx] (10)

_______________________________________________
SunRay-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/sunray-users

Reply via email to