Wired network works in live CD but not after installation
Live CD and installation have working network connection.
But after installing, the network connection is offline; it won't connect! No automatic configuration, aka DHCP doesn't work.
Static configuration allows it to connect to the network (so it says) but I'm unable to ping my DSL router, hence the NIC isn't working properly. It will ping the loopback and it's own static IP address and that's it. The router also doesn't see it connected to network! I've disabled IPv6, but still no luck. I've tried the command dhclient eth0
, but still no luck. I've tried service network-manager restart
, but still no luck. ifconfig
shows static IP configuration and IPv6 disabled. My guess is the installed network driver is different from the Live CD and Installation version; how retarded is that!
Ok, seeing how I have no internet connection on this machine, how in the heck do I manually install a network driver for a dual boot Intel Mac Mini (2009 model)? I've been searching for an answer for 3 days now. I've seen the same problem numerous times posted all over the internet, but I have yet to find a solution to the problem =).
By the way, in OSX, the network functions flawlessly so it's not a hardware or network problem. Also, seeing how this OS has driver issues among other things, would it kill someone to create a GUI Device Manager that installs with the OS. It would be nice to be able to manage device drivers without going into the terminal...just a thought.
networking network-manager dhcp
add a comment |
Live CD and installation have working network connection.
But after installing, the network connection is offline; it won't connect! No automatic configuration, aka DHCP doesn't work.
Static configuration allows it to connect to the network (so it says) but I'm unable to ping my DSL router, hence the NIC isn't working properly. It will ping the loopback and it's own static IP address and that's it. The router also doesn't see it connected to network! I've disabled IPv6, but still no luck. I've tried the command dhclient eth0
, but still no luck. I've tried service network-manager restart
, but still no luck. ifconfig
shows static IP configuration and IPv6 disabled. My guess is the installed network driver is different from the Live CD and Installation version; how retarded is that!
Ok, seeing how I have no internet connection on this machine, how in the heck do I manually install a network driver for a dual boot Intel Mac Mini (2009 model)? I've been searching for an answer for 3 days now. I've seen the same problem numerous times posted all over the internet, but I have yet to find a solution to the problem =).
By the way, in OSX, the network functions flawlessly so it's not a hardware or network problem. Also, seeing how this OS has driver issues among other things, would it kill someone to create a GUI Device Manager that installs with the OS. It would be nice to be able to manage device drivers without going into the terminal...just a thought.
networking network-manager dhcp
You need to copy and paste the output of the commands that you have run and not describe the results to help us assist you further. The output of ifconfig, route, arp is needed for starters.
– Fred Thomsen
May 20 '13 at 3:53
add a comment |
Live CD and installation have working network connection.
But after installing, the network connection is offline; it won't connect! No automatic configuration, aka DHCP doesn't work.
Static configuration allows it to connect to the network (so it says) but I'm unable to ping my DSL router, hence the NIC isn't working properly. It will ping the loopback and it's own static IP address and that's it. The router also doesn't see it connected to network! I've disabled IPv6, but still no luck. I've tried the command dhclient eth0
, but still no luck. I've tried service network-manager restart
, but still no luck. ifconfig
shows static IP configuration and IPv6 disabled. My guess is the installed network driver is different from the Live CD and Installation version; how retarded is that!
Ok, seeing how I have no internet connection on this machine, how in the heck do I manually install a network driver for a dual boot Intel Mac Mini (2009 model)? I've been searching for an answer for 3 days now. I've seen the same problem numerous times posted all over the internet, but I have yet to find a solution to the problem =).
By the way, in OSX, the network functions flawlessly so it's not a hardware or network problem. Also, seeing how this OS has driver issues among other things, would it kill someone to create a GUI Device Manager that installs with the OS. It would be nice to be able to manage device drivers without going into the terminal...just a thought.
networking network-manager dhcp
Live CD and installation have working network connection.
But after installing, the network connection is offline; it won't connect! No automatic configuration, aka DHCP doesn't work.
Static configuration allows it to connect to the network (so it says) but I'm unable to ping my DSL router, hence the NIC isn't working properly. It will ping the loopback and it's own static IP address and that's it. The router also doesn't see it connected to network! I've disabled IPv6, but still no luck. I've tried the command dhclient eth0
, but still no luck. I've tried service network-manager restart
, but still no luck. ifconfig
shows static IP configuration and IPv6 disabled. My guess is the installed network driver is different from the Live CD and Installation version; how retarded is that!
Ok, seeing how I have no internet connection on this machine, how in the heck do I manually install a network driver for a dual boot Intel Mac Mini (2009 model)? I've been searching for an answer for 3 days now. I've seen the same problem numerous times posted all over the internet, but I have yet to find a solution to the problem =).
By the way, in OSX, the network functions flawlessly so it's not a hardware or network problem. Also, seeing how this OS has driver issues among other things, would it kill someone to create a GUI Device Manager that installs with the OS. It would be nice to be able to manage device drivers without going into the terminal...just a thought.
networking network-manager dhcp
networking network-manager dhcp
edited May 20 '13 at 6:01
thomasrutter
27.1k46689
27.1k46689
asked May 20 '13 at 3:43
LinuxNoobLinuxNoob
11
11
You need to copy and paste the output of the commands that you have run and not describe the results to help us assist you further. The output of ifconfig, route, arp is needed for starters.
– Fred Thomsen
May 20 '13 at 3:53
add a comment |
You need to copy and paste the output of the commands that you have run and not describe the results to help us assist you further. The output of ifconfig, route, arp is needed for starters.
– Fred Thomsen
May 20 '13 at 3:53
You need to copy and paste the output of the commands that you have run and not describe the results to help us assist you further. The output of ifconfig, route, arp is needed for starters.
– Fred Thomsen
May 20 '13 at 3:53
You need to copy and paste the output of the commands that you have run and not describe the results to help us assist you further. The output of ifconfig, route, arp is needed for starters.
– Fred Thomsen
May 20 '13 at 3:53
add a comment |
1 Answer
1
active
oldest
votes
Try configuring your interfaces file:
- Open a terminal
- For sudo session type:
sudo -i
- Enter your password
If you are unsure what your network interface is, determine it by executing:
ip link show
. This will give you a list of network interfaces available.
You should see something like:
# ip link show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp24s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000
link/ether 00:d8:61:2e:27:7c brd ff:ff:ff:ff:ff:ff
lo
stands for the loopback interface, so ignore that. For cabled network interfaces look forethX
,enX
,enX
,ensX
,
enpXsY
,pXpY
(whereX
andY
are integers). For wireless look forwlanX
. Make note of the interface you will be configuring.
Edit the file
/etc/network/interfaces
(e.g.xdg-open /etc/network/interfaces
if you are on a GUI terminal or"${EDITOR:-nano}" /etc/network/interfaces
for a CLI editor)
You should see something like this in the file content:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
Add the network interface from above with dhcp configuration. For example:
#DHCP config for eth0
auto eth0
iface eth0 inet dhcp
OR
#DHCP config for wlan0
auto wlan0
iface wlan0 inet dhcp
Save the file and exit
- Restart networking by executing
service networking restart
.
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%2f297636%2fwired-network-works-in-live-cd-but-not-after-installation%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Try configuring your interfaces file:
- Open a terminal
- For sudo session type:
sudo -i
- Enter your password
If you are unsure what your network interface is, determine it by executing:
ip link show
. This will give you a list of network interfaces available.
You should see something like:
# ip link show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp24s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000
link/ether 00:d8:61:2e:27:7c brd ff:ff:ff:ff:ff:ff
lo
stands for the loopback interface, so ignore that. For cabled network interfaces look forethX
,enX
,enX
,ensX
,
enpXsY
,pXpY
(whereX
andY
are integers). For wireless look forwlanX
. Make note of the interface you will be configuring.
Edit the file
/etc/network/interfaces
(e.g.xdg-open /etc/network/interfaces
if you are on a GUI terminal or"${EDITOR:-nano}" /etc/network/interfaces
for a CLI editor)
You should see something like this in the file content:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
Add the network interface from above with dhcp configuration. For example:
#DHCP config for eth0
auto eth0
iface eth0 inet dhcp
OR
#DHCP config for wlan0
auto wlan0
iface wlan0 inet dhcp
Save the file and exit
- Restart networking by executing
service networking restart
.
add a comment |
Try configuring your interfaces file:
- Open a terminal
- For sudo session type:
sudo -i
- Enter your password
If you are unsure what your network interface is, determine it by executing:
ip link show
. This will give you a list of network interfaces available.
You should see something like:
# ip link show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp24s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000
link/ether 00:d8:61:2e:27:7c brd ff:ff:ff:ff:ff:ff
lo
stands for the loopback interface, so ignore that. For cabled network interfaces look forethX
,enX
,enX
,ensX
,
enpXsY
,pXpY
(whereX
andY
are integers). For wireless look forwlanX
. Make note of the interface you will be configuring.
Edit the file
/etc/network/interfaces
(e.g.xdg-open /etc/network/interfaces
if you are on a GUI terminal or"${EDITOR:-nano}" /etc/network/interfaces
for a CLI editor)
You should see something like this in the file content:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
Add the network interface from above with dhcp configuration. For example:
#DHCP config for eth0
auto eth0
iface eth0 inet dhcp
OR
#DHCP config for wlan0
auto wlan0
iface wlan0 inet dhcp
Save the file and exit
- Restart networking by executing
service networking restart
.
add a comment |
Try configuring your interfaces file:
- Open a terminal
- For sudo session type:
sudo -i
- Enter your password
If you are unsure what your network interface is, determine it by executing:
ip link show
. This will give you a list of network interfaces available.
You should see something like:
# ip link show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp24s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000
link/ether 00:d8:61:2e:27:7c brd ff:ff:ff:ff:ff:ff
lo
stands for the loopback interface, so ignore that. For cabled network interfaces look forethX
,enX
,enX
,ensX
,
enpXsY
,pXpY
(whereX
andY
are integers). For wireless look forwlanX
. Make note of the interface you will be configuring.
Edit the file
/etc/network/interfaces
(e.g.xdg-open /etc/network/interfaces
if you are on a GUI terminal or"${EDITOR:-nano}" /etc/network/interfaces
for a CLI editor)
You should see something like this in the file content:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
Add the network interface from above with dhcp configuration. For example:
#DHCP config for eth0
auto eth0
iface eth0 inet dhcp
OR
#DHCP config for wlan0
auto wlan0
iface wlan0 inet dhcp
Save the file and exit
- Restart networking by executing
service networking restart
.
Try configuring your interfaces file:
- Open a terminal
- For sudo session type:
sudo -i
- Enter your password
If you are unsure what your network interface is, determine it by executing:
ip link show
. This will give you a list of network interfaces available.
You should see something like:
# ip link show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp24s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000
link/ether 00:d8:61:2e:27:7c brd ff:ff:ff:ff:ff:ff
lo
stands for the loopback interface, so ignore that. For cabled network interfaces look forethX
,enX
,enX
,ensX
,
enpXsY
,pXpY
(whereX
andY
are integers). For wireless look forwlanX
. Make note of the interface you will be configuring.
Edit the file
/etc/network/interfaces
(e.g.xdg-open /etc/network/interfaces
if you are on a GUI terminal or"${EDITOR:-nano}" /etc/network/interfaces
for a CLI editor)
You should see something like this in the file content:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
Add the network interface from above with dhcp configuration. For example:
#DHCP config for eth0
auto eth0
iface eth0 inet dhcp
OR
#DHCP config for wlan0
auto wlan0
iface wlan0 inet dhcp
Save the file and exit
- Restart networking by executing
service networking restart
.
edited Feb 7 at 5:27
Mike
4101717
4101717
answered Aug 20 '13 at 21:34
DeusDeus
1538
1538
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%2f297636%2fwired-network-works-in-live-cd-but-not-after-installation%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
You need to copy and paste the output of the commands that you have run and not describe the results to help us assist you further. The output of ifconfig, route, arp is needed for starters.
– Fred Thomsen
May 20 '13 at 3:53