Are you sure that the line
is correct, my /etc/dhcpcd.conf has the equivalent of
note the plurality of routers, it never seems to fail, the man page has the plural version too
can anyone suggest the best way for me to proceed?
First thing to check is your syntax. I don't recall there being any white space in the configuration statements.
Next, know that dhcpcd works well. The people who have issues seem always to have the same problem as you: they read and follow various blogs on the Internet which are incompetent, ...
Virtually all modern torrent clients use some sort of internal caching to improve performance. If the cache is large, there will be a noticeable slowdown when it expires or is flushed.
Try running your torrent client with nice and try setting a smaller cache size with a shorter expiry time. If you primarily use the Pi for downloads, long expiry time is ...
At some point I switched the ethernet cable while troubleshooting static IP problems and did not switch which ethernet connection was being shared. Thus the RPI was sharing its network to the PC and the router was doing the same, instead of the RPI receiving a shared network from the PC.
On Raspberry Pi Zero and Zero W, the default /etc/network/interfaces contains a bunch of comments followed by a single line. First, make sure that's there.
I remedied /etc/network/interfaces.d/00-interfaces (the only file in there)
using inet dhcp, as suggested in https://wiki.debian.org/NetworkConfiguration
A Raspberry PI network configuration guide is here
Double-check that the file was written in plaintext, with no special characters.
Double-check that the file has disappeared from your boot
Connect the Pi to a TV or monitor via ...
"but no firm response on how to do this" because you haven't actually said what "this" is. I presume by "MAC" you mean an Apple Mac.
The Pi (or indeed ANY computer) can independently configure network interfaces. See How to set up networking/WiFi for details using the default dhcpcd.
I would't use a switch to connect a Mac to a ...
Okay, after some days of struggle and figuring this stuff out, I've finally made it happen. What I did was:
wrote a bash script that sends a magic packet with the mac address of the target pc to the local IP-address with a port of that pc.
sudo wakeonlan -i 188.8.131.52 -p 99 1a:2b:3c:4d:5e:6f
figured out the command which I ...
I manipulated the wpa_supplicant.conf file in the /etc/wpa_supplicant folder:
Copy the contents of the file to a temporary file. Use some basic string manipulations to extract only the top 3 header lines.
Overwrite the original wpa_supplicant.conf file with just the headers
Execute wpa_cli -i wlan0 reconfigure
This makes the Pi temporarily forget all ...
You should note that your SD card has two partitions: / (root), and /boot.
/ uses the ext4 filesystem & contains /etc
/boot uses fat32 - it's where you create /boot/ssh, and wpa_supplicant
Easiest thing to try 1st is mount /boot & create a new wpa_supplicant. But I doubt this will cure your problem. :(
The next option is to mount / & repair the ...
This guide describes one approach that saved me from having to reformat my RaspberryPi and got me back:
• internet connection
• functional OpenMediaVault
The following instructions are
• assuming your network is based on the eth0
• assuming that your WiFi/Router is on 192.168.3.1
• assuming that your static IP address is 192.168.3.41
• assuming you are ...
You could use tcpdump or wireshark to monitor the network interface on the Pi and set up a filter for the magic packet of your choice. For example, for a ping packet that could be:
tcpdump -i eth0 icmp and icmp[icmptype]=icmp-echo
Pipe the output of tcpdump to a script which wakes up the target computer on any new input:
while read line; do wakeonlan <...
This "answer" is in two parts. The first part is my assessment of your question, the second part is a suggestion intended to help you move toward a clearer understanding of your network management toolset, which will hopefully allow you to formulate a clearer question.
N.B. Networking questions can be difficult questions to ...
If there's no other network interfaces active, just stop dhcpcd:
sudo systemctl stop dhcpcd
This may leave the interface in a DOWN state but you can put it up again:
sudo ip l set wlan0 up
Whether or not that allows for your "certain other activities" I can't say since I don't know what they are.
Looks like I figured out something to make my Raspberry Pi 3B Router give me a somewhat private second network.
Created a file at /etc/network/interfaces containing:
iface br0 inet manual
bridge_ports eth1 br0
The ‘auto br0’ starts the bridge at boot.
The iface parts:
‘manual’ ==> bridge not meant to have an IP address