View Full Version : Fairly advanced problem.. Possible Bug?
5th February 2006, 16:14
My setup is this:
Linux Server: the latest as of today
Dsp: the latest as of today
Winamp: the latest as of today
I have a working station here:
EDIT - I set up another .conf file here just to make sure...
My Server is always rollin, I never get a hiccup.
It resides on a dsl connection that is NOT fixed IP, thus I use no-ip.
My issue is with winamp and dsp... whenever my isp decides to change my address, all hell breaks loose.
The server makes it through the change alright, I have no-ip set up to update every five minutes, so my server bounces back fine. But the DSP goes through a constant cycle of not being able to reconnect, AND I have to force it to quit... ctrl+alt+delete.. if I restart it, it connects fine until the next IP change.
RECAP the problem: when my DSL router IP address changes... winamp/dsp plugin goes haywire and cannot reconnect...
Server running Fedora Core 4
my server heirarchy goes like this
DSL router dynamic ip>
>pppoe bridge to linksys>
>port forward to server at fixed ip>
>no-ip update client>
my shoutcast client
is on a machine running windows xp home behind a linksys router. fixed ip 192.168.1.5
Newest winamp lite and DSP
There are no firewalls, or other programs running at all on the client machine.
I have made an asx file to point to /listen.pls
is there a more effiecient way to make my stream more compatible to the majority of the public, I intend to place my station directly on my host page for my free internet HotSpots. Specifically I plan to re-direct anybody who uses my hotspot to a webpage that contains local links, advertising for local business, and a link to listen to a local radio station, I have sucessfully got the radio station re-broadcasted, but I want to make sure the people using my hot spots dont have to download anything... I have achieved similar success with mp3's using flash, but not streams. Any help would be appreciated... I know this topic has been covered ALOT on this site, and I have read through most of it... I appreciate any help I get and i will be a contributer here once I figure this out...
you see... I have only started to play with linux 3 days ago/ server has been up since :), and shoutcast two days ago... I learn very fast...
Thanks in advance
5th February 2006, 17:42
Just wondering if anyone has had anything similiar?
5th February 2006, 18:08
On the DSP > DNAS issue, if both are on the 192.x.x.x network, I assume you're using the 192.x.x.x address of the DNAS in the DSP config? If you do that, it should never disconnect regardless how many times your ISP changes your public IP...
5th February 2006, 20:43
No that is not the case I am on two completely different networks... My stations are both currently down, This happened since my first post today... very frustrating. Now I believe my server is down, I am waiting for no-ip to update... I suspect my ip has changed...
Thanks for the try though
6th February 2006, 12:06
After testing the rest of the weekend I am completely dumbfounded....
Here are the results... I thought my server went down, alas it did not it was a linksys router...bastards.
My server resides in a network, one of my stations, http://mysticradio.no-ip.info:7000/listen.pls runs on the same network but logs in from the web...I sent it to the web address, not local to log into the server.
My other station runs from my home network http://jasonsmix-no-ip.info:5000/listen.pls
Both stations go down after an amount of time, usually over 4 hours... I cant figure it out, I have read and read.
What really sucks is this tidbit... the DSP's simply do not reconnect correctly, All I have to do is shut down winamp, restart, and it works fine. Why wouldnt the dsp reconnect? I believe there is a bug or a specific reason that winamp cannot reconnect after a public IP change on the server side... It should be able to, as long as the named physical address and password do not change. I could really use some insight here. I cant keep a station up long enough for anybody to hear it!
BTW - Installing our first commercial hotspot today! I will be putting a tutorial online for the Mikrotik Router Board 512 and it's RouterOS...
6th February 2006, 16:28
The reason it does not reconnect is because the IP changed. Your DNS cache is holding the old IP. Winamp does only one lookup, it does not keep re-looking up the hostname/IP every time it reconnects. Thus restarting winamp forces another DNS lookup.
The fix? Get a static IP, or paid hosting. You are most likely breaching the user agreement for your broadband ISP by running servers on a dynamic IP.
6th February 2006, 21:04
So basically everyone that connects through a server on a dynamic ip using no-ip domain, is bust!, because the DSP is holding dns cache? I would think that might exclude allot of users who want to set up a station/server for limited use...
Is anyone who writes the DSP listening?
Is there a specific reason the dsp cannot upon reconnect refresh the dns cache as well?
The fact that I am using a server on my Dynamic ISP is a moot point. Why else would one need a fixed ip? save for remote access.
Either way that's my business, if I get to the point where I need a fixed IP for functional reasons (i.e. more bandwidth) I'll get one inevitably.
Please for the love of god and all things nullsoft and winamp, fix this issue... FREE is the key, if I wanted to spend a bunch of money I would be using a windows streaming solution on a windows server on couple of T1's, paying royalties to bmi, sesac, ascap, and all of the above. Unfortunately, I am using linux/fedora, winamp, shoutcast, on a business class dsl connection that gives me half the bandwidth for twice the cost on a dynamic IP trying to buck the system with a little service called no-ip, and I cant keep my station up for more than 4 hours, because a DSP plugin reconnecting doesnt refresh the DNS cache? wow. The worst part is that 90% of the tutorials recommend no-ip if you dont have a static IP.
Oh well, I got my first hotspot running today, and I am feeling pretty good about that...
I await a response from someone, if it cant be done, I can accept that.
Do any of the "other" DSP's refresh dns cache?
6th February 2006, 22:11
I guess the only people that can tell you for sure is will, benski or tag. I wouldnt think that the dsp would be caching dns lookups, more likely its your local resolver. Try typing "ipconfig /flushdns" into your command line on windows (assumed).
6th February 2006, 22:16
Okay. I guess you learn something new every day. Maybe without at least one static IP, you're screwed. I'm usually pretty good at coming up with answers, but this one has me stumped.
On the upside, 10 slots from a streamhost doesn't run much. Maybe it's worth it to just pay and get it over with. For example, 10 slots at 64k from my host is only $9/month.
I can't think of any other way at the moment. If I do, I'll post back.
6th February 2006, 22:47
Windows is caching the DNS entry, not shoutcast.
6th February 2006, 22:55
Thanks for the replies... I wouldnt think it would cache DNS either, however my testing on two different machines at two different networks through two different isp's seems pretty conclusive that the error is in the DSP... It seems more likely that the reconnect script isnt restablishing a connection but refreshing the current one.
I know of my available options regarding streaming slots, thank you, but I already HAVE a server running on business class DSL of which I pay alot of money for, they want another 20$ per month for fixed IP, After speaking with them it is perfectly fine to run a server..."it's your bandwidth, do with it what you will" it seems that a simple DSP fix should keep me and hopefuly alot of others very happy!!!
I still await an official reply which will only come from the people who wrote the DSP... I welcome all other suggestions... I cant be the only one with this issue!! Can I? I would love for someone to tell me I am doing something wrong...then I could fix it! besides getting a fixed IP.
Being able to broadcast a radio station with my current configuration at minimal cost, is precisely the reason I am using this software combo and no-ip.com. I dont want to pay any more money, hell I dont even know if it will work for my application...yet... I don't dare to make my links live until they are 100% stable...
I apologize if this is getting to be a nagging post to anyone who thinks that.
I am a beta tester and this is what I do...
6th February 2006, 23:01
forgive me...but why would restarting winamp fix the problem?
And if it is indeed windows on the remote dsp client... should I build a batch file to flush the windows dns cache?
I just dont see the relationship with windows I guess.
6th February 2006, 23:15
Originally posted by pointclicksave
I still await an official reply which will only come from the people who wrote the DSP...
will wrote the dsp :)
But yeah, he gave the code a quick lookover at my request but could find little more than it calling jnetlib to make the connection, jnetlib itself just doing a call to the operating systems resolver.
If you want to review the jnetlib sources, well, its oss, code is available here:
Originally posted by pointclicksave
I just dont see the relationship with windows I guess.
Its just part and parcel of network programming. The operating system has a network library/stack which programs interface with. Things crop up all the time with software that reference this, steve gibsons misfounded windows xp raw sockets debacle? winnuke? portscan? DNS is obviously one of those functions. Why is it cached? Well, usually it doesnt change that much. At least not historically. Try "ipconfig /displaydns" and see what windows has happily cached the dns for.
6th February 2006, 23:20
I figured, I was actually typing my message when he posted...:), Talk about foot in mouth... sorry will!
I am waiting for it to screw up again then I am going to build an automated dns flusher for windows via batch and scheduling agent.. maybe that all I need! Thanks again to all!...
6th February 2006, 23:26
I would be more than happy to supply a login for my server if Will or Craig would like to test it...
vBulletin® v3.8.6, Copyright ©2000-2013, Jelsoft Enterprises Ltd.