Configuring network to set wlan0 as primaryHow to setup an alias for local facing interfaceNetworking stopped...
Explain the objections to these measures against human trafficking
Difference between `vector<int> v;` and `vector<int> v = vector<int>();`
If I deleted a game I lost the disc for, can I reinstall it digitally?
How to limit sight distance to 1 km
Why do stocks necessarily drop during a recession?
Do authors have to be politically correct in article-writing?
Who is this Ant Woman character in this image alongside the Wasp?
CREATE ASSEMBLY System.DirectoryServices.AccountManagement.dll without enabling TRUSTWORTHY
Incorporating research and background: How much is too much?
How would an AI self awareness kill switch work?
Can we use the stored gravitational potential energy of a building to produce power?
How can my powered armor quickly replace its ceramic plates?
Porting Linux to another platform requirements
Is it a fallacy if someone claims they need an explanation for every word of your argument to the point where they don't understand common terms?
Why zero tolerance on nudity in space?
Publishing research using outdated methods
How to remove lines through the legend markers in ListPlot?
How much mayhem could I cause as a sentient fish?
Can a person refuse a presidential pardon?
Can I become debt free or should I file bankruptcy ? How to manage my debt and finances?
Are there any modern advantages of a fire piston?
How to prevent cleaner from hanging my lock screen in Ubuntu 16.04
Cookies - Should the toggles be on?
Am I a Rude Number?
Configuring network to set wlan0 as primary
How to setup an alias for local facing interfaceNetworking stopped working on Ubuntu 10.04What is the correct syntax for /etc/network/interfaces?Connecting Two Computers Together: Assigning IP doesnt workWhat does it mean for a network interface to be primary?What does keywords in my /etc/network/interfaces means?Configure LXC with additional IP ubuntu 14.04server wont connect to network; cannot find device eth0Renaming ethernet devices in 16.04edit /etc/network/interfaces with wlp3s0 instead of wlan0
I recently had to rebuild my pc and decided to go for ubuntu 14.04. I think the mistake I made was I started from a 12.04 install disk instead of the 12.10 disk I'd used previously and when given the option set my primary connection as ethernet (because the wireless option didn't work).
After upgrading to 14.04 etc, I managed to get the wireless working, or more using steps like ifconfig -a and the likes I managed to prove that the wireless card etc. is all installed and working.
However every time I boot without a hard wired connection plugged in I get the message "waiting for network configuration".
I can then once it's booted without a network get my wirless working using
sudo ifconfig wlan0 up
iwlist wlan0 scan
This seems to kick the wireless module into life and it appears in the GUI and I can then select a network, however all the options like edit network and disconnect etc are all greyed out.
What I would like of course is if the WLAN0 was just set as my primary default network so I've been looking for a solution to this and it would seem that I need to adjust the old /etc/network/interfaces file but when I try to do so using the
sudo vi /etc/network/interfaces
command I, well I simply have no idea what I'm doing. Other than that typing :q! gets me out of there before I do to much damage!
As far as I can tell (by navigating to the file in the GUI) the output of my /etc/network/interfaces is as follows:
(obviously not including the " in each line that's just to break the heading rule of the #)
"# This file describes the network interfaces available on your system
"# and how to activate them. For more information, see interfaces(5).
"# The loopback network interface
auto lo
iface lo inet loopback
"# The primary network interface
auto eth0
iface eth0 inet dhcp
If this is the case then this clearly doesn't contain what it should do but I don't how to fix it. Nor do I even know if I'm on the right track.
Any help would be appreciated thanks :)
wireless networking
bumped to the homepage by Community♦ 11 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
I recently had to rebuild my pc and decided to go for ubuntu 14.04. I think the mistake I made was I started from a 12.04 install disk instead of the 12.10 disk I'd used previously and when given the option set my primary connection as ethernet (because the wireless option didn't work).
After upgrading to 14.04 etc, I managed to get the wireless working, or more using steps like ifconfig -a and the likes I managed to prove that the wireless card etc. is all installed and working.
However every time I boot without a hard wired connection plugged in I get the message "waiting for network configuration".
I can then once it's booted without a network get my wirless working using
sudo ifconfig wlan0 up
iwlist wlan0 scan
This seems to kick the wireless module into life and it appears in the GUI and I can then select a network, however all the options like edit network and disconnect etc are all greyed out.
What I would like of course is if the WLAN0 was just set as my primary default network so I've been looking for a solution to this and it would seem that I need to adjust the old /etc/network/interfaces file but when I try to do so using the
sudo vi /etc/network/interfaces
command I, well I simply have no idea what I'm doing. Other than that typing :q! gets me out of there before I do to much damage!
As far as I can tell (by navigating to the file in the GUI) the output of my /etc/network/interfaces is as follows:
(obviously not including the " in each line that's just to break the heading rule of the #)
"# This file describes the network interfaces available on your system
"# and how to activate them. For more information, see interfaces(5).
"# The loopback network interface
auto lo
iface lo inet loopback
"# The primary network interface
auto eth0
iface eth0 inet dhcp
If this is the case then this clearly doesn't contain what it should do but I don't how to fix it. Nor do I even know if I'm on the right track.
Any help would be appreciated thanks :)
wireless networking
bumped to the homepage by Community♦ 11 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
I recently had to rebuild my pc and decided to go for ubuntu 14.04. I think the mistake I made was I started from a 12.04 install disk instead of the 12.10 disk I'd used previously and when given the option set my primary connection as ethernet (because the wireless option didn't work).
After upgrading to 14.04 etc, I managed to get the wireless working, or more using steps like ifconfig -a and the likes I managed to prove that the wireless card etc. is all installed and working.
However every time I boot without a hard wired connection plugged in I get the message "waiting for network configuration".
I can then once it's booted without a network get my wirless working using
sudo ifconfig wlan0 up
iwlist wlan0 scan
This seems to kick the wireless module into life and it appears in the GUI and I can then select a network, however all the options like edit network and disconnect etc are all greyed out.
What I would like of course is if the WLAN0 was just set as my primary default network so I've been looking for a solution to this and it would seem that I need to adjust the old /etc/network/interfaces file but when I try to do so using the
sudo vi /etc/network/interfaces
command I, well I simply have no idea what I'm doing. Other than that typing :q! gets me out of there before I do to much damage!
As far as I can tell (by navigating to the file in the GUI) the output of my /etc/network/interfaces is as follows:
(obviously not including the " in each line that's just to break the heading rule of the #)
"# This file describes the network interfaces available on your system
"# and how to activate them. For more information, see interfaces(5).
"# The loopback network interface
auto lo
iface lo inet loopback
"# The primary network interface
auto eth0
iface eth0 inet dhcp
If this is the case then this clearly doesn't contain what it should do but I don't how to fix it. Nor do I even know if I'm on the right track.
Any help would be appreciated thanks :)
wireless networking
I recently had to rebuild my pc and decided to go for ubuntu 14.04. I think the mistake I made was I started from a 12.04 install disk instead of the 12.10 disk I'd used previously and when given the option set my primary connection as ethernet (because the wireless option didn't work).
After upgrading to 14.04 etc, I managed to get the wireless working, or more using steps like ifconfig -a and the likes I managed to prove that the wireless card etc. is all installed and working.
However every time I boot without a hard wired connection plugged in I get the message "waiting for network configuration".
I can then once it's booted without a network get my wirless working using
sudo ifconfig wlan0 up
iwlist wlan0 scan
This seems to kick the wireless module into life and it appears in the GUI and I can then select a network, however all the options like edit network and disconnect etc are all greyed out.
What I would like of course is if the WLAN0 was just set as my primary default network so I've been looking for a solution to this and it would seem that I need to adjust the old /etc/network/interfaces file but when I try to do so using the
sudo vi /etc/network/interfaces
command I, well I simply have no idea what I'm doing. Other than that typing :q! gets me out of there before I do to much damage!
As far as I can tell (by navigating to the file in the GUI) the output of my /etc/network/interfaces is as follows:
(obviously not including the " in each line that's just to break the heading rule of the #)
"# This file describes the network interfaces available on your system
"# and how to activate them. For more information, see interfaces(5).
"# The loopback network interface
auto lo
iface lo inet loopback
"# The primary network interface
auto eth0
iface eth0 inet dhcp
If this is the case then this clearly doesn't contain what it should do but I don't how to fix it. Nor do I even know if I'm on the right track.
Any help would be appreciated thanks :)
wireless networking
wireless networking
asked Jun 11 '14 at 3:26
SheedSheed
33128
33128
bumped to the homepage by Community♦ 11 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
bumped to the homepage by Community♦ 11 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
Open your terminal and type as
sudo nano /etc/network/interfaces
Assume that your Ethernet interface ID is eth0
.
Then ad this line to that file
iface eth0 inet manual
Then restart your Network-Manager with
sudo service network-manager restart
or restart your PC and check.
Hope that helps.
This seemed to work, as in when I did the network-manager restart the wireless didn't completely disappear as it had previously but upon restarting the pc it still booted up with the "waiting on network configuration" and I had to go through the process of manually booting the wireless again. Thanks though.
– Sheed
Jun 11 '14 at 13:11
add a comment |
What I do is remove the default and make a new default. Windows is much harder to manage, and both use metrics (by increasing the cost to "your" least likely choice) to handle "routing conflicts" when the same destination can be from either device. The smaller the number/cost of the connection will win -- but if you have two interface routes it can be quite bad if your tunnel dies and then your traffic becomes public again.
- you can simply type
route
to see your current routing table route del default eth0
route add default wlan0
I usually do this when I create tunnels, so I am usually deleting wlan0
and adding ppp0
. If I leave it alone, I still have the same ISP IP address; So, I need to change my default to the tunnel.
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f481645%2fconfiguring-network-to-set-wlan0-as-primary%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
Open your terminal and type as
sudo nano /etc/network/interfaces
Assume that your Ethernet interface ID is eth0
.
Then ad this line to that file
iface eth0 inet manual
Then restart your Network-Manager with
sudo service network-manager restart
or restart your PC and check.
Hope that helps.
This seemed to work, as in when I did the network-manager restart the wireless didn't completely disappear as it had previously but upon restarting the pc it still booted up with the "waiting on network configuration" and I had to go through the process of manually booting the wireless again. Thanks though.
– Sheed
Jun 11 '14 at 13:11
add a comment |
Open your terminal and type as
sudo nano /etc/network/interfaces
Assume that your Ethernet interface ID is eth0
.
Then ad this line to that file
iface eth0 inet manual
Then restart your Network-Manager with
sudo service network-manager restart
or restart your PC and check.
Hope that helps.
This seemed to work, as in when I did the network-manager restart the wireless didn't completely disappear as it had previously but upon restarting the pc it still booted up with the "waiting on network configuration" and I had to go through the process of manually booting the wireless again. Thanks though.
– Sheed
Jun 11 '14 at 13:11
add a comment |
Open your terminal and type as
sudo nano /etc/network/interfaces
Assume that your Ethernet interface ID is eth0
.
Then ad this line to that file
iface eth0 inet manual
Then restart your Network-Manager with
sudo service network-manager restart
or restart your PC and check.
Hope that helps.
Open your terminal and type as
sudo nano /etc/network/interfaces
Assume that your Ethernet interface ID is eth0
.
Then ad this line to that file
iface eth0 inet manual
Then restart your Network-Manager with
sudo service network-manager restart
or restart your PC and check.
Hope that helps.
answered Jun 11 '14 at 3:54
rɑːdʒɑrɑːdʒɑ
58.2k85218302
58.2k85218302
This seemed to work, as in when I did the network-manager restart the wireless didn't completely disappear as it had previously but upon restarting the pc it still booted up with the "waiting on network configuration" and I had to go through the process of manually booting the wireless again. Thanks though.
– Sheed
Jun 11 '14 at 13:11
add a comment |
This seemed to work, as in when I did the network-manager restart the wireless didn't completely disappear as it had previously but upon restarting the pc it still booted up with the "waiting on network configuration" and I had to go through the process of manually booting the wireless again. Thanks though.
– Sheed
Jun 11 '14 at 13:11
This seemed to work, as in when I did the network-manager restart the wireless didn't completely disappear as it had previously but upon restarting the pc it still booted up with the "waiting on network configuration" and I had to go through the process of manually booting the wireless again. Thanks though.
– Sheed
Jun 11 '14 at 13:11
This seemed to work, as in when I did the network-manager restart the wireless didn't completely disappear as it had previously but upon restarting the pc it still booted up with the "waiting on network configuration" and I had to go through the process of manually booting the wireless again. Thanks though.
– Sheed
Jun 11 '14 at 13:11
add a comment |
What I do is remove the default and make a new default. Windows is much harder to manage, and both use metrics (by increasing the cost to "your" least likely choice) to handle "routing conflicts" when the same destination can be from either device. The smaller the number/cost of the connection will win -- but if you have two interface routes it can be quite bad if your tunnel dies and then your traffic becomes public again.
- you can simply type
route
to see your current routing table route del default eth0
route add default wlan0
I usually do this when I create tunnels, so I am usually deleting wlan0
and adding ppp0
. If I leave it alone, I still have the same ISP IP address; So, I need to change my default to the tunnel.
add a comment |
What I do is remove the default and make a new default. Windows is much harder to manage, and both use metrics (by increasing the cost to "your" least likely choice) to handle "routing conflicts" when the same destination can be from either device. The smaller the number/cost of the connection will win -- but if you have two interface routes it can be quite bad if your tunnel dies and then your traffic becomes public again.
- you can simply type
route
to see your current routing table route del default eth0
route add default wlan0
I usually do this when I create tunnels, so I am usually deleting wlan0
and adding ppp0
. If I leave it alone, I still have the same ISP IP address; So, I need to change my default to the tunnel.
add a comment |
What I do is remove the default and make a new default. Windows is much harder to manage, and both use metrics (by increasing the cost to "your" least likely choice) to handle "routing conflicts" when the same destination can be from either device. The smaller the number/cost of the connection will win -- but if you have two interface routes it can be quite bad if your tunnel dies and then your traffic becomes public again.
- you can simply type
route
to see your current routing table route del default eth0
route add default wlan0
I usually do this when I create tunnels, so I am usually deleting wlan0
and adding ppp0
. If I leave it alone, I still have the same ISP IP address; So, I need to change my default to the tunnel.
What I do is remove the default and make a new default. Windows is much harder to manage, and both use metrics (by increasing the cost to "your" least likely choice) to handle "routing conflicts" when the same destination can be from either device. The smaller the number/cost of the connection will win -- but if you have two interface routes it can be quite bad if your tunnel dies and then your traffic becomes public again.
- you can simply type
route
to see your current routing table route del default eth0
route add default wlan0
I usually do this when I create tunnels, so I am usually deleting wlan0
and adding ppp0
. If I leave it alone, I still have the same ISP IP address; So, I need to change my default to the tunnel.
edited Jun 9 '18 at 21:30
Stephen Rauch
1,1546716
1,1546716
answered Jun 9 '18 at 17:14
Jason ZouikriJason Zouikri
1
1
add a comment |
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f481645%2fconfiguring-network-to-set-wlan0-as-primary%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
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
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown