** Changed in: network-manager
Importance: Unknown => Medium
--
NetworkManager does not set channel when creating ad-hoc network
https://bugs.launchpad.net/bugs/112009
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs ma
fixed in 0.7 (available in intrepid)
** Changed in: network-manager (Ubuntu)
Status: Triaged => Fix Released
--
NetworkManager does not set channel when creating ad-hoc network
https://bugs.launchpad.net/bugs/112009
You received this bug notification because you are a member of Ubuntu
Bug
can we close the NM task now that 0.7 is in intrepid?
--
NetworkManager does not set channel when creating ad-hoc network
https://bugs.launchpad.net/bugs/112009
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
** Changed in: network-manager (Ubuntu)
Target: ubuntu-8.04.1 => None
--
NetworkManager does not set channel when creating ad-hoc network
https://bugs.launchpad.net/bugs/112009
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
u
** Changed in: network-manager (Ubuntu)
Target: ubuntu-8.04 => ubuntu-8.04.1
--
NetworkManager does not set channel when creating ad-hoc network
https://bugs.launchpad.net/bugs/112009
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Attached. Note that I've changed my wireless interface to be called
"wlan0" using /etc/iftab.
** Attachment added: "Syslog after reproduction"
http://launchpadlibrarian.net/13263099/syslog_post.txt
--
NetworkManager does not set channel when creating ad-hoc network
https://bugs.launchpad.net/
please attach your /var/log/syslog taken after you reproduced this bug.
--
NetworkManager does not set channel when creating ad-hoc network
https://bugs.launchpad.net/bugs/112009
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu
Mode, ESSID and channel are now set correctly, but only momentarily -
network-manager roams to a stronger network (a preferred one) after a
few seconds. I'm not sure whether this should be considered a part of
this bug. (wpasupplicant 0.6.0+0.5.8-0ubuntu2, network-manager
0.6.6-0ubuntu5)
On Thu, A
I'll only be able to check this on Sunday, when I'm at my laptop.
Sorry for the delay.
On Thu, Apr 3, 2008 at 7:33 PM, Alexander Sack <[EMAIL PROTECTED]> wrote:
> ping! ... would be good to know if this need attention before we release
> hardy in a few days.
>
>
>
> --
> NetworkManager does not
ping! ... would be good to know if this need attention before we release
hardy in a few days.
--
NetworkManager does not set channel when creating ad-hoc network
https://bugs.launchpad.net/bugs/112009
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
ok, could you please test with the latest version?
--
NetworkManager does not set channel when creating ad-hoc network
https://bugs.launchpad.net/bugs/112009
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ub
The channel seems to be set appropriately (according to iwlist
channel), but I haven't had the chance to test this with another
laptop. (Also, I'm not sure, but it seems that the mode and ESSID
aren't set to what I request)
On Tue, Mar 18, 2008 at 11:54 PM, Alexander Sack <[EMAIL PROTECTED]> wrote
moving milestone ahead - waiting for answer.
** Changed in: network-manager (Ubuntu)
Target: ubuntu-8.04-beta => ubuntu-8.04
--
NetworkManager does not set channel when creating ad-hoc network
https://bugs.launchpad.net/bugs/112009
You received this bug notification because you are a memb
does this now work in hardy with the new supplicant?
--
NetworkManager does not set channel when creating ad-hoc network
https://bugs.launchpad.net/bugs/112009
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
This bug was fixed in the package wpasupplicant - 0.6.0+0.5.8-0ubuntu2
---
wpasupplicant (0.6.0+0.5.8-0ubuntu2) hardy; urgency=low
* 10_set_channel_in_adhoc_mode: make wpasupplicant set the frequency when.
LP: #112009. Patch prepared by Kel Modderman for debian.
* 10_silence_s
ok, we should try the supplicant patch then. milestoning.
** Changed in: wpasupplicant (Ubuntu)
Status: Invalid => Triaged
Target: None => ubuntu-8.04-beta
** Changed in: network-manager (Ubuntu)
Importance: Undecided => Medium
Status: In Progress => Triaged
Target:
Yes, that's the one.
On Feb 12, 2008 12:36 AM, Alexander Sack <[EMAIL PROTECTED]> wrote:
> is it: http://bugzilla.gnome.org/attachment.cgi?id=101662&action=view ?
>
>
> --
> NetworkManager does not set channel when creating ad-hoc network
> https://bugs.launchpad.net/bugs/112009
> You received thi
is it: http://bugzilla.gnome.org/attachment.cgi?id=101662&action=view ?
--
NetworkManager does not set channel when creating ad-hoc network
https://bugs.launchpad.net/bugs/112009
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
could you attach the supplicant patch for 0.5.8?
--
NetworkManager does not set channel when creating ad-hoc network
https://bugs.launchpad.net/bugs/112009
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing lis
On Tue, Jan 08, 2008 at 09:48:02AM -, Ohad Lutzky wrote:
> Note that this bug is only Fixed for wpasupplicant 0.6 and above, so if
> we want NM to work with it, wpasupplicant has to be updated. (I have a
> fix for current wpasupplicant, which Dan Williams sent, but it would
> probably be better
Note that this bug is only Fixed for wpasupplicant 0.6 and above, so if
we want NM to work with it, wpasupplicant has to be updated. (I have a
fix for current wpasupplicant, which Dan Williams sent, but it would
probably be better to go for all-out 0.6)
--
NetworkManager does not set channel when
** Changed in: network-manager (Ubuntu)
Assignee: (unassigned) => Alexander Sack (asac)
Status: Invalid => In Progress
** Changed in: wpasupplicant (Ubuntu)
Status: Confirmed => Invalid
--
NetworkManager does not set channel when creating ad-hoc network
https://bugs.launchpad.
** Changed in: network-manager
Status: Confirmed => Fix Released
--
NetworkManager does not set channel when creating ad-hoc network
https://bugs.launchpad.net/bugs/112009
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
** Changed in: network-manager
Status: New => Confirmed
--
NetworkManager does not set channel when creating ad-hoc network
https://bugs.launchpad.net/bugs/112009
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bu
In case it wasn't clear, I request to reopen, and remove wpasupplicant
from "affects".
--
NetworkManager does not set channel when creating ad-hoc network
https://bugs.launchpad.net/bugs/112009
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact fo
OK, I now have much more insight into how this works. This is not a
wpa_supplicant issue. Attached is a patch which *should* resolve the
problem.
** Attachment added: "Ad-hoc channel"
http://launchpadlibrarian.net/10990367/adhoc_channel.patch
--
NetworkManager does not set channel when creati
It is, at the very least, not STRICTLY a wpasupplicant issue: wpasupplicant
can add an interface to set the channel, but even if that were the case,
NetworkManager would still need to use that interface. Please reopen.
On 10/8/07, Alexander Sack <[EMAIL PROTECTED]> wrote:
>
> this looks like a wpa
this looks like a wpasupplicant issue.
** Also affects: wpasupplicant (Ubuntu)
Importance: Undecided
Status: New
** Changed in: wpasupplicant (Ubuntu)
Status: New => Confirmed
** Changed in: network-manager (Ubuntu)
Status: Incomplete => Invalid
--
NetworkManager does n
I don't really know... I usually choose 11, but I don't know if
there's a standard. I'm not too sure as to which one of them should do
it, but I guess it would be better to do it from NM first, as it's
easier, and then migrate it over into WPASupplicant if that solution
is deemed cleaner.
On 9/24/
so which channel should be chosen by network-manager? maybe that should
be done by wpasupplicant?
--
NetworkManager does not set channel when creating ad-hoc network
https://bugs.launchpad.net/bugs/112009
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
Here it is (grepped for NetworkManager from oldest syslog)
Sep 16 09:20:25 dolphin NetworkManager: [1189927225.033006]
nm_hal_device_added(): New device added (hal udi is
'/org/freedesktop/Hal/devices/pci_8086_3580').
Sep 16 09:20:25 dolphin NetworkManager: [1189927225.499577]
nm_hal_device_adde
you did not include the syslog bits that show which driver is detected.
Please do so (should be logged on n-m startup).
Thanks,
- Alexander
--
NetworkManager does not set channel when creating ad-hoc network
https://bugs.launchpad.net/bugs/112009
You received this bug notification because you
Relevant Syslog bit:
Sep 21 17:17:23 dolphin NetworkManager: Creating network
'my_adhoc_network' on device
'/org/freedesktop/NetworkManager/Devices/eth1'.
Sep 21 17:17:23 dolphin NetworkManager: Device eth1 activation
scheduled...
Sep 21 17:17:23 dolphin NetworkManager: Deactivating device e
sorry for the delay,
if you still see this bug, please attach your /var/log/syslog and
/var/log/daemon.log.
Thanks,
- Alexander
--
NetworkManager does not set channel when creating ad-hoc network
https://bugs.launchpad.net/bugs/112009
You received this bug notification because you are a membe
** Changed in: network-manager (upstream)
Status: Unknown => New
--
NetworkManager does not set channel when creating ad-hoc network
https://bugs.launchpad.net/bugs/112009
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
** Bug watch added: GNOME Bug Tracker #466954
http://bugzilla.gnome.org/show_bug.cgi?id=466954
** Also affects: network-manager (upstream) via
http://bugzilla.gnome.org/show_bug.cgi?id=466954
Importance: Unknown
Status: Unknown
--
NetworkManager does not set channel when creating
Yes, bug is still present in Gutsy Tribe 4.
--
NetworkManager does not set channel when creating ad-hoc network
https://bugs.launchpad.net/bugs/112009
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubu
is this bug still present in latest gutsy network-manager?
** Changed in: network-manager (Ubuntu)
Status: New => Incomplete
--
NetworkManager does not set channel when creating ad-hoc network
https://bugs.launchpad.net/bugs/112009
You received this bug notification because you are a memb
Very same problem here with ipw3945. Quite a disappointment for me,
since I hoped I will not have to touch the command-line for network
configuration in Feisty.
--
NetworkManager does not set channel when creating ad-hoc network
https://bugs.launchpad.net/bugs/112009
You received this bug notific
39 matches
Mail list logo
