How to send audio between two Linux computers using netcat

Monday, August 15th, 2011

Apparently there is no dead simple way to send audio from one computer to another in a low(er) latency way.

Can’t beat this, works for any ALSA app that you can change the output for (or just change your default in .asoundrc).

On source computer:
modprobe snd-aloop
arecord -f cd -D hw:Loopback,1,0 | netcat dest 1234
mplayer -ao alsa:device=hw=Loopback.0.0 something.mp3

On destination computer:
netcat -k -l -p 1234 | aplay

Linux layer 2 bridging can’t do Firewire

Friday, August 5th, 2011

Well, it seems and the Linux kernel can’t bridge dissimilar network types, which means I can’t bridge Ethernet and Firewire (workaround until I replace my NIC in my desktop because it fried, having my laptop route for my desktop).

My laptop’s IP is 192.168.2.4
My desktop’s IP is 192.168.2.2
My router’s IP is 192.168.2.1

So, the work around seems to be this…

On the laptop, with eth0 already up:
ifconfig firewire0 up 192.168.2.4
route del -net 192.168.2.0 netmask 255.255.255.0 dev firewire0
route add -host 192.168.2.2 dev firewire0
iptables -F
iptables -P FORWARD ACCEPT
echo 1 > /proc/sys/net/ipv4/conf/all/forwarding

On the desktop:
ifconfig firewire0 up 192.168.2.2
route add default gw 192.168.2.1

To make this permanent, you would edit /etc/networking/interfaces like this…

On the laptop:
auto eth0
iface eth0 inet static
address 192.168.2.4
netmask 255.255.255.0
broadcast 192.168.2.255
gateway 192.168.2.1
post-up ifconfig firewire0 down
post-up ifconfig firewire0 up 192.168.2.4
post-up route del -net 192.168.2.0 netmask 255.255.255.0 dev firewire0
post-up route add -host 192.168.2.2 dev firewire0
post-up iptables -F
post-up iptables -P FORWARD ACCEPT
post-up echo 1 > /proc/sys/net/ipv4/conf/all/forwarding

On the desktop:
auto eth0
iface firewire0 inet static
address 192.168.2.2
netmask 255.255.255.0
broadcast 192.168.2.255
gateway 192.168.2.1

I don’t believe 25k Bitcoins were ever stolen

Thursday, June 16th, 2011

According to this thread on the Bitcoin forums, some dude had is computer “hacked” and they stole his wallet.dat, which is the file Bitcoin uses to store the private keys of the transactions, ie, the coins.

Except I don’t believe it actually happened.

As far as I can tell, the user transferred 25,000 coins to another one of his addresses and is using this to intentionally depress the buying volume (by injecting irrational fear into the market) so Bitcoin prices will go down so he can buy more at “fire sale” prices.

If this was Wall Street, that would be fraud and insider trading.

6 years

Sunday, November 21st, 2010

And I only wrote 6 things last year. Meh.

New Bitcoin miner project

Saturday, November 6th, 2010

I’ve written a GPU miner in Java and OpenCL for Bitcoin so you can mine several times faster than you would on your CPU. See the Bitcoin forum post here. I licensed it under the GPLv3.