I am not able to tune in a URL, or use any other Internet Radio service available through the Slimserver interface at port 9000. I am able however to switch my SB3 to the Squeeze Network and stream internet radio that way without any difficulty.
When I attempt to "Tune In" a URL using the SS interface, the log.txt error message I get is that SS could not resolve the IP address. For example, if I attempt to select "Slim Picks" the error message I get is that the IP address for www.slimdevices.com could not be resolved. If I open an xterm window, I can ping www.slimdevices.com without any problem - it was resolved. I have a default gateway and dns. I can ping any pingable domain name on the web, except SS itself cannot get anything resolved. My setup: SlimCD - HDD install, Slimserver (6.5.2 - 9471 - Debian) My internet connection is via ppp (adapter is ppp0) using an EvDO cellphone modem USB device. Except for this one issue, this setup works well for me. My Linux box is sharing this internet connection with my local 192.168.0.X network on eth0. This has been working quite transparently. Machines on my local network have complete access to the internet. Here is output of having recently run ifconfig to see how the adapters are configured: [EMAIL PROTECTED]:/home/dsl# ifconfig eth0 Link encap:Ethernet HWaddr 44:4D:50:E1:C1:D1 inet addr:192.168.0.4 Bcast:192.168.0.255 Mask: 255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:9393107 errors:0 dropped:0 overruns:0 frame:0 TX packets:12138836 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:3186134607 (2.9 GiB) TX bytes:2946587741 (2.7 GiB) Interrupt:11 Base address:0xde00 lo Link encap:Local Loopback inet addr: 127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:54062 errors:0 dropped:0 overruns:0 frame:0 TX packets:54062 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:12169252 (11.6 MiB) TX bytes:12169252 (11.6 MiB) ppp0 Link encap:Point-Point Protocol inet addr:X.X.X.X P-t-P:Y.Y.Y.Y Mask:255.255.255.255 UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1 RX packets:97271 errors:0 dropped:0 overruns:0 frame:0 TX packets:85358 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:3 RX bytes:106358836 (101.4 MiB) TX bytes:6713889 (6.4 MiB) Where X.X.X.X and Y.Y.Y.Y are, or appear to be, routable addresses on the internet (I blacked them out.) Note: my default route is Y.Y.Y.Y. I see this using the route command. This route exists for the life of the ppp connection. I note something strange: Slimserver starts up when the system boots, but the ppp connection does not begin until I start it manually later. So, SS starts BEFORE the ppp connection exists. Nevertheless, in the "Server Settings" browser display, SS is reporting that the Server IP address is X.X.X.X! That makes no sense! Why is it not 192.168.0.4, which is the eth0 address of the machine??? The ppp adapter did not even exist when Slimserver had started running, so Slimserver changed it's IP address from eth0 to ppp0 while it was active - is that a bug? I verified also that my SB3 sees that the SS it is connected to has an IP address of X.X.X.X. It does not seem to care and works fine, but it looks very weird. So, can I force Slimserver to use the original 192.168.0.X nonroutable address, and NOT switch to the routable address after the ppp connection is running? Secondly, does anybody have any idea as to why I cannot tune into a URL? I presume the above issue might related:) I was thinking it could be a Linux firewall issue, despite the fact that "ping" works fine (the problem so far is restricted to SS.) So, here is the dump of "iptables --list": [EMAIL PROTECTED]:/home/dsl# iptables --list Chain INPUT (policy DROP) target prot opt source destination ACCEPT all -- anywhere anywhere state RELATED,ESTABLISHED ACCEPT all -- 192.168.0.0/24 anywhere state NEW ACCEPT udp -- anywhere anywhere state NEW udp dpt:bootps ACCEPT all -- anywhere anywhere TRUSTED all -- anywhere anywhere state NEW Chain FORWARD (policy DROP) target prot opt source destination ACCEPT all -- anywhere anywhere state RELATED,ESTABLISHED ACCEPT all -- 192.168.0.0/24 anywhere state NEW TRUSTED all -- anywhere anywhere state NEW Chain OUTPUT (policy ACCEPT) target prot opt source destination ACCEPT icmp -- anywhere 192.168.0.0/24 DROP icmp -- anywhere anywhere state INVALID Chain TRUSTED (2 references) target prot opt source destination DROP all -- anywhere anywhere [EMAIL PROTECTED]:/home/dsl# I notice that X.X.X.X does not appear in here, and maybe it should? Are packets originating with SS, appearing to come from X.X.X.X, which is NOT in the 192.168.0.X network, getting dropped before making it out? -Ron -- Ron F. *Squeezebox setup:* wireless SB3 -> CI Audio VDA.2 DAC + VAC.1 PSU *Main rig:* NAD 7600 + NAD 2600A -> Phase Tech PC-6.5 speakers *Headphone rig:* Headroom Max -> Sennheiser 650s *Music Server:* Nano-ITX computer running SlimCD + 750 GByte HDD -> Netgear wireless router *Other stuff:* NAD C542 CDP, NAD 6300 Tape, Monster 5100 Power conditioner, Outlaw Audio cables ------------------------------------------------------------------------ Ron F.'s Profile: http://forums.slimdevices.com/member.php?userid=5616 View this thread: http://forums.slimdevices.com/showthread.php?t=36057 _______________________________________________ unix mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/unix
