[RESOLVED] ifupdown / wpasupplicant wireless problem

[dkeg]

Something broke yesterday. I can no longer get dhcp offer from wireless. All was fine prior to yesterdays upgrade. I did restart the router too, but that's not the problem as all other devices sre still fine.

I rebooted for some forgotten reason after the upgrade and have been fucked since.

I can bring up eth0 no problem though.

I attempted to uninstall and reinstall the ifupdown package, but to no avail.

So I booted into Summer, which I have not been since installing Victory. I placed ifupdown and udev on hold and upgraded. But in the end, I have the same issue.

I even attempted to install the wheezy ifupdown package, but no go on that either.

So I need assistance here. I don't think it directly has to do with ifupdown, but I did not see other updates go through that could play a role.

Did wpasupplicant get upgraded? Maybe that's it. Is anyone else running into similar issues?

I'm on my phone so apologies for any fuck ups.

Thanks all!

[GekkoP]

I just dist-upgraded.
I still have the "ifup wlan0" in /etc/rc.local, everything is working fine.
I don't think it makes a difference, but I am on a setup with all the bloat that NetworkManager pulls in.
Sorry, not what you needed to hear.
Let me reboot and check if everything still works fine.

Edit: yes, still working here.

[machinebacon]

I can't nail the part that broke shit. The only fix I have for now:

sudo apt-get install wicd-curses

At least this shows my wireless device and the available networks.

Manu: it works for you /because/ of network-manager. All the 'allow-hotplug' devices are not recognized by ceni due to the udev bug.

[rhowaldt]

drew, my post here might be relevant to your situation? http://linuxbbq.org/bbs/viewtopic.php?p=42845#p42845
not that it solves anything, just info :)

[dkeg]

Thank you gents. But no, that's not it rho. I cannot not get the fuckin dhcp offer, but only on wlan0. I get all the request output. WTF. I'm pissed. I can deal with fuck ups, but not when it comes to network connections. Well, I'll look at it again tonight and post back.

[machinebacon]

^ totally understand you, Drew. This is a show-stopper. Try wicd-curses (or -cli), and maybe try the 'fixed' driver from siduction (which should be 0.43.x, not 0.44). I downgraded my ipw2200, installed wicd-curses, rebooted (with OpenRC, by the way), and all is well after running wicd-curses.

[dkeg]

Thank you. I'm also running openrc. I'll post an update tonight. Good to know I'm not crazy.

Thanks again!!

[rhowaldt]

perhaps if this is how ceni is working for us now, it is a good thing whatshisname was working on a script to do this, no?

[vic]

Ok, got wicd-curses to connect automatically to wireless network.

[dkeg]

I'm not going to set as resolved yet, but it started to work yesterday night. Not at first, and I had come home with the intent of just being done with it and installing wicd-curses. Then I saw what it brought in. I wasn't happy. So I just had to try again. I had connected to eth0 already of course, so I updated to see if whatever it was, got fixed. I should have scroted or copied the updates, not many, and nothing blaringly obvious having anything to do with network. And still, after the updates, nothing. I rebooted, tried again. Fail. Connected back to eth0.

By now, I was residing myself to wicd-curses even with the shit it brought in (dbus, dbus-x11). I was thinking positive and how I would take full advantage of a working dunst again. And that I would vow to never look at my dbus whored pstree again.

I tried one more time to connect, my last ditch 'well, one more time before I jump'. I had no hope, it was just for completeness. No one could say I didn't try.

Code: Select all

sudo ifdown eth0 && sudo ifup wlan0

But wlan0 was already configured. I guess I didn't bring it down prior to bringing up eth0 on one of my attempts. So I brought it down; then up

Code: Select all

sudo ifdown wlan0

Code: Select all

sudo ifup wlan0

and for fucks sake, it worked!. I have absolutely no idea. I don't even remember what was updated. Grub and grub-common, past that though, ???.

I have not rebooted yet, I'm scared. I usually don't reboot on weekends anyway, but maybe I will experiment for the sake of this thread.

Let me have some more coffee first ....

[dkeg]

successul wlan connection after reboot. Marking resolved. Thanks everyone for listening and helping.

[machinebacon]

So, is the solution this?

#optional: install wicd-curses
sudo ifdown wlan0
sudo ifup wlan0
#optional: scan for desired network with wicd if not already done so

[dkeg]

nope, I never installed wicd-curses. I really don't know what fixed it, but thought it would be a fun story.

[wuxmedia]

weird, I have not istalled anything at all, so no wlan0 this morning, after an upg just now;

Code: Select all

wux@numenor:~$ sudo ifdown wlan0
ifdown: interface wlan0 not configured
wux@numenor:~$ sudo ifup wlan0
Internet Systems Consortium DHCP Client 4.3.2
Copyright 2004-2015 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

Listening on LPF/wlan0/00:18:de:25:cf:1a
Sending on   LPF/wlan0/00:18:de:25:cf:1a
Sending on   Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 12
DHCPREQUEST on wlan0 to 255.255.255.255 port 67
DHCPOFFER from 192.168.1.254
DHCPACK from 192.168.1.254
bound to 192.168.1.70 -- renewal in 35761 seconds.

nothing too intersting in the upgrade:

Code: Select all

The following packages will be upgraded:
  cpp-4.9 g++-4.9 gcc-4.9 gcc-4.9-base libasan1 libgcc-4.9-dev libgnutls-deb0-28 libgnutls-openssl27 libpcre3 libssl1.0.0 libstdc++-4.9-dev libwayland-client0 libwayland-cursor0 libwayland-server0 openssl vim
  vim-common vim-runtime
18 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 42.7 MB of archives.
After this operation, 601 kB of additional disk space will be used.
Do you want to continue? [Y/n] y

[rhowaldt]

that's the same shit i had happen, but without it working after reboot. might dist-upgrade again just to see :)