Requiring IPv4 addressing for wi-fi connection in Bionic?
Clash Royale CLAN TAG#URR8PPP up vote
1
down vote
favorite
There's this coffee shop I visit occasionally whose Wi-Fi configuration does weird things to my Ubuntu laptop (a 2013 ThinkPad X1 Carbon running 18.04 LTS). Specifically, when the laptop connects to their network, it gets assigned an IPv6 address, but not an IPv4 address. So when I'm there, I can only access sites that have AAAA DNS records set up --- which many do not, even big/popular ones.
This has been a problem with some Wi-Fi networks for a long time, and not just for me either (here's someone else who experienced it). In older versions of Ubuntu, though, there was a relatively simple workaround: you could go into the settings for a particular network connection and, in the IPv4 settings tab, there was a checkbox labeled "Require IPv4 addressing for this connection to complete". Checking that box solved the problem; if it was checked, the problematic network would hand out an IPv4 address along with the IPv6 one, and all would be well.
I updated my laptop to Bionic a couple of weeks ago, though, and was surprised when returning to the coffee shop after the update to find that the problem had returned. Then I was even more surprised to find that, in Bionic, the "require IPv4 addressing" checkbox was no longer there in the network connection settings. So now I'm back to being IPv6-only on networks configured like this one.
Is there a way in Bionic to set the "require IPv4 addressing" preference on a network connection the way you used to be able to do with the checkbox? Or, failing that, some global way to tell Ubuntu to hang in there for as long as it must to get an IPv4 address if one is available?
networking wireless 18.04
asked Jun 6 at 18:19
jalefkowit
34627
add a comment |Â
up vote
1
down vote
favorite
There's this coffee shop I visit occasionally whose Wi-Fi configuration does weird things to my Ubuntu laptop (a 2013 ThinkPad X1 Carbon running 18.04 LTS). Specifically, when the laptop connects to their network, it gets assigned an IPv6 address, but not an IPv4 address. So when I'm there, I can only access sites that have AAAA DNS records set up --- which many do not, even big/popular ones.
This has been a problem with some Wi-Fi networks for a long time, and not just for me either (here's someone else who experienced it). In older versions of Ubuntu, though, there was a relatively simple workaround: you could go into the settings for a particular network connection and, in the IPv4 settings tab, there was a checkbox labeled "Require IPv4 addressing for this connection to complete". Checking that box solved the problem; if it was checked, the problematic network would hand out an IPv4 address along with the IPv6 one, and all would be well.
I updated my laptop to Bionic a couple of weeks ago, though, and was surprised when returning to the coffee shop after the update to find that the problem had returned. Then I was even more surprised to find that, in Bionic, the "require IPv4 addressing" checkbox was no longer there in the network connection settings. So now I'm back to being IPv6-only on networks configured like this one.
Is there a way in Bionic to set the "require IPv4 addressing" preference on a network connection the way you used to be able to do with the checkbox? Or, failing that, some global way to tell Ubuntu to hang in there for as long as it must to get an IPv4 address if one is available?
networking wireless 18.04
asked Jun 6 at 18:19
jalefkowit
34627
add a comment |Â
up vote
1
down vote
favorite
up vote
1
down vote
favorite
There's this coffee shop I visit occasionally whose Wi-Fi configuration does weird things to my Ubuntu laptop (a 2013 ThinkPad X1 Carbon running 18.04 LTS). Specifically, when the laptop connects to their network, it gets assigned an IPv6 address, but not an IPv4 address. So when I'm there, I can only access sites that have AAAA DNS records set up --- which many do not, even big/popular ones.
This has been a problem with some Wi-Fi networks for a long time, and not just for me either (here's someone else who experienced it). In older versions of Ubuntu, though, there was a relatively simple workaround: you could go into the settings for a particular network connection and, in the IPv4 settings tab, there was a checkbox labeled "Require IPv4 addressing for this connection to complete". Checking that box solved the problem; if it was checked, the problematic network would hand out an IPv4 address along with the IPv6 one, and all would be well.
I updated my laptop to Bionic a couple of weeks ago, though, and was surprised when returning to the coffee shop after the update to find that the problem had returned. Then I was even more surprised to find that, in Bionic, the "require IPv4 addressing" checkbox was no longer there in the network connection settings. So now I'm back to being IPv6-only on networks configured like this one.
Is there a way in Bionic to set the "require IPv4 addressing" preference on a network connection the way you used to be able to do with the checkbox? Or, failing that, some global way to tell Ubuntu to hang in there for as long as it must to get an IPv4 address if one is available?
networking wireless 18.04
asked Jun 6 at 18:19
jalefkowit
34627
There's this coffee shop I visit occasionally whose Wi-Fi configuration does weird things to my Ubuntu laptop (a 2013 ThinkPad X1 Carbon running 18.04 LTS). Specifically, when the laptop connects to their network, it gets assigned an IPv6 address, but not an IPv4 address. So when I'm there, I can only access sites that have AAAA DNS records set up --- which many do not, even big/popular ones.
This has been a problem with some Wi-Fi networks for a long time, and not just for me either (here's someone else who experienced it). In older versions of Ubuntu, though, there was a relatively simple workaround: you could go into the settings for a particular network connection and, in the IPv4 settings tab, there was a checkbox labeled "Require IPv4 addressing for this connection to complete". Checking that box solved the problem; if it was checked, the problematic network would hand out an IPv4 address along with the IPv6 one, and all would be well.
I updated my laptop to Bionic a couple of weeks ago, though, and was surprised when returning to the coffee shop after the update to find that the problem had returned. Then I was even more surprised to find that, in Bionic, the "require IPv4 addressing" checkbox was no longer there in the network connection settings. So now I'm back to being IPv6-only on networks configured like this one.
Is there a way in Bionic to set the "require IPv4 addressing" preference on a network connection the way you used to be able to do with the checkbox? Or, failing that, some global way to tell Ubuntu to hang in there for as long as it must to get an IPv4 address if one is available?
networking wireless 18.04
asked Jun 6 at 18:19
jalefkowit
34627
asked Jun 6 at 18:19
jalefkowit
34627
asked Jun 6 at 18:19
jalefkowit
34627
asked Jun 6 at 18:19
jalefkowit
34627
34627
add a comment |Â
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
0
down vote
accepted
If you run the nm-connection-editor program, you can enable this setting again.
answered Jun 6 at 18:51
dobey
31.7k33484
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
accepted
If you run the nm-connection-editor program, you can enable this setting again.
answered Jun 6 at 18:51
dobey
31.7k33484
add a comment |Â
up vote
0
down vote
accepted
If you run the nm-connection-editor program, you can enable this setting again.
answered Jun 6 at 18:51
dobey
31.7k33484
add a comment |Â
up vote
0
down vote
accepted
up vote
0
down vote
accepted
If you run the nm-connection-editor program, you can enable this setting again.
answered Jun 6 at 18:51
dobey
31.7k33484
If you run the nm-connection-editor program, you can enable this setting again.
answered Jun 6 at 18:51
dobey
31.7k33484
answered Jun 6 at 18:51
dobey
31.7k33484
answered Jun 6 at 18:51
dobey
31.7k33484
answered Jun 6 at 18:51
dobey
31.7k33484
31.7k33484
add a comment |Â
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%2f1044256%2frequiring-ipv4-addressing-for-wi-fi-connection-in-bionic%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