Like I said, I don't know how to get the stock network manager to connect to a network. I am on a late 2010 MacBook Air, so I don't have an ethernet port. I need wifi to connect to the internet. Everything else is running fine and dandy.
I'd usually assign this to some problems with the drivers or the firmware. This being a MacBook makes it even more likely. However, the weird part is that I CAN connect to wifi with no problems at all if I use the terminal. Here are the commands I use:
This makes it all work perfectly. But the thing is, it's a pain in the ass to connect to any network with a password, and it also doesn't support automatic reconnecting or anything like that. I don't want to have to do this every time.
Here are some other things I've tried:
This didn't help. It wasn't just a bad install.
I tried instaling WICD instead and seeing if that would work, but there were some things wrong with it. First, I couldn't get it into wingpanel. Second, it's as ugly as all hell. Third, it still wouldn't connect to a network. Seriously, it did the same thing the stock network manager did. Got stuck on "Obtaining IP Address".
I don't know what to do, guys. Can anyone help? Much appreciated.
I had problems with network manager on ubuntu , so i set up static networking. You can follow these steps and it will work ( i configured only wlan0 because i use wireless , you just need to skip the wireless related things in it)
Show your interfaces:
Note the default Ethernet and wifi interfaces:
It looks like our Ethernet port is eth0. Our WiFi radio is wlan0. Want to make this briefer?
The output of this command will look something like this:
Your gateway IP address is found with:
It provides access to destination 0.0.0.0 (everything). In the below image it is 192.168.0.1, which is perfectly nominal.
route-n Let’s do a bit of easy configuration in our /etc/networking/interfaces file. The format of this file is not difficult to put together from the man page, but really, you should search for examples first. interfaces Plug in your Ethernet port.
Basically, we’re just adding DHCP entries for our interfaces. Above you’ll see a route to another network that appears when I get a DHCP lease on my Ethernet port. Next, add this:
Next, enable and start the networking service:
Let’s make sure this works, by resetting the port with these commands:
This downs the interface, flushes the address assignment to it, and then brings it up. Test it out by pinging your gateway IP: ping 192.168.0.1. If you don’t get a response, your interface is not connected or your made a typo.
Let’s “do some WiFi” next! We want to make an /etc/wpa_supplicant.conf file. Consider mine:
Now we can reset the WiFi interface and put this to work:
That should do it. Use a ping to find out, and do it explicitly from wlan0, so it gets it’s address first:
you’re now running without NetworkManager!
answered Jan 3 '16 at 19:00