Pulseaudio lives upto the expectations..

After months of naughtiness, Pulseaudio seems to settling in nicely in Karmic Beta. Everything stable, no glitches, twitches, CPU usages back to depths of lowness ๐Ÿ™‚

Always knew pulseaudio has network access possible. Always wondered to be able to do it. Finally I have two laptops to try all those twosome things. And I did.

First I connected them using synergy(mouse/keyboard). Using SFTP to use them as file servers and pulseaudio as my audio servers.

Now the situation is, I have kept one laptop in that corner there. Its supposed to be my process intensive server. Its supposed to run my music, download stuff for me, check my mails – sound horns when they arrive and be busy and burn in hell in that corner. And it runs KDE. Now my powerful speakers (donated by a dear friend after he moved to US), remain connected to this busy bee. Well they sound like thunder, they are Altec Lansing MX5021.

What pulseaudio allowed me to do is, broadcast or redirect by audio from my mobile laptop to my server laptop. So while I want to play movies, I don’t need to get that speaker wire sorted out from the tangly world of wires. All is done by a mouse click. ๐Ÿ™‚

Pulseaudio delivers and I have a smile.

Just for a quick start –
– Install paman (pulseaudio device manager) from Synaptic and run PulseAudio Device Chooser from Application -> Sound & Video.
– On the device chooser click Configure Local Sound Server, Make sure your sound server is discoverable in first 2 tabs. I even by passed authentication.

Do that on all the machines in the LAN. Done.

Now you can simple send your sound to any machine, by simply selecting “Default Sink” to whichever machine you want.

Done. Sound starts playing in the remote machine. You can have your smile:) The best part is I can choose which application plays where. I can decide that this music plays there, this youtube plays locally here on my box and this alarm application sounds in the machine there in other room. You know where I am going with this. Bring out your Vista or Windows 7 or Windows 8 and do this for me. Oh wait, they got a new feature to sell Windows 7 Supreme.

Cost for all this – Around 200KB/s more wireless data flowing around me… Now only if I could get this charging wire off me, but I heard even that’s coming … ๐Ÿ™‚

Advertisements

Change default remote desktop port from 3389 to something else.

You can easily change the default remote desktop port from 3389 to something else by browsing to following registry key:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\TerminalServer\WinStations\RDP-Tcp\PortNumber

Double click this key, chose decimal and enter the new value. Restart terminal service port.

Why do this? Well if you expose your machine over internet for RDP, then its better to use a non-standard port. The moment I see a 3389 port open, my hands itch to try a few passwords.

General Updates, Control that bandwidth looter. “trickle” them. Play your favourite shoutcast stream while your torrents download happily in background.

Back after a long time. Will provide some general updates and introduce you to this fine little cuty called trickle.

Ever stuck with torrent downloads who steal all your bandwidth, and you can’t even open google .com. Talk about limiting download speeds from torrent clients, which never work efficiently. Or how about listening to shoutcast while your firefox blazes away.
Read the rest of this entry »

Local DNS caching – pdnsd. Reduce name resolutions times. Run your own caching DNS server. And there’s something about OpenDNS.

Often, I find, You hit a website and you see “Looking up http://www.zzzzz.com” in status bar. This becomes intensified if you are running a P2P software like torrents.

Often people enable host name resolution in torrents. With hundreds of connections and name resolutions, I often feel the rates of “Looking up … ” continuously increases. These are most definitely DNS name resolution delays. Running a quick sniff for a un-responding website suggests a name resolution delay.
Read the rest of this entry »

Proxy Hacks – Final. HTTPTunnel. Tunnel TCP / IP connections over plain old HTTP GET and POST requests.

This is the final post in Proxy Hack series. This post is about the most robust approach for by passing any proxy.

Read the rest of this entry »

Proxify any application. Tsocks and proxychains. Force any program to communicate through a SOCKS, HTTP(S) proxy. And how to use cascading proxies.

How many times have you found applications not having proper proxy support. Or sometimes, they support proxies but does not let you provide proxy authentication. Ever used plain old telnet through a proxy ? Ever ran port scanners through proxies ? ๐Ÿ˜‰

Ever found wanting on how to use multiple cascading proxies, like two or more proxy in series.

Read the rest of this entry »

Proxy hacks – IV. On Demand. Installing a web based proxy (phproxy) at your home. Install something like kproxy.com. Useful for almost all blocked websites.

I am back from a small vacation, from a beach place called GOA. It was just amazing. Today we learn about web based proxies as anonymizer, proxify or kproxy and how to install our own.

So, Here’s today’s *durty* trick.

Read the rest of this entry »