On 11/01/2026 14:40, David Higton wrote:
I installed OpenWRT on an RPi4 a few weeks ago,I dont want to go that far and replace existing DHCP allocation etc.
and it was very successful as an AP, although the need for it didn't last
long (my son installed a new mesh network, which gave whole house
coverage). Note that the RPi4 only does one wifi band; I don't know the
RPi5.
In message <10k0tjd$4hee$[email protected]>
The Natural Philosopher <[email protected]d> wrote:
On 11/01/2026 14:40, David Higton wrote:
I installed OpenWRT on an RPi4 a few weeks ago,I dont want to go that far and replace existing DHCP allocation etc.
and it was very successful as an AP, although the need for it didn't last >>> long (my son installed a new mesh network, which gave whole house
coverage). Note that the RPi4 only does one wifi band; I don't know the >>> RPi5.
You would set it up as an access point, not as a router. It would not
need to have DHCP running. DCHP traffic would go to and from your
existing router; the RasPi AP would just pass it through in both
directions.
David
On 11/01/2026 14:40, David Higton wrote:
Note that the RPi4 only does one wifi band; I don't know the RPi5.
The Raspberry Pi 3B+, 4 and 5 have both 2.4GHz and 5GHz Wifi bands, the
Zero W, Zero 2W and older Pi's only have 2.4GHz
In message <10k2bri$272ps$[email protected]>
druck <[email protected]> wrote:
On 11/01/2026 14:40, David Higton wrote:
Note that the RPi4 only does one wifi band; I don't know the RPi5.
The Raspberry Pi 3B+, 4 and 5 have both 2.4GHz and 5GHz Wifi bands, the
Zero W, Zero 2W and older Pi's only have 2.4GHz
Sorry, I should have been clearer. It only does one band at once.
There is only one radio.
David
On 11/01/2026 12:58, The Natural Philosopher wrote:
But I have never seen it configured as a *bridge* to the network and
DHCP server via the Ethernet.
I may be wrong and sometimes am but I thought all you needed to add was
edit /etc/sysctl.conf and ensure it contains "net.ipv4.ip_forward = 1",
save and reboot. Mine came with the line in there but commented out.
You need to allocate IP for ethernet and the TV manually and maybe play
with routing.
I have it running on a PI somewhere, I'll dig it out.
But I have never seen it configured as a *bridge* to the network and
DHCP server via the Ethernet.
On 12/01/2026 20:16, David Higton wrote:
In message <10k2bri$272ps$[email protected]>
���������� druck <[email protected]> wrote:
On 11/01/2026 14:40, David Higton wrote:
Note that the RPi4 only does one wifi band; I don't know the RPi5.
The Raspberry Pi 3B+, 4 and 5 have both 2.4GHz and 5GHz Wifi bands, the
Zero W, Zero 2W and older Pi's only have 2.4GHz
Sorry, I should have been clearer.� It only does one band at once.
There is only one radio.
You can always add another USB WiFi dongle if you want to act as an
access point on both bands simultaneously.
---druck
I may be wrong and sometimes am but I thought all you needed to add
was edit /etc/sysctl.conf and ensure it contains
"net.ipv4.ip_forward = 1", save and reboot.
4: nm-bridge: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9000 qdisc noqueue
state UP mode DEFAULT group default qlen 1000
link/ether d8:3a:dd:85:22:b1 brd ff:ff:ff:ff:ff:ff
The Natural Philosopher <[email protected]d> writes:
4: nm-bridge: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9000 qdisc noqueue
state UP mode DEFAULT group default qlen 1000
link/ether d8:3a:dd:85:22:b1 brd ff:ff:ff:ff:ff:ff
Hmm, mtu 9000 on the bridge? That means jumbo frames and your
performance issue might be because something chokes on them. Your router
or whatever is in the other end. So try setting it to 1500 in your
chosen config tool.
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 715 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 15:30:23 |
| Calls: | 12,102 |
| Calls today: | 2 |
| Files: | 15,004 |
| Messages: | 6,518,049 |