don't use "Inspect Element" to design filter rules

Never use your browsers Inspect Element to look at the HTML and expect it to be like this in the transmitted file!

I tried to use this to design a filter for Privoxy to remove a . The browser showed me the line as

But even

s///Usig

didn't remove any of the links. And I gave up.

Only after I was working at an other filter and using View Source to look a the HTM code I realised the difference. For Inspect Element the browser will use it's internal representation. And this results not only in the use of end tags, but also a different order of attributes.

A look at the actual source showed that the line in question actually looked like this

Now I was able to design the filter like this

s///Us

to remove the line.

NSLU2 downgrade from Debian to OpenWrt

Flashed openwrt-nslu2-squashfs.bin onto the NSLU2 over a Debian installation. After a reboot only the green Ethernet LED was on. A ping to the old IP address, 192.168.1.1 or 192.168.1.77 didn't work. Switching of the NSLU2 with the power button failed.

But what I noticed was that a ping to 192.168.1.1 produced no response but all other Destination Host Unreachable.

arp -an revealed for 192.168.1.1 the correct MAC address all other IP showed <incomplete>.

Unfortunately I couldn't find an upgrade story from Debian to OpenWrt on the internet. But I thought to remember that Debian used a different flash layout.

So I followed this description to erase the SysConf area and installed the Linksys Firmware.

As to be expected only the third attempt to enter the RedBoot worked. The first time the message to press ^C appeared, but no reaction. The ^C came to late. If correctly timed RedBoot > will appear.

After this the boot was successful and the installation of OpenWrt succeeded  without a problem.

samba mount without user account

It is not possible to mount a samba share without an user account on the server, even with the share set to public = yes. The reason and how to fix this is described here.

in short add/change smb.conf:

[global]

guest account = nobody
map to guest = bad user

[public]

comment = common downloads
browseable = no
path = /mnt/hd/location
public = yes
read only = yes

NFS server installation

My last NFS installation must have be nearly 10 years ago - was still using OS/2 on one machine.

On the server I installed nfs-kernel-server as I read about some problems with the user mode server. From the old day's I still remember the files used to configure the server.

• /etc/exports: /dir ip(rw)


• /etc/hosts.allow: ALL:ip


• /etc/hosts.deny: ALL:ALL

This didn't work. Access was denied. The access is controlled by the user and group ID. All users are created separately and not controlled by NIS or LDAP server. The quick solution is to map all access to the local user with anonuid and anongid.

Still not able to connect from the Mac. The user access is granted by the server. The Mac connects with a port number greater than 1024. Therefore insecure is needed.

Help was the nfs howto and this thread about mounting nfs on Mac.

TODO: look into the command exportfs to manipulate the NFS exported file systems.

network file system to use

Two thinks happened at the same time. I had again problems with my Samba/SMB setup and found and old article about OpenAFS.

AFS still sounds good but most of the advantages are not important on a home network. Also all the good features are now part of NFSv4. As it is still not widely used it probably is more difficult to find a already existing solution on the net. This is also true for all the other protocols found on wikipedia.

Therefore it still comes down to SMB or NFS for me. As the new file server I build will use ZFS and run on OpenSolaris NFS might be the way to go. At least I will give it a try and see if I have less problems or run into other disadvantages compared to my use of SMB.