hi again,
sorry to hear of your ongoing frustration, and since my entire career has been to make computers work despite themselves means i can sympathize, believe me.
in this case, getting the Shake Pi successfully connected to the internet involves more than one computer to be cooperative in making this succeed. and in our experience, school networks have proven to be extra challenging. home networks are usually less problematic (fewer firewall requirements to handle), but can still pose a challenge in some cases. you can read all about a very recent example of what can happen here. perhaps something in this thread may be of relevance to your use case.
like in that thread, i would like to see the log files again, from when the unit was connected to a LAN outside the school’s network. as well, if possible, please send along the following files:
/etc/resolv.conf/etc/dhcpcd.conf
Also the output of the following command:
> traceroute 8.8.8.8
this is clearly a networking issue where somewhere along the way something is mis-configured; solving it is a matter of identifying the exact source of the problem before the proper remedy can be applied.
rest assured, thousands of units have come online without any issue whatsoever when using all the default settings. and for all the cases when there was a problem, including when installed on school networks, our support team has persevered and has always been successful in getting the unit online.
thanks in advance for the log files. sometimes, unfortunately, finding the source of a problem is a process of eliminating the possible causes, one by one. this is especially true when success requires the cooperation of other computers.
cheers,
richard