*** This bug is a duplicate of bug 1439109 ***
https://bugs.launchpad.net/bugs/1439109
I did not have to create the symlink, but once I separated my
/etc/network/interfaces into 3 separate files in
/etc/network/interfaces.d (along with an /etc/network/interfaces that
sourced them) my bridge in
*** This bug is a duplicate of bug 1439109 ***
https://bugs.launchpad.net/bugs/1439109
Fixed for me.
zoolook@venkman:~$ ls /etc/rcS.d/ | grep net
zoolook@venkman:~$ sudo update-rc.d networking remove
zoolook@venkman:~$ sudo update-rc.d networking defaults
zoolook@venkman:~$ ls /etc/rcS.d/ | g
*** This bug is a duplicate of bug 1439109 ***
https://bugs.launchpad.net/bugs/1439109
Timo confirmed as well, so confirming as a duplicate of bug 1439109.
** This bug has been marked a duplicate of bug 1439109
Network interface not coming up due to missing /etc/rcS.d/*networking
--
You
Re-creating the symlink with the command above was enough to fix the
issue for me.
Thanks !
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1430675
Title:
fails to set up
Sorry, I typoed. The correct commands are:
sudo update-rc.d networking remove
sudo update-rc.d networking defaults
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1430675
Vincent Ladeuil reported this on IRC as well, and for him the problem
was that /etc/init.d/networking was disabled. I. e. there is no
/etc/rcS.d/*networking symlink. Timo, Philip, zoolook, can you please
check this?
If you don't have such a symlink, please run
sudo update-r.cd networking remove
See also bug 1439109 which is about the missing networking symlink.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1430675
Title:
fails to set up a bridged network interfa
Mine is an old install too.
In my case, I have 3 nics. Nothing in interfaces.d/
br0 is my lan
br1 wan (behind router)
br2 is not connected, and no, I don't want an ip address there unless is really
necessary .
Here is my interfaces:
auto lo
iface lo inet loopback
auto eth0
iface eth0 inet man
And I only have the builtin eth0 on the motherboard, nothing else.
Nothing in interfaces.d either.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1430675
Title:
fails to s
all my interfaces has besides br0 is:
<--
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
-->
it's an old installation..
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
ht
I tried this with Philip's config, but I still can't reproduce this, I'm
afraid. I launch a VM with two network cards, like this:
qemu-system-x86_64 -enable-kvm -m 2048 -snapshot -drive file=/srv/vm
/adt-vivid-amd64-cloud.img,if=virtio -net nic,model=virtio -net user
-net nic,vlan=1,macaddr=10:1
nope, I don't have separate /usr
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1430675
Title:
fails to set up a bridged network interface
Status in systemd package in Ub
I found this in dmesg:
[ 10.604132] systemd[1]: /usr appears to be on its own filesystem and
is not already mounted. This is not a supported setup. Some things will
probably break (sometimes even silently) in mysterious ways. Consult
http://freedesktop.org/wiki/Software/systemd/separate-usr-is-b
I tried again on current vivid, br0 is still not auto-starting. Here's
the logs
** Attachment added: "iflogs.log"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1430675/+attachment/4358701/+files/iflogs.log
--
You received this bug notification because you are a member of Ubuntu
Touc
I'll do that. Here's the debug output anyway, which I forgot to attach
sooner..
** Attachment added: "debug info"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1430675/+attachment/4356510/+files/br0-debug.txt
--
You received this bug notification because you are a member of Ubuntu
T
Can you please try with current vivid? There were some ifup@ fixes
recently.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1430675
Title:
fails to set up a bridged networ
** Changed in: systemd (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1430675
Title:
fails to set up a bridged network interface
OK, as we don't have a reproducer, I need some further logs. Right after
booting, can you please give me the output of
systemctl --all|grep ifup
journalctl -u ifup-wait-all-auto.service
systemctl status ifup@br0.service
Thanks!
** Changed in: systemd (Ubuntu)
Status: New => Incom
Ok after installing bridge-utils I get br0 _and_ eth0 devices show up on
ifconfig, and br0 was started fine. But it didn't start on my
workstation..
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bu
** Tags added: systemd-boot
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1430675
Title:
fails to set up a bridged network interface
Status in systemd package in Ubuntu:
hrm, though on the vm 'ifup br0' says 'no such device' when the same
worked on my desktop/server.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1430675
Title:
fails to se
21 matches
Mail list logo
