Missing /etc/network/interfaces in my debian 9Debian network bridge configuration - /etc/network/interfacesIs...
Optimising a list searching algorithm
Print a physical multiplication table
Can a wizard cast a spell during their first turn of combat if they initiated combat by releasing a readied spell?
Pronounciation of the combination "st" in spanish accents
What (if any) is the reason to buy in small local stores?
Writing in a Christian voice
Worshiping one God at a time?
Help prove this basic trig identity please!
HP P840 HDD RAID 5 many strange drive failures
Brake pads destroying wheels
Can other pieces capture a threatening piece and prevent a checkmate?
Why are there no stars visible in cislunar space?
Bash - pair each line of file
What does Jesus mean regarding "Raca," and "you fool?" - is he contrasting them?
PTIJ What is the inyan of the Konami code in Uncle Moishy's song?
Variable completely messes up echoed string
Are dual Irish/British citizens bound by the 90/180 day rule when travelling in the EU after Brexit?
What does "mu" mean as an interjection?
What is the term when voters “dishonestly” choose something that they do not want to choose?
In what cases must I use 了 and in what cases not?
What does Deadpool mean by "left the house in that shirt"?
What does "^L" mean in C?
How can an organ that provides biological immortality be unable to regenerate?
Should I use acronyms in dialogues before telling the readers what it stands for in fiction?
Missing /etc/network/interfaces in my debian 9
Debian network bridge configuration - /etc/network/interfacesIs there a way to disable IPv6 SLAAC on a per-interface basis in Debian?A script that updates interfaces if /etc/network/interfaces changesDebian error: ifup: couldn't read interfaces file “/etc/network/interfaces”Aliased network interfaces and isc dhcp serverDebian up in /etc/network/interfaces not working/etc/network/if-pre-up.d/iptables script makeeth interfaces disappear in debian jessie?Debian - static ip, /etc/network/interfacesDebian : Can't ifdown eth0How to access machine from multiple network interfaces/WANs
I do not understand why, because a have multiple debian 9 servers and i have this problem only one one server:
I do not have /etc/network/interfaces files.
I need to host multiple ip addresses on this server.
I have read some documentations and i have added ip address into this file:
/etc/systemd/network/50-default.network
I have added a line with Address=x.x.x.x for each IP in [Network] section.
Everything works but i do not see all my IP in ifconfig... I only see first IP.
I have notice i have a eno3 interface.
On my other servers, i can see eth0, eth0:0, eth0:1
Thanks
debian debian-stretch
asked Jun 28 '18 at 10:15
Bob5421Bob5421
1113
bumped to the homepage by Community♦ 5 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
I do not understand why, because a have multiple debian 9 servers and i have this problem only one one server:
I do not have /etc/network/interfaces files.
I need to host multiple ip addresses on this server.
I have read some documentations and i have added ip address into this file:
/etc/systemd/network/50-default.network
I have added a line with Address=x.x.x.x for each IP in [Network] section.
Everything works but i do not see all my IP in ifconfig... I only see first IP.
I have notice i have a eno3 interface.
On my other servers, i can see eth0, eth0:0, eth0:1
Thanks
debian debian-stretch
asked Jun 28 '18 at 10:15
Bob5421Bob5421
1113
bumped to the homepage by Community♦ 5 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
try ip addr show, not ifconfig. the "virtual" ips might not be visible with ifconfig anymore if you configure them via systemd
– Dennis Nolte
Jun 28 '18 at 13:03
/etc/network/interface is if i remember just a fallback service when you use systemd. we had this issue as well, but we disabled the fallback service so no network/interfaces at all.
– Dennis Nolte
Jun 28 '18 at 13:05
add a comment |
I do not understand why, because a have multiple debian 9 servers and i have this problem only one one server:
I do not have /etc/network/interfaces files.
I need to host multiple ip addresses on this server.
I have read some documentations and i have added ip address into this file:
/etc/systemd/network/50-default.network
I have added a line with Address=x.x.x.x for each IP in [Network] section.
Everything works but i do not see all my IP in ifconfig... I only see first IP.
I have notice i have a eno3 interface.
On my other servers, i can see eth0, eth0:0, eth0:1
Thanks
debian debian-stretch
asked Jun 28 '18 at 10:15
Bob5421Bob5421
1113
I do not understand why, because a have multiple debian 9 servers and i have this problem only one one server:
I do not have /etc/network/interfaces files.
I need to host multiple ip addresses on this server.
I have read some documentations and i have added ip address into this file:
/etc/systemd/network/50-default.network
I have added a line with Address=x.x.x.x for each IP in [Network] section.
Everything works but i do not see all my IP in ifconfig... I only see first IP.
I have notice i have a eno3 interface.
On my other servers, i can see eth0, eth0:0, eth0:1
Thanks
debian debian-stretch
debian debian-stretch
asked Jun 28 '18 at 10:15
Bob5421Bob5421
1113
asked Jun 28 '18 at 10:15
Bob5421Bob5421
1113
asked Jun 28 '18 at 10:15
Bob5421Bob5421
1113
asked Jun 28 '18 at 10:15
Bob5421Bob5421
1113
asked Jun 28 '18 at 10:15
Bob5421Bob5421
1113
1113
bumped to the homepage by Community♦ 5 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
bumped to the homepage by Community♦ 5 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
try ip addr show, not ifconfig. the "virtual" ips might not be visible with ifconfig anymore if you configure them via systemd
– Dennis Nolte
Jun 28 '18 at 13:03
/etc/network/interface is if i remember just a fallback service when you use systemd. we had this issue as well, but we disabled the fallback service so no network/interfaces at all.
– Dennis Nolte
Jun 28 '18 at 13:05
add a comment |
try ip addr show, not ifconfig. the "virtual" ips might not be visible with ifconfig anymore if you configure them via systemd
– Dennis Nolte
Jun 28 '18 at 13:03
/etc/network/interface is if i remember just a fallback service when you use systemd. we had this issue as well, but we disabled the fallback service so no network/interfaces at all.
– Dennis Nolte
Jun 28 '18 at 13:05
try ip addr show, not ifconfig. the "virtual" ips might not be visible with ifconfig anymore if you configure them via systemd
– Dennis Nolte
Jun 28 '18 at 13:03
try ip addr show, not ifconfig. the "virtual" ips might not be visible with ifconfig anymore if you configure them via systemd
– Dennis Nolte
Jun 28 '18 at 13:03
/etc/network/interface is if i remember just a fallback service when you use systemd. we had this issue as well, but we disabled the fallback service so no network/interfaces at all.
– Dennis Nolte
Jun 28 '18 at 13:05
/etc/network/interface is if i remember just a fallback service when you use systemd. we had this issue as well, but we disabled the fallback service so no network/interfaces at all.
– Dennis Nolte
Jun 28 '18 at 13:05
add a comment |
1 Answer
1
active
oldest
votes
Do this:
echo '#!/bin/bash' > /etc/init.d/ipaliases
echo 'ifconfig eno3 1.2.3.4' >> /etc/init.d/ipaliases
echo 'ifconfig eno3 4.5.6.7' >> /etc/init.d/ipaliases
chmod 755 /etc/init.d/ipaliases
ln -s /etc/init.d/ipaliases /etc/rc2.d/S01ipaliases
Then reboot you machine.
answered Jun 28 '18 at 12:31
Jonas BjorkJonas Bjork
1884
Replace 1.2.3.4 etc with your IP addresses.
– Jonas Bjork
Jun 28 '18 at 12:32
This sets the ip additionally to the systemd way, which might result in problems. Setting an ip twice to the same interface usually overwrites it. additionally you forgot the subnetmask. additionally please use the private IPs for examples like that (RFC1918 f.e.) creating an init script outside systemd when using systemd as INIT is not that a good idea as well in my opinion. you dont need to reboot to reinitalise network interface values as well.
– Dennis Nolte
Jun 28 '18 at 13:10
@Dennis Nolte You don't need a netmask when dealing with ip aliases - they are the same and they inherit the netmask from the primary address. Regarding the init stuff - no it won't cause any problems. You don't need to reboot but it's a good way of confirming that it works on-boot.
– Jonas Bjork
Jun 28 '18 at 13:13
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "2"
};
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%2fserverfault.com%2fquestions%2f918635%2fmissing-etc-network-interfaces-in-my-debian-9%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
Do this:
echo '#!/bin/bash' > /etc/init.d/ipaliases
echo 'ifconfig eno3 1.2.3.4' >> /etc/init.d/ipaliases
echo 'ifconfig eno3 4.5.6.7' >> /etc/init.d/ipaliases
chmod 755 /etc/init.d/ipaliases
ln -s /etc/init.d/ipaliases /etc/rc2.d/S01ipaliases
Then reboot you machine.
answered Jun 28 '18 at 12:31
Jonas BjorkJonas Bjork
1884
Replace 1.2.3.4 etc with your IP addresses.
– Jonas Bjork
Jun 28 '18 at 12:32
This sets the ip additionally to the systemd way, which might result in problems. Setting an ip twice to the same interface usually overwrites it. additionally you forgot the subnetmask. additionally please use the private IPs for examples like that (RFC1918 f.e.) creating an init script outside systemd when using systemd as INIT is not that a good idea as well in my opinion. you dont need to reboot to reinitalise network interface values as well.
– Dennis Nolte
Jun 28 '18 at 13:10
@Dennis Nolte You don't need a netmask when dealing with ip aliases - they are the same and they inherit the netmask from the primary address. Regarding the init stuff - no it won't cause any problems. You don't need to reboot but it's a good way of confirming that it works on-boot.
– Jonas Bjork
Jun 28 '18 at 13:13
add a comment |
Do this:
echo '#!/bin/bash' > /etc/init.d/ipaliases
echo 'ifconfig eno3 1.2.3.4' >> /etc/init.d/ipaliases
echo 'ifconfig eno3 4.5.6.7' >> /etc/init.d/ipaliases
chmod 755 /etc/init.d/ipaliases
ln -s /etc/init.d/ipaliases /etc/rc2.d/S01ipaliases
Then reboot you machine.
answered Jun 28 '18 at 12:31
Jonas BjorkJonas Bjork
1884
Replace 1.2.3.4 etc with your IP addresses.
– Jonas Bjork
Jun 28 '18 at 12:32
This sets the ip additionally to the systemd way, which might result in problems. Setting an ip twice to the same interface usually overwrites it. additionally you forgot the subnetmask. additionally please use the private IPs for examples like that (RFC1918 f.e.) creating an init script outside systemd when using systemd as INIT is not that a good idea as well in my opinion. you dont need to reboot to reinitalise network interface values as well.
– Dennis Nolte
Jun 28 '18 at 13:10
@Dennis Nolte You don't need a netmask when dealing with ip aliases - they are the same and they inherit the netmask from the primary address. Regarding the init stuff - no it won't cause any problems. You don't need to reboot but it's a good way of confirming that it works on-boot.
– Jonas Bjork
Jun 28 '18 at 13:13
add a comment |
Do this:
echo '#!/bin/bash' > /etc/init.d/ipaliases
echo 'ifconfig eno3 1.2.3.4' >> /etc/init.d/ipaliases
echo 'ifconfig eno3 4.5.6.7' >> /etc/init.d/ipaliases
chmod 755 /etc/init.d/ipaliases
ln -s /etc/init.d/ipaliases /etc/rc2.d/S01ipaliases
Then reboot you machine.
answered Jun 28 '18 at 12:31
Jonas BjorkJonas Bjork
1884
Do this:
echo '#!/bin/bash' > /etc/init.d/ipaliases
echo 'ifconfig eno3 1.2.3.4' >> /etc/init.d/ipaliases
echo 'ifconfig eno3 4.5.6.7' >> /etc/init.d/ipaliases
chmod 755 /etc/init.d/ipaliases
ln -s /etc/init.d/ipaliases /etc/rc2.d/S01ipaliases
Then reboot you machine.
answered Jun 28 '18 at 12:31
Jonas BjorkJonas Bjork
1884
answered Jun 28 '18 at 12:31
Jonas BjorkJonas Bjork
1884
answered Jun 28 '18 at 12:31
Jonas BjorkJonas Bjork
1884
answered Jun 28 '18 at 12:31
Jonas BjorkJonas Bjork
1884
1884
Replace 1.2.3.4 etc with your IP addresses.
– Jonas Bjork
Jun 28 '18 at 12:32
This sets the ip additionally to the systemd way, which might result in problems. Setting an ip twice to the same interface usually overwrites it. additionally you forgot the subnetmask. additionally please use the private IPs for examples like that (RFC1918 f.e.) creating an init script outside systemd when using systemd as INIT is not that a good idea as well in my opinion. you dont need to reboot to reinitalise network interface values as well.
– Dennis Nolte
Jun 28 '18 at 13:10
@Dennis Nolte You don't need a netmask when dealing with ip aliases - they are the same and they inherit the netmask from the primary address. Regarding the init stuff - no it won't cause any problems. You don't need to reboot but it's a good way of confirming that it works on-boot.
– Jonas Bjork
Jun 28 '18 at 13:13
add a comment |
Replace 1.2.3.4 etc with your IP addresses.
– Jonas Bjork
Jun 28 '18 at 12:32
This sets the ip additionally to the systemd way, which might result in problems. Setting an ip twice to the same interface usually overwrites it. additionally you forgot the subnetmask. additionally please use the private IPs for examples like that (RFC1918 f.e.) creating an init script outside systemd when using systemd as INIT is not that a good idea as well in my opinion. you dont need to reboot to reinitalise network interface values as well.
– Dennis Nolte
Jun 28 '18 at 13:10
@Dennis Nolte You don't need a netmask when dealing with ip aliases - they are the same and they inherit the netmask from the primary address. Regarding the init stuff - no it won't cause any problems. You don't need to reboot but it's a good way of confirming that it works on-boot.
– Jonas Bjork
Jun 28 '18 at 13:13
Replace 1.2.3.4 etc with your IP addresses.
– Jonas Bjork
Jun 28 '18 at 12:32
Replace 1.2.3.4 etc with your IP addresses.
– Jonas Bjork
Jun 28 '18 at 12:32
This sets the ip additionally to the systemd way, which might result in problems. Setting an ip twice to the same interface usually overwrites it. additionally you forgot the subnetmask. additionally please use the private IPs for examples like that (RFC1918 f.e.) creating an init script outside systemd when using systemd as INIT is not that a good idea as well in my opinion. you dont need to reboot to reinitalise network interface values as well.
– Dennis Nolte
Jun 28 '18 at 13:10
This sets the ip additionally to the systemd way, which might result in problems. Setting an ip twice to the same interface usually overwrites it. additionally you forgot the subnetmask. additionally please use the private IPs for examples like that (RFC1918 f.e.) creating an init script outside systemd when using systemd as INIT is not that a good idea as well in my opinion. you dont need to reboot to reinitalise network interface values as well.
– Dennis Nolte
Jun 28 '18 at 13:10
@Dennis Nolte You don't need a netmask when dealing with ip aliases - they are the same and they inherit the netmask from the primary address. Regarding the init stuff - no it won't cause any problems. You don't need to reboot but it's a good way of confirming that it works on-boot.
– Jonas Bjork
Jun 28 '18 at 13:13
@Dennis Nolte You don't need a netmask when dealing with ip aliases - they are the same and they inherit the netmask from the primary address. Regarding the init stuff - no it won't cause any problems. You don't need to reboot but it's a good way of confirming that it works on-boot.
– Jonas Bjork
Jun 28 '18 at 13:13
add a comment |
Thanks for contributing an answer to Server Fault!
- 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%2fserverfault.com%2fquestions%2f918635%2fmissing-etc-network-interfaces-in-my-debian-9%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
try ip addr show, not ifconfig. the "virtual" ips might not be visible with ifconfig anymore if you configure them via systemd
– Dennis Nolte
Jun 28 '18 at 13:03
/etc/network/interface is if i remember just a fallback service when you use systemd. we had this issue as well, but we disabled the fallback service so no network/interfaces at all.
– Dennis Nolte
Jun 28 '18 at 13:05