The packages libnm-glib0_0.6.5-0ubuntu2, libnm-util0_0.6.5-0ubuntu2 and
network-manager_0.6.5-0ubuntu2 fix the problem for me. I can connect to
PAL2.0 and the connection doesn't drop (so far!) but I still have to
setup PAL2.0 every time I want to connect to the wireless network here
at Purdue. Is t
This has fixed the problem. Thanks Alex and Brandon!
--
Purdue Wireless + NetworkManager does not provide wireless connectivity
https://bugs.launchpad.net/bugs/144140
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs
the hidden network fix is in gutsy. If you still see your specific
problem, please reopen this bug.
** Changed in: network-manager (Ubuntu)
Status: Incomplete => Fix Released
--
Purdue Wireless + NetworkManager does not provide wireless connectivity
https://bugs.launchpad.net/bugs/144140
please test the network-manager packages available in my ppa (
http://ppa.launchpad.net/asac/ubuntu/pool/main/n/network-manager/) ...
the version to test is 0.6.5-0ubuntu16~ppa3 ... it contains a fix for
hidden networks. Maybe it helps for you as well.
--
Purdue Wireless + NetworkManager does not
I went through my syslog compared to Brandon's and marked a line in mine
(an IPv6 error) that Brandon didn't have. Also, I noticed that he
connects to the network after the timeout period that stops my
NetworkManager. Is there a way to configure NM's timeout to be greater?
** Attachment added: "Up
I can't seem to get NM to crash again. Sometimes it crashes regularly
(as seen in my first syslog post) but when I want it to crash, no luck.
I'll keep trying.
--
Purdue Wireless + NetworkManager does not provide wireless connectivity
https://bugs.launchpad.net/bugs/144140
You received this bug n
Thanks Alexander. I may not get to this until the weekend but I will do it.
-Luke
--
Purdue Wireless + NetworkManager does not provide wireless connectivity
https://bugs.launchpad.net/bugs/144140
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact
Luke, I added a section for DebuggingCrashes to
https://wiki.ubuntu.com/DebuggingNetworkManager ... please try if it
gets you a good backtrace and attach that.
Thanks,
- Alexander
--
Purdue Wireless + NetworkManager does not provide wireless connectivity
https://bugs.launchpad.net/bugs/144140
Luke, please capture a crash with debug symbols installed and with gdb
attached.
--
Purdue Wireless + NetworkManager does not provide wireless connectivity
https://bugs.launchpad.net/bugs/144140
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact f
Alexander,
Here is a syslog from Gutsy. I couldn't use my D620 for this since all that's
available in the current daily builds is the alternate CD and not the live CD.
So I ended up using a Dell Inspiron 700m with an Intel 2915ABG chipset in it
for this test. Again, it worked just fine (after I
Alexander,
Here's the syslog that fails to connect (and with Gutsy, will not attempt to
connect again even if I click on PAL2.0 from the NM menu) without crashing. I'm
realizing that it crashes a lot more than I thought, though, and I can only get
the crash on PAL2.0.
** Attachment added: "Sysl
Luke, yes please install debug symbols post the crash backtrace.
Brandon, thats great ... can you please test if this works with the
latest gutsy livecd as well? You can download it from
http://cdimage.ubuntu.com/daily/current/
Thanks,
- Alexander
--
Purdue Wireless + NetworkManager does not
... one more thing, please get syslog up that fails to connect even
though nm doesn't crash.
Thanks a lot,
- Alexander
--
Purdue Wireless + NetworkManager does not provide wireless connectivity
https://bugs.launchpad.net/bugs/144140
You received this bug notification because you are a member o
I got Fiesty up and running on my Dell D620 laptop this afternoon via
LiveCD running from a USB pendrive. The machine has an Intel 3945ABG
chipset in it and I've got it running on PAL2.0 just fine right now. Not
sure what I did either, I just configured it from NetworkManager and off
it went. I've
I realized after coming to campus and grabbing the syslog that I don't
have the debug symbols installed. I'll have to grab those and I'll post
an updated syslog tomorrow. I figured you may be able to get something
out of this one in the meantime, Alex.
** Attachment added: "Syslog of failed NM con
I am the wireless network administrator for Purdue. Luke has gotten me
involved in this issue for the technical background on how our wireless
environment is put together and how it functions. To answer your
question, we do not use mbssid because the hardware we have does not
support it. We have Ci
I don't have the technical background to answer this question. I'm
trying to get the experts from Purdue IT to jump on this thread. I'll
have to wait until I go on campus Monday to grab a syslog in the right
context.
--
Purdue Wireless + NetworkManager does not provide wireless connectivity
https
Thanks for (finally) open this bug.
So if I understand what you say correctly, your APs have to be hidden
because you cannot use mbssid, right?
Anyway, please attach the syslog for now.
Thanks,
- Alexander
** Changed in: network-manager (Ubuntu)
Status: New => Incomplete
** Changed in:
18 matches
Mail list logo
