Is your config detecting that there's no cable? Search for eth messages
in /var/log/syslog.
--
[feisty] nm gives me an ip even if there is no cable
https://launchpad.net/bugs/78078
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
I have this problem on my laptop with a cardbus ethernet adaptor. You
can see in the attached log that the card is detected and after dhcp
fails it is assigned an address via avahi-autoipd. If I then plug in the
cable the kernel reports a link beat and the network works as it is pre-
configured. Th
** Changed in: network-manager (Ubuntu)
Sourcepackagename: network-manager => avahi
--
[feisty] nm gives me an ip even if there is no cable
https://launchpad.net/bugs/78078
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Thanks for your bug report.
I think, the fact that you have an ip address is normal, this is the new
feature of avahi called IPv4LL.
you say: "this is not usefull since sometimes (rarely) this prevents wireless
to work", do you know when this happens ?
The eth0:avahi interface should not prevent
Whats that IP? if it begin with 169 I think it's normal
--
[feisty] nm gives me an ip even if there is no cable
https://launchpad.net/bugs/78078
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Assignment of a local net IP is incorrect if the link status is down.
Avahi should only assign the local IP (169.154.x.x) if the link is up
and there is neither a static definition nor a DHCP assignment. This
would cover the case where a crossover cable or local hub/switch is
used, yet not cause s
Which information is needed?
I think that the bug can be solved preventing avahi to give an IP to an
interface without a plugged cable.
--
[feisty] nm gives me an ip even if there is no cable
https://launchpad.net/bugs/78078
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://list
I think that it is fixed in gutsy. I don't have eth0:avahi no more!
Let's mark it fixed for now. Reopen it if you still have this problem in
gutsy
** Changed in: avahi (Ubuntu)
Status: Confirmed => Fix Released
--
[feisty] nm gives me an ip even if there is no cable
https://bugs.launchpad
Sorry, the bug is still here. I will attach some logs and describe the new
situation in gutsy:
now if you boot without the cable, nm will think that you are connected, this
is different in feisty, because there was the missing connectivity icon!
When you start gnome you can see the 2 meteors icon
relevant part
Jul 10 10:00:32 yelo3-laptop NetworkManager: Will activate wired
connection 'eth0' because it now has a link.
this is not true. The link is down
** Attachment added: "daemon.log"
http://launchpadlibrarian.net/8354717/daemon.log
--
[feisty] nm gives me an ip even if there is
Unfortunately this not only happens on boot, but every time I remove and
reinstall the module, with the cable unplugged.
relevant part of /var/log/messages
Jul 10 10:20:24 yelo3-laptop kernel: [ 1232.272000] tg3: eth0: Link is down.
Jul 10 10:20:29 yelo3-laptop kernel: [ 1237.048000] ACPI: PCI in
seems fixed again:
1. 24a_svn2578-gnome354565-fix-ethernet-link-detection-races.patch:
- prefetch patch from 0.6.0 release branch (rev 2578)
** Changed in: avahi (Ubuntu)
Status: Confirmed => Fix Released
--
[feisty] nm gives me an ip even if there is no cable
https://bugs.launchp
** Changed in: avahi (Ubuntu)
Assignee: (unassigned) => Riccardo Setti
--
[feisty] nm gives me an ip even if there is no cable
https://bugs.launchpad.net/bugs/78078
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bu
I have the same problem described. I am using Linux Mint 4.0, based on Ubuntu
7.10 Gutsy Gibbon quite recent so.
The cause of the problem I can only think of is: I recently reported a bug to
Ubuntu. Some program started in the background then. A tab was added, I
couldnot refuse that. A screenpr
But all works if you edit /etc/network/interface and put # before all line
except the line there is "lo"
I open a report bug for this because all how-to in wiki-ubuntu about "nm" say
this.
thanks
--
[feisty] nm gives me an ip even if there is no cable
https://bugs.launchpad.net/bugs/78078
You
Open the network-admin:
$: gksu network-admin
The cable interface has the roaming mode anabled ???
By default it is not so :(
--
[feisty] nm gives me an ip even if there is no cable
https://bugs.launchpad.net/bugs/78078
You received this bug notification because you are a member of Ubuntu
Bugs
On my workstation, both wired interfaces have the roaming mode enabled
(I have never adjusted network manager settings).
--
[feisty] nm gives me an ip even if there is no cable
https://bugs.launchpad.net/bugs/78078
You received this bug notification because you are a member of Ubuntu
Bugs, which
this happens only if I remove the cable: if I boot without any cable the
avahi interface is not enabled
it is important to fix this bug because every application thinks that
the system is connected (because it has a default route assigned by
avahi)
further info: I don't know what's happening, bug
I found a simple fix. maybe we have this problem only because we were
upgrading from and older ubuntu version
try with this and tell me if it works
sudo apt-get --purge install avahi-autoipd --reinstall
--
[feisty] nm gives me an ip even if there is no cable
https://bugs.launchpad.net/bugs/780
This seems to address the issue. When first running the command,
there was no change to my configuration (eth0 with DHCP address, eth1
with none, and eth1:avahi with adhoc address). Unplugging eth0 did not
generate any eth0 adhoc address. Connecting eth1 disabled the
eth1:avahi interface, an
My switch is currently in use by a DHCP server and other users. I
should have an opportunity to be alone with the switch in the next
couple days, and I'll try then. Thanks for the reminder that I don't
need a crossover to establish LINK UP.
--
[feisty] nm gives me an ip even if there is no cabl
Great! I'm not sure about closing the bug though: is it present in the
released 6.10 or 6.06LTS? If so, logic should be in the postinst to
clean up the brokenness for upgrades, as otherwise other users may
encounter this bug after it has been closed, and open a new one.
Perhaps just updating the
Hannes,
I had the same problem and did a writeup of the fix here:
http://omingo.zorngrid.com/
Hope it works for you too.
--
[feisty] nm gives me an ip even if there is no cable
https://bugs.launchpad.net/bugs/78078
You received this bug notification because you are a member of Ubuntu
Bugs, whi
I have a similar problem:
upgraded from edgy to feisty. network worked fine for several days. SOME
incident then suddenly broke it tis morning (with yet no solution).
the symptomes are: I suddenly get an additional interface eth0:avahi in Network
Tools -> Devices. It is one of those, that have a
I have a bug report with a similar error log, but I believe it is a
separate issue. Bug #110394. Possibly, may be affected by this issue?
--
[feisty] nm gives me an ip even if there is no cable
https://bugs.launchpad.net/bugs/78078
You received this bug notification because you are a member of Ub
I think that it is fixed in gutsy. I don't have eth0:avahi no more!
Let's mark it fixed for now. Reopen it if you still have this problem in
gutsy
** Changed in: avahi (Ubuntu)
Status: Confirmed => Fix Released
--
[feisty] nm gives me an ip even if there is no cable
https://bugs.launchpad
Sorry, the bug is still here. I will attach some logs and describe the new
situation in gutsy:
now if you boot without the cable, nm will think that you are connected, this
is different in feisty, because there was the missing connectivity icon!
When you start gnome you can see the 2 meteors icon
relevant part
Jul 10 10:00:32 yelo3-laptop NetworkManager: Will activate wired
connection 'eth0' because it now has a link.
this is not true. The link is down
** Attachment added: "daemon.log"
http://launchpadlibrarian.net/8354717/daemon.log
--
[feisty] nm gives me an ip even if there is
Unfortunately this not only happens on boot, but every time I remove and
reinstall the module, with the cable unplugged.
relevant part of /var/log/messages
Jul 10 10:20:24 yelo3-laptop kernel: [ 1232.272000] tg3: eth0: Link is down.
Jul 10 10:20:29 yelo3-laptop kernel: [ 1237.048000] ACPI: PCI in
seems fixed again:
1. 24a_svn2578-gnome354565-fix-ethernet-link-detection-races.patch:
- prefetch patch from 0.6.0 release branch (rev 2578)
** Changed in: avahi (Ubuntu)
Status: Confirmed => Fix Released
--
[feisty] nm gives me an ip even if there is no cable
https://bugs.launchp
Which information is needed?
I think that the bug can be solved preventing avahi to give an IP to an
interface without a plugged cable.
--
[feisty] nm gives me an ip even if there is no cable
https://launchpad.net/bugs/78078
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://list
But all works if you edit /etc/network/interface and put # before all line
except the line there is "lo"
I open a report bug for this because all how-to in wiki-ubuntu about "nm" say
this.
thanks
--
[feisty] nm gives me an ip even if there is no cable
https://bugs.launchpad.net/bugs/78078
You
Open the network-admin:
$: gksu network-admin
The cable interface has the roaming mode anabled ???
By default it is not so :(
--
[feisty] nm gives me an ip even if there is no cable
https://bugs.launchpad.net/bugs/78078
You received this bug notification because you are a member of Ubuntu
Bugs
On my workstation, both wired interfaces have the roaming mode enabled
(I have never adjusted network manager settings).
--
[feisty] nm gives me an ip even if there is no cable
https://bugs.launchpad.net/bugs/78078
You received this bug notification because you are a member of Ubuntu
Bugs, which
Is your config detecting that there's no cable? Search for eth messages
in /var/log/syslog.
--
[feisty] nm gives me an ip even if there is no cable
https://launchpad.net/bugs/78078
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
I have this problem on my laptop with a cardbus ethernet adaptor. You
can see in the attached log that the card is detected and after dhcp
fails it is assigned an address via avahi-autoipd. If I then plug in the
cable the kernel reports a link beat and the network works as it is pre-
configured. Th
this happens only if I remove the cable: if I boot without any cable the
avahi interface is not enabled
it is important to fix this bug because every application thinks that
the system is connected (because it has a default route assigned by
avahi)
further info: I don't know what's happening, bug
I found a simple fix. maybe we have this problem only because we were
upgrading from and older ubuntu version
try with this and tell me if it works
sudo apt-get --purge install avahi-autoipd --reinstall
--
[feisty] nm gives me an ip even if there is no cable
https://bugs.launchpad.net/bugs/780
This seems to address the issue. When first running the command,
there was no change to my configuration (eth0 with DHCP address, eth1
with none, and eth1:avahi with adhoc address). Unplugging eth0 did not
generate any eth0 adhoc address. Connecting eth1 disabled the
eth1:avahi interface, an
My switch is currently in use by a DHCP server and other users. I
should have an opportunity to be alone with the switch in the next
couple days, and I'll try then. Thanks for the reminder that I don't
need a crossover to establish LINK UP.
--
[feisty] nm gives me an ip even if there is no cabl
Great! I'm not sure about closing the bug though: is it present in the
released 6.10 or 6.06LTS? If so, logic should be in the postinst to
clean up the brokenness for upgrades, as otherwise other users may
encounter this bug after it has been closed, and open a new one.
Perhaps just updating the
I have the same problem described. I am using Linux Mint 4.0, based on Ubuntu
7.10 Gutsy Gibbon quite recent so.
The cause of the problem I can only think of is: I recently reported a bug to
Ubuntu. Some program started in the background then. A tab was added, I
couldnot refuse that. A screenpr
I have a bug report with a similar error log, but I believe it is a
separate issue. Bug #110394. Possibly, may be affected by this issue?
--
[feisty] nm gives me an ip even if there is no cable
https://bugs.launchpad.net/bugs/78078
You received this bug notification because you are a member of Ub
** Changed in: avahi (Ubuntu)
Assignee: (unassigned) => Riccardo Setti
--
[feisty] nm gives me an ip even if there is no cable
https://bugs.launchpad.net/bugs/78078
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bu
** Changed in: network-manager (Ubuntu)
Sourcepackagename: network-manager => avahi
--
[feisty] nm gives me an ip even if there is no cable
https://launchpad.net/bugs/78078
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Thanks for your bug report.
I think, the fact that you have an ip address is normal, this is the new
feature of avahi called IPv4LL.
you say: "this is not usefull since sometimes (rarely) this prevents wireless
to work", do you know when this happens ?
The eth0:avahi interface should not prevent
Whats that IP? if it begin with 169 I think it's normal
--
[feisty] nm gives me an ip even if there is no cable
https://launchpad.net/bugs/78078
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Assignment of a local net IP is incorrect if the link status is down.
Avahi should only assign the local IP (169.154.x.x) if the link is up
and there is neither a static definition nor a DHCP assignment. This
would cover the case where a crossover cable or local hub/switch is
used, yet not cause s
I have a similar problem:
upgraded from edgy to feisty. network worked fine for several days. SOME
incident then suddenly broke it tis morning (with yet no solution).
the symptomes are: I suddenly get an additional interface eth0:avahi in Network
Tools -> Devices. It is one of those, that have a
Hannes,
I had the same problem and did a writeup of the fix here:
http://omingo.zorngrid.com/
Hope it works for you too.
--
[feisty] nm gives me an ip even if there is no cable
https://bugs.launchpad.net/bugs/78078
You received this bug notification because you are a member of Ubuntu
Bugs, whi
** Changed in: network-manager (Ubuntu)
Sourcepackagename: network-manager => avahi
--
[feisty] nm gives me an ip even if there is no cable
https://launchpad.net/bugs/78078
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Thanks for your bug report.
I think, the fact that you have an ip address is normal, this is the new
feature of avahi called IPv4LL.
you say: "this is not usefull since sometimes (rarely) this prevents wireless
to work", do you know when this happens ?
The eth0:avahi interface should not prevent
Whats that IP? if it begin with 169 I think it's normal
--
[feisty] nm gives me an ip even if there is no cable
https://launchpad.net/bugs/78078
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Assignment of a local net IP is incorrect if the link status is down.
Avahi should only assign the local IP (169.154.x.x) if the link is up
and there is neither a static definition nor a DHCP assignment. This
would cover the case where a crossover cable or local hub/switch is
used, yet not cause s
Is your config detecting that there's no cable? Search for eth messages
in /var/log/syslog.
--
[feisty] nm gives me an ip even if there is no cable
https://launchpad.net/bugs/78078
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
I have this problem on my laptop with a cardbus ethernet adaptor. You
can see in the attached log that the card is detected and after dhcp
fails it is assigned an address via avahi-autoipd. If I then plug in the
cable the kernel reports a link beat and the network works as it is pre-
configured. Th
I have a similar problem:
upgraded from edgy to feisty. network worked fine for several days. SOME
incident then suddenly broke it tis morning (with yet no solution).
the symptomes are: I suddenly get an additional interface eth0:avahi in Network
Tools -> Devices. It is one of those, that have a
But all works if you edit /etc/network/interface and put # before all line
except the line there is "lo"
I open a report bug for this because all how-to in wiki-ubuntu about "nm" say
this.
thanks
--
[feisty] nm gives me an ip even if there is no cable
https://bugs.launchpad.net/bugs/78078
You
Open the network-admin:
$: gksu network-admin
The cable interface has the roaming mode anabled ???
By default it is not so :(
--
[feisty] nm gives me an ip even if there is no cable
https://bugs.launchpad.net/bugs/78078
You received this bug notification because you are a member of Ubuntu
Bugs
On my workstation, both wired interfaces have the roaming mode enabled
(I have never adjusted network manager settings).
--
[feisty] nm gives me an ip even if there is no cable
https://bugs.launchpad.net/bugs/78078
You received this bug notification because you are a member of Ubuntu
Bugs, which
this happens only if I remove the cable: if I boot without any cable the
avahi interface is not enabled
it is important to fix this bug because every application thinks that
the system is connected (because it has a default route assigned by
avahi)
further info: I don't know what's happening, bug
I found a simple fix. maybe we have this problem only because we were
upgrading from and older ubuntu version
try with this and tell me if it works
sudo apt-get --purge install avahi-autoipd --reinstall
--
[feisty] nm gives me an ip even if there is no cable
https://bugs.launchpad.net/bugs/780
This seems to address the issue. When first running the command,
there was no change to my configuration (eth0 with DHCP address, eth1
with none, and eth1:avahi with adhoc address). Unplugging eth0 did not
generate any eth0 adhoc address. Connecting eth1 disabled the
eth1:avahi interface, an
My switch is currently in use by a DHCP server and other users. I
should have an opportunity to be alone with the switch in the next
couple days, and I'll try then. Thanks for the reminder that I don't
need a crossover to establish LINK UP.
--
[feisty] nm gives me an ip even if there is no cabl
Great! I'm not sure about closing the bug though: is it present in the
released 6.10 or 6.06LTS? If so, logic should be in the postinst to
clean up the brokenness for upgrades, as otherwise other users may
encounter this bug after it has been closed, and open a new one.
Perhaps just updating the
I have the same problem described. I am using Linux Mint 4.0, based on Ubuntu
7.10 Gutsy Gibbon quite recent so.
The cause of the problem I can only think of is: I recently reported a bug to
Ubuntu. Some program started in the background then. A tab was added, I
couldnot refuse that. A screenpr
Hannes,
I had the same problem and did a writeup of the fix here:
http://omingo.zorngrid.com/
Hope it works for you too.
--
[feisty] nm gives me an ip even if there is no cable
https://bugs.launchpad.net/bugs/78078
You received this bug notification because you are a member of Ubuntu
Bugs, whi
I think that it is fixed in gutsy. I don't have eth0:avahi no more!
Let's mark it fixed for now. Reopen it if you still have this problem in
gutsy
** Changed in: avahi (Ubuntu)
Status: Confirmed => Fix Released
--
[feisty] nm gives me an ip even if there is no cable
https://bugs.launchpad
Sorry, the bug is still here. I will attach some logs and describe the new
situation in gutsy:
now if you boot without the cable, nm will think that you are connected, this
is different in feisty, because there was the missing connectivity icon!
When you start gnome you can see the 2 meteors icon
relevant part
Jul 10 10:00:32 yelo3-laptop NetworkManager: Will activate wired
connection 'eth0' because it now has a link.
this is not true. The link is down
** Attachment added: "daemon.log"
http://launchpadlibrarian.net/8354717/daemon.log
--
[feisty] nm gives me an ip even if there is
Unfortunately this not only happens on boot, but every time I remove and
reinstall the module, with the cable unplugged.
relevant part of /var/log/messages
Jul 10 10:20:24 yelo3-laptop kernel: [ 1232.272000] tg3: eth0: Link is down.
Jul 10 10:20:29 yelo3-laptop kernel: [ 1237.048000] ACPI: PCI in
seems fixed again:
1. 24a_svn2578-gnome354565-fix-ethernet-link-detection-races.patch:
- prefetch patch from 0.6.0 release branch (rev 2578)
** Changed in: avahi (Ubuntu)
Status: Confirmed => Fix Released
--
[feisty] nm gives me an ip even if there is no cable
https://bugs.launchp
Which information is needed?
I think that the bug can be solved preventing avahi to give an IP to an
interface without a plugged cable.
--
[feisty] nm gives me an ip even if there is no cable
https://launchpad.net/bugs/78078
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://list
I have a bug report with a similar error log, but I believe it is a
separate issue. Bug #110394. Possibly, may be affected by this issue?
--
[feisty] nm gives me an ip even if there is no cable
https://bugs.launchpad.net/bugs/78078
You received this bug notification because you are a member of Ub
** Changed in: avahi (Ubuntu)
Assignee: (unassigned) => Riccardo Setti
--
[feisty] nm gives me an ip even if there is no cable
https://bugs.launchpad.net/bugs/78078
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bu
I think that it is fixed in gutsy. I don't have eth0:avahi no more!
Let's mark it fixed for now. Reopen it if you still have this problem in
gutsy
** Changed in: avahi (Ubuntu)
Status: Confirmed => Fix Released
--
[feisty] nm gives me an ip even if there is no cable
https://bugs.launchpad
Sorry, the bug is still here. I will attach some logs and describe the new
situation in gutsy:
now if you boot without the cable, nm will think that you are connected, this
is different in feisty, because there was the missing connectivity icon!
When you start gnome you can see the 2 meteors icon
relevant part
Jul 10 10:00:32 yelo3-laptop NetworkManager: Will activate wired
connection 'eth0' because it now has a link.
this is not true. The link is down
** Attachment added: "daemon.log"
http://launchpadlibrarian.net/8354717/daemon.log
--
[feisty] nm gives me an ip even if there is
Unfortunately this not only happens on boot, but every time I remove and
reinstall the module, with the cable unplugged.
relevant part of /var/log/messages
Jul 10 10:20:24 yelo3-laptop kernel: [ 1232.272000] tg3: eth0: Link is down.
Jul 10 10:20:29 yelo3-laptop kernel: [ 1237.048000] ACPI: PCI in
seems fixed again:
1. 24a_svn2578-gnome354565-fix-ethernet-link-detection-races.patch:
- prefetch patch from 0.6.0 release branch (rev 2578)
** Changed in: avahi (Ubuntu)
Status: Confirmed => Fix Released
--
[feisty] nm gives me an ip even if there is no cable
https://bugs.launchp
Which information is needed?
I think that the bug can be solved preventing avahi to give an IP to an
interface without a plugged cable.
--
[feisty] nm gives me an ip even if there is no cable
https://launchpad.net/bugs/78078
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://list
** Changed in: network-manager (Ubuntu)
Sourcepackagename: network-manager => avahi
--
[feisty] nm gives me an ip even if there is no cable
https://launchpad.net/bugs/78078
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Thanks for your bug report.
I think, the fact that you have an ip address is normal, this is the new
feature of avahi called IPv4LL.
you say: "this is not usefull since sometimes (rarely) this prevents wireless
to work", do you know when this happens ?
The eth0:avahi interface should not prevent
Whats that IP? if it begin with 169 I think it's normal
--
[feisty] nm gives me an ip even if there is no cable
https://launchpad.net/bugs/78078
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Assignment of a local net IP is incorrect if the link status is down.
Avahi should only assign the local IP (169.154.x.x) if the link is up
and there is neither a static definition nor a DHCP assignment. This
would cover the case where a crossover cable or local hub/switch is
used, yet not cause s
Is your config detecting that there's no cable? Search for eth messages
in /var/log/syslog.
--
[feisty] nm gives me an ip even if there is no cable
https://launchpad.net/bugs/78078
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
I have this problem on my laptop with a cardbus ethernet adaptor. You
can see in the attached log that the card is detected and after dhcp
fails it is assigned an address via avahi-autoipd. If I then plug in the
cable the kernel reports a link beat and the network works as it is pre-
configured. Th
I have the same problem described. I am using Linux Mint 4.0, based on Ubuntu
7.10 Gutsy Gibbon quite recent so.
The cause of the problem I can only think of is: I recently reported a bug to
Ubuntu. Some program started in the background then. A tab was added, I
couldnot refuse that. A screenpr
But all works if you edit /etc/network/interface and put # before all line
except the line there is "lo"
I open a report bug for this because all how-to in wiki-ubuntu about "nm" say
this.
thanks
--
[feisty] nm gives me an ip even if there is no cable
https://bugs.launchpad.net/bugs/78078
You
Open the network-admin:
$: gksu network-admin
The cable interface has the roaming mode anabled ???
By default it is not so :(
--
[feisty] nm gives me an ip even if there is no cable
https://bugs.launchpad.net/bugs/78078
You received this bug notification because you are a member of Ubuntu
Bugs
On my workstation, both wired interfaces have the roaming mode enabled
(I have never adjusted network manager settings).
--
[feisty] nm gives me an ip even if there is no cable
https://bugs.launchpad.net/bugs/78078
You received this bug notification because you are a member of Ubuntu
Bugs, which
this happens only if I remove the cable: if I boot without any cable the
avahi interface is not enabled
it is important to fix this bug because every application thinks that
the system is connected (because it has a default route assigned by
avahi)
further info: I don't know what's happening, bug
I found a simple fix. maybe we have this problem only because we were
upgrading from and older ubuntu version
try with this and tell me if it works
sudo apt-get --purge install avahi-autoipd --reinstall
--
[feisty] nm gives me an ip even if there is no cable
https://bugs.launchpad.net/bugs/780
This seems to address the issue. When first running the command,
there was no change to my configuration (eth0 with DHCP address, eth1
with none, and eth1:avahi with adhoc address). Unplugging eth0 did not
generate any eth0 adhoc address. Connecting eth1 disabled the
eth1:avahi interface, an
My switch is currently in use by a DHCP server and other users. I
should have an opportunity to be alone with the switch in the next
couple days, and I'll try then. Thanks for the reminder that I don't
need a crossover to establish LINK UP.
--
[feisty] nm gives me an ip even if there is no cabl
Great! I'm not sure about closing the bug though: is it present in the
released 6.10 or 6.06LTS? If so, logic should be in the postinst to
clean up the brokenness for upgrades, as otherwise other users may
encounter this bug after it has been closed, and open a new one.
Perhaps just updating the
Which information is needed?
I think that the bug can be solved preventing avahi to give an IP to an
interface without a plugged cable.
--
[feisty] nm gives me an ip even if there is no cable
https://launchpad.net/bugs/78078
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://list
** Changed in: network-manager (Ubuntu)
Sourcepackagename: network-manager => avahi
--
[feisty] nm gives me an ip even if there is no cable
https://launchpad.net/bugs/78078
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Thanks for your bug report.
I think, the fact that you have an ip address is normal, this is the new
feature of avahi called IPv4LL.
you say: "this is not usefull since sometimes (rarely) this prevents wireless
to work", do you know when this happens ?
The eth0:avahi interface should not prevent
Whats that IP? if it begin with 169 I think it's normal
--
[feisty] nm gives me an ip even if there is no cable
https://launchpad.net/bugs/78078
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
1 - 100 of 204 matches
Mail list logo
