Looks like the kinks of my new two-server setup are not ironed out. I just got home from RPI and the old Dell is acting wacky at school. I thoroughly checked both machines before I left for home, and I thought everything was okay. However, upon arriving home, I checked the web server to find that it doesn’t work – not even a 404 page or a time out error, the browser just hangs.
To use anything other than HTTP on port 80, I need to be on RPI’s VPN. I log into the VPN and start with the basics. The machine (which is not behind a NAT router) responds to ping, however ssh shows the same symptoms as apache and the connection just hangs. I don’t even get a connection refused, path not found or timeout error.
After being thoroughly baffled by this, I ran NMAP from another machine on the same network:
[luke@void ~]$ nmap -A -T4 stonelinks.org Starting Nmap 4.11 ( http://www.insecure.org/nmap/ ) at 2010-12-27 03:39 EST Interesting ports on doylel2.stu.rpi.edu (220.127.116.11): Not shown: 1676 closed ports PORT STATE SERVICE VERSION 21/tcp open ftp? 22/tcp open ssh? 80/tcp open http? 111/tcp open rpcbind?
I have VPN access and control over other computers on the same network, but obviously no physical access to the machine. I have no idea what is going on here. My assumption is that the kernel is hanging on something? But I guess I’ll find out when I get back. Because of the way RPI manages IP addresses, the firewall at RPI, and the uncertainty of the other computer, I’m hesitant to just tell my desktop to take the old MAC / IP combo for Stonelinks until I get back on campus in case I lose both machines. Luckily I had a backup of Stonelinks that I moved to my house. Until I get back on campus, I am hosting off my houses internet connection! Be warned in this time Stonelinks will be operating in a pretty crippled capacity.
Ever wanted to use google imagery inside of a leaflet map? This is just a small example of a google maps imagery / base layers hosted inside of a leaflet map. Check out where the magic happens on github: here.
Written by Lucas Doyle, a robotics engineer who does a lot of web development in San Francisco.