** Branch unlinked: lp:~mathieu-tl/network-manager/0.9.4.0-0ubuntu4.2
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/1004775
Title:
NetworkManager restarts dnsmasq and adds host
** Changed in: network-manager (Ubuntu)
Status: Confirmed = In Progress
** Changed in: network-manager (Ubuntu)
Assignee: (unassigned) = Mathieu Trudel-Lapierre (mathieu-tl)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
dnsmasq is now in updates, and there is no SRU blocking network-manager
-- I'll upload the fix for this in -proposed today.
** Changed in: dnsmasq (Ubuntu Precise)
Status: In Progress = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team,
** Description changed:
+ [Impact]
+ This issue affects all users of NetworkManager in a dual stack (IPv4 w/ IPv6
on the same network) environment. When any router advertisement is received,
NetworkManager restarts dnsmasq in order to update the DNS configuration it
uses.
+ This change
I uploaded a new package to the precise queue last week.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/1004775
Title:
NetworkManager restarts dnsmasq and adds host route on every
It indeed appears to be directly related to bringing up IPv6.. However,
since IPv6 hotspots don't appear to currently being supported (no
iptables code, no parameters passed for it to dnsmasq, etc.; it probably
simply should be ignored in all cases.
** Changed in: network-manager (Ubuntu)
This was an issue in NM, fixed in 0.9.1.90-0ubuntu6: we'll default to IPv6:
Ignore if creating an ad-hoc network:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/830178
Closing as Fix Released for n-m and Invalid for dnsmasq.
** Changed in: network-manager (Ubuntu)
Status:
Public bug reported:
Please sync quota 4.00-3 (main) from Debian unstable (main)
Changelog entries since current precise version 4.00-1:
quota (4.00-3) unstable; urgency=low
* Port to libnl3 version 3.2.3+.
Thanks to Mathieu Trudel-Lapierre mathieu...@ubuntu.com (Closes: #653096
Closing as Fix Released since the upstream bug was also closed. All
indicates that this works properly at this point.
** Changed in: network-manager (Ubuntu)
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
** Also affects: dhcp3 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dhcp3 in Ubuntu.
https://bugs.launchpad.net/bugs/869635
Title:
long delay at shutdown/reboot -
** Package changed: dhcp3 (Ubuntu) = isc-dhcp (Ubuntu)
** Changed in: isc-dhcp (Ubuntu)
Status: New = In Progress
** Changed in: isc-dhcp (Ubuntu)
Importance: Undecided = High
** Changed in: isc-dhcp (Ubuntu)
Assignee: (unassigned) = Mathieu Trudel-Lapierre (mathieu-tl)
--
You
That wouldn't be the right process though. The configuration itself
shipped by default should be patched, that can be done with a simple
patch to the dnsmasq package.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dnsmasq in Ubuntu.
Well, that would normally be correct, but the VPN plugins depend on
vpnc, pptp, openvpn, etc. to be running to establish and keep the VPN
connection up for rekeying and such. Those don't get a pid file in
/run/sendsigs.omit.d yet, and so they would get killed by the sendsigs
script shortly before
I'll open a bug myself shortly for the VPN case; and reply here with the
bug number.
** No longer affects: network-manager
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/211631
Title:
This wouldn't really be different that=n using libc for resolving, so I
don't think it really qualifies as a security issue.
You can still perform DNSSEC validation, which is the actual difference
from if DNSSEC proxying wasn't supported by dnsmasq. Granted, it doesn't
automatically do the
Listening on lo is fine; and blocking other DNS servers from being
started isn't. I think we're in violent agreement there. The problem is
how to fix this.
I'm not saying dnsmasq should be crippled, but that it should special-
case lo and not just listen on 0.0.0.0; because that binds to any
of the problem cases here.
** Changed in: network-manager (Ubuntu)
Status: Confirmed = In Progress
** Changed in: network-manager (Ubuntu)
Assignee: (unassigned) = Mathieu Trudel-Lapierre (mathieu-tl)
** Changed in: network-manager (Ubuntu Precise)
Assignee: (unassigned
Shantanu Tushar: Since you can't reproduce your issue with your new ISP,
I'm closing this bug as Invalid. If you manage to reproduce it, feel
free to reopen by setting it back to New.
** Changed in: network-manager (Ubuntu)
Status: Incomplete = Invalid
** Changed in: dnsmasq (Ubuntu)
Public bug reported:
With software-properties 0.86 (https://launchpad.net/ubuntu/+source
/software-properties/0.86) which is about to land in quantal (in NEW at
the time of this writing); add-apt-repository is being moved from
python-software-properties to the software-properties-common package.
This also affects ubuntu-orchestra-client-juju; which also needs to
update its Depends line.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1021418
Title:
Replace
Thomas, Stéphane;
Yes, let's track the change for network-manager in bug #959037 -- marking the
task for n-m here as Invalid.
** Changed in: network-manager (Ubuntu)
Status: New = Invalid
** Changed in: network-manager (Ubuntu Precise)
Status: New = Invalid
--
You received this
** Also affects: dnsmasq (Ubuntu Precise)
Importance: Undecided
Status: New
** Also affects: pdnsd (Ubuntu Precise)
Importance: Undecided
Status: New
** Also affects: network-manager (Ubuntu Precise)
Importance: Undecided
Status: New
** Also affects: pdns-recursor
Well, first we'll ship the file for /etc/dnsmasq.d; changing it to bind-
dynamic after the fact is quick.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/959037
Title:
NM-controlled
No, it's supported in NM regardless of the distro used; it's just not
easy to configure; depends on the proper use of the config files.
Closing as Fix Released.
To configure it you'll need to create a new connection manually in
/etc/NetworkManager/system-connections; something like a file
The available parameters for the [vlan] block are defined in source:
http://cgit.freedesktop.org/NetworkManager/NetworkManager/tree/libnm-util/nm-setting-vlan.c#n608
However, the actual names to use (as key=) for the parameters are the
NM_SETTING_VLAN_* constants; which are defined here:
Trudel-Lapierre (mathieu-tl)
Status: In Progress
** Changed in: dnsmasq (Ubuntu)
Status: New = In Progress
** Changed in: dnsmasq (Ubuntu)
Importance: Undecided = Medium
** Changed in: dnsmasq (Ubuntu)
Assignee: (unassigned) = Mathieu Trudel-Lapierre (mathieu-tl)
--
You
(Ubuntu Precise)
Importance: Undecided = Medium
** Changed in: dnsmasq (Ubuntu Precise)
Assignee: (unassigned) = Mathieu Trudel-Lapierre (mathieu-tl)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dnsmasq in Ubuntu.
https
Thanks Simon!
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/1029977
Title:
dnsmasq-base should ship the dnsmasq dbus configuration file
To manage notifications about this bug go
** Description changed:
+ [Rationale]
+ Required for network-manager SRU for bug 1004775:
+ To properly handle updating DNS nameservers in the dnsmasq instance spawned
by NetworkManager; it would require starting dnsmasq with dbus enabled so that
all future dns changes could be done through
** Changed in: dnsmasq (Ubuntu Precise)
Status: In Progress = Triaged
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/1029977
Title:
dnsmasq-base should ship the dnsmasq dbus
Should it really be evolution to do this or postfix directly?
AFAIUI it makes more sense if it's done by postfix, if only to avoid
duplicating work in every application that might want to send mail...
and also because someone might want to manually send mail, and then
translating manually to an
** Also affects: dnsmasq (Ubuntu)
Importance: Undecided
Status: New
** Changed in: dnsmasq (Ubuntu)
Status: New = In Progress
** Changed in: dnsmasq (Ubuntu)
Importance: Undecided = High
** Changed in: dnsmasq (Ubuntu)
Assignee: (unassigned) = Mathieu Trudel-Lapierre
Any news about this?
There's actually multiple issues here; one of them being that loopback
probably isn't ready yet, which is something we fixed in NetworkManager
(which had the same issue) by depending on it through upstart before
starting the network-manager job.
Then, we now ship
** Changed in: dnsmasq (Ubuntu)
Status: Confirmed = In Progress
** Changed in: dnsmasq (Ubuntu)
Assignee: (unassigned) = Mathieu Trudel-Lapierre (mathieu-tl)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dnsmasq
** Changed in: network-manager (Ubuntu)
Status: Triaged = In Progress
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/1034946
Title:
dnsmasq and network manager broken if
Thomas, it would be best to open a bug upstream for documentation for
VLAN... and/or anyway file a new bug here for the documentation too
rather than reusing old bugs.
Michael: I think all you need for this is that the top section
('[connection]') is set autoconnect=true or so. It does work
** Changed in: network-manager (Ubuntu)
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/1034946
Title:
dnsmasq and network manager broken
in: dnsmasq (Ubuntu)
Importance: Undecided = Medium
** Changed in: dnsmasq (Ubuntu)
Assignee: (unassigned) = Mathieu Trudel-Lapierre (mathieu-tl)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dnsmasq in Ubuntu.
https
Thomas: no, this is a dnsmasq bug. Even if nothing is set to listen on
127.0.0.1, if dnsmasq is configured to avoid lo and bind to interfaces
(as it is per the network-manager provided configuration) it should
still do so and not write out lo.dnsmasq.
** Package changed: network-manager (Ubuntu)
(Ubuntu Precise)
Assignee: (unassigned) = Mathieu Trudel-Lapierre (mathieu-tl)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/959037
Title:
NM-controlled dnsmasq prevents other
in: dnsmasq (Ubuntu Precise)
Status: Confirmed = Triaged
** Changed in: dnsmasq (Ubuntu Precise)
Assignee: (unassigned) = Mathieu Trudel-Lapierre (mathieu-tl)
** Changed in: network-manager (Ubuntu Precise)
Importance: Low = High
--
You received this bug notification because you
This remains a bug, but fixing bug 1044388 is going to make this a much
more rare occurence.
Unassigning for now, the bug needs to be filed upstream and fixed by the
upstream maintainer.
** Changed in: dnsmasq (Ubuntu)
Assignee: Mathieu Trudel-Lapierre (mathieu-tl) = (unassigned)
--
You
I'm reassinging this to network-manager. The issue here is not related
to that upstream thread. Unfortunately, we don't have enough information
to debug this. Please answer the following questions:
Is 'dnsmasq' (the package), installed? (check with dpkg -l dnsmasq)
If so, what is its
I didn't try to reproduce yet, but I definitely believe there might be a
problem; so I'll look into it.
It's probably my fault too ;)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dnsmasq in Ubuntu.
(Ubuntu)
Assignee: (unassigned) = Mathieu Trudel-Lapierre (mathieu-tl)
** Package changed: dnsmasq (Ubuntu) = network-manager (Ubuntu)
** Changed in: network-manager (Ubuntu)
Milestone: None = ubuntu-12.10
--
You received this bug notification because you are a member of Ubuntu
Server
in: dnsmasq (Ubuntu Quantal)
Status: New = Fix Released
** Changed in: dnsmasq (Ubuntu Precise)
Status: New = In Progress
** Changed in: dnsmasq (Ubuntu Precise)
Importance: Undecided = High
** Changed in: dnsmasq (Ubuntu Precise)
Assignee: (unassigned) = Mathieu Trudel-Lapierre
** Changed in: dnsmasq (Ubuntu Precise)
Status: Triaged = In Progress
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/1029977
Title:
dnsmasq-base should ship the dnsmasq dbus
to the same
scripts in /etc/dhcp3; and changing this would need to be done in
Debian.
** Changed in: isc-dhcp (Ubuntu)
Status: In Progress = Triaged
** Changed in: isc-dhcp (Ubuntu)
Assignee: Mathieu Trudel-Lapierre (mathieu-tl) = (unassigned)
** Also affects: samba (Ubuntu
Seems the symlinks in Samba were done on purpose for upgrade
compatibility, since samba doesn't depend on the installed DHCP client
and can't know which is the correct directory to put the hooks in. At a
later point in Debian samba should drop that symlink.
** Changed in: samba (Ubuntu)
Closing vpnc/kvpnc/network-manager tasks. It's not an issue in network-
manager or vpnc; they were just inconvenienced by the fact that the
module wasn't available.
** Changed in: kvpnc (Ubuntu)
Status: New = Invalid
** Changed in: kvpnc (Ubuntu Lucid)
Status: New = Invalid
**
Now that we can use bind-dynamic, I have nothing against setting that
value instead of bind-interfaces, if it indeed solves the latest issues
that were reported.
However, I'd really appreciate if separate bugs could be opened rather
than reopening this bug, it would make each individual issue
(Ubuntu)
Assignee: (unassigned) = Mathieu Trudel-Lapierre (mathieu-tl)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1277450
Title:
lxc-autostart crashed with SIGSEGV in strlen
** Patch added: no_name_build_path.patch
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1277450/+attachment/3972302/+files/no_name_build_path.patch
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
I'm fixing this since it's so obvious... package is building in sbuild
right now, will test and upload shortly.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1277450
Title:
Actually, even better yet, the new patched attached.
Otherwise:
# lxc-autostart -L
lxc-autostart: could not build log path
lxc-autostart: could not build log path
lxc-autostart: could not build log path
--
You received this bug notification because you are a member of Ubuntu
Server Team, which
** Patch added: dont_crash_log_init.patch
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1277450/+attachment/3972362/+files/dont_crash_log_init.patch
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
Hi, thanks for filing this bug and helping to make Ubuntu better!
Unfortunately, this does not appear to be a bug in debian-installer, and
also it doesn't seem to be a bug at all: named listens on port 953 only
for the localhost, and that port is used by things like ndc to control
the server
It seems like this is a bug that has already been reported to the
developers of openSSH. Please consider commenting in the upstream bug
(https://bugzilla.mindrot.org/show_bug.cgi?id=1585) and proposing your
patch, possibly integrating some of the work in the draft patch that is
already included
Alexey, this indeed has nothing to do with NetworkManager.
If you just do:
sudo ifdown eth0.20
sudo ifup eth0.20
Is the device properly initialized and brought up?
** Package changed: network-manager (Ubuntu) = vlan (Ubuntu)
** Changed in: vlan (Ubuntu)
Status: New = Incomplete
--
It will take a few hours before evolution-mapi 3.2.0 is available (it's
currently in the queue, waiting for approval from the release team). In
the meantime, I think we can close this as Fix Released: there's been
various other revisions of Evolution and related packages, up to stable
version
Aaron, the issue you're reporting is something different, please file a
separate new bug report. We don't support just Unity but it does happen
that people run into issues that don't get identified until after
release, which is why it's good to file separate bugs for your own issue
(and I'll mark
Setting Invalid as per my conversation with Rick earlier today on IRC;
seems this is no longer reproduceable.
** Changed in: network-manager (Ubuntu)
Status: Incomplete = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
And... in excitement I write this in the wrong bug report. :) Please
disregard the above, it was meant for bug 856333.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/854833
Title:
(oneiric) wireless
Okay, I believe I've finally made good progress.. Even if it's quite sad
it happened so late ;)
To get more information, I decided to give the Fedora 16 Live CD a try,
since it was likely broken there too in which case I could provide
useful information to upstream to help with the debugging --
Okay, I believe I've finally made good progress.. Even if it's quite sad
it happened so late ;)
To get more information, I decided to give the Fedora 16 Live CD a try,
since it was likely broken there too in which case I could provide
useful information to upstream to help with the debugging --
So it was a painful issue, caused by the rtnl_route_alloc_cache() call
in... NetworkManager. Passing NL_AUTO_PROVIDE as a flag for the cache
creation causes issues, switching that to no flags (0) fixes the issue.
** Changed in: libnl3 (Ubuntu)
Status: Confirmed = Invalid
--
You received
** Changed in: network-manager (Ubuntu)
Assignee: (unassigned) = Mathieu Trudel-Lapierre (mathieu-tl)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/849994
Title:
FFE: add NetworkManager DUID
I was fixing a similar bug in NetworkManager (specific to having both
wired and wifi connected at the same time to the same underlying
network)... that's bug 856333. The upload of network-manager
0.9.1.90-0ubuntu2 fixes that issue.
--
You received this bug notification because you are a member
It's a pretty annoying bug, but it requires large changes to the design,
not something we can easily backport to Lucid.
Fortunately, the changes have been done upstream and the package that
includes this is now at least in the current development version:
Oneiric.
I'll mark this as Fix Released,
Thank you for taking the time to report this bug and helping to make
Ubuntu better. The issue that you reported is one that should be
reproducible with the live environment of the Desktop CD of the
development release - Oneiric Ocelot. It would help us greatly if you
could test with it so we can
This is likely an issue at the driver level with b43; have you tried the
other available driver, STA, which should be available to be installed
from the Restricted Drivers dialog (System-Administration) ?
** Package changed: network-manager-applet (Ubuntu) = linux (Ubuntu)
** Changed in: linux
Thank you for taking the time to report this bug and helping to make
Ubuntu better. The issue you are reporting is an upstream one and it
would be nice if somebody having it could send the bug to the developers
of the software by following the instructions at
Obviously, I'm an idiot so I didn't notice it was already upstream, so
please disregard this :)
** Changed in: network-manager-applet (Ubuntu)
Status: New = Confirmed
** Changed in: network-manager-applet (Ubuntu)
Importance: Undecided = High
** Changed in: network-manager-applet
Jo-Erlend; please file a separate bug. What you're describing doesn't
sound like the same issue at all, and instead looks like it might be
related to bug 855171. Please see that bug report and use the
workaround/fix in its description; and if this doesn't completely fix
your issue, file a new bug
Public bug reported:
NM 0.9.1.90 is arguably a beta for 0.9.2, but contains many useful
bugfix, despite very minimal new features:
d8edf0e release: bump version to 0.9.1.90 (0.9.2-beta1)
e6b834f release: update NEWS
f082e24 ifcfg-rh: fix crash when system bus isn't around
833bc16 build: honor
This is further useful to ship nm-applet 0.9.1.90 which is required for
gnome-control-center.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/855592
Title:
FFE: NetworkManager 0.9.1.90
To manage
** Changed in: network-manager-applet (Ubuntu)
Status: Incomplete = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/839883
Title:
no network icon after upgrade to oneiric
To manage
** Changed in: network-manager (Ubuntu Oneiric)
Status: Triaged = In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/797868
Title:
NetworkManager crashed with SIGSEGV in
** Changed in: network-manager (Ubuntu)
Status: New = Confirmed
** Changed in: network-manager (Ubuntu)
Importance: Undecided = High
** Changed in: network-manager (Ubuntu)
Assignee: (unassigned) = Mathieu Trudel-Lapierre (mathieu-tl)
--
You received this bug notification
There's an issue here at the driver level, NM can't read the MAC address for
the device which is why it can't start it for wifi:
Sep 19 10:41:49 eee-fede NetworkManager[608]: error [1316421709.315789]
[nm-device-wifi.c:3100] real_update_permanent_hw_address(): (wlan0): unable to
read permanent
I think this is driver-specific, really doesn't happen on any system
I've tried; reassigning to 'linux'.
Maybe there's something that changed in carrier-detection.
** Package changed: network-manager (Ubuntu) = linux (Ubuntu)
--
You received this bug notification because you are a member of
** Changed in: network-manager-applet (Ubuntu)
Status: Incomplete = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/852251
Title:
You can not edit or create new connection
To manage
Since a similar bug was closed as Invalid due to being fixed in an
update, could you please try again and comment here if it changed
anything after making sure your system is fully up to date?
My system here, also running iwlagn (but not the same device or laptop),
I have no issues clicking on
Closing as per reporter's comment.
** Changed in: network-manager (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/852121
Title:
network-manager failed to
There's an kernel crash listed there, and it seems to be the most likely
cause for failing to be able to send or receive data:
Sep 14 23:06:15 Latitude-E6400 NetworkManager[958]: info (wlan0): supplicant
interface state: 4-way handshake - completed
Sep 14 23:06:34 Latitude-E6400 kernel:
That's very weird. The last messages before disconnection is the following:
Sep 21 07:27:37 rick-qsus NetworkManager[894]: info Activation (wlan0) Stage
4 of 5 (IP6 Configure Timeout) complete.
Sep 21 07:56:15 rick-qsus wpa_supplicant[901]: CTRL-EVENT-DISCONNECTED
bssid=5c:33:8e:bd:99:70
Confirming; and this is fixed in Oneiric.
** Changed in: network-manager (Ubuntu)
Status: New = Fix Released
** Also affects: network-manager (Ubuntu Natty)
Importance: Undecided
Status: New
** Changed in: network-manager (Ubuntu Natty)
Status: New = Confirmed
--
You
This is a feature request I've already discussed shortly with Etienne
Goyer.
Setting as Wishlist/Confirmed since I can acknowledge the issue, except
there is a lack of easy ways to fix this.
Thinking back however, I'm certain there is a way of at least patching
NM so that the default wired
Looking at the code quickly, maybe emptying nm_settings_device_added()
(in src/settings/nm-settings.c:1425) is sufficient to block this
functionality.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Please use 'apport-collect 802948' to add additional debugging
information to this bug report (after reproducing the issue).
This is probably a kernel issue because NM didn't really change much for
hot-spots/ad-hoc networks, but we'll know more with the additional logs.
** Changed in:
Note the differences in DHCP requests and responses, all on the same
device:
Jul 3 06:48:25 zsolt-1000H dhclient: Listening on LPF/eth0/00:23:54:09:d2:fe
Jul 3 06:48:25 zsolt-1000H dhclient: Sending on LPF/eth0/00:23:54:09:d2:fe
Jul 3 06:48:25 zsolt-1000H dhclient: Sending on
Note the states NM_STATE_CONNECTED_GLOBAL and NM_STATE_CONNECTED are
essentially the same. Work is still needed to revise that patch but I
think it also needs work at the application level to check how available
the network is before trying to do stuff.
I'll need to know more about what's going
This is likely due to a local change on the system:
Jul 14 13:38:58 svart NetworkManager[812]: warn VPN connection
'BTGuard VPN' failed to connect: 'property 'progname=nm-openvpn-auth-
dialog; RGBA=on' invalid or not supported'
Please make sure your install is clean. You can reinstall
Please copy here what the output of the following command shows:
ip route list
** Changed in: network-manager (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This is possibly due to an issue at the network level, for instance with
the router. Please see if when you're connected and the traffic no
longer passes, what goes in and out of each interface eth0 and wlan0:
sudo tcpdump -i wlan0
sudo tcpdump -i eth0
I think you'll be able to see traffic going
Are you using the same process on both systems?
Note the errors here:
Sep 13 14:16:30 kristopher-LT21 NetworkManager[503]: info Executing:
/sbin/iptables --table filter --insert FORWARD --destination
10.42.43.0/255.255.255.0 --out-interface eth0 --match state --state
ESTABLISHED,RELATED --jump
AFAIK, autoconnection for mobile broadband is not yet supported.
Marking Wishlist/Confirmed. Some work will be needed there.
** Changed in: network-manager (Ubuntu)
Status: New = Confirmed
** Changed in: network-manager (Ubuntu)
Importance: Undecided = Wishlist
** Summary changed:
-
Hi, Could you please follow the steps in the NetworkManager debugging
page at http://live.gnome.org/NetworkManager/Debugging, in the
Debugging NetworkManager 0.8 and 0.9 3G connections section at attach
both ModemManager debugging logs and NetworkManager logs. Thanks in
advance!
** Package
*** This bug is a duplicate of bug 846868 ***
https://bugs.launchpad.net/bugs/846868
Marking as duplicate of your other bug 846868. The modem appears to be
seen properly (see ttyUSB3 which tried to activate the Virgin Mobile 1
connection).
** This bug has been marked a duplicate of bug
This should be been mostly fixed in Oneiric now, with the latest
revision of NetworkManager and nm-applet.
To clarify, I guess what you mean was that wired would be connected but
then no traffic at all would pass unless the connection was re-
established?
Regardless, I can see it appears to work
1 - 100 of 8150 matches
Mail list logo
