Timeline for How do I set up networking/WiFi/static IP address on Raspbian/Raspberry Pi OS?
Current License: CC BY-SA 4.0
40 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Oct 15, 2023 at 6:43 | history | edited | Milliways | CC BY-SA 4.0 |
added 189 characters in body
|
Nov 5, 2022 at 7:51 | history | edited | Milliways | CC BY-SA 4.0 |
deleted 5 characters in body
|
Apr 17, 2022 at 0:12 | history | edited | Milliways | CC BY-SA 4.0 |
inform
|
Apr 17, 2022 at 0:03 | comment | added | Seamus |
As I read some of the comments here, it seems clear that a surprising number of the readership here is pathetically misinformed. The author and I disagree on many things, but he is correct here. I may take exception with a couple of points, but they are minor - mostly having to do with the use of request instead of inform . But we agree on this: Using the static option is brain-dead, and an invitation for trouble in the vast majority of cases. Strangely however, it is the "option of choice" for those who imagine they know what they are doing.
|
|
Mar 26, 2022 at 4:25 | history | edited | Milliways | CC BY-SA 4.0 |
added 24 characters in body
|
Jan 18, 2022 at 16:02 | comment | added | NiKiZe |
Who come up with the idea of setting static ip in /etc/dhcpcd.conf ? This makes no sense, and is just purely unacceptable at so many levels. This post is also wrong about "Telecommunications Engineers do not do this" They do it all the time, especially if there is no DHCP server, or static machines that are intended to be outside the range etc.
|
|
Nov 23, 2021 at 23:26 | history | edited | Milliways | CC BY-SA 4.0 |
Bullseye update
|
Aug 21, 2021 at 6:04 | history | edited | Milliways | CC BY-SA 4.0 |
Fix Documentation links
|
Aug 10, 2021 at 0:07 | history | edited | Milliways | CC BY-SA 4.0 |
Apology
|
Oct 17, 2020 at 1:29 | history | edited | Milliways | CC BY-SA 4.0 |
formatting
|
Sep 4, 2020 at 1:53 | history | edited | Milliways | CC BY-SA 4.0 |
request [address]
|
Jul 25, 2020 at 3:25 | history | edited | Milliways | CC BY-SA 4.0 |
request [address]
|
Jul 4, 2020 at 0:43 | history | edited | Milliways | CC BY-SA 4.0 |
Note - Address Reservation
|
Jul 4, 2020 at 0:36 | history | edited | Milliways | CC BY-SA 4.0 |
Note - Address Reservation
|
Apr 3, 2020 at 10:18 | history | edited | Milliways | CC BY-SA 4.0 |
IPV6 settings
|
Mar 3, 2020 at 8:17 | comment | added | TheArchitecta | "Finally note down the address of your DNS server, which is often the same as your gateway." I believe this is poor advice, because the DNS should not be your router, DNS should only be in your network if you have a dedicated DNS device. Routers generally stop working due to being used as a DNS. especially the routers provided by ISPs. Instead get your dns from your ISP, Google, Cloudfalre, Opendns | |
Nov 13, 2019 at 21:29 | comment | added | Albert van der Horst | network administrators do not like this. That is not a reason to have dhcp addresses on rapsberry pi's and orange pi's and local printers. Almost everybody who reads this is is a home user, and is not served by smug comments about what "professionals" do. Albert | |
Oct 28, 2019 at 17:22 | comment | added | Stefan Profanter | Performance is better disabling dhcpd I just tested the second non recommended approach, and it speeds up the boottime by 7 seconds on my RasPI Zero W. | |
Aug 6, 2019 at 5:48 | comment | added | Milliways | @seadoggie01 static IP addresses are a Pi disease - Windows & macOS users seem to get by without. If you are connected to a network with a DHCP server don't use a static IP address - let the server assign one. | |
Aug 6, 2019 at 3:42 | comment | added | seadoggie01 | Is using a static IP to setup a personal SFTP server an exception to the 'not recommended' warning? Everything I've found suggests static IPs | |
Apr 20, 2019 at 22:51 | history | edited | Milliways | CC BY-SA 4.0 |
clarify Network Interfaces method
|
Mar 23, 2019 at 7:04 | comment | added | Talal |
You can also use wpa-ssid and wpa-psk instead of the wpa-conf
|
|
Feb 5, 2019 at 1:58 | history | edited | Milliways | CC BY-SA 4.0 |
Network Interfaces method not recommended
|
Jan 25, 2019 at 23:14 | comment | added | Milliways | @T3db0t The post starts by advising people not to do it; /etc/network/interfaces contains a warning to use dhcpcd. People continue to ignore these - adding another would be futile. This post is only there because those who ignore the warnings get it wrong. | |
Jan 25, 2019 at 18:33 | comment | added | T3db0t | @Milliways I take it you mean via /etc/network/interfaces. Does this post say anywhere that it's obsolete? | |
Jan 23, 2019 at 22:40 | comment | added | Milliways | @T3db0t You should ask your own question, but if you use the obsolete method you have to accept its limitations. | |
Jan 23, 2019 at 17:30 | comment | added | T3db0t |
I'm connecting my Pi to a proprietary device via eth0 , but also want to use wlan0 as normal for an internet connection. Using the /etc/network/interfaces method, I tried adding ONLY the eth0 section but it seems to kill my (previously working) Wifi connection. If I need to provide a wlan0 section, how do I set it up to use dhcp as normal?
|
|
Jan 7, 2019 at 4:22 | comment | added | Milliways |
@CrouZ I have seen a few references to domain_search=.local but 1) it is not mentioned in the dhcpcd documentation, and 2) Should not be needed on a network which supports standard Zero-conf. I have had many comments that this answer is already too complex. You might like to add your own answer explaining the option and the environment in which it is needed.
|
|
Jan 6, 2019 at 22:09 | comment | added | CrouZ |
I also had to add static domain_search=.local to be able access the Pi from the LAN using its hostname.
|
|
Nov 13, 2018 at 0:24 | history | edited | Milliways | CC BY-SA 4.0 |
added 14 characters in body
|
Nov 6, 2018 at 23:38 | history | edited | Milliways | CC BY-SA 4.0 |
add note
|
Sep 11, 2018 at 9:57 | comment | added | MadMike |
I've added static domain_search=example.local to the dhcpcd.conf method. Feel free to revert/edit/contact me.
|
|
Sep 11, 2018 at 9:55 | review | Suggested edits | |||
Sep 11, 2018 at 12:38 | |||||
Jun 25, 2018 at 5:11 | comment | added | Milliways | I don't use either - this is only there because so many people try (for whatever reason - which eludes me) BUT get it wrong, because they don't understand networking. There is no simple answer because it depends on what else you are doing. NOTE setting a static IP is unlikely to have ANY impact on boot time, unless you have a very slow DHCP server. If you have questions you should ask a Question - this is not a discussion forum. | |
Jun 25, 2018 at 4:42 | comment | added | Elliott B |
I did read that, I'm just wondering about the two methods dhcpcd vs networking. I want to see if a static IP lets it boot faster, because I see a 15s delay for dhcpcd in systemd-analyze .
|
|
Jun 25, 2018 at 4:39 | comment | added | Milliways | @ElliottB read the Disclaimer above. | |
Jun 24, 2018 at 23:51 | comment | added | Elliott B | What are the pros and cons of these two methods you mention? | |
Nov 5, 2017 at 5:27 | history | edited | Milliways | CC BY-SA 3.0 |
ls /sys/class/net/
|
Oct 28, 2017 at 23:42 | history | edited | Milliways | CC BY-SA 3.0 |
added 107 characters in body
|
Oct 28, 2017 at 23:34 | history | answered | Milliways | CC BY-SA 3.0 |