I am on 8.10 and have following cards: eth1 + ath1 (both wireless). Now
I would like to be able to use eth1 as usually without the other one
connecting to the same network (which is cause strange delays while
fetching web pages). So I decided to add ath1 to interfaces file:
iface ath1 inet manual
It seems that I'm also affected by this particular problem on my old Hp
Omnibook XE2. I've got roaming mode enabled and network manager applet
sees wired connection, but never connects to it right away after boot. I
must manually choose wired connection, to receive ip address. My network
card is 3c
I don't know, whether it is exactly the same bug, but for me fix
released didn't solve the problem.
--
network-manager should stop managing any interface configured in
/etc/network/interfaces
https://bugs.launchpad.net/bugs/139403
You received this bug notification because you are a member of Ub
I'm still not sure it's the same underlying problem that I'm trying to
report, and I wish someone would post a clear diagnostic test here. What
I can say is that the problem has survived the Gutsy upgrade. The
workaround of disabling and then enabling networking still works to fix
it. I've only upg
Hi @all,
this is my first post on the launchpad - so please excuse any formal
mistakes.
What you've described, I've also figured out. It's really frustating, that
after bootup I do never have an internet connection automatically.
My "/etc/network/interfaces" is empty except the "auto lo" entry
Though the last comment from Alexander wasn't addressed to me, I hoped
to apply it, but roaming was not selected, and my wired interface is not
listed in /etc/network/interfaces.
I have done some more experiments, but still have no real understanding
of the problem. I still can't even understand w
On Sun, Sep 30, 2007 at 07:08:27PM -, martinlanghoff wrote:
> Does the statement that "network manager should stop to manage _any_
> interface that is configured in /etc/network/interfaces" mean that for
> things to work well I have to remove eth0 from /etc/network/interfaces?
> How about lo?
>
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/133374
was where I came from, and that description seems to match my problem
very exactly. However, it is listed as a duplicate of this bug, and when
I read this one I am unable to understand the relationship.
To recap: After booting,
Hi Alexander - I am seeing problems with network-manager / network-
manager-gnome that seem related to this. At least the bugs that seem to
describe it are marked as dups of this one ;-)
The symptom I see is that network-manager is *not* managing my wired
network, when it should. At the office I h
** Changed in: ifupdown (Ubuntu)
Assignee: (unassigned) => Alexander Sack (asac)
--
network-manager should stop managing any interface configured in
/etc/network/interfaces
https://bugs.launchpad.net/bugs/139403
You received this bug notification because you are a member of Ubuntu
Bugs, whi
Alexander, that might well be the case. I'll wait until the fix is built
and pushed and then comment on the appropriate bug if necessary.
--
network-manager should stop managing any interface configured in
/etc/network/interfaces
https://bugs.launchpad.net/bugs/139403
You received this bug notif
Martin, your crash is most likely dealt with in bug 141233 and its
duplicate.
--
network-manager should stop managing any interface configured in
/etc/network/interfaces
https://bugs.launchpad.net/bugs/139403
You received this bug notification because you are a member of Ubuntu
Bugs, which is th
That somehow completely broke wifi support here.
I have tried purposely commenting out ath0 and wifi0 and restarting both
networking and dbus, but that didn't help; the nm-applet keeps on dying.
I ended up having to manually associate the essid and launch dhcp from
interfaces by defining ath0 the
** Changed in: netcfg (Ubuntu)
Sourcepackagename: debian-installer => netcfg
--
network-manager should stop managing any interface configured in
/etc/network/interfaces
https://bugs.launchpad.net/bugs/139403
You received this bug notification because you are a member of Ubuntu
Bugs, which is the
ifupdown (0.6.8ubuntu8) gutsy; urgency=low
* ifupdown.nw: use 100 as default route metric unless an explicit metric
parameter is set in /etc/network/interface; this applies for static and
dhcp interfaces and passes the -e IF_METRIC=%metric% option to dhclient{3}
in order to accomplis
network-manager (0.6.5-0ubuntu12) gutsy; urgency=low
* debian/patches/05-debian_backend.patch: don't manage auto/allow-* dhcp
interfaces anymore (LP: #139403).
- debian/ifblacklist_migrate.sh: new helper script that blacklists
auto/allow-* dhcp interfaces without any options.
-
The ifupdown change looks good to me. I gave it some extensive testing
on my desktop (eth only) and laptop (eth+wifi) with various metric
options and configurations.
--
network-manager should stop managing any interface configured in
/etc/network/interfaces
https://bugs.launchpad.net/bugs/139403
casper (1.103) gutsy; urgency=low
* Disable anacron harder so that it doesn't get started by battery events.
* Don't write out DHCP network interface stanzas if network-manager is
installed (LP: #139403).
-- Colin Watson <[EMAIL PROTECTED]> Wed, 19 Sep 2007 12:52:21 +0100
** Changed i
ubiquity just copies the /etc/network/interfaces generated by casper, so
this goes hand in hand with using n-m properly on the live CD.
** Changed in: casper (Ubuntu)
Sourcepackagename: ubiquity => casper
--
network-manager should stop managing any interface configured in
/etc/network/interface
netcfg (1.39ubuntu3) gutsy; urgency=low
* Call /usr/lib/network-manager/ifblacklist_migrate.sh from finish-install
if present, so that 'auto dhcp' interfaces are disabled if
network-manager is in use (LP: #139403).
-- Colin Watson <[EMAIL PROTECTED]> Wed, 19 Sep 2007 12:38:08 +0100
** Also affects: ubiquity (Ubuntu)
Importance: Undecided
Status: New
** Changed in: ubiquity (Ubuntu)
Target: None => ubuntu-7.10-beta
** Also affects: debian-installer (Baltix)
Importance: Undecided
Status: New
** Changed in: debian-installer (Baltix)
Status: N
** Changed in: network-manager (Ubuntu)
Importance: Undecided => High
--
network-manager should stop managing any interface configured in
/etc/network/interfaces
https://bugs.launchpad.net/bugs/139403
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
network manager invokes this script during postinst configure like:
if dpkg --compare-versions "$2" "<<" 0.6.5-0ubuntu12; then
sh /usr/lib/network-manager/ifblacklist_migrate.sh
fi
** Attachment added: "ifblacklist_migrate.sh"
http://launchp
Patch to set route metric to 100 unless there is metric definition in
the /etc/network/interfaces iface block. ATM, we do this for static +
dhcp inet iface definitions only.
** Attachment added: "1st version of ifupdown default metric"
http://launchpadlibrarian.net/9307142/ifupdown.nw-defaultme
as discussed in previous irc log we want to add a default metric to all
ifupdown managed routes unless an explicit metric is configured in
/etc/network/interfaces.
Adding ifupdown to bug and targetting for 7.10 beta.
** Also affects: ifupdown (Ubuntu)
Importance: Undecided
Status: New
meeting log:
17:50 < asac> pitti: please rephrase :) ?
17:51 < pitti> ok, I plug my laptop into my ethernet and have auto eth0/dhcp
17:51 < asac> yeah
17:51 < pitti> (in /e/n/i)
17:51 < pitti> then I unplug it, and want to use my wifi
17:51 < pitti> but since n-m doesn't manage eth0 any more, the
** Changed in: network-manager (Ubuntu)
Target: None => ubuntu-7.10-beta
--
network-manager should stop managing any interface configured in
/etc/network/interfaces
https://bugs.launchpad.net/bugs/139403
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Summary changed:
- network-manager should stop managing auto dhcp interfaces
+ network-manager should stop managing any interface configured in
/etc/network/interfaces
--
network-manager should stop managing any interface configured in
/etc/network/interfaces
https://bugs.launchpad.net/bugs
28 matches
Mail list logo
