Basically, you can follow any socket server tutorial, and you don't really need to use any library for this, although they would make it somewhat simpler some of the time, as long as you understand the basics.
I would try to make a basic chat program using simple TCP/UDP sockets (make sure you understand the difference and choose what best suits your case) ...
With respect to my question at https://raspberrypi.stackexchange.com/a/117643/125839 I found that,editing /etc/dhcpcd.conf file (and do not confuse with /etc/dhcp/dhcclient.conf) can force dhcpdcd to give static ip of out choice.
example (add following in /etc/dhcpcd.conf):
Based on ingo's answer, I thought of using dhcpcd.
I am Sharing my experience (Likely to be useful to newbee and irritating to masters)
I kept my old /etc/network/interface file as it is.
First, as soon as dhcpcd was started, my ssh connection hanged
After first reboot, it momentarily pinged to old( 192.168.1.2 , see question above) address. But in few ...
Read 100s of answers for How to setup static wifi on pi
I am summarizing my experience:
Relevant for oragepi / rasberrypi
Why: a pi attached to USB power supply with no 'strings' attached is the goal
Connect with LAN (Because Wifi is not set / may get broken during trial
systemctl disable NetworkManager (to disable nmtui)
content of /etc/network/...
You can setup an access point on the RasPi so the smartphone can connect to it. There are hundreds of tutorials about this on the web, but many of them are outdated. The official Raspberry Pi web site for this you can find at Setting up a Raspberry Pi as a routed wireless access point or at Setting up a Raspberry Pi as a bridged wireless access point but ...
I have the same issue, and did not really understood the root cause but found a solution. It looks like DHCPC service failed to load once docker is running/started
You can check by running this, if Wireless is back to life it's likely the same issue I had
sudo systemctl restart dhcpcd
The clean fixed I did, was to edit the dhcpcd.service and adding a ...
The setup should not be a big problem because there are no routing requirements. The wired subnet is isolated from the wireless subnet. So you can just connect wireless to the internet router with wpa_supplicant as usual. The wired connections should work out of the box when only using static ip addresses and no name resolution. To be more comfortable you ...