So I’ve had this problem with Windows Live Messenger since it’s release.
In WLM 2011 (version 15.4) they introduced a new feature that integrates with Facebook, which I
initially didn’t like, but now I like it! Only problem was that the feature that shows Facebook galleries within WLM always failed on access with Error code: 0x80042f0f after it comes up with “Loading album via Facebook”
After many months of it bugging me, I sorta gave up. Until now.
Whilst on holiday in South Australia, I noticed that my laptop did not exhibit the same problem (though I had tried it at home).
So obviously it was a problem with my internet connection (I used mobile broadband on holiday).
Today, I ran a Wireshark on my LAN connection when the error comes up and I managed to find the conversation and found some interesting information. Apparently the return page from that error was actually a HTML Error 417; a quick Google got me to this page
Simply put, Windows Live Messenger is asking for a specific header response. Apparently my Squid proxy (on my IPFire box) isn’t playing nice. WLM wants confirmation (Expect 100-continue), but Squid instead sends out an error message, and thus WLM doesn’t get what it expects and fails.
So to fix it, we need to put
In the squid.conf file (‘/var/ipfire/proxy’ in IPFire)
Although you should really put it in ‘/var/ipfire/proxy/advanced/acls/include.acl’ and reset the proxy from the web interface (if you change squid.conf directly you will overwrite it if you change anything in the web configuration page)
This will tell Squid to ignore the request, thus it will not send an error, and BAM its working!
Only updated this a while ago, being a router I didn’t need much in the way of power, just reliability. So its mainly made of old parts.
Generic Desktop ATX (horizontal) ‘modified’ to *erhem* fit the power supply =D.
ASUS M2N SLI Deluxe
AMD Sempron 140 2.8GHz (underclocked to 1GHz) 45w Single Core, unlocked to Dual Core with NVIDIA Unleashed mode. Shows as AMD Athlon(tm) II X2 4400e.
Western Digital Caviar SE 160GB | SATAII
Western Digital Green 2TB | SATAII
2x 1GB Corsair XMS2 DDR2-800
Vantec ION2 CAN460-C 460W
ExpertColor S3 Trio64 86C764X 8MB | PCI
Its running IPFire, which is actually software based on the first Linux router/firewall distro I ran (IPCop) which was really nice, except it only ran Linux kernel 1.4, which is rather old and lacks many features.
Received my eBay el-cheapo ($8) PCI graphics card the other day, and it turned out to be an ExpertColor S3 Trio64 86C764X 8MB; Perfect for my purposes.
I am now very grateful that I didn’t splurge on a PCI-e card which would have costed me ~$70 and would have caused an overheating situation and also increased power consumption.
On that note, I noticed the CPU wasn’t really being used, so I dropped it from 2.6GHz to 1GHz by dropping the CPU multiplier to its lowest. So now I get a reduced power usage, improved thermal efficiency and no really to any performance detriment.
Also, the 4x1GB sticks of RAM seemed a bit much. So I ended up taking out 2 sticks so that I can still have it running in dual-channel mode. I know 2GB is still way too much (its currently utilising a maximum of 1% at any given time) but I just cant bring myself to keep at least enough to have it in dual channel mode. At any rate, at least they aren’t all squeezed together now so there’s room for the heat to dissipate evenly.
The only thing left to do is get the media drives (one on the router, one on the media-pc) to sync up automatically. I’ve been using rsync to accomplish this, but I haven’t yet been bothered to figure out how to sync from the router to the media-pc, currently it only works the other way around.
Perhaps I can simply reverse the paths i’m using so:
rsync -r -t -v -u -h --progress /mnt/mediaSMB /mnt/media
Will sync new/updated files from the media-pc to the router
rsync -r -t -v -u -h --progress /mnt/media /mnt/mediaSMB
Should do it the other way around … or will it?
Anyways, we’ll see how it goes, though I’m hesitant to try it considering I have already lost the media drive once.