Debian 9.6 not using static IP defined in interfaces
I have the following configuration:
root@pihole:~# cat /etc/network/interfaces
auto lo
iface lo inet loopback
allow-hotplug enp0s4
iface enp0s4 inet static
address 192.168.2.225
netmask 255.255.255.0
gateway 192.168.2.1
The IP is somehow getting assigned to 192.168.2.110 when it should be .225:
root@pihole:~# systemctl restart networking.service
root@pihole:~# ifconfig
enp0s4: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.2.110 netmask 255.255.255.0 broadcast 192.168.2.255
inet6 fe80::2a0:98ff:fe2a:67fe prefixlen 64 scopeid 0x20<link>
ether 00:a0:98:2a:67:0e txqueuelen 1000 (Ethernet)
RX packets 5322438 bytes 1348940213 (1.2 GiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 333698 bytes 66021804 (62.9 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
Any suggestions why this is? This configuration was working... then sometime a few days later it changed to .110.
Edit: Adding output of 'ip a' command, as this shows the IP is set as 'secondary':
2: enp0s4: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 00:a0:98:2a:67:0e brd ff:ff:ff:ff:ff:ff
inet 192.168.2.110/24 brd 192.168.2.255 scope global enp0s4
valid_lft forever preferred_lft forever
inet 192.168.2.225/24 brd 192.168.2.255 scope global secondary enp0s4
valid_lft forever preferred_lft forever
inet6 fe80::2a0:98ff:fe2a:670e/64 scope link
valid_lft forever preferred_lft forever
debian ip
add a comment |
I have the following configuration:
root@pihole:~# cat /etc/network/interfaces
auto lo
iface lo inet loopback
allow-hotplug enp0s4
iface enp0s4 inet static
address 192.168.2.225
netmask 255.255.255.0
gateway 192.168.2.1
The IP is somehow getting assigned to 192.168.2.110 when it should be .225:
root@pihole:~# systemctl restart networking.service
root@pihole:~# ifconfig
enp0s4: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.2.110 netmask 255.255.255.0 broadcast 192.168.2.255
inet6 fe80::2a0:98ff:fe2a:67fe prefixlen 64 scopeid 0x20<link>
ether 00:a0:98:2a:67:0e txqueuelen 1000 (Ethernet)
RX packets 5322438 bytes 1348940213 (1.2 GiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 333698 bytes 66021804 (62.9 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
Any suggestions why this is? This configuration was working... then sometime a few days later it changed to .110.
Edit: Adding output of 'ip a' command, as this shows the IP is set as 'secondary':
2: enp0s4: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 00:a0:98:2a:67:0e brd ff:ff:ff:ff:ff:ff
inet 192.168.2.110/24 brd 192.168.2.255 scope global enp0s4
valid_lft forever preferred_lft forever
inet 192.168.2.225/24 brd 192.168.2.255 scope global secondary enp0s4
valid_lft forever preferred_lft forever
inet6 fe80::2a0:98ff:fe2a:670e/64 scope link
valid_lft forever preferred_lft forever
debian ip
What is the status ofifup@enp0s4.service
and ofsystemd-networkd.service
?
– grawity
Dec 26 '18 at 15:21
I'm not sure what you mean? It shows 'up' in ifconfig.
– Ted Scheckler
Dec 26 '18 at 15:24
I've also added the output of "ip a" which shows the .225 IP as secondary... I have no idea what this means
– Ted Scheckler
Dec 26 '18 at 15:30
add a comment |
I have the following configuration:
root@pihole:~# cat /etc/network/interfaces
auto lo
iface lo inet loopback
allow-hotplug enp0s4
iface enp0s4 inet static
address 192.168.2.225
netmask 255.255.255.0
gateway 192.168.2.1
The IP is somehow getting assigned to 192.168.2.110 when it should be .225:
root@pihole:~# systemctl restart networking.service
root@pihole:~# ifconfig
enp0s4: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.2.110 netmask 255.255.255.0 broadcast 192.168.2.255
inet6 fe80::2a0:98ff:fe2a:67fe prefixlen 64 scopeid 0x20<link>
ether 00:a0:98:2a:67:0e txqueuelen 1000 (Ethernet)
RX packets 5322438 bytes 1348940213 (1.2 GiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 333698 bytes 66021804 (62.9 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
Any suggestions why this is? This configuration was working... then sometime a few days later it changed to .110.
Edit: Adding output of 'ip a' command, as this shows the IP is set as 'secondary':
2: enp0s4: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 00:a0:98:2a:67:0e brd ff:ff:ff:ff:ff:ff
inet 192.168.2.110/24 brd 192.168.2.255 scope global enp0s4
valid_lft forever preferred_lft forever
inet 192.168.2.225/24 brd 192.168.2.255 scope global secondary enp0s4
valid_lft forever preferred_lft forever
inet6 fe80::2a0:98ff:fe2a:670e/64 scope link
valid_lft forever preferred_lft forever
debian ip
I have the following configuration:
root@pihole:~# cat /etc/network/interfaces
auto lo
iface lo inet loopback
allow-hotplug enp0s4
iface enp0s4 inet static
address 192.168.2.225
netmask 255.255.255.0
gateway 192.168.2.1
The IP is somehow getting assigned to 192.168.2.110 when it should be .225:
root@pihole:~# systemctl restart networking.service
root@pihole:~# ifconfig
enp0s4: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.2.110 netmask 255.255.255.0 broadcast 192.168.2.255
inet6 fe80::2a0:98ff:fe2a:67fe prefixlen 64 scopeid 0x20<link>
ether 00:a0:98:2a:67:0e txqueuelen 1000 (Ethernet)
RX packets 5322438 bytes 1348940213 (1.2 GiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 333698 bytes 66021804 (62.9 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
Any suggestions why this is? This configuration was working... then sometime a few days later it changed to .110.
Edit: Adding output of 'ip a' command, as this shows the IP is set as 'secondary':
2: enp0s4: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 00:a0:98:2a:67:0e brd ff:ff:ff:ff:ff:ff
inet 192.168.2.110/24 brd 192.168.2.255 scope global enp0s4
valid_lft forever preferred_lft forever
inet 192.168.2.225/24 brd 192.168.2.255 scope global secondary enp0s4
valid_lft forever preferred_lft forever
inet6 fe80::2a0:98ff:fe2a:670e/64 scope link
valid_lft forever preferred_lft forever
debian ip
debian ip
edited Dec 26 '18 at 15:29
Ted Scheckler
asked Dec 26 '18 at 15:15
Ted SchecklerTed Scheckler
1237
1237
What is the status ofifup@enp0s4.service
and ofsystemd-networkd.service
?
– grawity
Dec 26 '18 at 15:21
I'm not sure what you mean? It shows 'up' in ifconfig.
– Ted Scheckler
Dec 26 '18 at 15:24
I've also added the output of "ip a" which shows the .225 IP as secondary... I have no idea what this means
– Ted Scheckler
Dec 26 '18 at 15:30
add a comment |
What is the status ofifup@enp0s4.service
and ofsystemd-networkd.service
?
– grawity
Dec 26 '18 at 15:21
I'm not sure what you mean? It shows 'up' in ifconfig.
– Ted Scheckler
Dec 26 '18 at 15:24
I've also added the output of "ip a" which shows the .225 IP as secondary... I have no idea what this means
– Ted Scheckler
Dec 26 '18 at 15:30
What is the status of
ifup@enp0s4.service
and of systemd-networkd.service
?– grawity
Dec 26 '18 at 15:21
What is the status of
ifup@enp0s4.service
and of systemd-networkd.service
?– grawity
Dec 26 '18 at 15:21
I'm not sure what you mean? It shows 'up' in ifconfig.
– Ted Scheckler
Dec 26 '18 at 15:24
I'm not sure what you mean? It shows 'up' in ifconfig.
– Ted Scheckler
Dec 26 '18 at 15:24
I've also added the output of "ip a" which shows the .225 IP as secondary... I have no idea what this means
– Ted Scheckler
Dec 26 '18 at 15:30
I've also added the output of "ip a" which shows the .225 IP as secondary... I have no idea what this means
– Ted Scheckler
Dec 26 '18 at 15:30
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
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%2fsuperuser.com%2fquestions%2f1387842%2fdebian-9-6-not-using-static-ip-defined-in-interfaces%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Super User!
- 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%2fsuperuser.com%2fquestions%2f1387842%2fdebian-9-6-not-using-static-ip-defined-in-interfaces%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
What is the status of
ifup@enp0s4.service
and ofsystemd-networkd.service
?– grawity
Dec 26 '18 at 15:21
I'm not sure what you mean? It shows 'up' in ifconfig.
– Ted Scheckler
Dec 26 '18 at 15:24
I've also added the output of "ip a" which shows the .225 IP as secondary... I have no idea what this means
– Ted Scheckler
Dec 26 '18 at 15:30