Well, referencing the old setup, it was time to change locations which included a new router, gotten from German Telekom. You may figure, that many people look for repeaters extending their range, but not that many speak of client bridge routers. Even more, they reduce the router to a vdsl modem and put their very own – though for the Entertain package you’ll require various vlan tagging which may be broken then. So, my goal is still to add clients in the flat and do not use any cables (and no powerplugs either).
Luckily, the Speedport W921V provides the 2,5 and 5Ghz bands too, so I will be re-using the 5Ghz one for adding the client bridge like before. The only slight change in this regard is the ssid and the wpa key. The speedport supports WPA2 Personal plus TKIP as well as AES, so perfectly fine. If there are connection issues, keep in mind that the 5Ghz band got a lower range than the 2,4Ghz.
So, no need to buy the Telekom bridge combinations, but use an old working router with dd-wrt 🙂
Newest Samba from Debian Squeeze introduces a change on the way symlinks are handled/followed.
On previous Samba versions, you had to just define this in the [global] section of your smb.conf
unix extensions = No
follow symlinks = Yes
wide links = Yes
Right now, this has been split up into the share sections so that you need to allow symlink following by share.
unix extensions = No
comment = share XY
path = /path/to/share/XY
follow symlinks = Yes
wide links = Yes
After a reload, everything’s fine again.
Firefox currently offers the possibility to automatically add ‘www’ as URL prefix – so called ‘URL guessing feature’. Regarding the different behavior on DNS resolving (www vs @ zone record), this is rather annoying.
To turn that off, open a new tab and type about:config and search for browser.fixup.alternate.enabled. Doubleclick it to disable it and close the tab.
Following up to this thread I got lazy pasting those commands by hand.
So I finally wrote another Perl script doing all the demux-encode-mux stuff alone, also taking all sub directories, parsing for DTS encoded tracks within the mkv’s. It also creates a new output file with a fine AC3 track, and removes the old file with the DTS track. Note: This currently works only with single audio tracks, and ignores non-DTS files. And it is being written for directory usage, meaning one working dir and sub dirs with mkvs.
The script has several dependencies on used software, as there are
Resolve them like this:
# apt-get install mkvtoolnix mkvtoolnix-gui libdca0 libdca-utils cmake
# cd /usr/src; wget wget http://downloads.sourceforge.net/project/aften/aften/0.0.8/aften-0.0.8.tar.bz2; tar xvjf aften-0.0.8.tar.bz2
# cd aften-0.0.8; mkdir default; cd default
# cmake .. -DCMAKE_INSTALL_PREFIX:STRING="/usr"; make && make install
Current script can be found here at pastebin 🙂
In order to get DLNA back to work through a client bridged setup, simply add 1900 and 8200 to “NAT/QoS” -> “Portforwarding” and add your client IP address, mapping 1900 -> IP:1900 and 8200 -> IP:8200
So the DLNA client in the other subnet believes that the router is hosting the DNLA server and everything is fine again 🙂
Currently, all Linksys/Cisco WRT routers ship with their basic firmware. Doing something else than AP mode isn’t possible by default. Also it’s rather limited on system information and extended setup. In this specific case, I wanted to create a client bridge (WRT320N) onto the primary router (WRT610N).
Both support dual band (2,4 and 5 GHz) and the main target was to use the 5 GHz band in order to allow others use 2,4Ghz for them alone (300MBit/s each on draft N). Currently, the WRT610N runs with basic firmware and handles main internet access. In order to create a client bridge with wrt320n, I needed to update the firmware.
From what I have read on the DD-WRT Wiki, the WRT320N series is a bit tricky to install. But on a fresh router it is not that difficult:
* forget the wiki instructions, follow those and lookup 320n in router’s database
* make sure you’ll get v24-k26 (not the presp2)
* download dd-wrt.v24-13493_NEWD-2_K2.6_mini_wrt320n.bin (with “_wrt320n” suffix) and dd-wrt.v24-13493_NEWD-2_K2.6_mini.bin
* take the router on a pc on a seperated subnet, login to 192.168.1.1 with defaults
* reset to factory defaults, reboot, login again and go to the firmware upgrade page (Administration – Firmware Upgrade)
* chose the file with the “_wrt320n” suffix (this has the headers for first time flashing of dd-wrt)
* wait several minutes until upgrade and reboot is complete. the new dd-wrt interface will demand setting new admin credentials.
* check the firmware build and go to the firmware upgrade section again, now chosing the firmware with the “_mini” suffix. Do the same stuff again and login then.
Now having the firmware flashed, the main task will be to change the router into a client bridged version of WRT320N. I am following these instructions, while adapting several of them.
* assign your pc a static ip like 192.168.1.9
* go to 192.168.1.1 and login
* go FIRST to “wireless” -> “wireless security” and enter the security type and key that matches your primary router (WPA2 Personal, TKIP+AES, passphrase)
* hit SAVE, APPLY
* go to “setup” and check that the DHCP-Server is enabled if you want that (changing settings for wireless mode might accidently disabled this!)
* go to “wireless” -> “basic settings” and change the wireless mode to “Client Bridge”
* “channel” should be kept to “auto”. “channel width” should match the primary router on the specified band (in this case 5GHz). All these settings will disappear if you save into client bridged mode!!!
* “wireless network mode” is the tricky part – if you want the router using the 5 GHz band and channels, set this to “NA-Only” – tip here
* set the “wireless network name” to exactly the same as your primary router, in this case the secondary band.
* set “ack timing” to 0 unless you have a long distance (>300 meter) link
* hit SAVE at the bottom. then hit APPLY and check that all settings have been applied properly
* go to “setup” -> “basic setup” and enter a router Local IP address of 192.168.1.2. leave subnet mask at 255.255.255.0
* add the gateway with the primary router ip address (of WRT610N).
* leave Local DNS blank
* change timezone and DST
* hit apply
* set your browser to 192.168.1.2 and login
* go to “security” -> “firewall”. Below “Block Wan Requests”, uncheck everything but “Filter Multicast” (Leave Filter multicast checked).
* hit SAVE
* disable SPI firewall
* hit APPLY
* go to “setup” -> “advanced routing” and change the operating mode from “gateway” to router. hit APPLY.
* change your pc IP address back to DHCP and ping an external Url.