dazedandlost
Regular Contributor
Thank you for your reply. My skynet install issues seem solved atm.
I have given up trying to put the router in media bridge mode because I have been unable to find the new router ip. Nmap, traceroute, ipconfig, various web based tools, etc don't give output that is useful to me. Asus discover.exe complains, iirc, that my router and computer are on different subnet masks. I'm not smart enough to figure this double-nat situation out, and it does not seem to be a showstopper right now.
Done.
After the above, a clean upgrade process and reconfig after factory defaults (as detailed by L&LD, thank you) my problems getting skynet to install seem to have gone away.
First of all your ISP modem ideally should be put in bridge mode as you are currently in a Double-NAT situation which isn't ideal.
I have given up trying to put the router in media bridge mode because I have been unable to find the new router ip. Nmap, traceroute, ipconfig, various web based tools, etc don't give output that is useful to me. Asus discover.exe complains, iirc, that my router and computer are on different subnet masks. I'm not smart enough to figure this double-nat situation out, and it does not seem to be a showstopper right now.
Secondly I highly recommend one unified partition rather then 3 separate, there isn't any good reason on these devices to-do so and this can cause issues with scripts.
Done.
This indicates some sort of connection issue between your router and GitHub rather then Skynet its-self as Skynet fails to download necessary files
After the above, a clean upgrade process and reconfig after factory defaults (as detailed by L&LD, thank you) my problems getting skynet to install seem to have gone away.