No Way Know How

to detect the printer on my new WAN, I tried `avahi-browse -alr` but the demon wasn't running. `systemctl start avahi-daemon.service` sorted that.

I followed the post here: http://weworkweplay.com/play/automatically-connect-a-raspberry-pi-to-a-wifi-network/ to get a rpi wirelessly connected via a dongle. I set it with a static IP (207), but for some reason it's on the network twice - as 207 and 217. Why? Don't fucking know, don't fucking care.

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...

I just upgraded my raspberry pi media centre to raspi 3 running kodi on osmc. all is well apart from being unable to ping or ssh into my new pi on static IP 192.168.1.239. pinging gives me host unreachable. ssh gives me no route to host on port 22. tried adding -v to ping command on the suggestion of a forum troubleshooting post [mitch@latitude ~]$ ping -v 192.168.1.239 ping: socket: Permission denied, attempting raw socket... ping: socket: Permission denied, attempting raw socket... PING 192.168.1.239 (192.168.1.239) 56(84) bytes of data. From 192.168.1.153 icmp_seq=1 Destination Host Unreachable From 192.168.1.153 icmp_seq=2 Destination Host Unreachable From 192.168.1.153 icmp_seq=3 Destination Host Unreachable 64 bytes from 192.168.1.239: icmp_seq=4 ttl=64 time=83.6 ms 64 bytes from 192.168.1.239: icmp_seq=5 ttl=64 time=102 ms 64 bytes from 192.168.1.239: icmp_seq=6 ttl=64 time=22.7 ms 64 bytes from 192.168.1.239: icmp_seq=7 ttl=64 time=44.2 ms 64 bytes from 192.168.1.239: i...

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.