Raspberry Pi - Who's gonna have a dabble?
Discussion
Nimby said:
FWIW I have my router as DHCP server, setting RPi-PiHole as primary DNS to clients and itself as secondary.
The router uses my ISP's DNS server.
PiHole uses Google DNS server. That way I can rebuild the RPi (or it can crash, as it does occasionally) without affecting clients.
Also note- if you're running Buster version of Raspbian you have to type "pi.hole/admin/" in the browser for the admin console. "pi.hole" by itself no longer works.
That would also mean that only 50% of all DNS activity goes over the RPi, as the router will use the Round Robin approach and randomly pick one of the addresses you provided. The obvious positive side of this is indeed that your network won't go down when the RPi is not working for some reason.The router uses my ISP's DNS server.
PiHole uses Google DNS server. That way I can rebuild the RPi (or it can crash, as it does occasionally) without affecting clients.
Also note- if you're running Buster version of Raspbian you have to type "pi.hole/admin/" in the browser for the admin console. "pi.hole" by itself no longer works.
Bought one and had it delivered, my mission is to install Retropi and use it as a part of a arcade console running MAMA games. I'm a complete novice and have no experience of programming or computers so I am a little worried about how easy it is to set up and if I have bitten off more than I can chew!
So far I managed to put it together and get it showing on my TV but couldnt get it to connect to WIFI so that's tonights mission! Youtube on the laptop all night for me!
So far I managed to put it together and get it showing on my TV but couldnt get it to connect to WIFI so that's tonights mission! Youtube on the laptop all night for me!
Tony Angelino said:
So far I managed to put it together and get it showing on my TV but couldnt get it to connect to WIFI so that's tonights mission! Youtube on the laptop all night for me!
This requires a bit of manual editing:https://raspberrypihq.com/how-to-connect-your-raspberry-pi-to-wifi/ said:
Configuring your WiFi network
To tell the Raspberry Pi to automatically connect to your WiFi network you need to edit a file called: wpa_supplicant.conf.
To open the file in nano type the following command:
sudo nano /etc/wpa_supplicant/wpa_supplicant.conf
Scroll to the end of the file and add the following to the file to configure your network:
network={
ssid="Test Wifi Network"
psk="SecretPassWord"
}
Remember to replace this with your own network name and password.
Save and close the file by pressing Ctrl+X followed by Y. At this point the Raspberry Pi should automatically connect to your network.
To tell the Raspberry Pi to automatically connect to your WiFi network you need to edit a file called: wpa_supplicant.conf.
To open the file in nano type the following command:
sudo nano /etc/wpa_supplicant/wpa_supplicant.conf
Scroll to the end of the file and add the following to the file to configure your network:
network={
ssid="Test Wifi Network"
psk="SecretPassWord"
}
Remember to replace this with your own network name and password.
Save and close the file by pressing Ctrl+X followed by Y. At this point the Raspberry Pi should automatically connect to your network.
Church of Noise said:
Nimby said:
FWIW I have my router as DHCP server, setting RPi-PiHole as primary DNS to clients and itself as secondary.
The router uses my ISP's DNS server.
PiHole uses Google DNS server. That way I can rebuild the RPi (or it can crash, as it does occasionally) without affecting clients.
Also note- if you're running Buster version of Raspbian you have to type "pi.hole/admin/" in the browser for the admin console. "pi.hole" by itself no longer works.
That would also mean that only 50% of all DNS activity goes over the RPi, as the router will use the Round Robin approach and randomly pick one of the addresses you provided. The obvious positive side of this is indeed that your network won't go down when the RPi is not working for some reason.The router uses my ISP's DNS server.
PiHole uses Google DNS server. That way I can rebuild the RPi (or it can crash, as it does occasionally) without affecting clients.
Also note- if you're running Buster version of Raspbian you have to type "pi.hole/admin/" in the browser for the admin console. "pi.hole" by itself no longer works.
I have another Pi running a webcam - perhaps I'll use that as a backup Pihole DNS. Thanks!
Edited by Nimby on Friday 16th August 18:08
Church of Noise said:
That would also mean that only 50% of all DNS activity goes over the RPi, as the router will use the Round Robin approach and randomly pick one of the addresses you provided. The obvious positive side of this is indeed that your network won't go down when the RPi is not working for some reason.
Why would the router round robin DNS? It would just send both DNS servers to the client in the DHCP response surely? Then the client makes a decision about which server to use.Church of Noise said:
Tony Angelino said:
So far I managed to put it together and get it showing on my TV but couldnt get it to connect to WIFI so that's tonights mission! Youtube on the laptop all night for me!
This requires a bit of manual editing:https://raspberrypihq.com/how-to-connect-your-raspberry-pi-to-wifi/ said:
Configuring your WiFi network
To tell the Raspberry Pi to automatically connect to your WiFi network you need to edit a file called: wpa_supplicant.conf.
To open the file in nano type the following command:
sudo nano /etc/wpa_supplicant/wpa_supplicant.conf
Scroll to the end of the file and add the following to the file to configure your network:
network={
ssid="Test Wifi Network"
psk="SecretPassWord"
}
Remember to replace this with your own network name and password.
Save and close the file by pressing Ctrl+X followed by Y. At this point the Raspberry Pi should automatically connect to your network.
To tell the Raspberry Pi to automatically connect to your WiFi network you need to edit a file called: wpa_supplicant.conf.
To open the file in nano type the following command:
sudo nano /etc/wpa_supplicant/wpa_supplicant.conf
Scroll to the end of the file and add the following to the file to configure your network:
network={
ssid="Test Wifi Network"
psk="SecretPassWord"
}
Remember to replace this with your own network name and password.
Save and close the file by pressing Ctrl+X followed by Y. At this point the Raspberry Pi should automatically connect to your network.
dxg said:
I have just realised that the square hyperpixel touch display that pimoroni sell is more or less the same size as a light switch. I now have visions of an embedded screen displaying.... Something. Would be awesome if it were to control the guess lights... Hmmm....
First step is to check that a zero and the screen will fit inside a single back box...
This didn't get any traction, but I have been exploring...First step is to check that a zero and the screen will fit inside a single back box...
The display and the backbox are exactly the same size! It would take a bit of trimming to get the display to sit flush and a flexible cable down to the pi zero, but it's a definite possibility. Take the power off the lighting circuit in some way?
Tune in next week when I tell you the story of how I burnt my house down...
Nimby said:
Church of Noise said:
Nimby said:
FWIW I have my router as DHCP server, setting RPi-PiHole as primary DNS to clients and itself as secondary.
The router uses my ISP's DNS server.
PiHole uses Google DNS server. That way I can rebuild the RPi (or it can crash, as it does occasionally) without affecting clients.
Also note- if you're running Buster version of Raspbian you have to type "pi.hole/admin/" in the browser for the admin console. "pi.hole" by itself no longer works.
That would also mean that only 50% of all DNS activity goes over the RPi, as the router will use the Round Robin approach and randomly pick one of the addresses you provided. The obvious positive side of this is indeed that your network won't go down when the RPi is not working for some reason.The router uses my ISP's DNS server.
PiHole uses Google DNS server. That way I can rebuild the RPi (or it can crash, as it does occasionally) without affecting clients.
Also note- if you're running Buster version of Raspbian you have to type "pi.hole/admin/" in the browser for the admin console. "pi.hole" by itself no longer works.
I have another Pi running a webcam - perhaps I'll use that as a backup Pihole DNS. Thanks!
Edited by Nimby on Friday 16th August 18:08
I have two for redundancy as you mention.
I've had a PiHut email this morning about an 8GB 4B model released for £74 (2GB is £34 and 4GB is £54)
https://thepihut.com/products/raspberry-pi-4-model...
https://thepihut.com/products/raspberry-pi-4-model...
ajprice said:
I've had a PiHut email this morning about an 8GB 4B model released for £74 (2GB is £34 and 4GB is £54)
https://thepihut.com/products/raspberry-pi-4-model...
Interesting development but what will it give us? I've been working with the 4GB one since lockdown on two screens - one displays an internet browser (multiple tabs), and the other a Citrix client into "work".https://thepihut.com/products/raspberry-pi-4-model...
It's not fast - all pages take a little while to load, and YouTube is a little choppy (screen tearing) but it's absolutely usable. If additional RAM would improve upon the page loading times, and YouTube quality, I would consider changing mine for one of the new ones but surely 4GB is enough to have fully loaded the OS into memory?
Anyone got a decent solution for a dashboard to view/manage multiple pis? Currently using RPI-monitor which gives the basics but it's one webpage per pi, although you can add a 'friends' link to easily get to the others. Just wondered if there's something out there to easily aggregate all pis into one display without going overboard with zabbix and the like.
Gassing Station | Computers, Gadgets & Stuff | Top of Page | What's New | My Stuff