YP2 is not looking up the correct IP address (Cannot see your station/computer)

[mavmike]

Hi, does anyone know how to fix the YP2 to look up the correct station IP?
It's looking in the wrong place right now, but the port is correct.
Port forwarding is not a solution, that would only allow one person on the machine to use that port. Example, if you want 2 people to both use port 8000 on different IPs then port forwarding is not possible.

E msg:[YP2] Connection attempt failed. YP2 error code is 480 (Cannot see your station/computer (URL: http://184.154.185.162:8600) from the Internet, disable Internet Sharing/NAT/firewall/ISP cache.)

The IP of 184.154.185.162 is incorrect, I have the station running at 184.154.185.170
I msg:[SRC 184.154.185.170:39081 sid=1] SHOUTcast 1 source connection.

sc_serv.conf:
srcip=184.154.185.170
dstip=184.154.185.170

Yet, YP2 continues to look for http://184.154.185.162:8600 instead of the correct location at http://184.154.185.170:8600

How do you fix this YP2 lookup IP?

I should also mention that 184.154.185.162 is the main machine's IP. I did not tell shoutcast to use this main IP anywhere.

[DrO]

see first point at http://forums.winamp.com/showthread.php?p=2790357#known

-daz

[mavmike]

DrO, just to confirm I read that and it basically says there is no solution right now.
Is that correct? I have to wait until they release the fix in a new update?

[DrO]

you are correct.

unfortunately it requires changes on both ends to be able to get it to work correctly along with a number of other changes in the YP+v2 DNAS handling which were missing for some reason that i've just about finished adding in but with other things going on it's not been completed and fully tested yet.

so to answer the next question that i'd expect to see, there is no eta other than when it's done.

-daz

[eoRadio]

I am experiencing this same issue as I have a firewall between my servers and the public. I realize that this is fixed for the new release, however the post indicates that this is known issue since at least 07/31/2011, which is well over a year ago.

Is there any update as to when this will be released to the public, or where we can get a dev build to test out? I would love to add shoutcast to my streaming but it's not workable as is.

Thank you,



Just as a quick overview of my config and issue in the event that it helps clarify any questions.

Firewall to the public (Interfaces xxx.xxx.xxx.130 - xxx.xxx.xxx.137)
Shoutcast server (behind firewall) - 10.0.0.20

DNAT Rule -
* DNS A Record directs URL requests to xxx.xxx.xxx.136)
* Shoutcast Traffic (Ports 8000-8004) on xxx.xxx.xxx.136 directs to 10.0.0.20

This allows me to connect an external source to my shoutcast server and works correctly.

The problem is that I get this error, looking at the root interface IP:

msg:[YP2] Connection attempt failed. YP2 error code is 480 (Cannot see your station/computer (URL: http://xxx.xxx.xxx.130:8000/stream/1/) from the Internet, disable Internet Sharing/NAT/firewall/ISP cache.)

This occurs EVEN if I use a SNAT and ensure that shoutcast traffic from 10.0.0.20 is forced to use interface xxx.xxx.xxx.136 when leaving the server.

[ThiefMaster]

@eoRadio: How did you configure the rule to change the source IP? You cannot restrict it by dest ip since there are multiple ips involved

[eoRadio]

I am changing the source IP through the firewall, upon with all Public IP addresses reside. In our network ALL servers (including the shoutcast server) use private IP addresses behind the firewall.

So when traffic enters OR leaves through the firewall we can set/get the IP address and Port of the traffic and redirect as needed.

with the destIP value i've tried to set it by domain (e.g. shoutcast.domain.com) or by IP (xxx.xxx.xx.136) - neither of which seem to have any effect as all YP lookups continue to try xxx.xxx.xx.130.

[DrO]

the v2 DNAS isn't sending destip to the YP properly so even if you change things on your side and with the YP2 handling having been fixed (as that also didn't help), unless you have a newer DNAS no matter what you do it won't work.

there is no eta other than when it's done.

-daz

[eoRadio]

@DrO - I realized from your other postings that you had no ETA other than when it's done, as you had posted last year and earlier this year. However, I wanted to follow up now however to see if you had a better idea now than you did then, perhaps not from the sound of things.

Is it possible to get a dev/test build of whats in development to test against, or perhaps there is an alternative shoutcast server option that we might be able to try?

Just looking for possibilities/options here.

Thank you

[DrO]

i've given the only answer i have on the matter (which i'm sure is not going to be liked but i'm not going to go into details / specifics as doing so previously has caused me more issues and really i don't have to explain internal reasons).

i only give out dev/test builds for new issues not ones that i know have been confirmed as fixed (can thank the people who ruined that process for me no longer being freer in doing that). so as said above the only fix is to have a new dnas and that is not available.

and before anyone says, i know this is putting people off using v2 but my hands are tied.

-daz

[eoRadio]

No worries, I get it. I've been in tech for over 14 years and I know how some people can sour any attempts to be nice to them.

Well I'll just put Shoutcast on the shelf for now and look at FMS instead. If you're able to release the next build sooner than later and we haven't already standardized I'll try it out then and see if we add it.

Thank you