Ubuntu Server 12.10 not obtaining IP address until a user logs in
I just did a recent install of Ubuntu Server 12.10 (no GUI, command line only) on a new system. I noticed that upon booting the server does not obtain an IP address from my router. However, once I log into the machine locally the server shows up on my list of DCHP clients and I can connect remotely without issue. After some initial research, I looked at my /etc/network/interfaces/
# The loopback network interface
auto lo eth0
iface lo inet loopback
# The primary network interface
iface eth0 inet dhcp
Others who had similar issues usually were missing either "auto eth0" or the "dhcp" and were able to fix their problem by adding those lines in. My set up seems to be fine the way it is.
Next up, I tried looking at /etc/local.rc and made two different attempts for the server to add eth0 on boot:
Attempt #1
ifup eth0
exit 0
Attempt #2
dhclient eth0
exit 0
Yet neither of these changes caused the server to obtain IP before an initial local login. Since I'm trying to run this server headless, being able to remotely login upon boot is pretty important for my needs. Any insight would be greatly appreciated since most forums suggest to make the changes that I've already tried. Thanks for your help.
12.10 command-line boot server ethernet
asked Mar 14 '13 at 0:16
TaylorTaylor
111
add a comment |
I just did a recent install of Ubuntu Server 12.10 (no GUI, command line only) on a new system. I noticed that upon booting the server does not obtain an IP address from my router. However, once I log into the machine locally the server shows up on my list of DCHP clients and I can connect remotely without issue. After some initial research, I looked at my /etc/network/interfaces/
# The loopback network interface
auto lo eth0
iface lo inet loopback
# The primary network interface
iface eth0 inet dhcp
Others who had similar issues usually were missing either "auto eth0" or the "dhcp" and were able to fix their problem by adding those lines in. My set up seems to be fine the way it is.
Next up, I tried looking at /etc/local.rc and made two different attempts for the server to add eth0 on boot:
Attempt #1
ifup eth0
exit 0
Attempt #2
dhclient eth0
exit 0
Yet neither of these changes caused the server to obtain IP before an initial local login. Since I'm trying to run this server headless, being able to remotely login upon boot is pretty important for my needs. Any insight would be greatly appreciated since most forums suggest to make the changes that I've already tried. Thanks for your help.
12.10 command-line boot server ethernet
asked Mar 14 '13 at 0:16
TaylorTaylor
111
add a comment |
I just did a recent install of Ubuntu Server 12.10 (no GUI, command line only) on a new system. I noticed that upon booting the server does not obtain an IP address from my router. However, once I log into the machine locally the server shows up on my list of DCHP clients and I can connect remotely without issue. After some initial research, I looked at my /etc/network/interfaces/
# The loopback network interface
auto lo eth0
iface lo inet loopback
# The primary network interface
iface eth0 inet dhcp
Others who had similar issues usually were missing either "auto eth0" or the "dhcp" and were able to fix their problem by adding those lines in. My set up seems to be fine the way it is.
Next up, I tried looking at /etc/local.rc and made two different attempts for the server to add eth0 on boot:
Attempt #1
ifup eth0
exit 0
Attempt #2
dhclient eth0
exit 0
Yet neither of these changes caused the server to obtain IP before an initial local login. Since I'm trying to run this server headless, being able to remotely login upon boot is pretty important for my needs. Any insight would be greatly appreciated since most forums suggest to make the changes that I've already tried. Thanks for your help.
12.10 command-line boot server ethernet
asked Mar 14 '13 at 0:16
TaylorTaylor
111
I just did a recent install of Ubuntu Server 12.10 (no GUI, command line only) on a new system. I noticed that upon booting the server does not obtain an IP address from my router. However, once I log into the machine locally the server shows up on my list of DCHP clients and I can connect remotely without issue. After some initial research, I looked at my /etc/network/interfaces/
# The loopback network interface
auto lo eth0
iface lo inet loopback
# The primary network interface
iface eth0 inet dhcp
Others who had similar issues usually were missing either "auto eth0" or the "dhcp" and were able to fix their problem by adding those lines in. My set up seems to be fine the way it is.
Next up, I tried looking at /etc/local.rc and made two different attempts for the server to add eth0 on boot:
Attempt #1
ifup eth0
exit 0
Attempt #2
dhclient eth0
exit 0
Yet neither of these changes caused the server to obtain IP before an initial local login. Since I'm trying to run this server headless, being able to remotely login upon boot is pretty important for my needs. Any insight would be greatly appreciated since most forums suggest to make the changes that I've already tried. Thanks for your help.
12.10 command-line boot server ethernet
12.10 command-line boot server ethernet
asked Mar 14 '13 at 0:16
TaylorTaylor
111
asked Mar 14 '13 at 0:16
TaylorTaylor
111
asked Mar 14 '13 at 0:16
TaylorTaylor
111
asked Mar 14 '13 at 0:16
TaylorTaylor
111
asked Mar 14 '13 at 0:16
TaylorTaylor
111
111
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
I've never seen more than one device named on an auto line before. This could be a dud suggestion but try this instead:
auto lo
iface lo inet loopback
auto eth0
iface eth0 inet dhcp
And also check that it is eth0 and not eth1 or eth2. Probably nothing but it doesn't hurt to double-check.
$ ifconfig -a | grep eth
eth0 Link encap:Ethernet HWaddr aa:bb:cc:dd:ee:ff
edited Mar 20 '13 at 10:03
jdthood
10.4k14163
answered Mar 14 '13 at 0:49
Oli♦Oli
222k87563764
According to interfaces(5) it is permitted to list more than one interface name on anautoline. But having a separateautoline for each interface name is more readable.
– jdthood
Mar 20 '13 at 10:02
I made the changes suggested but no changes to the issue at hand. Additionally, I've tried assigning a static IP address, but that has not helped the situation either. I still need to physically log in using a keyboard in order for the eth0 interface to come online.
– Taylor
Apr 1 '13 at 16:32
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%2f267550%2fubuntu-server-12-10-not-obtaining-ip-address-until-a-user-logs-in%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
I've never seen more than one device named on an auto line before. This could be a dud suggestion but try this instead:
auto lo
iface lo inet loopback
auto eth0
iface eth0 inet dhcp
And also check that it is eth0 and not eth1 or eth2. Probably nothing but it doesn't hurt to double-check.
$ ifconfig -a | grep eth
eth0 Link encap:Ethernet HWaddr aa:bb:cc:dd:ee:ff
edited Mar 20 '13 at 10:03
jdthood
10.4k14163
answered Mar 14 '13 at 0:49
Oli♦Oli
222k87563764
According to interfaces(5) it is permitted to list more than one interface name on anautoline. But having a separateautoline for each interface name is more readable.
– jdthood
Mar 20 '13 at 10:02
I made the changes suggested but no changes to the issue at hand. Additionally, I've tried assigning a static IP address, but that has not helped the situation either. I still need to physically log in using a keyboard in order for the eth0 interface to come online.
– Taylor
Apr 1 '13 at 16:32
add a comment |
I've never seen more than one device named on an auto line before. This could be a dud suggestion but try this instead:
auto lo
iface lo inet loopback
auto eth0
iface eth0 inet dhcp
And also check that it is eth0 and not eth1 or eth2. Probably nothing but it doesn't hurt to double-check.
$ ifconfig -a | grep eth
eth0 Link encap:Ethernet HWaddr aa:bb:cc:dd:ee:ff
edited Mar 20 '13 at 10:03
jdthood
10.4k14163
answered Mar 14 '13 at 0:49
Oli♦Oli
222k87563764
According to interfaces(5) it is permitted to list more than one interface name on anautoline. But having a separateautoline for each interface name is more readable.
– jdthood
Mar 20 '13 at 10:02
I made the changes suggested but no changes to the issue at hand. Additionally, I've tried assigning a static IP address, but that has not helped the situation either. I still need to physically log in using a keyboard in order for the eth0 interface to come online.
– Taylor
Apr 1 '13 at 16:32
add a comment |
I've never seen more than one device named on an auto line before. This could be a dud suggestion but try this instead:
auto lo
iface lo inet loopback
auto eth0
iface eth0 inet dhcp
And also check that it is eth0 and not eth1 or eth2. Probably nothing but it doesn't hurt to double-check.
$ ifconfig -a | grep eth
eth0 Link encap:Ethernet HWaddr aa:bb:cc:dd:ee:ff
edited Mar 20 '13 at 10:03
jdthood
10.4k14163
answered Mar 14 '13 at 0:49
Oli♦Oli
222k87563764
I've never seen more than one device named on an auto line before. This could be a dud suggestion but try this instead:
auto lo
iface lo inet loopback
auto eth0
iface eth0 inet dhcp
And also check that it is eth0 and not eth1 or eth2. Probably nothing but it doesn't hurt to double-check.
$ ifconfig -a | grep eth
eth0 Link encap:Ethernet HWaddr aa:bb:cc:dd:ee:ff
edited Mar 20 '13 at 10:03
jdthood
10.4k14163
answered Mar 14 '13 at 0:49
Oli♦Oli
222k87563764
edited Mar 20 '13 at 10:03
jdthood
10.4k14163
edited Mar 20 '13 at 10:03
jdthood
10.4k14163
edited Mar 20 '13 at 10:03
jdthood
10.4k14163
10.4k14163
answered Mar 14 '13 at 0:49
Oli♦Oli
222k87563764
answered Mar 14 '13 at 0:49
Oli♦Oli
222k87563764
answered Mar 14 '13 at 0:49
Oli♦Oli
222k87563764
222k87563764
According to interfaces(5) it is permitted to list more than one interface name on anautoline. But having a separateautoline for each interface name is more readable.
– jdthood
Mar 20 '13 at 10:02
I made the changes suggested but no changes to the issue at hand. Additionally, I've tried assigning a static IP address, but that has not helped the situation either. I still need to physically log in using a keyboard in order for the eth0 interface to come online.
– Taylor
Apr 1 '13 at 16:32
add a comment |
According to interfaces(5) it is permitted to list more than one interface name on anautoline. But having a separateautoline for each interface name is more readable.
– jdthood
Mar 20 '13 at 10:02
I made the changes suggested but no changes to the issue at hand. Additionally, I've tried assigning a static IP address, but that has not helped the situation either. I still need to physically log in using a keyboard in order for the eth0 interface to come online.
– Taylor
Apr 1 '13 at 16:32
According to interfaces(5) it is permitted to list more than one interface name on an
auto line. But having a separate auto line for each interface name is more readable.– jdthood
Mar 20 '13 at 10:02
According to interfaces(5) it is permitted to list more than one interface name on an
auto line. But having a separate auto line for each interface name is more readable.– jdthood
Mar 20 '13 at 10:02
I made the changes suggested but no changes to the issue at hand. Additionally, I've tried assigning a static IP address, but that has not helped the situation either. I still need to physically log in using a keyboard in order for the eth0 interface to come online.
– Taylor
Apr 1 '13 at 16:32
I made the changes suggested but no changes to the issue at hand. Additionally, I've tried assigning a static IP address, but that has not helped the situation either. I still need to physically log in using a keyboard in order for the eth0 interface to come online.
– Taylor
Apr 1 '13 at 16:32
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%2f267550%2fubuntu-server-12-10-not-obtaining-ip-address-until-a-user-logs-in%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
