assuming eth0 is the name of your network interface and 192.168.0.1 is the ip of your gateway,
if you want your pi on dhcp, try this config:
addresses: [188.8.131.52, 184.108.40.206]
if you want a static ip: (lets say 192.168.0.15)
I was having some weird behavior on raspberry pi when I had the WiFi connected to my home network and the ethernet cable was plugged directly into my computer.
WiFi would only work after I unplugged the ethernet cable, verified this with a continous ping to google before and after remove the cable and vice versa.
Setting the metric in dhcpcd.conf worked ...
To elaborate the answer from @Ingo: please consider using the link
ln -s /run/systemd/resolve/stub-resolv.conf resolv.conf
instead of the link to /run/systemd/resolve/resolv.conf. This enable the "integrated" DNS stub and enables things like per-interface DNS server which could be important if you use VPNs that provide their own DNS server with non-public ...
After some years there have been found a solution to this specific problem with Raspberry Pi. You very clearly described that you want to have a bridge on the RasPi but this cannot be done with a WiFi client connection to the router. For this it must supported by the WiFi chip but it doesn't. For further information about this look at Raspberry Pi WiFi to ...
This solved my problems or is this just my setup?
With a prebuilt custom version of Raspbian Buster on Pi 3 the dhclient was a problem interfering with dhcpcd so first had to remove the isc-dhcp-common and isc-dhcp-client packages.
Then /etc/network/interfaces with the wpa-conf for /etc/wpa_supplicant/wpa_supplicant.conf and desired /etc/dhcpcd.conf ...
In your netplan folder try deleting or commenting in your .yaml file the lines related to the MAC info:
match: #Comment or delete
macaddress: yourMacAddress #Comment or delete
There are some things mixed up. I assume you are using Raspbian. Please don't ignore the note in /etc/network/interfaces:
# Please note that this file is written to be used with dhcpcd
# For static IP, consult /etc/dhcpcd.conf and 'man dhcpcd.conf'
With Raspbian you have three networking systems available out of the box. First you have to decide which ...
You haven't specified concurrent calls and if you are doing transcoding in Asterisk, but the short answer is YES a raspberry Pi 3 can do both if you don't have a lot of transcoding and playing a lot of voice prompts.
Following joan hint I found a possibile solution into making a new .dts (enc28j60-spi1-overlay):
// Overlay for the Microchip ENC28J60 Ethernet Controller - SPI1
// Interrupt pin: 25
compatible = "brcm,bcm2708";
target = <&spi1>;
/* needed to avoid dtc warning ...
As far as I can tell from /boot/overlays/README you need to add the following entry in /boot/config.txt (and remove or comment out any existing enc28j60 entry).
From your forum link that should use chip enable 0.
The relevant part of the README is:
Info: Overlay for the Microchip ENC28J60 Ethernet ...