Timeline for How do I set up networking/WiFi/static IP address on Raspbian/Raspberry Pi OS?
Current License: CC BY-SA 3.0
19 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 3, 2022 at 14:44 | comment | added | Seamus |
Readers should do their homework before adopting the static ip configuration advocated by this answer. For example, the author of dhcpcd discourages use of static ip!! In man dhcpcd.conf he states, For IPv4, you should use the inform ipaddress option instead of setting a static address. Ask yourself why you should follow the recommendation in this answer when the author of dhcpcd says otherwise?
|
|
| Apr 13, 2020 at 20:37 | comment | added | Roland |
This answer is more to the point than the other longer answers. In my case, only the line static ip_address= was relevant, because the dhcp over wifi does the rest. Only the IP address needed to be static. Key was that the config file as mentioned here. +1
|
|
| Mar 7, 2018 at 17:23 | comment | added | Adam | What if the router is me? I mean I create a subnet. | |
| Oct 26, 2017 at 22:08 | comment | added | Bruno Bronosky | I created a script to generate that conf based on your current network connection. gist.github.com/RichardBronosky/… | |
| May 31, 2017 at 3:57 | comment | added | Pedro Lobito | This can be a copied answer but has everything you need to setup a static ip on raspberry, the accepted answer is unnecessarily long. | |
| S Dec 27, 2016 at 13:10 | history | suggested | Peter Mortensen | CC BY-SA 3.0 |
Copy edited (e.g. ref. <http://en.wikipedia.org/wiki/Ethernet>). IP is a protocol; it is IP addresses that are static, filtered, whitelisted, have different representations, that devices have, etc., not the protocol itself.
|
| Dec 27, 2016 at 12:30 | review | Suggested edits | |||
| S Dec 27, 2016 at 13:10 | |||||
| Nov 4, 2016 at 22:52 | comment | added | Barmaley |
And if sudo service networking restart does not work, you can try sudo ip link set eth0 down && sudo ip link set eth0 up
|
|
| Nov 2, 2016 at 4:21 | comment | added | Barmaley |
If you want to restart networking services without reboot, make sure you have auto eth0 above iface eth0 inet manual line in your /etc/network/interface file. Restart network via sudo service networking restart command
|
|
| May 12, 2016 at 23:10 | comment | added | JayEye | You assert that /etc/network/interfaces should be left alone, but you do not say why. In fact, quite the opposite is true. See my answer below. | |
| S Jan 16, 2016 at 14:48 | history | suggested | Alastair McCormack | CC BY-SA 3.0 |
Removed code quotes and indented config lines to show without breaks. Added highlights to reach change quota
|
| Jan 16, 2016 at 14:11 | review | Suggested edits | |||
| S Jan 16, 2016 at 14:48 | |||||
| Dec 17, 2015 at 0:58 | comment | added | Milliways |
It probably did work in your case, but not in general because dhcpcd inferred the netmask, which it cannot for other address ranges. Read the man pages.
|
|
| Dec 17, 2015 at 0:48 | comment | added | Danica Panica | What did I get wrong? Was it the /24 after the IP address? Why do you need that? Things seem to be working fine without it. | |
| Dec 15, 2015 at 23:37 | comment | added | Milliways | If you are going to copy parts of the answer at least you should get it right. | |
| Dec 15, 2015 at 23:37 | history | edited | Milliways | CC BY-SA 3.0 |
error in static ip_address
|
| Dec 11, 2015 at 13:56 | history | edited | Ghanima♦ | CC BY-SA 3.0 |
formatting
|
| Dec 11, 2015 at 13:55 | review | Late answers | |||
| Dec 11, 2015 at 19:54 | |||||
| Dec 11, 2015 at 13:38 | history | answered | Danica Panica | CC BY-SA 3.0 |