** Changed in: gnome-system-tools (Ubuntu)
Assignee: (unassigned) = Ubuntu Desktop Bugs
Status: Needs Info = Unconfirmed
--
Changing ESSID requires reboot or, or manual iwconfig for changes to take effect
https://bugs.launchpad.net/bugs/80499
You received this bug notification
Did some more searching today and I now think my problem is a duplicate
of bug #92299
--
Changing ESSID requires reboot or, or manual iwconfig for changes to take effect
https://bugs.launchpad.net/bugs/80499
You received this bug notification because you are a member of Ubuntu
Bugs, which is the
Hi guys,
Just in case it helps ... I was having the same problem and the best way I
found to get over this situation was just to remove:
#wireless-essid mySSID
#wireless-key myWirelessKey
then reboot. After that the icon showing signal strength appeared in the
quick launch bar. Clicking on it
The netbase part of this seems to be working according to the most
recent message (it would actually have been a wireless-tools bug) -- so
the bug now must be just that the network admin tool doesn't ifdown/ifup
the card properly?
** Changed in: gnome-system-tools (Ubuntu)
Sourcepackagename:
Did a little experiment on boot today. I booted into safe mode. When I
landed at the root command prompt I typed ifconfig and discovered that
the network was working fine at that point. ifconfig reported my IP
address and I was able to ping the internet.
I then did telinit 5 to complete the
the new comment seems to describe a network-manager bug
--
Changing ESSID requires reboot or, or manual iwconfig for changes to take effect
https://launchpad.net/bugs/80499
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Since yesterday's updates, the behaviour has changed a little - I still
have no network connection on boot (and the essid is not set). But now,
when I run
$ sudo /etc/init.d/networking restart
it does set the essid and start the network properly. So only one
command to run each time I start my
Related to this (I think) is that the network restart does not set the
essid for me any more. I've just upgraded to feisty with settings that
used to work. The relevant part of /etc/network/interfaces is
auto wlan0
iface wlan0 inet dhcp
wireless-essid default
wlan0 is my primary interface.
** Tags added: essid iwconfig network-admin reboot restart wep wi-fi
--
Changing ESSID requires reboot or, or manual iwconfig for changes to take effect
https://launchpad.net/bugs/80499
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
The user that reported bug #67152 is now experiencing identical behavior:
https://launchpad.net/ubuntu/+source/gnome-system-tools/+bug/67152
--
Changing ESSID requires reboot or, or manual iwconfig for changes to take effect
https://launchpad.net/bugs/80499
--
ubuntu-bugs mailing list
Not a gnome-system-tools, not sure of if that's a linux or network stack
problem, reassigning to netbase the bug has probably enough information
to be picked by somebody working on network
** Changed in: gnome-system-tools (Ubuntu)
Sourcepackagename: gnome-system-tools = netbase
--
Changing
I did some more troubleshooting. I can get the exact same results by
manually editing the /etc/networking/interfaces and restarting
networking thus yes -- I mis-categorized this bug report by selecting
gnome-system-tools package. I don't know if the problem is in the
ifupdown package, or
Thank you for your bug. The network-config job is to the change the
config file and restart the network, if sudo /etc/init.d/networking
restart doesn't apply the changes that's not a network-admin bug. The
DHCP doesn't reply according to No DHCPOFFERS received., are you sure
that's not a bug from
13 matches
Mail list logo
