Archive for the ‘internet’ Category

Webserver switched from lighttpd to nginx

Saturday, December 5th, 2009

For some time now, I have been experiencing weird bugs with my webserver. I was running a lighttpd, version 1.4.22. Two annoying bugs occurred:

The first was more a nuisance when uploading files through a POST, which resulted in error 417 "Expectation failed" on the first attempt (while on the second it worked).

The second bug resulted in a reproducible denial-of-service, as it crashed the webserver. It occurred whenever a firefox-webbrowser attempted to connect to the server through HTTPS.

I hoped these bugs to be solved by upgrading from 1.4.22 to 1.4.23 and 1.4.24, but that did not happen. As I needed a solution to these bugs, I decided to switch from lighttpd to nginx.

The transition went surprisingly smooth. The configuration is a bit more complicated as it was with lighttpd, but easily set up and quite good explained on nginx's website, too.

Now, nginx runs all my websites, interacts with PHP through FastCGI, and problems seem to be gone.

netbsd.org online again

Friday, April 10th, 2009

Since Thursday, 9th April 2009, 17:00 UTC internet, landline and cellular phone services seem to be restored. That means netbsd.org is available again :)

For more details, see the appropriate articles on sfgate.com and cnet.

netbsd.org down due to cut fiber-optic cables

Thursday, April 9th, 2009

Since Thursday, 09th April 2009, 01:30 a.m. PDT netbsd.org and quite a lot other hosts and services like landline and cellular telephone were knocked out, as "vandals" cut fiber-optic cable lines in two different locations around southern Santa Clara County, in Santa Cruz and San Benito counties and along the Peninsula.

See sfgate.com and cnet for more information.

Windows-Update and Proxies

Tuesday, April 7th, 2009

After a discussion on IRCnet, I decided this topic might be worth a blog-post: How do I get Windows Update on Windows XP Home to work with proxies?

Windows XP Professional seems to accept the Administrator's Proxy-Settings automagically, but Windows XP Home doesn't. If you have a network that only permits HTTP-Access through a configured proxy, you have a problem: Windows XP Home won't update, because it attempts a direct connection to Microsoft's servers.

My own setup at home is like this: I have a Cisco C836 Router, which ACL's prohibit any traffic not coming from the proxyhost, or being from certain selected reserved protocols. The proxyhost is a NetBSD 5.0 RC3 Box (see this page and this post), running a Squid 3.0 Web-Proxy.  Since I needed to update my XP-Home-running NetBook, I found a simple solution to this problem some time ago: each Windows comes with a small tool named "proxycfg". All you need to do is call it appropriately, and even Windows XP will update through the proxy like a charm.

This is the help-output from proxycfg:

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\>proxycfg -?
Microsoft (R) WinHTTP Default Proxy Configuration Tool
Copyright (c) Microsoft Corporation. All rights reserved.

usage:

    proxycfg -?  : to view help information

    proxycfg     : to view current WinHTTP proxy settings

    proxycfg [-d] [-p <server-name> [<bypass-list>]]

        -d : set direct access
        -p : set proxy server(s), and optional bypass list

    proxycfg -u  : import proxy settings from current user's
                   Microsoft Internet Explorer manual settings
                   (in HKCU)

C:\>

If you have configured the Internet Explorer to use the proxy, you can simply call

 C:\> proxycfg -u

And the settings will be used. If you don't have the IE configured (which is a wise decision if you don't use it), you need to specify the proxy using the -p switch. In my case, this would look like this:

 C:\> proxycfg -p http://proxy.home.nifelheim.info:3128

After this, Windows Update will use these settings and you can update your machine.

What’s up with Wasabi Systems Inc.?

Thursday, April 2nd, 2009

When I logged in into my blog today, a plugin called "broken-link-checker" notified me about a broken link. I wondered which link this might be, and checked it - which just increased my irritation and confusion, because it was the link to Wasabi Systems Inc. (http://www.wasabisystems.com). I checked it manually from several different hosts, and even tried to ping it - with no success. The servers really seem to be down, though the routes are still there, and the name-server still (at least at the time of this post) resolve the name into the corresponding IP-Address.

I asked around in the IRC, with the result, that I was not the only baffeld one finding the Wasabi System Inc. hosts down. According to unconfirmed rumors, Wasabi Systems Inc. is said to have closed down business some weeks ago. This is an unconfirmed rumor, and I though I have tried and searched the internet, there is absolutely no way in finding out anything reliable about the current state of Wasabi System Inc., except that their servers are shut down. When you look at the entries of the employees of Wasabi Systems Inc., which you can find on business-contact-platforms, their current employment status is "working at Wasabi System Inc. in Position <x>".

Because there is not even a page stating some kind of technical problem, and since a downtime like this would be really really expensive for a modern IT-Company, I don't believe in technical issues. On the other hand I find it really hard to believe that a promising company like Wasabi Systems Inc. should have shut down business, especially in such a mysterious, dead-silent way. Even an April's Fool's Day Joke can probably be dismissed, because while that would have been funny yesterday, today it is not. And besides that, as I said before, a Joke like this is bad publicity, and the unavailability would harm Wasabi System Inc. more than the joke would do good, because support is as unreachable as anything else.

Wasabi System Inc. was building and selling Network Storage Devices based on NetBSD and provided a journalling filesystem called wapbl, which they donated to the NetBSD community some time ago.

Here are my ping-stats:

mjoellnir@unknown:~$ ping wasabisystems.com
PING wasabisystems.com (69.9.177.46): 56 data bytes
^C
----wasabisystems.com PING Statistics----
9 packets transmitted, 0 packets received, 100.0% packet loss
mjoellnir@unknown:~$ ping support.wasabisystems.com
PING support.wasabisystems.com (69.9.177.82): 56 data bytes
^C
----support.wasabisystems.com PING Statistics----
32 packets transmitted, 0 packets received, 100.0% packet loss
mjoellnir@unknown:~$

Update:

I tried to call them, but their phone-lines are permanently "busy", no matter what time of day. As it seems, the rumours about them having closed down business are getting more and more substantial. What I wonder is, why they seem to keep it such a mystery.

Smartphone-Experiments, Part 1

Sunday, March 30th, 2008

Over the last two days, I finally found a few hours to experiment with my Windows Mobile driven smartphone, an HTC Touch (ok, it's branded, so it's aka MDA Touch).

With Windows, it syncs out-of-the-box, what a surprise, but with linux, things are a bit more interesting. I am running a Debian/Lenny on my laptop, an old Acer Travelmate 732TL, a Pentium III-500 with 256MB RAM. My intention was to enable the laptop to synchronize with the phone through a USB-cable-connection, and to use the phone for internet-connections. I installed the SynCE-suite packages, along with multisync, and tried my luck. Well, what shall I say, it failed. After looking at the SynCE-manpages, I found out why: Windows Mobile smartphones require a special kernel-module to work properly. So I downloaded the module-sources from the SynCE-website, compiled and installed them, and tried again, running the following commands:

modprobe rndis_host
synce-serial-config ttyUSB0
synce-serial-start
pls

This time, it worked. I got my directory-listing. An ifconfig showed me this:

ppp0      Link encap:Point-to-Point Protocol
          inet addr:192.168.131.102  P-t-P:192.168.131.201  Mask:255.255.255.255
          UP POINTOPOINT RUNNING NOARP MULTICAST  MTU:1500  Metric:1
          RX packets:13 errors:0 dropped:0 overruns:0 frame:0
          TX packets:9 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:3
          RX bytes:994 (994.0 B)  TX bytes:119 (119.0 B)

The two ip-addresses are the default-values of windows-mobile-phones. As far I as can tell, one should leave them as they are, since it does not seem to work with different ip-addresses (at least not for me, that is). Of course, you are free to try and comment on this ;) .

Internet-Connections

The next thing I tried now was to establish an internet-connection through the smartphone. From the phone's manual I knew there was a program for a shared internet-connection, where the telephone connected itself into the internet by using GPRS/EDGE, and acted as a router/nameserver for the connected computer. I activated that program from the programs-folder (in german, this program is called "Internetfreigabe"), selected "USB" for the connection to the computer, and the GPRS-profile, and then let the program connect to the internet. Though the telephone complained about ActiveSync being "active", it connected me to the internet. An ifconfig gave me now this output:

rndis0    Link encap:Ethernet  HWaddr 80:00:60:0f:e8:00
          inet addr:192.168.0.102  Bcast:192.168.0.255  Mask:255.255.255.0
          inet6 addr: fe80::8200:60ff:fe0f:e800/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:8050  Metric:1
          RX packets:59 errors:53 dropped:0 overruns:0 frame:0
          TX packets:102 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:6848 (6.6 KiB)  TX bytes:19488 (19.0 KiB)

I tried to ping my server using its ip the first time, and its name the second, and both worked fine: I was connected. However, further experiments showed that simply connecting the phone and loading the modules, and then activating the internet-connection on the phone would not work. And rndis0-interface would show up, yes, but it will look like this:

rndis0    Link encap:Ethernet  HWaddr 80:00:60:0f:e8:00
          inet addr:169.254.2.2  Bcast:169.254.2.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:8050  Metric:1
          RX packets:12 errors:9 dropped:0 overruns:0 frame:0
          TX packets:48 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:1124 (1.0 KiB)  TX bytes:7168 (7.0 KiB)

Take a good look at the ip-address, you will notice that it is different from the first two ifconfig-dumps, which used the same ip-adress. A connection will not be possible this way, it has to be set-up and established through synce-serial-config and synce-serial-start before.

Though I have installed Evolution, multisync, and several plugins/modules for both programs, I was not yet able to synchronize my telephone's address-book, calender, todo-list etc. with the laptop. May be Debian/lenny uses packages which are not as up-to-date as I would need it, I have take a further look into this, still. The most important two things, anyhow, being able to transfer files between telephone and laptop, as well as establishing an internet-connection for the laptop by using the telephone as a router/modem, are working now, and quite without an effort, too.

I will continue with my smartphone-experiments, so stay tuned! ;)