Another issue found/resolved: (separate to the one experienced with
wpasupplicant)
If the alias interfaces have a broadcast address defined, they fail to
come up at boot also.
Could you try putting defining broadcast on the parent interface only,
and see if the issue is sorted?
e.g:
auto eth0
i
The work around does not work in jaunty!
--
ifup -a does not start alias interfaces
https://bugs.launchpad.net/bugs/114457
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://
jaunty workaround:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/123773
(either wpasupplicant or wireless-tools at fault)
--
ifup -a does not start alias interfaces
https://bugs.launchpad.net/bugs/114457
You received this bug notification because you are a member of Ubuntu
Bugs, which
I solved this problem!
The reason is that networking subsystem does not start at boot. I don't know
why Canonical decided to do that)) You can add /etc/init.d/networking manually
or by this command
# update-rc.d networking defaults
(i do this by sysv-rc-conf program (you can check by this progr
** Changed in: ifupdown (Ubuntu)
Assignee: (unassigned) => LinU (linu-realweb)
--
ifup -a does not start alias interfaces
https://bugs.launchpad.net/bugs/114457
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
I also have this problem with jaunty/server. My workaround is to comment
out the auto line for the alias and us post-up / pre-down to bring the
aliases up:
auto eth0
iface eth0 inet static
address 1.2.3.4
broadcast 1.2.3.255
netmask 255.255.255.0
gateway 1.2.3.1
post-up ifup eth0
well, I just upgraded my server to 9.04 and I no longer have eth0:1.
this is a server i am using, are not there any quick fixes? I guess it was not
a good idea to use ubuntu for a server to begin with. eth0:1 will come up after
running /etc/init.d/networking from command line.
Best.
--
ifup -a
Using Jaunty Server 32 bit.
Here is my /etc/network/interfaces file:
# The primary network interface
auto eth0
iface eth0 inet dhcp
# A static interface
auto eth0:1
iface eth0:1 inet static
address 192.168.222.120
netmask 255.255.255.0
network 192.168.222.0
broadcast 192.168.222.255
eth0 comes
Confirm this bug at Jaunty release.
/etc/init.d/networking brings eth0:0 and eth0:1 up
No errors (as i see) in logs
--
ifup -a does not start alias interfaces
https://bugs.launchpad.net/bugs/114457
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
I can confirm this bug in jaunty server since RC
** Changed in: ifupdown (Ubuntu)
Status: Triaged => New
--
ifup -a does not start alias interfaces
https://bugs.launchpad.net/bugs/114457
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
Same bug in Jaunty since RC.
Ifup eth0:0 after boot brings it up.
No way to have a quick fix?
--
ifup -a does not start alias interfaces
https://bugs.launchpad.net/bugs/114457
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-
** Changed in: ifupdown (Debian)
Status: Unknown => New
--
ifup -a does not start alias interfaces
https://bugs.launchpad.net/bugs/114457
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lis
** Bug watch added: Debian Bug tracker #418326
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=418326
** Also affects: ifupdown (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=418326
Importance: Unknown
Status: Unknown
** Changed in: ifupdown (Ubuntu)
Importance:
Correction: after boot I have to use ifdown THEN ifup because the
interface is supposedly "already configured" although it is NOT working
or showing up in ifconfig. I can reproduce this using networking
restart. It only seems to work (although bug 123773 shows up) when I use
ifup or ifconfig up.
/
I have this problem on both Feisty ppc and Gutsy x86. If I use "sudo
ifup eth0:0" after boot it works although I am affected by this bug:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/123773. This
seems like a major problem. I am unable to share files via NFS between 2
boxes hardwired int
15 matches
Mail list logo
