Started by blakespot, April 20, 2018, 06:12:35 pm
QuoteHowto: Setup networking on NeXTstep 3.0 and later:1. Use Simple Network Starter (you find it in the NextAdmin directory) and set up some values: a Check "Provide the services specified below." b Choose a hostname (whatever you want). c Set IP address to "10.0.2.15". d Go to "Network Options..." and set Router to "10.0.2.2" Broadcast Address to "10.0.2.255" Netmask to "255.255.255.0" and NIS Domain Name to "None". e Hit configure. You will be prompted to connect the Ethernet cable. f If not already done, connect emulated Ethernet now using Previous' GUI and hit OK.2. Using root access rights open and edit these files: a /etc/hostconfig and replace "-ROUTER-" with "10.0.2.2". b /etc/resolv.conf and add "nameserver 10.0.2.3". If this file does not exist, you have to first create it. Be sure you create a plain text file. If you use Edit.app you can do this by selecting Format > Text > Make ASCII. Howto: Open the above files using root privileges (NeXTstep 3.3): a Open the /etc directory with this command in Terminal: "open /etc" b Select the file/application to open and from Workspace select Services > Open Sesame > Open As Root. c For making a new resolv.conf open Edit.app the same way (b) and in the save dialog type as name "/etc/resolv.conf"3. Reboot.
Quote from: "neozeed"start with the basics..with SLiRP the only thing you can ping is the gateway, see if that works.ping 10.0.2.2I think NeXTSTEP should have nslookup, try to resolve a DNS name...
Quote from: "blakespot"Quote from: "neozeed"start with the basics..with SLiRP the only thing you can ping is the gateway, see if that works.ping 10.0.2.2I think NeXTSTEP should have nslookup, try to resolve a DNS name...As root I can, indeed, ping 10.0.2.2 -- getting successful ping returns. I can't nslookup anything -- just stalls. Any ideas from here? Thanks.bp
Quote from: "neozeed"what is your /etc/resolv.confI'd try the following:10.0.2.3this should have slirp intercept and ask the OS on your behalf...184.108.40.206the google....220.127.116.11.0.0.1 the new cloudflare ones...also check your route table..netstat -nrmake sure your gateway is set to 10.0.2.2
nslookup> server 18.104.22.168Default server: 22.214.171.124Address: 126.96.36.199#53> www.google.comServer: 188.8.131.52Address: 184.108.40.206#53Non-authoritative answer:Name: www.google.comAddress: 220.127.116.11Name: www.google.comAddress: 18.104.22.168Name: www.google.comAddress: 22.214.171.124Name: www.google.comAddress: 126.96.36.199Name: www.google.comAddress: 188.8.131.52Name: www.google.comAddress: 184.108.40.206>
Quote from: "neozeed"Try all the servers... See if any of this resolves...Try telnetting to 220.127.116.11
Quote from: "neozeed"Admin privileges shouldn't matter at all when it comes to slirp...What version of Windows was it anyway?Cmake hides everything so I really have no idea if it's doing anything strange while building...