Posts

Showing posts with the label netctl

wifi confirmation

`systemctl start netctl-auto@wlp58s0` is definitely the way to go in the first instance when I don't automatically connect to an established profile. I think in the past I would restart netctl and that would take ownership away from from netctl-auto and that's when things started getting additionally messed up.

netctl issues? netctl-auto not working?

Throwing errors: could not create configuration file for wlp58s0 blah blah in journalctl -xe? sudo killall dhcpcp sudo ip link set wlp58s0 down systemctl start netctl-auto@[network]@wlp58s0

christ

OK, got netctl-auto handling my wifi as per the instructions on the nrtctl page in the Arch wiki (see last post for link). I also added a new service as described here: https://wiki.archlinux.org/index.php/netctl#Problems_with_netctl-auto_on_resume to handle automatic reconnection on resume from suspend. All good. Then I had a nice time adding some lines to .conkyrc to display relevant information about the network connection (when up). So now I think I have everything I need. The next ball-ache started when I started trying to add a netctl profile for the eduroam service at work. Not only could I not get this working, in the process of trying I somehow managed to stop my previously functional netctl-auto service from doing it's thing. *sigh*. Anyway, long story short: after trying all kinds of start/stop enable/disable I found that netctl start [profile] worked fine, it just wouln't work automatically. I found this forum post: https://bbs.archlinux.org/viewtopi...

wifi drama

xps suddenly started having wifi problems. something weird with NetworkManager and the brcmfmac driver/kernel module. p2p_disc error and the network interface wlp58s0 already assigned and nonsense like that. After fucking around for ages I thought I'd identified the issue as being a conflict between netctl and NM, but I've tried disabling netctl and it doesn't seem to resolve the problem with NM. netctl does, however, work perfectly for me, but it's not that useful for logging on to random networks when I'm out and about - the whole point of the xps. so, I'vebeen all round the houses, even trying to get rid of NM completely (can't becuase it's a cinnamon dependency *sigh*) and use systemd.networkd with the wpa_gui  (which is promising, but I can't get to work. I've also mesed about hiding .conf files and creating test ones at /etc/wpa_supplicant /etc/systemd/network, so look out for those if you're looking at this in the future!) my c...

losing network (dell latitude)

This has been bothering me for a while, and I've been rebooting to get reconnected. Not a good solution. The following command just worked for me: netctl restart my-network I'll continue testing with this and see if it works out for me. Forums suggest this is a bug with netctl and downgrading to an earlier version of wpa-supplicant might be a fix. [UPDATE] the above command won't work on if the ip interface (for me wlp2s0) is already up - the netctl service won't touch it. To correct: ip link set wlp2s0 down then netctl restart my-network the my-network profile is kept at /etc/netcl/ btw.