RTL on RPI authentication issue

Status
Not open for further replies.

va3mw

Newbie
Joined
Aug 3, 2006
Messages
2
Location
Thornhill, Ontario
All

I am trying to set up my feed and get it off my PC with a dedicated full radio over to the RPI and the RTL dongle.

The RTL dongle is installed on RPI - all tested and works. The configuration file is modified with my user name, password and correct mount point (no slash).

When I start rtl_airband with the correctly configured I can't seem to get authenticated.

Details

I am using the Credentials from my Windows installation, server, username, password and mountpoint, so I know they are valid. I have also tried the authentication password as provided by autoconfig from RadioFeed on Windows. So, that data is good.

On the Pi, as root, when I run

/usr/local/bin/rtl_airband -f -e

That fails with "Could not connect to audio1.broadcastify.com:80"

If I wireshark it the firewall, I can see that I am getting

You need to authenticate

Can I assume the RTL_airband code does work even on non-airband frequencies, or is that a different configuration situation on the server side? I am using it for a 2M VHF frequency.

Or, is there another RPI tool I can use other than rtl_airband?

thanks in advance

Mike
 

DC31

Member
Feed Provider
Joined
Feb 19, 2011
Messages
1,569
Location
Massachusetts
Can you post the output section of your config file? Scramble the text if you want.

this stuff:

outputs: (
{
type = "icecast";
server = "icecast.server.example.org";
port = 8080;
mountpoint = "TWR.mp3";
username = "source";
password = "mypassword";
# name = "Tower";
# description = "This is a Tower feed from my local airport";
# genre = "ATC";
}
);
 

va3mw

Newbie
Joined
Aug 3, 2006
Messages
2
Location
Thornhill, Ontario
I figured it out not long ago. :)

The issue is with the username being "source" and the password from the connection as posted on my account. I must have missed that.

I appreciate your posting as once I saw that the user was "source" I would have figured out the rest.

Mike
 
Status
Not open for further replies.
Top