NeXT Computers Forum Index NeXT Computers
www.NeXTComputers.org
 
Log in to check your private messagesLog in to check your private messages

Log inLog in  RegisterRegister


Profile  Search  Memberlist  FAQ  Usergroups
netbooting a cube from openstep in virtual box [SOLVED]

 
Post new topic   Reply to topic    NeXT Computers Forum Index -> Emulation / Virtualization
View previous topic :: View next topic  
Author Message
bight



Joined: 05 Feb 2008
Posts: 11
Location: PEI, Canada

PostPosted: Tue Mar 05, 2019 10:43 am    Post subject: netbooting a cube from openstep in virtual box [SOLVED] Reply with quote

I've started a new topic, so there's no confusion with the "previous" topic.

I'm trying to use my macbook pro running openstep in Virtual Box 5.26 as a netboot, configuration, and fileserver for my cube. Currently works perfectly as configuration server providing IP, name, User directories etc. But... the cube won't netboot.

Bootp itmes out every time. Here is the tcpdump output.
Using the "ben" command.

Code:

AdminisatorsMBP:TFTP administrator$ sudo tcpdump -vv -n udp dst portrange 67-70
tcpdump: data link type PKTAP
tcpdump: listening on pktap, link-type PKTAP (Apple DLT_PKTAP), capture size 262144 bytes
11:42:18.866826 IP (tos 0x0, ttl 255, id 1, offset 0, flags [none], proto UDP (17), length 328)
    0.0.0.0.68 > 255.255.255.255.67: [no cksum] BOOTP/DHCP, Request from 00:00:0f:00:77:7d, length 300, xid 0x23de4d, Flags [none] (0x0000)
     Client-Ethernet-Address 00:00:0f:00:77:7d
     file "boot"[|bootp]
11:44:23.591140 IP (tos 0x0, ttl 255, id 1, offset 0, flags [none], proto UDP (17), length 328)
    0.0.0.0.68 > 255.255.255.255.67: [no cksum] BOOTP/DHCP, Request from 00:00:0f:00:77:7d, length 300, xid 0x248dd5, Flags [none] (0x0000)
     Client-Ethernet-Address 00:00:0f:00:77:7d
     file "boot"[|bootp]
11:44:24.205459 IP (tos 0x0, ttl 255, id 1, offset 0, flags [none], proto UDP (17), length 328)
    0.0.0.0.68 > 255.255.255.255.67: [no cksum] BOOTP/DHCP, Request from 00:00:0f:00:77:7d, length 300, xid 0x248dd5, Flags [none] (0x0000)
     Client-Ethernet-Address 00:00:0f:00:77:7d
     file "boot"[|bootp]



But "bsd" netstat is working properly.

Code:

11:49:16.662269 IP (tos 0x0, ttl 255, id 55075, offset 0, flags [none], proto UDP (17), length 328)
    0.0.0.0.68 > 255.255.255.255.67: [no cksum] BOOTP/DHCP, Request from 00:00:0f:00:77:7d, length 300, xid 0x5c7dd7cd, Flags [none] (0x0000)
     Client-Ethernet-Address 00:00:0f:00:77:7d
     Vendor-#0x4e655854
11:49:16.662805 IP (tos 0x0, ttl 60, id 56546, offset 0, flags [none], proto UDP (17), length 328)
    192.168.1.70.67 > 192.168.1.10.68: [udp sum ok] BOOTP/DHCP, Reply, length 300, xid 0x5c7dd7cd, Flags [none] (0x0000)
     Your-IP 192.168.1.10
     Server-IP 192.168.1.70
     Gateway-IP 192.168.1.70
     Client-Ethernet-Address 00:00:0f:00:77:7d
     sname "vb_openstep"[|bootp]
11:49:16.662864 IP (tos 0x0, ttl 255, id 55075, offset 0, flags [none], proto UDP (17), length 328)
    0.0.0.0.68 > 255.255.255.255.67: [no cksum] BOOTP/DHCP, Request from 00:00:0f:00:77:7d, length 300, xid 0x5c7dd7cd, Flags [none] (0x0000)
     Client-Ethernet-Address 00:00:0f:00:77:7d
     Vendor-#0x4e655854
11:49:16.969609 IP (tos 0x0, ttl 60, id 56548, offset 0, flags [none], proto UDP (17), length 328)
    192.168.1.70.67 > 192.168.1.10.68: [udp sum ok] BOOTP/DHCP, Reply, length 300, xid 0x5c7dd7cd, Flags [none] (0x0000)
     Your-IP 192.168.1.10
     Server-IP 192.168.1.70
     Gateway-IP 192.168.1.70
     Client-Ethernet-Address 00:00:0f:00:77:7d
     sname "vb_openstep"[|bootp]


I'm sort of stumped.


Last edited by bight on Thu Mar 07, 2019 9:46 am; edited 1 time in total
Back to top
View user's profile Send private message
bight



Joined: 05 Feb 2008
Posts: 11
Location: PEI, Canada

PostPosted: Thu Mar 07, 2019 8:31 am    Post subject: Almost Working. [solved] Reply with quote

OK, the initial problem was [obviously] the "boot" file was missing from the /private/tftpboot directory.

I have imaged the Cube's harddrive and it is happily starting from the Virtualbox on my mac using a combination of the NeXTStep Network Admin Manual:

http://www.nextcomputers.org/NeXTfiles/Docs/NeXTStep/3.3/nsa/13_NetBoot.htmld/index.html

and the netboot topic here:

http://www.nextcomputers.org/forums/viewtopic.php?t=2965

EXCEPT:

The login window won't start. It keeps cycling a message from loginwindow saying it can't find the window server port. I will see what I can find from single user mode.

EDIT

It's now working!

I had incorrectly entered the private directory in HostManager.app[/img]
Back to top
View user's profile Send private message
neozeed



Joined: 15 Apr 2006
Posts: 734
Location: Hong Kong

PostPosted: Fri Mar 08, 2019 11:55 pm    Post subject: Re: Almost Working. [solved] Reply with quote

bight wrote:
OK, the initial problem was [obviously] the "boot" file was missing from the /private/tftpboot directory.

I have imaged the Cube's harddrive and it is happily starting from the Virtualbox on my mac using a combination of the NeXTStep Network Admin Manual:

http://www.nextcomputers.org/NeXTfiles/Docs/NeXTStep/3.3/nsa/13_NetBoot.htmld/index.html

and the netboot topic here:

http://www.nextcomputers.org/forums/viewtopic.php?t=2965

EXCEPT:

The login window won't start. It keeps cycling a message from loginwindow saying it can't find the window server port. I will see what I can find from single user mode.

EDIT

It's now working!

I had incorrectly entered the private directory in HostManager.app[/img]


Nice job!
_________________
# include <wittycomment.h>
Back to top
View user's profile Send private message Visit poster's website
Display posts from previous:   
Post new topic   Reply to topic    NeXT Computers Forum Index -> Emulation / Virtualization All times are GMT - 7 Hours
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum



Powered by phpBB © 2017 phpBB Group