Ok, I've looked up loads of stuff on the interwebbery, and all the
solutions to make a pi into a wifi *bridge* are actually making it into
a router, with its own DHCP etc
Not the same as the average wifi access works in a WAP at all.
Can this actually be done at all?
I basically want a pi on the network to be connected to by wifi clients,
and forward the packets over its ethernet to the main LAN. And let the
main DHCP server do the business.
On 01/02/2024 18:55, The Natural Philosopher wrote:
You set it up as an AP and enable ip4 forwarding so so stuff received on
Ok, I've looked up loads of stuff on the interwebbery, and all the
solutions to make a pi into a wifi *bridge* are actually making it
into a router, with its own DHCP etc
Not the same as the average wifi access works in a WAP at all.
Can this actually be done at all?
I basically want a pi on the network to be connected to by wifi
clients, and forward the packets over its ethernet to the main LAN.
And let the main DHCP server do the business.
the wifi goes to the ethernet and back. I've got this on an old Pi but
it's not handy or I'd look at the config.
Ok, I've looked up loads of stuff on the interwebbery, and all the
solutions to make a pi into a wifi *bridge* are actually making it into
a router, with its own DHCP etc
Not the same as the average wifi access works in a WAP at all.
Can this actually be done at all?
I basically want a pi on the network to be connected to by wifi clients,
and forward the packets over its ethernet to the main LAN. And let the
main DHCP server do the business.
On 01/02/2024 18:55, The Natural Philosopher wrote:
Ok, I've looked up loads of stuff on the interwebbery, and all the solutions to make a pi into a wifi *bridge* are actually making it into
a router, with its own DHCP etc
Not the same as the average wifi access works in a WAP at all.
Can this actually be done at all?
I basically want a pi on the network to be connected to by wifi clients, and forward the packets over its ethernet to the main LAN. And let the
main DHCP server do the business.
You set it up as an AP and enable ip4 forwarding so so stuff received on
the wifi goes to the ethernet and back. I've got this on an old Pi but
it's not handy or I'd look at the config.
mm0fmf <none@invalid.com> wrote:
On 01/02/2024 18:55, The Natural Philosopher wrote:
You set it up as an AP and enable ip4 forwarding so so stuff received on
Ok, I've looked up loads of stuff on the interwebbery, and all the
solutions to make a pi into a wifi *bridge* are actually making it into
a router, with its own DHCP etc
Not the same as the average wifi access works in a WAP at all.
Can this actually be done at all?
I basically want a pi on the network to be connected to by wifi clients, >>> and forward the packets over its ethernet to the main LAN. And let the
main DHCP server do the business.
the wifi goes to the ethernet and back. I've got this on an old Pi but
it's not handy or I'd look at the config.
That's routing not bridging. With bridging you create a bridge device and attach two network devices to it - packets received on one device are sent
to another. It's as if the wifi and LAN are one network. Most consumer routers bridge their wifi and LAN ports.
If you want to go ethernet->wifi->ethernet there are some issues with the Pi 0W/3 hardware not having the right features in the wifi chip: https://raspberrypi.stackexchange.com/questions/51057/raspberry-pi-3-model-b-wireless-bridge-to-ethernet
Not sure if the same applies to the 4 and 5 or if they fixed it in the hardware.
(I previously had a better source than that, which I can't find now)
If bridging doesn't work then you can still route, ie put wifi and LAN on different subnets and have forwarding rules to pass packets between. Which is probably why most of the guides out there are discussing that not bridging.
You can also use proxy ARP to make IPv4 routing look like bridging: https://raspberrypi.stackexchange.com/questions/88954/workaround-for-a-wifi-bridge-on-a-raspberry-pi-with-proxy-arp
and for IPv6 there's Proxy NDP.
I've done Proxy ARP on other machines long ago but not a Pi.
Theo
Ok, I've looked up loads of stuff on the interwebbery, and all the
solutions to make a pi into a wifi *bridge* are actually making it into
a router, with its own DHCP etc
| Sysop: | Xerxes |
|---|---|
| Location: | Azle, Texas |
| Users: | 119 |
| Nodes: | 10 (0 / 10) |
| Uptime: | 162:12:59 |
| Calls: | 3,036 |
| Calls today: | 4 |
| Files: | 156 |
| U/L today: |
0 files (0K bytes) |
| D/L today: |
0 files (0K bytes) |
| Messages: | 294,120 |
| Posted today: | 0 |