Slimserver and 54G

As everyone know pulling cables around the house for networking is a blast (NOT!). I therefor got my self some wireless equipment again (used to have 11b), to power my SliMP3 (old version of Slimserver - <a href="www.slimdevices.com">www.slimdevices.com</a>) - which is not wireless.



I got a Linksys WAP54G and a WET54G, not nice looking but I was hoping that they where working... NOT!!!!!!!!



My SliMP3 was choking; strange characteres on the display drop out's etc. the whole storie - I spend 6 hours yesterday troubleshooting the problem, and some time today. And it turned out that I had to change the networking parameters on the Slimserver:



Maximum number of TCP sockets to read per pass: 20

Maximum number of TCP sockets to write per pass: 20

Maximum number of simultaneous TCP connections to accept: 30

Maximum number of bytes of audio data to send to player in a UDP packet (SLIMP3 only): 1400



I think that the issue is solved with the last paramter. First thing is that I use WEP which adds some overhead to the package (UDP/IP frame), and there is an issue with UDP and fragmenttation, like in <i>IT DOES NOT WORK WONDERFULLY WELL</i>.



Now I can listen to music again......



Oh, if you do as I do rip all your CD's get a slimdevice. Also another thing; get a <a href="http://www.c-note.dk/blog/exit.php?url_id=63&amp;entry_id=23" title="http://www.plextor.com" onmouseover="window.status='http://www.plextor.com';return true;" onmouseout="window.status='';return true;">Plextor</a> drive they rock, and they do not have problems with the CD copy protection.

Comments

Post a Comment

Popular posts from this blog

Kviknet and IPv6

Image
 I decided to switch ISP, mainly due to Hiper (Danish) was using a VLAN for their connection which made pfSense and my APU3 board require a reboot everytime I changed anything. Kviknet has a good reputation (wonder why) in Denmark, they are not cheap and they have the same opening hours as everyone else - meaning until 16:30 and closed during weekends. I sometimes wonder how companies who need 24/7 internet get on with that ... well it's Denmark. Kviknet has an interesting way to do IPv6, your router get and SLAAC assigned IPv6 address on the public side (wan) and you get a ::/48 network from Kviknet to use on your lan.  To some degree it does make sense, you can then configure your lan with static addresses as you see fit, and for dynamic assignment you use RA stateless dhcp *) ... which works for everything.  (I need to get my piHole configured with an static IPv6 so that I can use that ...). pfSense is a pain, I do like it, but they are light years behind their main competitor
Read more

Apple AirPort Express and Digital Jitter..

I'm doing something which I can't really afford, but doing it anyway ... I'm upgrading my Stereo ... I like music, and  believe it should be played at the highest affordable quality. So after getting a new Stereo Amp (Creek Evolution 50A), I got a new Phono Amp. and then started looking for a DAC ... and after reading I do not know how many posts I decided to get an S.M.S.L M8 (from  Amazon  fro €249.99), not too expensive and according to what I can read very good. So I got it hooked it up to my amp, connected my Notebook (Macbook Air 11" / 2011) using USB ... sounded nice, then my Macbook Pro Retina with digital (fiber) in some way better than USB, slightly more air and openness. Then decided to use my old Apple Airport Express ( MB321LL/A  - 802.11n version 1) using it's digital output (I don't like the build in DAC - it's a bit too dark for me), and this is where I started having doubts about my buy. There was drop out, all the time. Right I changed, to
Read more

MacOS: Disable start of xterm when starting XQuartz

 There are many good references to how to disable the start of xterm when starting XQuartz on MacOS. But as some of us are installing it using (home)brew the preferences file is not the one many are pointing to. Using the (home)brew version of XQuartz the preferences file is org.xquartz.X11.plist, and to disable xterm from auto starting do the forllowing; Start a terminal and type the following: $ defaults write org.xquartz.X11 app_to_run $(which false) To see the result do: $ defaults read org.xquartz.X11 {     SUHasLaunchedBefore = 1;     SULastCheckTime = "2021-04-22 11:33:05 AM +0000";     "app_to_run" = "/usr/bin/false";     "cache_fonts" = 1;     depth = "-1";     "done_xinit_check" = 1;     "enable_fake_buttons" = 0;     "enable_iglx" = 0;     "no_auth" = 0;     "nolisten_tcp" = 1; } Now (re-)start XQuartz and xterm should no longer autostart.
Read more