I decided to install an Asterisk on my home gw/server, and figured that the version via apt-get was waaaaaay to old.
I’m not much of a fan of “polluting” my servers with things compiled from source – makes reinstallation boring. But sometimes there just isn’t much choice.
I found a nice guide for installing Asterisk on squeeze.
For most of the time the guide was fine for Wheezy, but I had to install some additional packages
Want to be able to start your computer @home while you’re somewhere else?
The answer might be as simple as 3 letters: WOL (Wake On Lan)
In short – WOL sends a “magic packet” to the host you want to wake up.
Saving some money on the electricity bill is always a good thing – but how do you do it without limiting yourself in your nerdy life?
One answer might be to get a Soekris 5501 and use it as a gateway.
I’ve just received two of those nice boxes (had a 4801 before, but had to replace it with an Atom based system, due to lack of throughput).
Finally some good news on IPv6 connectivity via bredband2.se 🙂
(link updated to reflect new place)
It means that I still can’t get native connectivity, but they have realized the need to tell why they can’t deliver now, and give some pointers on how to get IPv6 anyway – now I’ll just wait for an upgrade to the equipment where I live 🙂
With the IPv4 address exhaustion around the corner you might want to take a look at IPv6.
The lucky ones have an ISP which is already IPv6 ready – I’m not one of the lucky ones … in fact my ISP (bredband2.se) have responded to me that they don’t have any plans for deploying IPv6 to their customers 🙁
So – what do I have to do to get my IPv6 fix?
Now we have a nice IPsec tunnel between two sites we would like to get some IPv6 connectivity between the two sites as well.
This is _really_ easy to do.
All we have to do in order to achieve our goal is to attach the following to our ipsec.conf (this is on router1, router2 should have minor changes) + add ipv6 addresses to the inside interfaces on the routers
Don’t look too much on the addresses 😛
With the amount of insecure wifi networks all around it’s tempting just to use them for Internet access – right?
Doing so opens up a nasty way of messing with your data – getting to know what sites you visit, and also access to all transmitted data, sent in clear. Read More
Got two or more places you want to connect in a secure manner?
Then building a VPN might be a good idea.
For opensource VPN solutions you have two choices (roughly said) – OpenVPN or IPsec
OpenVPN is great for connections from roadwarriors, and some cases for site-to-site, but securing all trafiic between two sites – including between the two routers, is a pain. Another thing to consider is: both endpoints have to run OpenVPN.
IPsec on the other hand is fairly easy to use, once you’ve tried it once + you can use a lot of different equipment as endpoints.
This blog will look at setting up a VPN between two Debian/Ubuntu nodes.