Wrong IP for Airport Express v1 - AirPlay in PulseAudio RAOP, Ubuntu 18.04
Clash Royale CLAN TAG#URR8PPP up vote
0
down vote
favorite
Since upgrading from 17.10 to 18.04, I'm presented with AirPort outputs with a wrong IP address for my AirPort Express v1 which I'm using to stream over AirPlay.
Instead of showing the local address (192.168.1.2), I get some unreal 169.254.2.109 for reasons I can't understand, so - most obviously - audio won't be sent when selecting that, and streaming applications freeze.
PulseAudio and all necessary modules (pulseaudio-module-raop and pulseaudio-module-zeroconf in particular) are installed and defaulted. Maybe some Avahi/Zeroconf? I have no clue.
Any idea or help would be greatly appreciated. Thank you in advance!
networking pulseaudio
asked Apr 30 at 5:17
F. Flower
34
add a comment |Â
up vote
0
down vote
favorite
Since upgrading from 17.10 to 18.04, I'm presented with AirPort outputs with a wrong IP address for my AirPort Express v1 which I'm using to stream over AirPlay.
Instead of showing the local address (192.168.1.2), I get some unreal 169.254.2.109 for reasons I can't understand, so - most obviously - audio won't be sent when selecting that, and streaming applications freeze.
PulseAudio and all necessary modules (pulseaudio-module-raop and pulseaudio-module-zeroconf in particular) are installed and defaulted. Maybe some Avahi/Zeroconf? I have no clue.
Any idea or help would be greatly appreciated. Thank you in advance!
networking pulseaudio
asked Apr 30 at 5:17
F. Flower
34
add a comment |Â
up vote
0
down vote
favorite
up vote
0
down vote
favorite
Since upgrading from 17.10 to 18.04, I'm presented with AirPort outputs with a wrong IP address for my AirPort Express v1 which I'm using to stream over AirPlay.
Instead of showing the local address (192.168.1.2), I get some unreal 169.254.2.109 for reasons I can't understand, so - most obviously - audio won't be sent when selecting that, and streaming applications freeze.
PulseAudio and all necessary modules (pulseaudio-module-raop and pulseaudio-module-zeroconf in particular) are installed and defaulted. Maybe some Avahi/Zeroconf? I have no clue.
Any idea or help would be greatly appreciated. Thank you in advance!
networking pulseaudio
asked Apr 30 at 5:17
F. Flower
34
Since upgrading from 17.10 to 18.04, I'm presented with AirPort outputs with a wrong IP address for my AirPort Express v1 which I'm using to stream over AirPlay.
Instead of showing the local address (192.168.1.2), I get some unreal 169.254.2.109 for reasons I can't understand, so - most obviously - audio won't be sent when selecting that, and streaming applications freeze.
PulseAudio and all necessary modules (pulseaudio-module-raop and pulseaudio-module-zeroconf in particular) are installed and defaulted. Maybe some Avahi/Zeroconf? I have no clue.
Any idea or help would be greatly appreciated. Thank you in advance!
networking pulseaudio
asked Apr 30 at 5:17
F. Flower
34
asked Apr 30 at 5:17
F. Flower
34
asked Apr 30 at 5:17
F. Flower
34
asked Apr 30 at 5:17
F. Flower
34
34
add a comment |Â
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
1
down vote
accepted
I was beating my head against the same issue for a while on Arch, and eventually found a solution via this thread:
https://github.com/hfujita/pulseaudio-raop2/issues/21
The solution was to run the command sudo avahi-autoipd --force-bind wlp4s0. You would have to replace wlp4s0 with the name of the interface you are using to connect to the internet. For you it might be wlan0 for wifi or eth0 for ethernet; I expect you can figure out that part yourself.
Not being an IT expert, I gathered that the AirPort Express is putting out a link-local address (169.x instead of 192.x), and your computer can see it, but since your machine doesn't have a link-local address of its own it can't stream to the AirPort. The above command assigns your computer a link-local address.
If this doesn't work for you, there are a few other workarounds in that thread, but they appear to be more complex.
answered May 20 at 15:18
Stume
261
Brilliant! It worked straight away! Thank you a lot for your answer, Stume! I was really tired of not being able to send music to the AirPort. Thank you again!
– F. Flower
May 21 at 8:42
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
accepted
I was beating my head against the same issue for a while on Arch, and eventually found a solution via this thread:
https://github.com/hfujita/pulseaudio-raop2/issues/21
The solution was to run the command sudo avahi-autoipd --force-bind wlp4s0. You would have to replace wlp4s0 with the name of the interface you are using to connect to the internet. For you it might be wlan0 for wifi or eth0 for ethernet; I expect you can figure out that part yourself.
Not being an IT expert, I gathered that the AirPort Express is putting out a link-local address (169.x instead of 192.x), and your computer can see it, but since your machine doesn't have a link-local address of its own it can't stream to the AirPort. The above command assigns your computer a link-local address.
If this doesn't work for you, there are a few other workarounds in that thread, but they appear to be more complex.
answered May 20 at 15:18
Stume
261
Brilliant! It worked straight away! Thank you a lot for your answer, Stume! I was really tired of not being able to send music to the AirPort. Thank you again!
– F. Flower
May 21 at 8:42
add a comment |Â
up vote
1
down vote
accepted
I was beating my head against the same issue for a while on Arch, and eventually found a solution via this thread:
https://github.com/hfujita/pulseaudio-raop2/issues/21
The solution was to run the command sudo avahi-autoipd --force-bind wlp4s0. You would have to replace wlp4s0 with the name of the interface you are using to connect to the internet. For you it might be wlan0 for wifi or eth0 for ethernet; I expect you can figure out that part yourself.
Not being an IT expert, I gathered that the AirPort Express is putting out a link-local address (169.x instead of 192.x), and your computer can see it, but since your machine doesn't have a link-local address of its own it can't stream to the AirPort. The above command assigns your computer a link-local address.
If this doesn't work for you, there are a few other workarounds in that thread, but they appear to be more complex.
answered May 20 at 15:18
Stume
261
Brilliant! It worked straight away! Thank you a lot for your answer, Stume! I was really tired of not being able to send music to the AirPort. Thank you again!
– F. Flower
May 21 at 8:42
add a comment |Â
up vote
1
down vote
accepted
up vote
1
down vote
accepted
I was beating my head against the same issue for a while on Arch, and eventually found a solution via this thread:
https://github.com/hfujita/pulseaudio-raop2/issues/21
The solution was to run the command sudo avahi-autoipd --force-bind wlp4s0. You would have to replace wlp4s0 with the name of the interface you are using to connect to the internet. For you it might be wlan0 for wifi or eth0 for ethernet; I expect you can figure out that part yourself.
Not being an IT expert, I gathered that the AirPort Express is putting out a link-local address (169.x instead of 192.x), and your computer can see it, but since your machine doesn't have a link-local address of its own it can't stream to the AirPort. The above command assigns your computer a link-local address.
If this doesn't work for you, there are a few other workarounds in that thread, but they appear to be more complex.
answered May 20 at 15:18
Stume
261
I was beating my head against the same issue for a while on Arch, and eventually found a solution via this thread:
https://github.com/hfujita/pulseaudio-raop2/issues/21
The solution was to run the command sudo avahi-autoipd --force-bind wlp4s0. You would have to replace wlp4s0 with the name of the interface you are using to connect to the internet. For you it might be wlan0 for wifi or eth0 for ethernet; I expect you can figure out that part yourself.
Not being an IT expert, I gathered that the AirPort Express is putting out a link-local address (169.x instead of 192.x), and your computer can see it, but since your machine doesn't have a link-local address of its own it can't stream to the AirPort. The above command assigns your computer a link-local address.
If this doesn't work for you, there are a few other workarounds in that thread, but they appear to be more complex.
answered May 20 at 15:18
Stume
261
answered May 20 at 15:18
Stume
261
answered May 20 at 15:18
Stume
261
answered May 20 at 15:18
Stume
261
261
Brilliant! It worked straight away! Thank you a lot for your answer, Stume! I was really tired of not being able to send music to the AirPort. Thank you again!
– F. Flower
May 21 at 8:42
add a comment |Â
Brilliant! It worked straight away! Thank you a lot for your answer, Stume! I was really tired of not being able to send music to the AirPort. Thank you again!
– F. Flower
May 21 at 8:42
Brilliant! It worked straight away! Thank you a lot for your answer, Stume! I was really tired of not being able to send music to the AirPort. Thank you again!
– F. Flower
May 21 at 8:42
Brilliant! It worked straight away! Thank you a lot for your answer, Stume! I was really tired of not being able to send music to the AirPort. Thank you again!
– F. Flower
May 21 at 8:42
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1029951%2fwrong-ip-for-airport-express-v1-airplay-in-pulseaudio-raop-ubuntu-18-04%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password