Why do you all insist on DHCP for your Raspberries?
In my set up all wired devices use a static IP address. Only roaming and wireless use DHCP.
My Raspberries are wired.
Makes my life much easier.
In my set up all wired devices use a static IP address. Only roaming and wireless use DHCP.
My Raspberries are wired.
Makes my life much easier.
I have 2 set up at opposite ends of my home. Why run wires from my wireless router all over the place when I can use wifi and stream FLAC right to the amp?
Well, I got ethernet drops everywhere. Our house has 1600 linear feet of Cat5e, with two wireless access points -AP. (*) and three switches using Spanning Tree.
I don't have a "wireless router"... I have real router and my DHCP server is in one of the APs.
To build this, the easiest way is configure your standard "wireless router" so it runs as a transparent bridge: No IP address on the WAN side and make sure the network configuration points to the real router wired in the LAN side. The APs have a static IP address on their LAN side.
Now just to make life a bit more complicated, for the APs, the configuration page is *** backwards. Their WAN side is actually the wired LAN segment. The side "upstream" from the wireless segment.
I don't have a "wireless router"... I have real router and my DHCP server is in one of the APs.
To build this, the easiest way is configure your standard "wireless router" so it runs as a transparent bridge: No IP address on the WAN side and make sure the network configuration points to the real router wired in the LAN side. The APs have a static IP address on their LAN side.
Now just to make life a bit more complicated, for the APs, the configuration page is *** backwards. Their WAN side is actually the wired LAN segment. The side "upstream" from the wireless segment.
Last edited:
With absolutely no RPi or Linux experience I had my music server up and running in about a half an hour using Volumio, and that included the unboxing of the Pi. I had already downloaded the Volumio image to my Mac. I vaguely recall using Etcher to burn the image to an SD card, but I know there is another program I use now. I plugged the SD card into the Pi and it booted into Volumio. I found the network hotspot it created from my Mac, went into a browser and typed Volumio.Local (I think that was it) and the setup screen came up and prompted me for the real network name/PW. I put those in and rebooted the Pi and reconnected to my wifi and it just worked. It showed up on my Mac as an audio output device via Airplay, and from within Audirvana as a UPnP/DLNA device. And it just played...
Yeah, but like all things Apple, good luck debugging it the day it fails.
And the day will come.
And the day will come.
I gave my first RPi + Allo Boss to a relative. When I got to her house, I found she had a cable model with one lonely Ethernet port on it plugged straight into a Google Home wireless setup (with no Ethernet ports on it). A purely wireless network. Ugh. I tried to make the RPi a wireless hotspot but that refused to work. I don't know why. In the end I had to go a friend's house to borrow their Ethernet connection to set up Moode with the SSH and password. That got it working, but... then I tried to lock in the IP address by switching the RPI IP to STATIC and typing in the IP address Google Home had assigned to the RPi. But that did not work. I had to make a second trip back to the friend's place to set the RPi back to DHCP. Then Google Home worked with the RPi again. So Google Home requires use of DHCP? It was all very weird. That experience left me thinking it's just as easy to leave things at the default DHCP and let it do what it wants.
I use a static IP address for my living room setup, which connects to the network through Ethernet. But my bedroom RPi connects through WiFi and I find it connects more reliably if I leave it up to DHCP to assign an IP address.
is the OP @davym still here?
EDIT TO ADD:
I think you can do that with Moode Audio too.
- Connect a keyboard and/or mouse to the RPi's USB port(s).
- Connect a monitor to the RPi's HDMI port.
- Power up the RPi and you should be able to get into Moode's Config menu to adjust WiFi settings.
--
Last edited:
Yes, headless is the only way to go when you set up your RPi to do remote controlling stuff.
I do have one right under my monitor via a KVM. That's my "development" machine. I can use the built in tools to write code.
gcc
vi
grep
find
Awesome little machine
But normally I access it via the network. I only use the console when something really went wrong and I got to fix the network or the kernel.
I do have one right under my monitor via a KVM. That's my "development" machine. I can use the built in tools to write code.
gcc
vi
grep
find
Awesome little machine
But normally I access it via the network. I only use the console when something really went wrong and I got to fix the network or the kernel.
Last edited:
I'm dumb so cant find out the logic in this setting pane when reading help text..
Do I make the choice On to have wifi off... or?
It would be clear if the help text read: 'State of built in wifi.' (i.e. either On or Off as per radio button)
//
- Set wifi configuration: neautral
- wifi: on / off - OK... so far...
- RPi built in Wifi: On / off : OK but then things get problematic.. guide text: Turn off Pi built in wifi... off? help text 2: This will load... don't help..
Do I make the choice On to have wifi off... or?
It would be clear if the help text read: 'State of built in wifi.' (i.e. either On or Off as per radio button)
//
Seems like the user interface was outsourced.
If you want to use the internal modem, then enable the built-in WiFi. Enable both. ON-ON
If you want to use an external modem, say like something that plugs into an USB, then just enable WiFi. ON-OFF
Heck.... you think you're having issues... my personal computer won't boot this morning. Thank God I got a back up so at least I got my email working and I haven't lost any data ( OK, my Chrome configuration is a bit old... ).
Advice... use a wired connection if you can help it.
If you want to use the internal modem, then enable the built-in WiFi. Enable both. ON-ON
If you want to use an external modem, say like something that plugs into an USB, then just enable WiFi. ON-OFF
Heck.... you think you're having issues... my personal computer won't boot this morning. Thank God I got a back up so at least I got my email working and I haven't lost any data ( OK, my Chrome configuration is a bit old... ).
Advice... use a wired connection if you can help it.
If you ever change anything about your network you then have to go around reprogramming all your devices. With DHCP they’ll all update eventually when the lease expires. If you assigned fixed IP based on MAC address it’s the best of both worlds. I just changed my gateway ip the other day and because everything used DHCP it all magically worked out without having to reconfigure everything had I done static IPs.
Yes, I could, used to, assign IPADDRs based on the MAC ADDR. I found it easier to publish an etc/hosts file in the network server. Those are the machines that I can remote access into, or that export file systems, so I prefer to use a mnemonic name to connect to them.
For the machines that are strictly agents, not servers, I let them use DHCP, and I have another server for that. This includes the phones, tablets, chromebooks, smart TVs.
For my own personal machine, PCs, I run them wired and with a static IP address.
My work PC uses DHCP.
So, for DHCP I set up 100 address with a time to live of 24 hours. It works great, except my brother in law... he had ( have still? ) a machine that was misconfigured. It would get into DHCP and ask for a new address like every minute. So, it would exhaust the number of available addresses and then he'd blame me that our network was not working. He used to drive me nuts. Until my daughter and I figured out the issue... then, of course, we couldn't change his set up because "it works in my house"... so, I had to map his MAC ADDR to an IPADDR...
Users...
For the machines that are strictly agents, not servers, I let them use DHCP, and I have another server for that. This includes the phones, tablets, chromebooks, smart TVs.
For my own personal machine, PCs, I run them wired and with a static IP address.
My work PC uses DHCP.
So, for DHCP I set up 100 address with a time to live of 24 hours. It works great, except my brother in law... he had ( have still? ) a machine that was misconfigured. It would get into DHCP and ask for a new address like every minute. So, it would exhaust the number of available addresses and then he'd blame me that our network was not working. He used to drive me nuts. Until my daughter and I figured out the issue... then, of course, we couldn't change his set up because "it works in my house"... so, I had to map his MAC ADDR to an IPADDR...
Users...
I don't know about Moode, but accessing Volumio can be a bit tricky on DHCP. I found that I got really fed up with having to run an IP sniffer on my network regularly to find out what IP address Volumio was now using, so I set it to a fixed IP address. Yes, I know that Volumio SAYS the streamer can be accessed by typing the IP address 127.0.0.1 into your browser, but I found that to be a hit-and-miss situation, with the misses outranking the hits.
The simplest way of keeping the DHCP server from interfering with static IP addresses is to set a scope on the DHCP server, something I always do. As home networks, and even small business networks, don't use that much IP addresses, I routinely set the scope to start at 100. So on a router or other DHCP server that uses 192.168.1.1 as its gateway address, I will set the DHCP scope from 192.168.1.100 to 192.168.250. That gives me plenty of addresses for DHCP and plenty static addresses for servers, printers, streamers etc. Make a list of the few machines that use a static IP address or put a label on each one of them with the static address and you can easily re-configure your network when something changes.
Yep.... pretty close. I set up 192.168.x.x as my LAN. 1-99 are for the static addresses, 100-199 are for DHCP. Anything about that is for the switches, router, cable modem (it has an IP address...) and NAS. My router ( AKA gateway ) is 240. I have a backup at 239.
Yes, reconfiguring the static IP address machines takes more work. The DHCP machines are easy.
If you hook up the RPI to the network with a cable, then it's wifi: off.
The RPI built in Wifi is only used when you DON'T have a DHCP server or a wired network and it puts the RPI into a quasi DHCP server mode, so the wireless of your computer or tablet can connect to it. Some HP printers also have this option and it plays havoc with the internet connection of your PC or tablet, as WiFi can only connect to ONE server at the time.
Peer to Peer WiFi.
You can have two (or more) DHCP servers in a network... just so long as the served IP addresses don't overlap. I guess it becomes a race condition to see which server replies first.
How do I know?
Sometimes I'm in a hurry when I open the box and plug the things in. Just like my first power supply didn't need a switch, Tony don't need to read the stinkin' manual... go configure the IP addresses and be done...
Trust me... not necessarily a good idea... but, it will actually work. Actually, in some ways it makes sense, it makes the network more robust.