Archive for the ‘Tech topics’ Category

What I wish my N810 had

Wednesday, May 20th, 2009

There are some things that would make my Nokia N810 better or easier to use (for my purposes).

  1. Line-out. Apple got this right, there’s line-out on the iPods (and even then you need to buy the right adapter). I plug the N810 into an FM modulator wired inline into my car’s antenna; in order to get the audio loud enough, I have to turn the volume on the N810 and on the car radio way up. There’s an audible background noise from all this, and I need to remember to turn it down before I switch back to headphones (N810) or an FM station (radio).

    I could use a USB audio widget, plugged through a converter to get down to the N810’s mini connector. But the USB connector on the N810 is only accessible if the easel-legs are open, which isn’t exactly car-friendly. Plus I might have to fool around with kernel modules. I haven’t tried any of this yet.

  2. Working GPS. ‘nuf said.
  3. gphoto. When I’m on vacation I’d like to be able to pull pictures off my camera, and view them on the N810. I could also push them to my home server next time I found a network (WiFi or 3G, using my phone). To do this I need gphoto, or something like it. This is probably a simple matter of setting up the cross-dev environment and porting it, I haven’t gotten around to trying.
  4. fsck in the boot menu. I should ask fanoush, or hack it together myself.
  5. Automated podcast downloads. It would be nice if gpodder would do this for me, instead of having to be manually triggered. It’s on their roadmap.
  6. Polishing: I wish the keyboard were a little better, that it had a Tab key, that I didn’t need to use the Fn key to get to “/” (come on, if I’m typing it’s likely to be URLs or filenames!), that the directional-button-thing were on the front of the tablet and not buried on the keyboard. None of these are killers.

To reiterate, I’m happy and I use it alot. In fact the screen protector has gotten scarred up and I may need to replace it – I’ve never had to do that before. This is just the “room for improvement” category.

How to Set Up a Nokia N810

Friday, March 20th, 2009

Herewith my hard-won knowledge on setting up a Nokia N810. You want to boot off the removable memory card – partly because it’s replaceable (when the flash memory wears out), and partly because it’s removeable (for backups, and when you need to reflash it).

  1. Learn how to reflash the tablet. I do this from my Linux box.
  2. Get root. My favorite way to do this is by installing OpenSSH, which sets the root password as part of its install process. Then you can open an X Terminal and ssh root@localhost.
  3. Prepare the removeable card. Mine is an 8GB SDHC micro card (with the mini adapter), formatted as 1GB for the bootable ext2 partition, and the rest as VFAT for N810 data. This is also a good time to practice with fsck on the two partitions, and to define your backup strategy (I use tar).
  4. Set up to boot from the removeable card. Download and follow instructions from fanoush’s site.
  5. Shutdown the tablet, and back up the removeable card.
  6. Put the card back in. boot up, and start installing and configuring software.

I use these apps daily:

  1. gpodder
  2. claws-mail
  3. mediabox
  4. maemo-mapper
  5. omweather on the desktop
  6. openssh

I also have iodine installed, but use it less often. I gave myself sudo access as well. Beware the published recipes for sudo access – believe it or not, the ones that were current 6 months not only didn’t worked, they soft-bricked the tablet so I would have to reflash, or at least reboot to the internal card (see why we did that?) and undo my changes.

6 months with the Nokia N810 tablet

Thursday, March 19th, 2009

Six months ago, when I was between jobs, I bought myself a Nokia N810 tablet. I’ve had time to get used to it – it no longer “smells new” – and I still like it. It took me awhile to get the software setup just right, I’ll cover that in a separate post.

There has been an iPhone in the house for several months now, but I’m still happy with the N810. In fact, I use it several times a day. I use it for:

music and podcasts: this is the real winner, I’ve basically stopped using my iPod. While the iPod interface is easier to use, especially without looking at it, the WiFi connectivity of the tablet makes it much easier to get the content on. iPods are tethered to a Mac (for iTunes) or some other computer, the tablet isn’t.

I use gpodder for podcasts, and mediabox for my music. I used Canola2 for months, but although it’s prettier and integrates podcasts and music together, it’s slow, and doesn’t do a great job with the podcasts.

email and blog reading: it’s smaller than a laptop, but quite usable for reading and for short-to-medium replies. I couldn’t live without the slide-out keyboard. I use claws-mail with its RSS and HTML plugins.

GPS: the open source maemo-mapper app is fantastic, but there’s some sort of impedance mismatch with the N810 GPS, and it takes forever to get synced up. (The system GPS software seems to get a location long before maemo-mapper.) So this is the weakest app, and it doesn’t get much use.

Web surfing: The small screen starts to become an issue here, but for many web sites it’s OK. I use the builtin browser.

ssh: for the obvious reasons.

Connectivity: I already mentioned the WiFi connectivity. I also have it paired to my phone, so I can leach off the AT&T 3G data networking. I also have iodine installed, although it hasn’t been very successful when travelling. With the phone pairing, I don’t really need it.

Multi-homing Linux

Thursday, October 20th, 2005

I’m running multi-homed while I exercise FiOS and make sure everything works. It took a few tricks to make everything work. My Linux box actually has three Ethernet NICs:

  • eth0, the onboard 100M NIC, for FiOS
  • eth1, a 10M NIC, for RCN
  • eth2, a 1G NIC, for the internal LAN

The first thing to do is adjust your firewall. I run iptables, with very few dependencies on the external IP address. I did have to add some rules to the FORWARD and INPUT chains for the FiOS NIC – but only for network 192.168.0.0/16, because of the d-link firewalling. Things will get more interesting if/when the d-link comes out of the network, because I’ve seen VZ allocate IP addresses from both net 70 and net 71. I’ll probably change things around so the network-specific rules get changed dynamically, as the IP address changes.

The next thing you have to do is set up per-interface route tables. If you don’t do this then only one external IP will actually work, because a packet may be received on NIC A, but its reply be routed out NIC B. This especially doesn’t work in a NATted environment! A good reference to get you started is an article in Linux Journal.

The third thing is to make sure that your various services don’t rely on specific IP addresses. DNS (BIND) and Apache configuration are good places for this dependency to sneak in. I’ve been around this block before, so I didn’t have those problems. I did get bitten by my CUPS configuration, because it “knew” that eth1 was the LAN interface – when the LAN moved to eth2, CUPSd was broadcasting its notifications on the wrong network.

Email is another challenge. I’m running my outbound email server (postfix) bound to the RCN IP address for the time being. (The dynamic Verizon IP addresses are running into SPAM filters around the network.) I have worked out how to feed email from my domain into Verizon’s servers. You need to a) turn on SMTP AUTH, and b) pass your Verizon username & password in the SMTP AUTH transaction. In postfix this looks like:

  1. /etc/postfix/main.cf

    smtp_sasl_auth_enable = yes
    smtp_sasl_security_options =
    smtp_sasl_password_maps = hash:/etc/postfix/saslpass

  2. /etc/postfix/saslpass

    # remote user:password
    outgoing.verizon.net user@verizon.net:password

  3. create /etc/postfix/saslpass.db with:

    % sudo postmap /etc/postfix/saslpass

  4. Last thing: I noted above that my outgoing email is all coming off the RCN IP address. This broke the connection to amavis, the Virus/Spam scanner. Previously amavis was set up to only accept connections from the loopback (127.0.0.1) IP address, now it needs to accept the RCN IP address as well:

    in /etc/amavisd.conf

    @inet_acl = qw(207.172.210.134 127.0.0.1 [::1]);

FiOS, d-link, and firewalling

Wednesday, October 19th, 2005

I already mentioned that I want access to my Linux server from the network. Verizon’s d-link – still in my network, but not forever – is set up to prevent this. Verizon assumes you have a standard PC, so they preconfigure the d-link to firewall any incoming connections.

That’s not my situation, I have a Linux server with extensive firewalling and more than a few services running on it. I want all the network traffic coming to MY firewall, please, not Verizon’s.

The solution – partial as usual – is the “DMZ” setting. In the d-link configuration you can set a “DMZ” host, which gets most of the traffic the d-link sees forwarded to it. Specifically it seems to forward TCP and UDP traffic, which is a big step. But it’s still intercepting ICMP – so any Ping or traceroute traffic goes to d-link, not Linux. Yet another reason to disable the d-link.