In infrastructure mode (aka AP mode) ethernet bridging isn’t possible on the client side. That question is quite settled.
Powerline adapters or proprietary wireless hardware/protocol might be able to provide bridging on the client side if required.
Bridging on the AP side is perfectly possible. In your setup that would entail creating a wireless AP on the Pi. Wireless clients connecting to the AP on Pi could reach the PLC.
However in this case the Pi loses its connection to the main LAN and the internet.
Adding an USB wireless adapter is an option to remedy that problem.
In the Pi, the built in wireless interface has a dual mode by which it works as client and as a minimalistic AP at the same time. Avoids adding an USB adapter but reliability/performance are not the best.
If the Pi is simply to act as router, forwarding ports is the general idea. However I haven’t used RaspiOS in a good while and I’m not sure of the right way of implementing that.
Powerline adapters or proprietary wireless hardware/protocol might be able to provide bridging on the client side if required.
Bridging on the AP side is perfectly possible. In your setup that would entail creating a wireless AP on the Pi. Wireless clients connecting to the AP on Pi could reach the PLC.
However in this case the Pi loses its connection to the main LAN and the internet.
Adding an USB wireless adapter is an option to remedy that problem.
In the Pi, the built in wireless interface has a dual mode by which it works as client and as a minimalistic AP at the same time. Avoids adding an USB adapter but reliability/performance are not the best.
If the Pi is simply to act as router, forwarding ports is the general idea. However I haven’t used RaspiOS in a good while and I’m not sure of the right way of implementing that.
Statistics: Posted by epoch1970 — Wed Mar 27, 2024 8:25 pm