DSL Config For Shoutcast on Cisco 675

Hello!
I have Shoutcast all set up - it's working fine. Except that no one can get to my station. The reason is I'm running DSL on a Cisco 675 router. I assume I must config my router to allow users to listen. I know how to change NAT params on the router. So! Does anyone know exactly what NAT params I need to enter into my 675?

Thanks!

-PJ

PJ,

You are running NAT... Two questions. Do you have a dedicated IP address? And second, are your running firewall software on the router? I do not run a Shoutcast Server yet, but am monitoring this forum to learn about problems before setting a server up. That said, I do know quite a bit about routers. In most cases we find that if you need to run an application like this, you will need to setup a "static" NAT entry. The problem (typically)is that there needs to be a direct line of IP based communication between the receiving Host and the Server. If NAT is running in standard form on your router, then it actually has the valid IP address and not your server. When your server replies, the reply is sent with the correct IP address of the router, but the receiving Host cannot effectively see beyond the translation at the router and therefore never truely establishes communication with the Server. With this scenario, the receiving Host cannot receive the audio stream, because the actual Server is unknown. NAT running on the router translates from the WAN port to the LAN port, not from Host to Host.

I suspect you are not running a valid (legal) IP address at the Server since you are running NAT on the router. You should be able to get around this if you purchase an additional (legal) IP address from your ISP. Leave the one assigned to the router the way it is, then setup a static NAT from the new IP address to your Server's IP address.

Hope this helps. Please post reply as I am curious to know how it turns out!

Regards,

Gene

Hey Gene!

That sounds logical what you said. Although now I am wondering from all the hoopla I've been reading that the problem could be on the Shoutcast directory server. People are reporting the same errors that I'm getting..

<06/01/00@07:56:37> [SHOUTcast] DNAS/win32 v1.6.0rc2 (May 16 2000) starting up...
<06/01/00@07:56:37> [main] loaded config from C:\WINDOWS\DESKTOP\SC_SERV.ini
<06/01/00@07:56:37> [main] initializing (usermax:32 portbase:8000)...
<06/01/00@07:56:37> [main] No ban file found (sc_serv.ban)
<06/01/00@07:56:37> [main] No rip file found (sc_serv.rip)
<06/01/00@07:56:37> [main] opening source socket
<06/01/00@07:56:37> [main] source thread starting
<06/01/00@07:56:37> [main] opening client socket
<06/01/00@07:56:37> [main] Client Stream thread [0] starting
<06/01/00@07:56:37> [main] client main thread starting
<06/01/00@07:56:37> [source] listening for connection on port 8001
<06/01/00@07:56:47> [source] connected from 127.0.0.1
<06/01/00@07:56:47> [http:127.0.0.1] REQ:"/index.html" (ShoutcastDSP (Mozilla Compatible))
<06/01/00@07:56:47> [source] icy-name:PJs Mostly Guitar Music ; icy-genre:Rock
<06/01/00@07:56:47> [source] icy-pub:1 ; icy-br:48 ; icy-url:http://www.pjspage.com
<06/01/00@07:56:47> [source] icy-irc:%23shoutcast ; icy-icq:0 ; icy-aim:N%2FA
<06/01/00@07:56:50> [http:127.0.0.1] REQ:"/admin.cgi" (Mozilla)
<06/01/00@07:56:58> [yp_add] yp.shoutcast.com gave error (nak)
<06/01/00@07:56:58> [yp_add] yp.shoutcast.com gave extended error (Connection timed out)
<06/01/00@07:57:09> [yp_add] yp.shoutcast.com gave error (nak)
<06/01/00@07:57:09> [yp_add] yp.shoutcast.com gave extended error (Connection timed out)
<06/01/00@07:57:17> [http:127.0.0.1] REQ:"/index.html" (ShoutcastDSP (Mozilla Compatible))
<06/01/00@07:57:20> [yp_add] yp.shoutcast.com gave error (nak)
<06/01/00@07:57:20> [yp_add] yp.shoutcast.com gave extended error (Connection timed out)
<06/01/00@07:57:27> [main] shutting down via UI.
<06/01/00@07:57:27> [main] connecting to yp.shoutcast.com to remove myself before I die...

Notice it connects and runs just fine - but the "extended error connection times out" tells me it's making it's way to the Shoutcast directory server. But they* aren't accepting it.. Does that sound right to you Gene?

Thanks,

PJ

I think it's on thier end Gene. I posted a reply in here but I don't see it.

A lot of people are reporting the same errors that I'm getting. So I'm thinking now that the directory server may be experiencing some sort of malfunction.

[peppert]

Again, PJ is confused. There's no issue here.

The issue is that your router isn't forwarding the request on to your internal machine (as is the nature of NAT). You need to configure the Cisco to forward the port, as per the instructions in the FAQ.

Again, if you see *any* entries in the SHOUTcast directory, then things are working on our end.

So what your saying is my 675 is not set up right, thats it?

I added NAT entries like:

set nat entry add 10.1.1.0 8000 209.98.250.32 8000 tcp

set nat entry add 10.1.1.0 8001 209.98.250.32
8001 tcp

Where 10.1.1.0 id my inside IP and 209.98.250.32 is my outside IP.

So your saying thats wrong huh?

Then what are* the entries?

<BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by peppert:
Again, PJ is confused. There's no issue here.

The issue is that your router isn't forwarding the request on to your internal machine (as is the nature of NAT). You need to configure the Cisco to forward the port, as per the instructions in the FAQ.

Again, if you see *any* entries in the SHOUTcast directory, then things are working on our end.<HR></BLOCKQUOTE>

I called my ISP and we set the router to ALL ports, a wildcard if you will. And still error connecting to yp.shoutcast.com

I hooked up my old 56k modem and it did connect to shoutcast. So the router is to blame.

I'm going to try and hack some NAT params in if I have any luck I will surely post them here.

Thanks for bearing with me.

I have been having the same problem too and i have no idea how i can make it to work, i hope u will post the solution soon, when u get it. Thanks..

What version of cbos is installed on your 675 you should upgrade to 2.3.0 they have made some iprovements made to NAT. Thid may help but I'm not sure. The disk image and docs can be dowloaded here http://adsl.contamination.org/downloads.html
Your dsl service provider probably doesn't offer technical support for any thing newer than 2.2.0

Thats a good idea - but I'm not sure that updating the CBOS is going instantly solve this problem.

A friend of mine gave me a book called Cisco TCP/IP to read. I tell ya that book reads like a science tech manual.

I feel like I'm the only one working on this NAT problem.. Isin't anyone at Winamp or Shoutcast have an answer for this?

I called Cisco and US West for information on how to map port 8000 to my internal PC - and neither of those two companies had an answer for me. Can you believe this? Not even the damn manufacturer, Cisco - could give me an answer.. US West, they had no answer either. All they gave we was a web site http://www.users.uswest.net/~scottz/

I can't believe the lack of help - even from the people that built this damn router, what a joke!

So far I seem to be the only cat in town working on this problem and trying to dig up some damn answers. I've gone as far as I can go here people. I've run out of ideas now. If they manufacturer can't even provide an answer, who can?

This blows MAJOR puke chunks people!

[pj]

Cisco did take on the problem. They said they would contact me when the have something. And my ISP? Those bozo's have no clue as to what I'm talking about. http://www.visi.com is my ISP. Those dorks have no clue.

[peppert]

um. dunno. i don't have any 675s, or dsl running under a 675 out here in california (they use something else out here)

back when i used to have uswest, i used a 675 once. your config line looks pretty correct to me. i *WOULD STRONGLY* recommend upgrading the CBOS, but it'll likely wipe your config in the process so be careful.

can you send me the syntax of the set nat command? (set nat ? will display it)

feel free to email me on this: tom@shoutcast.com

<BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by pj:
So what your saying is my 675 is not set up right, thats it?

I added NAT entries like:

set nat entry add 10.1.1.0 8000 209.98.250.32 8000 tcp

set nat entry add 10.1.1.0 8001 209.98.250.32
8001 tcp

Where 10.1.1.0 id my inside IP and 209.98.250.32 is my outside IP.

So your saying thats wrong huh?

Then what are* the entries?<HR></BLOCKQUOTE>

[pj]

When your at the prompt in your router - type show nat and it will display all current nat configs..

Guess what? Cisco Emailed me back saying they want $210 to fix the problem. Then they said even though I paied, it might not even get fixed. So I told them forget it.

So people it looks like I'm at the end of the dock, ready to jump into the cold lake. I have no further options except to bail out.

The people at my ISP said "we don't support SHOUTcast" yet I was running it the day before on my 56k modem. Shows ya how much they know..

If I hear anything about how to set up the Router, I'll post them here. But don't count on it! Seems no one is willing to look into it.

[pj]

I looked at updating my CBOS at the link provided above. Whats up with these BIN files? I thought you needed an IMG file to do the upgreade?
http://adsl.contamination.org/downlo...c675.2.3.0.bin

Bin? Wheres the IMG file?

i use the same dsl modem and have no problems at all

[pj]

Are you running under 2.2 CBOS or 2.3?

What NAT entries did you enter into the router?

I'm starting to think that maybe the router (mine anyway) isin't forwarding packets to my inside machine. And I also saw that mentioned as one of the new fixes for 2.3

hmmmm, silly me, i didnt change a thing in the router setup. just plugged it in, it worked and off i went a'browsin

I have had the same problem for awhile I just cant get anything to work I was wondering if i had the wrong potocol set mabey the ports needed udp instead of tcp or a combo of the two or am i going at the problem all wrong i hate firewalls I need to switch ISPs uswest.net sucks.

[pj]

I entered both NAT params SirFrag..

So it would have looked like:

set nat entry add 10.0.0.1 8000 209.98.230.225 8000 tcp

ect.. For 8001, for udp and tcp.. Nothing..

Iam having the same problem with my linux box routing to my windows box that is running shoutcast. I took off the firewall. Then I mapped ports 8000 and 8001 to the Windows box running shoutcast. I even forwarded both tcp and udp connections to those ports. I can connect no problem from the internal network but not from the internet. This is a really frustrating problem and if anybody could help I would greatly appreciate it.

thanks.

[Romilar_D]

<BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>
My server gets this error: "[yp_add] yp.shoutcast.com gave error (nak)" -- What's wrong with my server?

Answer: The SHOUTcast directory has refused to publish your directory entry for one of a number of reasons. Your server should have an extended error message as well which might correspond with one of the following:

* NOTE: If the extended-error message is accompanied by an IP address, check to make sure it's the same IP address and port you're running the SHOUTcast server from. If it's different, then something is changing your IP address before it gets to us. This is usually because of internet sharing devices or software. DSL routers and cable modems typically are the culprit, as are corporate firewalls, NAT devices, or web caches.
We are working on a solution for the web caches, but if any of the other devices are changing your IP, you will *have* to follow the instructions under Connection refused: below to solve your problem. Listeners on the internet will not be able to listen to your server until you fix the problem.

* Connection refused: This typically means your server is not visible from the Internet. The usual cause is that you're located behind a firewall or NAT device (this includes internet sharing programs like Sygate, Wingate, etc.). These devices block incoming connections to your network. You need to configure these devices to map port 8000 on the device to port 8000 on the computer running the SHOUTcast server. If you have changed the SHOUTcast DNAS configuration to have different values for the ports, you should map that port instead. The important detail is that the SAME PORT YOU BROADCAST ON MUST BE THE PORT MAPPED FROM THE OUTSIDE. That is, you can't map port 99 to port 8000 and expect it to work. It won't.

* Connection timed out: This means the SHOUTcast directory attempted to contact your server, but never reached it. This is usually due to ISPs or corporate networks blocking incoming traffic. Occasionally this is because the Internet is tweaked and the directory can't find a route to your server. Reasons for this can be as various as ISPs around the world disagreeing on route tables, overburdened connections between your ISP and the backbone, or just general net flakiness. If it doesn't clear up after a day or so, ask your network provider if they block incoming traffic.
<HR></BLOCKQUOTE>

My problem was that my ISP blocks traffic on port 80 for a web cache, shoutcast also touches servers to see if they're alive on port 80, so the server would return NAK error when yp.shoutcast.com tries to list. The remedy was to change the YP port in shoutcast configuration to use port 666 instead of port 80.


------------------
ParaDynamic Roadhouse
Drink or Die! Barstool Blues