Why i have an ip for ssh and ifconfig shows another one in eth0?
OS: Ubuntu 16.04 LTS (GNU/Linux 4.4.0-1009-raspi2 armv7l)
So when i connect to my machine through ssh from windows with putty, i am able to do it with the IP 192.168.0.60.
Now when im listing my devices from the router admin web, it shows that its using the IP 192.168.0.109.
This is the output for the ifconfig cmd.
eth0 Link encap:Ethernet HWaddr b8:27:eb:86:e1:e0
inet addr:192.168.0.109 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::ba27:ebff:fe86:e1e0/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:2233 errors:0 dropped:0 overruns:0 frame:0
TX packets:1067 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:163132 (163.1 KB) TX bytes:167801 (167.8 KB)
And this is what i have in etc/network/interfaces
auto eth0
iface eth0 inet static
address 192.168.0.60
netmask 255.255.255.0
gateway 192.168.0.1
dns-nameserver 8.8.8.8
dns-nameserver 8.8.4.4
Another fact to think about is that when i restart the networking service, it throws the following error:
Job for networking.service failed because the control process exited with
error code. See "systemctl status networking.service" and "journalctl -xe" for details.
This is the systemctl status networking.service output:
networking.service - Raise network interfaces
Loaded: loaded (/lib/systemd/system/networking.service; enabled; vendor preset: enabled)
Drop-In: /run/systemd/generator/networking.service.d
└─50-insserv.conf-$network.conf
Active: failed (Result: exit-code) since Thu 2017-03-23 15:31:59 UTC; 2min 1s ago
Docs: man:interfaces(5)
Process: 2046 ExecStart=/sbin/ifup -a --read-environment (code=exited, status=1/FAILURE)
Process: 2038 ExecStartPre=/bin/sh -c [ "$CONFIGURE_INTERFACES" != "no" ] && [ -n "$(ifquery --read-environment --list
Main PID: 2046 (code=exited, status=1/FAILURE)
Mar 23 15:31:58 ubuntu dhclient[2065]: DHCPREQUEST of 192.168.0.109 on eth0 to 255.255.255.255 port 67 (xid=0x6fc3c068)
Mar 23 15:31:58 ubuntu dhclient[2065]: DHCPACK of 192.168.0.109 from 192.168.0.1
Mar 23 15:31:58 ubuntu ifup[2046]: RTNETLINK answers: File exists
Mar 23 15:31:59 ubuntu ifup[2046]: bound to 192.168.0.109 -- renewal in 657200529 seconds.
Mar 23 15:31:59 ubuntu ifup[2046]: RTNETLINK answers: File exists
Mar 23 15:31:59 ubuntu ifup[2046]: Failed to bring up eth0.
Mar 23 15:31:59 ubuntu systemd[1]: networking.service: Main process exited, code=exited, status=1/FAILURE
Mar 23 15:31:59 ubuntu systemd[1]: Failed to start Raise network interfaces.
Mar 23 15:31:59 ubuntu systemd[1]: networking.service: Unit entered failed state.
Mar 23 15:31:59 ubuntu systemd[1]: networking.service: Failed with result 'exit-code'.
Notice the following line:
Mar 23 15:31:59 ubuntu systemd[1]: Failed to start Raise network interfaces.
Can somebody tell me what is going on and how i could fix that?
Edit: Results of route -n:
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 192.168.0.1 0.0.0.0 UG 0 0 0 eth0
192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
networking 16.04 server ssh ip
add a comment |
OS: Ubuntu 16.04 LTS (GNU/Linux 4.4.0-1009-raspi2 armv7l)
So when i connect to my machine through ssh from windows with putty, i am able to do it with the IP 192.168.0.60.
Now when im listing my devices from the router admin web, it shows that its using the IP 192.168.0.109.
This is the output for the ifconfig cmd.
eth0 Link encap:Ethernet HWaddr b8:27:eb:86:e1:e0
inet addr:192.168.0.109 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::ba27:ebff:fe86:e1e0/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:2233 errors:0 dropped:0 overruns:0 frame:0
TX packets:1067 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:163132 (163.1 KB) TX bytes:167801 (167.8 KB)
And this is what i have in etc/network/interfaces
auto eth0
iface eth0 inet static
address 192.168.0.60
netmask 255.255.255.0
gateway 192.168.0.1
dns-nameserver 8.8.8.8
dns-nameserver 8.8.4.4
Another fact to think about is that when i restart the networking service, it throws the following error:
Job for networking.service failed because the control process exited with
error code. See "systemctl status networking.service" and "journalctl -xe" for details.
This is the systemctl status networking.service output:
networking.service - Raise network interfaces
Loaded: loaded (/lib/systemd/system/networking.service; enabled; vendor preset: enabled)
Drop-In: /run/systemd/generator/networking.service.d
└─50-insserv.conf-$network.conf
Active: failed (Result: exit-code) since Thu 2017-03-23 15:31:59 UTC; 2min 1s ago
Docs: man:interfaces(5)
Process: 2046 ExecStart=/sbin/ifup -a --read-environment (code=exited, status=1/FAILURE)
Process: 2038 ExecStartPre=/bin/sh -c [ "$CONFIGURE_INTERFACES" != "no" ] && [ -n "$(ifquery --read-environment --list
Main PID: 2046 (code=exited, status=1/FAILURE)
Mar 23 15:31:58 ubuntu dhclient[2065]: DHCPREQUEST of 192.168.0.109 on eth0 to 255.255.255.255 port 67 (xid=0x6fc3c068)
Mar 23 15:31:58 ubuntu dhclient[2065]: DHCPACK of 192.168.0.109 from 192.168.0.1
Mar 23 15:31:58 ubuntu ifup[2046]: RTNETLINK answers: File exists
Mar 23 15:31:59 ubuntu ifup[2046]: bound to 192.168.0.109 -- renewal in 657200529 seconds.
Mar 23 15:31:59 ubuntu ifup[2046]: RTNETLINK answers: File exists
Mar 23 15:31:59 ubuntu ifup[2046]: Failed to bring up eth0.
Mar 23 15:31:59 ubuntu systemd[1]: networking.service: Main process exited, code=exited, status=1/FAILURE
Mar 23 15:31:59 ubuntu systemd[1]: Failed to start Raise network interfaces.
Mar 23 15:31:59 ubuntu systemd[1]: networking.service: Unit entered failed state.
Mar 23 15:31:59 ubuntu systemd[1]: networking.service: Failed with result 'exit-code'.
Notice the following line:
Mar 23 15:31:59 ubuntu systemd[1]: Failed to start Raise network interfaces.
Can somebody tell me what is going on and how i could fix that?
Edit: Results of route -n:
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 192.168.0.1 0.0.0.0 UG 0 0 0 eth0
192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
networking 16.04 server ssh ip
check if you have configured it with DHCP and also specified an static address in the cfg.
– Puffy
Feb 3 at 0:39
add a comment |
OS: Ubuntu 16.04 LTS (GNU/Linux 4.4.0-1009-raspi2 armv7l)
So when i connect to my machine through ssh from windows with putty, i am able to do it with the IP 192.168.0.60.
Now when im listing my devices from the router admin web, it shows that its using the IP 192.168.0.109.
This is the output for the ifconfig cmd.
eth0 Link encap:Ethernet HWaddr b8:27:eb:86:e1:e0
inet addr:192.168.0.109 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::ba27:ebff:fe86:e1e0/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:2233 errors:0 dropped:0 overruns:0 frame:0
TX packets:1067 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:163132 (163.1 KB) TX bytes:167801 (167.8 KB)
And this is what i have in etc/network/interfaces
auto eth0
iface eth0 inet static
address 192.168.0.60
netmask 255.255.255.0
gateway 192.168.0.1
dns-nameserver 8.8.8.8
dns-nameserver 8.8.4.4
Another fact to think about is that when i restart the networking service, it throws the following error:
Job for networking.service failed because the control process exited with
error code. See "systemctl status networking.service" and "journalctl -xe" for details.
This is the systemctl status networking.service output:
networking.service - Raise network interfaces
Loaded: loaded (/lib/systemd/system/networking.service; enabled; vendor preset: enabled)
Drop-In: /run/systemd/generator/networking.service.d
└─50-insserv.conf-$network.conf
Active: failed (Result: exit-code) since Thu 2017-03-23 15:31:59 UTC; 2min 1s ago
Docs: man:interfaces(5)
Process: 2046 ExecStart=/sbin/ifup -a --read-environment (code=exited, status=1/FAILURE)
Process: 2038 ExecStartPre=/bin/sh -c [ "$CONFIGURE_INTERFACES" != "no" ] && [ -n "$(ifquery --read-environment --list
Main PID: 2046 (code=exited, status=1/FAILURE)
Mar 23 15:31:58 ubuntu dhclient[2065]: DHCPREQUEST of 192.168.0.109 on eth0 to 255.255.255.255 port 67 (xid=0x6fc3c068)
Mar 23 15:31:58 ubuntu dhclient[2065]: DHCPACK of 192.168.0.109 from 192.168.0.1
Mar 23 15:31:58 ubuntu ifup[2046]: RTNETLINK answers: File exists
Mar 23 15:31:59 ubuntu ifup[2046]: bound to 192.168.0.109 -- renewal in 657200529 seconds.
Mar 23 15:31:59 ubuntu ifup[2046]: RTNETLINK answers: File exists
Mar 23 15:31:59 ubuntu ifup[2046]: Failed to bring up eth0.
Mar 23 15:31:59 ubuntu systemd[1]: networking.service: Main process exited, code=exited, status=1/FAILURE
Mar 23 15:31:59 ubuntu systemd[1]: Failed to start Raise network interfaces.
Mar 23 15:31:59 ubuntu systemd[1]: networking.service: Unit entered failed state.
Mar 23 15:31:59 ubuntu systemd[1]: networking.service: Failed with result 'exit-code'.
Notice the following line:
Mar 23 15:31:59 ubuntu systemd[1]: Failed to start Raise network interfaces.
Can somebody tell me what is going on and how i could fix that?
Edit: Results of route -n:
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 192.168.0.1 0.0.0.0 UG 0 0 0 eth0
192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
networking 16.04 server ssh ip
OS: Ubuntu 16.04 LTS (GNU/Linux 4.4.0-1009-raspi2 armv7l)
So when i connect to my machine through ssh from windows with putty, i am able to do it with the IP 192.168.0.60.
Now when im listing my devices from the router admin web, it shows that its using the IP 192.168.0.109.
This is the output for the ifconfig cmd.
eth0 Link encap:Ethernet HWaddr b8:27:eb:86:e1:e0
inet addr:192.168.0.109 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::ba27:ebff:fe86:e1e0/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:2233 errors:0 dropped:0 overruns:0 frame:0
TX packets:1067 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:163132 (163.1 KB) TX bytes:167801 (167.8 KB)
And this is what i have in etc/network/interfaces
auto eth0
iface eth0 inet static
address 192.168.0.60
netmask 255.255.255.0
gateway 192.168.0.1
dns-nameserver 8.8.8.8
dns-nameserver 8.8.4.4
Another fact to think about is that when i restart the networking service, it throws the following error:
Job for networking.service failed because the control process exited with
error code. See "systemctl status networking.service" and "journalctl -xe" for details.
This is the systemctl status networking.service output:
networking.service - Raise network interfaces
Loaded: loaded (/lib/systemd/system/networking.service; enabled; vendor preset: enabled)
Drop-In: /run/systemd/generator/networking.service.d
└─50-insserv.conf-$network.conf
Active: failed (Result: exit-code) since Thu 2017-03-23 15:31:59 UTC; 2min 1s ago
Docs: man:interfaces(5)
Process: 2046 ExecStart=/sbin/ifup -a --read-environment (code=exited, status=1/FAILURE)
Process: 2038 ExecStartPre=/bin/sh -c [ "$CONFIGURE_INTERFACES" != "no" ] && [ -n "$(ifquery --read-environment --list
Main PID: 2046 (code=exited, status=1/FAILURE)
Mar 23 15:31:58 ubuntu dhclient[2065]: DHCPREQUEST of 192.168.0.109 on eth0 to 255.255.255.255 port 67 (xid=0x6fc3c068)
Mar 23 15:31:58 ubuntu dhclient[2065]: DHCPACK of 192.168.0.109 from 192.168.0.1
Mar 23 15:31:58 ubuntu ifup[2046]: RTNETLINK answers: File exists
Mar 23 15:31:59 ubuntu ifup[2046]: bound to 192.168.0.109 -- renewal in 657200529 seconds.
Mar 23 15:31:59 ubuntu ifup[2046]: RTNETLINK answers: File exists
Mar 23 15:31:59 ubuntu ifup[2046]: Failed to bring up eth0.
Mar 23 15:31:59 ubuntu systemd[1]: networking.service: Main process exited, code=exited, status=1/FAILURE
Mar 23 15:31:59 ubuntu systemd[1]: Failed to start Raise network interfaces.
Mar 23 15:31:59 ubuntu systemd[1]: networking.service: Unit entered failed state.
Mar 23 15:31:59 ubuntu systemd[1]: networking.service: Failed with result 'exit-code'.
Notice the following line:
Mar 23 15:31:59 ubuntu systemd[1]: Failed to start Raise network interfaces.
Can somebody tell me what is going on and how i could fix that?
Edit: Results of route -n:
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 192.168.0.1 0.0.0.0 UG 0 0 0 eth0
192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
networking 16.04 server ssh ip
networking 16.04 server ssh ip
edited Mar 23 '17 at 18:47
JD0001
asked Mar 23 '17 at 15:37
JD0001JD0001
12
12
check if you have configured it with DHCP and also specified an static address in the cfg.
– Puffy
Feb 3 at 0:39
add a comment |
check if you have configured it with DHCP and also specified an static address in the cfg.
– Puffy
Feb 3 at 0:39
check if you have configured it with DHCP and also specified an static address in the cfg.
– Puffy
Feb 3 at 0:39
check if you have configured it with DHCP and also specified an static address in the cfg.
– Puffy
Feb 3 at 0:39
add a comment |
2 Answers
2
active
oldest
votes
I have found that if you're making use of the /etc/network/interfaces file within Ubuntu that it's best to disable Ubuntu's NetworkManager. My colleagues and I have experience weird issues when you've set static IPs and such in the config file but then NetworkManager likes to do its own thing.
Check out the Stopping and Disabling NetworkManager on the Ubuntu help site.
Though since you can access the Static IP even though your interface is receiving a dynamic one, it would be interesting to see what your routing table is like: route -n
I edited the ask and added the output of route -n
– JD0001
Mar 23 '17 at 19:15
So i disabled the network manager as the post says and im still getting the same error when restarting the networking service
– JD0001
Mar 23 '17 at 19:19
add a comment |
Potentially you had a static IP address defined but also had DHCP running.
Instead of using ifconfig, see if there are multiple ip addresses configured on the interface via
ip addr show eth0
See if there is a dhcp service running
ps -ef | grep dhcp
You can disable the dhcp service via
sudo systemctl disable dhcpcd
Then i would say restart the device and see if the secondary IP address has disappeared.
This could have happened because your DNS (/etc/resolv.conf) is setup correctly and points to your DHCP server to grab an IP
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%2f896082%2fwhy-i-have-an-ip-for-ssh-and-ifconfig-shows-another-one-in-eth0%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
I have found that if you're making use of the /etc/network/interfaces file within Ubuntu that it's best to disable Ubuntu's NetworkManager. My colleagues and I have experience weird issues when you've set static IPs and such in the config file but then NetworkManager likes to do its own thing.
Check out the Stopping and Disabling NetworkManager on the Ubuntu help site.
Though since you can access the Static IP even though your interface is receiving a dynamic one, it would be interesting to see what your routing table is like: route -n
I edited the ask and added the output of route -n
– JD0001
Mar 23 '17 at 19:15
So i disabled the network manager as the post says and im still getting the same error when restarting the networking service
– JD0001
Mar 23 '17 at 19:19
add a comment |
I have found that if you're making use of the /etc/network/interfaces file within Ubuntu that it's best to disable Ubuntu's NetworkManager. My colleagues and I have experience weird issues when you've set static IPs and such in the config file but then NetworkManager likes to do its own thing.
Check out the Stopping and Disabling NetworkManager on the Ubuntu help site.
Though since you can access the Static IP even though your interface is receiving a dynamic one, it would be interesting to see what your routing table is like: route -n
I edited the ask and added the output of route -n
– JD0001
Mar 23 '17 at 19:15
So i disabled the network manager as the post says and im still getting the same error when restarting the networking service
– JD0001
Mar 23 '17 at 19:19
add a comment |
I have found that if you're making use of the /etc/network/interfaces file within Ubuntu that it's best to disable Ubuntu's NetworkManager. My colleagues and I have experience weird issues when you've set static IPs and such in the config file but then NetworkManager likes to do its own thing.
Check out the Stopping and Disabling NetworkManager on the Ubuntu help site.
Though since you can access the Static IP even though your interface is receiving a dynamic one, it would be interesting to see what your routing table is like: route -n
I have found that if you're making use of the /etc/network/interfaces file within Ubuntu that it's best to disable Ubuntu's NetworkManager. My colleagues and I have experience weird issues when you've set static IPs and such in the config file but then NetworkManager likes to do its own thing.
Check out the Stopping and Disabling NetworkManager on the Ubuntu help site.
Though since you can access the Static IP even though your interface is receiving a dynamic one, it would be interesting to see what your routing table is like: route -n
answered Mar 23 '17 at 17:06
OnyxdragunOnyxdragun
134
134
I edited the ask and added the output of route -n
– JD0001
Mar 23 '17 at 19:15
So i disabled the network manager as the post says and im still getting the same error when restarting the networking service
– JD0001
Mar 23 '17 at 19:19
add a comment |
I edited the ask and added the output of route -n
– JD0001
Mar 23 '17 at 19:15
So i disabled the network manager as the post says and im still getting the same error when restarting the networking service
– JD0001
Mar 23 '17 at 19:19
I edited the ask and added the output of route -n
– JD0001
Mar 23 '17 at 19:15
I edited the ask and added the output of route -n
– JD0001
Mar 23 '17 at 19:15
So i disabled the network manager as the post says and im still getting the same error when restarting the networking service
– JD0001
Mar 23 '17 at 19:19
So i disabled the network manager as the post says and im still getting the same error when restarting the networking service
– JD0001
Mar 23 '17 at 19:19
add a comment |
Potentially you had a static IP address defined but also had DHCP running.
Instead of using ifconfig, see if there are multiple ip addresses configured on the interface via
ip addr show eth0
See if there is a dhcp service running
ps -ef | grep dhcp
You can disable the dhcp service via
sudo systemctl disable dhcpcd
Then i would say restart the device and see if the secondary IP address has disappeared.
This could have happened because your DNS (/etc/resolv.conf) is setup correctly and points to your DHCP server to grab an IP
add a comment |
Potentially you had a static IP address defined but also had DHCP running.
Instead of using ifconfig, see if there are multiple ip addresses configured on the interface via
ip addr show eth0
See if there is a dhcp service running
ps -ef | grep dhcp
You can disable the dhcp service via
sudo systemctl disable dhcpcd
Then i would say restart the device and see if the secondary IP address has disappeared.
This could have happened because your DNS (/etc/resolv.conf) is setup correctly and points to your DHCP server to grab an IP
add a comment |
Potentially you had a static IP address defined but also had DHCP running.
Instead of using ifconfig, see if there are multiple ip addresses configured on the interface via
ip addr show eth0
See if there is a dhcp service running
ps -ef | grep dhcp
You can disable the dhcp service via
sudo systemctl disable dhcpcd
Then i would say restart the device and see if the secondary IP address has disappeared.
This could have happened because your DNS (/etc/resolv.conf) is setup correctly and points to your DHCP server to grab an IP
Potentially you had a static IP address defined but also had DHCP running.
Instead of using ifconfig, see if there are multiple ip addresses configured on the interface via
ip addr show eth0
See if there is a dhcp service running
ps -ef | grep dhcp
You can disable the dhcp service via
sudo systemctl disable dhcpcd
Then i would say restart the device and see if the secondary IP address has disappeared.
This could have happened because your DNS (/etc/resolv.conf) is setup correctly and points to your DHCP server to grab an IP
answered Feb 27 at 8:00
A KingscoteA Kingscote
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%2f896082%2fwhy-i-have-an-ip-for-ssh-and-ifconfig-shows-another-one-in-eth0%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
check if you have configured it with DHCP and also specified an static address in the cfg.
– Puffy
Feb 3 at 0:39