How to activate IPv4 address on physical Ubuntu Server on home network?
My research group has a multi-compute node HPC running ubuntu server 14.04.5 hosted at a home address (ISP is Comcast Xfinity). Internally, we use only one of the compute nodes. The machine can ping both IPv4 & IPv6 networks, so it seems the ISP is running dual stack and if I'm correct, both an IPv4 and IPv6 address should be assigned. The IPv6 address is available, and that is what we've been using, but the public IPv4 address is not being correctly activated or assigned. We've been using miredo
(a Teredo tunneling service), but that requires that we (1) are on the IPv6 net or (2) use a Teredo tunnel remotely (e.g. use miredo
on a remote Linux machine or use a tunnel broker service). Ideally, we would like to configure the machine/network such that the IPv4 address is also assigned and can be used (from say, a remote Windows machine on the IPv4 net - when IPv6 net is unavailable).
With ifconfig
, the following is the line for em3
(not eth0 for some reason?):
inet addr:10.0.1.27 Bcast:10.0.1.255 Mask:255.255.255.0
This looks like the router assigned (local) address. If I run the following command, I do receive a public facing IPv4 address - so it seems that the ISP is serving one:
$ curl -4 icanhazip.com
Here are the contents of the /etc/network/interfaces
file:
# The loopback network interface
auto lo
iface lo inet loopback
# The primary network interface
auto em3
iface em3 inet dhcp
# This is an autoconfigured IPv6 interface
iface em3 inet6 auto
My best guess from searching through help forums is that either the home router is not correctly serving the IP address or the machine itself is not properly receiving/configuring the address. The individual running the server has not been able to resolve this issue. Any thoughts? I'm happy to provide more information as needed - I know the information that I've provided is pretty limited. Any tools or commands that might help me diagnose the issue?
Thanks
Related questions:
How to set Ubuntu Server to ipv4 network address Here is a virtual server example of a similar situation. Static assignment of the IPv4 address doesn't seem like the correct solution.
IPv4 is not getting configured on Ubuntu in a dualstack (IPv4/IPv6) network Maybe this is relevant? Is there an equivalent to Require IPv4 addressing for this connection to complete
on Ubuntu Server?
how to obtain ipv4 address of ubuntu server running in virtual box along with ipv6? Another virtual box. Solution has a bunch of commands, but I'm not sure. Disabling IPv6 doesn't seem like a good solution either.
networking server ssh network-manager
New contributor
add a comment |
My research group has a multi-compute node HPC running ubuntu server 14.04.5 hosted at a home address (ISP is Comcast Xfinity). Internally, we use only one of the compute nodes. The machine can ping both IPv4 & IPv6 networks, so it seems the ISP is running dual stack and if I'm correct, both an IPv4 and IPv6 address should be assigned. The IPv6 address is available, and that is what we've been using, but the public IPv4 address is not being correctly activated or assigned. We've been using miredo
(a Teredo tunneling service), but that requires that we (1) are on the IPv6 net or (2) use a Teredo tunnel remotely (e.g. use miredo
on a remote Linux machine or use a tunnel broker service). Ideally, we would like to configure the machine/network such that the IPv4 address is also assigned and can be used (from say, a remote Windows machine on the IPv4 net - when IPv6 net is unavailable).
With ifconfig
, the following is the line for em3
(not eth0 for some reason?):
inet addr:10.0.1.27 Bcast:10.0.1.255 Mask:255.255.255.0
This looks like the router assigned (local) address. If I run the following command, I do receive a public facing IPv4 address - so it seems that the ISP is serving one:
$ curl -4 icanhazip.com
Here are the contents of the /etc/network/interfaces
file:
# The loopback network interface
auto lo
iface lo inet loopback
# The primary network interface
auto em3
iface em3 inet dhcp
# This is an autoconfigured IPv6 interface
iface em3 inet6 auto
My best guess from searching through help forums is that either the home router is not correctly serving the IP address or the machine itself is not properly receiving/configuring the address. The individual running the server has not been able to resolve this issue. Any thoughts? I'm happy to provide more information as needed - I know the information that I've provided is pretty limited. Any tools or commands that might help me diagnose the issue?
Thanks
Related questions:
How to set Ubuntu Server to ipv4 network address Here is a virtual server example of a similar situation. Static assignment of the IPv4 address doesn't seem like the correct solution.
IPv4 is not getting configured on Ubuntu in a dualstack (IPv4/IPv6) network Maybe this is relevant? Is there an equivalent to Require IPv4 addressing for this connection to complete
on Ubuntu Server?
how to obtain ipv4 address of ubuntu server running in virtual box along with ipv6? Another virtual box. Solution has a bunch of commands, but I'm not sure. Disabling IPv6 doesn't seem like a good solution either.
networking server ssh network-manager
New contributor
add a comment |
My research group has a multi-compute node HPC running ubuntu server 14.04.5 hosted at a home address (ISP is Comcast Xfinity). Internally, we use only one of the compute nodes. The machine can ping both IPv4 & IPv6 networks, so it seems the ISP is running dual stack and if I'm correct, both an IPv4 and IPv6 address should be assigned. The IPv6 address is available, and that is what we've been using, but the public IPv4 address is not being correctly activated or assigned. We've been using miredo
(a Teredo tunneling service), but that requires that we (1) are on the IPv6 net or (2) use a Teredo tunnel remotely (e.g. use miredo
on a remote Linux machine or use a tunnel broker service). Ideally, we would like to configure the machine/network such that the IPv4 address is also assigned and can be used (from say, a remote Windows machine on the IPv4 net - when IPv6 net is unavailable).
With ifconfig
, the following is the line for em3
(not eth0 for some reason?):
inet addr:10.0.1.27 Bcast:10.0.1.255 Mask:255.255.255.0
This looks like the router assigned (local) address. If I run the following command, I do receive a public facing IPv4 address - so it seems that the ISP is serving one:
$ curl -4 icanhazip.com
Here are the contents of the /etc/network/interfaces
file:
# The loopback network interface
auto lo
iface lo inet loopback
# The primary network interface
auto em3
iface em3 inet dhcp
# This is an autoconfigured IPv6 interface
iface em3 inet6 auto
My best guess from searching through help forums is that either the home router is not correctly serving the IP address or the machine itself is not properly receiving/configuring the address. The individual running the server has not been able to resolve this issue. Any thoughts? I'm happy to provide more information as needed - I know the information that I've provided is pretty limited. Any tools or commands that might help me diagnose the issue?
Thanks
Related questions:
How to set Ubuntu Server to ipv4 network address Here is a virtual server example of a similar situation. Static assignment of the IPv4 address doesn't seem like the correct solution.
IPv4 is not getting configured on Ubuntu in a dualstack (IPv4/IPv6) network Maybe this is relevant? Is there an equivalent to Require IPv4 addressing for this connection to complete
on Ubuntu Server?
how to obtain ipv4 address of ubuntu server running in virtual box along with ipv6? Another virtual box. Solution has a bunch of commands, but I'm not sure. Disabling IPv6 doesn't seem like a good solution either.
networking server ssh network-manager
New contributor
My research group has a multi-compute node HPC running ubuntu server 14.04.5 hosted at a home address (ISP is Comcast Xfinity). Internally, we use only one of the compute nodes. The machine can ping both IPv4 & IPv6 networks, so it seems the ISP is running dual stack and if I'm correct, both an IPv4 and IPv6 address should be assigned. The IPv6 address is available, and that is what we've been using, but the public IPv4 address is not being correctly activated or assigned. We've been using miredo
(a Teredo tunneling service), but that requires that we (1) are on the IPv6 net or (2) use a Teredo tunnel remotely (e.g. use miredo
on a remote Linux machine or use a tunnel broker service). Ideally, we would like to configure the machine/network such that the IPv4 address is also assigned and can be used (from say, a remote Windows machine on the IPv4 net - when IPv6 net is unavailable).
With ifconfig
, the following is the line for em3
(not eth0 for some reason?):
inet addr:10.0.1.27 Bcast:10.0.1.255 Mask:255.255.255.0
This looks like the router assigned (local) address. If I run the following command, I do receive a public facing IPv4 address - so it seems that the ISP is serving one:
$ curl -4 icanhazip.com
Here are the contents of the /etc/network/interfaces
file:
# The loopback network interface
auto lo
iface lo inet loopback
# The primary network interface
auto em3
iface em3 inet dhcp
# This is an autoconfigured IPv6 interface
iface em3 inet6 auto
My best guess from searching through help forums is that either the home router is not correctly serving the IP address or the machine itself is not properly receiving/configuring the address. The individual running the server has not been able to resolve this issue. Any thoughts? I'm happy to provide more information as needed - I know the information that I've provided is pretty limited. Any tools or commands that might help me diagnose the issue?
Thanks
Related questions:
How to set Ubuntu Server to ipv4 network address Here is a virtual server example of a similar situation. Static assignment of the IPv4 address doesn't seem like the correct solution.
IPv4 is not getting configured on Ubuntu in a dualstack (IPv4/IPv6) network Maybe this is relevant? Is there an equivalent to Require IPv4 addressing for this connection to complete
on Ubuntu Server?
how to obtain ipv4 address of ubuntu server running in virtual box along with ipv6? Another virtual box. Solution has a bunch of commands, but I'm not sure. Disabling IPv6 doesn't seem like a good solution either.
networking server ssh network-manager
networking server ssh network-manager
New contributor
New contributor
edited 2 days ago
fkraiem
8,86431829
8,86431829
New contributor
asked Jan 25 at 23:08
hugeyakmanhugeyakman
111
111
New contributor
New contributor
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
My best guess from searching through help forums is that either the home router is not correctly serving the IP address or the machine itself is not properly receiving/configuring the address.
The IP's you posted (10.0.1.27
) is RFC1918 address, commonly known as private IPs. They are commonly used for NAT.
You have a router that performs NATing in front of your computer, which explains the behavior. To get a public IP at the Linux machine, you have to turn of the NAT function of your router. Please refer to the manual of the router for instructions on this.
Alternatively, you may use port forwarding to forward traffic to the machine in question.
Thanks. This is a big help! I'll post updates as they come through.
– hugeyakman
8 hours ago
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
});
}
});
hugeyakman is a new contributor. Be nice, and check out our Code of Conduct.
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%2f1112948%2fhow-to-activate-ipv4-address-on-physical-ubuntu-server-on-home-network%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
My best guess from searching through help forums is that either the home router is not correctly serving the IP address or the machine itself is not properly receiving/configuring the address.
The IP's you posted (10.0.1.27
) is RFC1918 address, commonly known as private IPs. They are commonly used for NAT.
You have a router that performs NATing in front of your computer, which explains the behavior. To get a public IP at the Linux machine, you have to turn of the NAT function of your router. Please refer to the manual of the router for instructions on this.
Alternatively, you may use port forwarding to forward traffic to the machine in question.
Thanks. This is a big help! I'll post updates as they come through.
– hugeyakman
8 hours ago
add a comment |
My best guess from searching through help forums is that either the home router is not correctly serving the IP address or the machine itself is not properly receiving/configuring the address.
The IP's you posted (10.0.1.27
) is RFC1918 address, commonly known as private IPs. They are commonly used for NAT.
You have a router that performs NATing in front of your computer, which explains the behavior. To get a public IP at the Linux machine, you have to turn of the NAT function of your router. Please refer to the manual of the router for instructions on this.
Alternatively, you may use port forwarding to forward traffic to the machine in question.
Thanks. This is a big help! I'll post updates as they come through.
– hugeyakman
8 hours ago
add a comment |
My best guess from searching through help forums is that either the home router is not correctly serving the IP address or the machine itself is not properly receiving/configuring the address.
The IP's you posted (10.0.1.27
) is RFC1918 address, commonly known as private IPs. They are commonly used for NAT.
You have a router that performs NATing in front of your computer, which explains the behavior. To get a public IP at the Linux machine, you have to turn of the NAT function of your router. Please refer to the manual of the router for instructions on this.
Alternatively, you may use port forwarding to forward traffic to the machine in question.
My best guess from searching through help forums is that either the home router is not correctly serving the IP address or the machine itself is not properly receiving/configuring the address.
The IP's you posted (10.0.1.27
) is RFC1918 address, commonly known as private IPs. They are commonly used for NAT.
You have a router that performs NATing in front of your computer, which explains the behavior. To get a public IP at the Linux machine, you have to turn of the NAT function of your router. Please refer to the manual of the router for instructions on this.
Alternatively, you may use port forwarding to forward traffic to the machine in question.
answered yesterday
vidarlovidarlo
10.1k52447
10.1k52447
Thanks. This is a big help! I'll post updates as they come through.
– hugeyakman
8 hours ago
add a comment |
Thanks. This is a big help! I'll post updates as they come through.
– hugeyakman
8 hours ago
Thanks. This is a big help! I'll post updates as they come through.
– hugeyakman
8 hours ago
Thanks. This is a big help! I'll post updates as they come through.
– hugeyakman
8 hours ago
add a comment |
hugeyakman is a new contributor. Be nice, and check out our Code of Conduct.
hugeyakman is a new contributor. Be nice, and check out our Code of Conduct.
hugeyakman is a new contributor. Be nice, and check out our Code of Conduct.
hugeyakman is a new contributor. Be nice, and check out our Code of Conduct.
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%2f1112948%2fhow-to-activate-ipv4-address-on-physical-ubuntu-server-on-home-network%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