On 11/01/2026 14:40, David Higton wrote:

In message <10k06pm$3qvn9$25@dont-email.me>
The Natural Philosopher <tnp@invalid.invalid> wrote:

Situation: I have one ethernet port in a room near the TV and would like
to make the smart TV not a TV so to speak, and instead drive it from a Pi >> 5 as a HDMI screen and use the Pi for any or all smart capabilities.

But I also need wifi access to the network in that room as well, and the
pi 5 comes with wifi,

But I have never seen it configured as a *bridge* to the network and DHCP >> server via the Ethernet.

Does anyone have a link to a magic spell book for this configuration?

If I've understood correctly, turning the RPi into an access point would
do half of what you want.

Yes., it would.

I installed OpenWRT on an RPi4 a few weeks ago,
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.

I dont want to go that far and replace existing DHCP allocation etc.

I'm not an expert on OpenWRT, so you'll need to web search for information.

As for the other half of what you want, there might be enough processing power left over. You haven't given us any detail of what you want to do
in that regard.

That is why I don't want to start with opemwrt. Its too intrusive.

David

--
?Politics is the art of looking for trouble, finding it everywhere,
diagnosing it incorrectly and applying the wrong remedies.?
? Groucho Marx


--- PyGate Linux v1.5.2
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)

In message <10k06pm$3qvn9$25@dont-email.me>
The Natural Philosopher <tnp@invalid.invalid> wrote:

Situation: I have one ethernet port in a room near the TV and would like
to make the smart TV not a TV so to speak, and instead drive it from a Pi
5 as a HDMI screen and use the Pi for any or all smart capabilities.

But I also need wifi access to the network in that room as well, and the
pi 5 comes with wifi,

But I have never seen it configured as a *bridge* to the network and DHCP server via the Ethernet.

Does anyone have a link to a magic spell book for this configuration?

If I've understood correctly, turning the RPi into an access point would
do half of what you want. I installed OpenWRT on an RPi4 a few weeks ago,
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.

I'm not an expert on OpenWRT, so you'll need to web search for information.

As for the other half of what you want, there might be enough processing
power left over. You haven't given us any detail of what you want to do
in that regard.

David

--- PyGate Linux v1.5.2
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)

On Sun, 11 Jan 2026 12:58:30 +0000, The Natural Philosopher <tnp@invalid.invalid> wrote:

Situation: I have one ethernet port in a room near the TV and would like
to make the smart TV not a TV so to speak, and instead drive it from a
Pi 5 as a HDMI screen and use the Pi for any or all smart capabilities.

But I also need wifi access to the network in that room as well, and the
pi 5 comes with wifi,

But I have never seen it configured as a *bridge* to the network and
DHCP server via the Ethernet.

Does anyone have a link to a magic spell book for this configuration?

TIA TNP

How about one of these?

<https://insberr.github.io/pi-internet-bridge/>

<https://pimylifeup.com/raspberry-pi-wifi-bridge/> - may be back-arse-
wards but may still work

<https://www.willhaley.com/blog/raspberry-pi-wifi-ethernet-bridge/>

No I've not actually tried them, I've been fitting ZigBee without 'smart-
life' /tuya cloud & bulbs that won't pair.

Have fun

Avpx
--
[...] she [Esk] was already learning that if you ignore the rules people
will, half the time, quietly rewrite them so they don't apply to you.
(Equal Rites)
Sun 11821 Sep 13:55:01 GMT 1993
13:55:01 up 30 days, 22:33, 1 user, load average: 0.98, 0.48, 0.41

--- PyGate Linux v1.5.2
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)

In message <10k06pm$3qvn9$25@dont-email.me>, The Natural Philosopher <tnp@invalid.invalid> writes

Situation: I have one ethernet port in a room near the TV and would
like to make the smart TV not a TV so to speak, and instead drive it
from a Pi 5 as a HDMI screen and use the Pi for any or all smart >capabilities.

But I also need wifi access to the network in that room as well, and
the pi 5 comes with wifi,

But I have never seen it configured as a *bridge* to the network and
DHCP server via the Ethernet.

Does anyone have a link to a magic spell book for this configuration?

Not a direct answer to your question, but ...

I started looking at doing something similar to this a couple of years
ago (using the Pi as a WiFi access point in a location beyond the range
of my router's WiFi). I didn't complete the task for various reasons,
but one thing that was clear, was that if I were to do it again, I would
do the initial configuration of the Pi locally (keyboard etc. plugged
in) rather than across the network (ssh session) as at each step of the
way, it seemed that the Pi was inaccessible for something like 20-30
minutes whilst it sorted out what to do with each configuration change
(of which there were several needed).

Good Luck

Adrian
--
To Reply :
replace "bulleid" with "adrian" - all mail to bulleid is rejected
Sorry for the rigmarole, If I want spam, I'll go to the shops
Every time someone says "I don't believe in trolls", another one dies.

--- PyGate Linux v1.5.2
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)

On 11/01/2026 14:33, Adrian Caspersz wrote:

On 11/01/2026 12:58, The Natural Philosopher wrote:

Situation: I have one ethernet port in a room near the TV and would
like to make theÿ smart TV not a TV so to speak, and instead drive it
from a Pi 5 as a HDMI screen and use the Pi for any or all smart
capabilities.

But I also need wifi access to the network in that room as well, and
the pi 5 comes with wifi,

But I have never seen it configured as a *bridge* to the network and
DHCP server via the Ethernet.

Does anyone have a link to a magic spell book for this configuration?

TIA
TNP

Start with a recipe for a wireless access point?

That is all I need. The tv doesnt need to be on the LAN at all post that
and indeed could use the wifi anyway IIRC.

that will have a built-in bridge that the wireless clients will appear
on, DHCP etc, and will connect to the pi's physical NIC

The problem is how that is to be accomplished

Then you'll need to add a virtual NIC to this, for your TV software and connect that also to the bridge, via some local firewall rules.

https://linuxconfig.org/configuring-virtual-network-interfaces-in-linux

That isn't particularly helpful.

I am already where I want to be at that moment. The TV will be taken
off the net anyway.
Or connect via wifi. Or I will add a teensy two port swichth somewhere.

It is the use of teh pi as a bridge that I am after.

Or perhaps switch-like something hanging both the bridge i/o and a
virtual NIC on the original physical NIC, using VLAN IDs to segregate traffic to each?

No need to segregate. Originally I had a wifi equipped router set up as
a bridge but I want to move that functionality to a PI.

(theoretically handwaving here, I've done the above in the OS of a
carboot sale cheepie 50p speedtouch router, not linux)

--
Future generations will wonder in bemused amazement that the early twenty-first century?s developed world went into hysterical panic over a globally average temperature increase of a few tenths of a degree, and,
on the basis of gross exaggerations of highly uncertain computer
projections combined into implausible chains of inference, proceeded to contemplate a rollback of the industrial age.

Richard Lindzen


--- PyGate Linux v1.5.2
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)

On 11/01/2026 19:18, The Natural Philosopher wrote:

On 11/01/2026 14:13, Adrian wrote:

I started looking at doing something similar to this a couple of years
ago (using the Pi as a WiFi access point in a location beyond the
range of my router's WiFi).ÿ I didn't complete the task for various
reasons, but one thing that was clear, was that if I were to do it
again, I would do the initial configuration of the Pi locally
(keyboard etc. plugged in) rather than across the network (ssh
session) as at each step of the way, it seemed that the Pi was
inaccessible for something like 20-30 minutes whilst it sorted out
what to do with each configuration change (of which there were several
needed).

Many thanks for good advice. I have a 4B available to test all this on
with a scream and keybored, and I have been through all this myself with headless servers and IP changes. :-)

Further to this I right clicked on the network icon on my desktop to
select 'edit connections' and got the option to add an interface, and
type 'bridge' was one of the options.

It looks like a Gui interface may allow everything I want.

I think if I add Ethernet and Wlan interfaces to a bridge device I get
most of what I want, but I don't understand which interface gets the one
and only IP address.
Perhaps it doesn't matter...


--
Civilization exists by geological consent, subject to change without notice.
? Will Durant


--- PyGate Linux v1.5.2
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)

Situation: I have one ethernet port in a room near the TV and would like
to make the smart TV not a TV so to speak, and instead drive it from a
Pi 5 as a HDMI screen and use the Pi for any or all smart capabilities.

But I also need wifi access to the network in that room as well, and the
pi 5 comes with wifi,

But I have never seen it configured as a *bridge* to the network and
DHCP server via the Ethernet.

Does anyone have a link to a magic spell book for this configuration?

TIA
TNP

--
"Anyone who believes that the laws of physics are mere social
conventions is invited to try transgressing those conventions from the
windows of my apartment. (I live on the twenty-first floor.) "

Alan Sokal

--- PyGate Linux v1.5.2
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)

On 11/01/2026 12:58, The Natural Philosopher wrote:

Situation: I have one ethernet port in a room near the TV and would like
to make theÿ smart TV not a TV so to speak, and instead drive it from a
Pi 5 as a HDMI screen and use the Pi for any or all smart capabilities.

But I also need wifi access to the network in that room as well, and the
pi 5 comes with wifi,

But I have never seen it configured as a *bridge* to the network and
DHCP server via the Ethernet.

Does anyone have a link to a magic spell book for this configuration?

TIA
TNP

Start with a recipe for a wireless access point?

that will have a built-in bridge that the wireless clients will appear
on, DHCP etc, and will connect to the pi's physical NIC

Then you'll need to add a virtual NIC to this, for your TV software and connect that also to the bridge, via some local firewall rules.

https://linuxconfig.org/configuring-virtual-network-interfaces-in-linux

Or perhaps switch-like something hanging both the bridge i/o and a
virtual NIC on the original physical NIC, using VLAN IDs to segregate
traffic to each?


(theoretically handwaving here, I've done the above in the OS of a
carboot sale cheepie 50p speedtouch router, not linux)

--
Adrian C

--
Adrian C

--- PyGate Linux v1.5.2
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)

On 11/01/2026 14:13, Adrian wrote:

I started looking at doing something similar to this a couple of years
ago (using the Pi as a WiFi access point in a location beyond the range
of my router's WiFi).ÿ I didn't complete the task for various reasons,
but one thing that was clear, was that if I were to do it again, I would
do the initial configuration of the Pi locally (keyboard etc. plugged
in) rather than across the network (ssh session) as at each step of the
way, it seemed that the Pi was inaccessible for something like 20-30
minutes whilst it sorted out what to do with each configuration change
(of which there were several needed).

Many thanks for good advice. I have a 4B available to test all this on
with a scream and keybored, and I have been through all this myself with headless servers and IP changes. :-)

--
Future generations will wonder in bemused amazement that the early twenty-first century?s developed world went into hysterical panic over a globally average temperature increase of a few tenths of a degree, and,
on the basis of gross exaggerations of highly uncertain computer
projections combined into implausible chains of inference, proceeded to contemplate a rollback of the industrial age.

Richard Lindzen


--- PyGate Linux v1.5.2
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)

On 11/01/2026 14:02, The Nomad wrote:

On Sun, 11 Jan 2026 12:58:30 +0000, The Natural Philosopher <tnp@invalid.invalid> wrote:

Situation: I have one ethernet port in a room near the TV and would like
to make the smart TV not a TV so to speak, and instead drive it from a
Pi 5 as a HDMI screen and use the Pi for any or all smart capabilities.

But I also need wifi access to the network in that room as well, and the
pi 5 comes with wifi,

But I have never seen it configured as a *bridge* to the network and
DHCP server via the Ethernet.

Does anyone have a link to a magic spell book for this configuration?

TIA TNP

How about one of these?

<https://insberr.github.io/pi-internet-bridge/>

That one is replacing the DNS server and acting as a router. I jsut want
a bridge.

<https://pimylifeup.com/raspberry-pi-wifi-bridge/> - may be back-arse-
wards but may still work

Ah. That all rings a bell. Adding an interface called 'wifibridge' type 'ethernet' to the wifi interface may just do the trick

<https://www.willhaley.com/blog/raspberry-pi-wifi-ethernet-bridge/>

No I've not actually tried them, I've been fitting ZigBee without 'smart- life' /tuya cloud & bulbs that won't pair.

That doesnt look up to date.

Have fun

Avpx

--
"Anyone who believes that the laws of physics are mere social
conventions is invited to try transgressing those conventions from the
windows of my apartment. (I live on the twenty-first floor.) "

Alan Sokal


--- PyGate Linux v1.5.2
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)

In message <10k0tjd$4hee$5@dont-email.me>
The Natural Philosopher <tnp@invalid.invalid> wrote:

On 11/01/2026 14:40, David Higton wrote:

I installed OpenWRT on an RPi4 a few weeks ago,
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.

I dont want to go that far and replace existing DHCP allocation etc.

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

--- PyGate Linux v1.5.2
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)

On 11/01/2026 22:37, David Higton wrote:

In message <10k0tjd$4hee$5@dont-email.me>
The Natural Philosopher <tnp@invalid.invalid> wrote:

On 11/01/2026 14:40, David Higton wrote:

I installed OpenWRT on an RPi4 a few weeks ago,
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.

I dont want to go that far and replace existing DHCP allocation etc.

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.

Sigh, eggs, grandmother.

That is why one of the solutions posted was rejected. It didnt do that.

David

--
In todays liberal progressive conflict-free education system, everyone
gets full Marx.


--- PyGate Linux v1.5.2
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)

In message <10k2bri$272ps$1@druck.eternal-september.org>
druck <news@druck.org.uk> 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

--- PyGate Linux v1.5.2
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)

On 12/01/2026 20:16, David Higton wrote:

In message <10k2bri$272ps$1@druck.eternal-september.org>
druck <news@druck.org.uk> 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

Does that preclude 2 band operation?

--
"Nature does not give up the winter because people dislike the cold."

? Confucius


--- PyGate Linux v1.5.2
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)

On 13/01/2026 13:27, mm0fmf wrote:

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.

That would be kind





--
?Ideas are inherently conservative. They yield not to the attack of
other ideas but to the massive onslaught of circumstance"

- John K Galbraith



--- PyGate Linux v1.5.2
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)

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.






--- PyGate Linux v1.5.2
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)

On 13/01/2026 14:45, druck wrote:

On 12/01/2026 20:16, David Higton wrote:

In message <10k2bri$272ps$1@druck.eternal-september.org>
ÿÿÿÿÿÿÿÿÿÿ druck <news@druck.org.uk> 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 saw something (hostapd) that implies it can in fact do both...

Well in due course I will find out.

--
?Ideas are inherently conservative. They yield not to the attack of
other ideas but to the massive onslaught of circumstance"

- John K Galbraith



--- PyGate Linux v1.5.2
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)

On Tue, 13 Jan 2026 13:27:40 +0000, mm0fmf wrote:

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.

Set that line in /etc/sysctl.conf, and also do it manually this one
time, just to save a reboot.

--- PyGate Linux v1.5.2
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)

On 2026-01-13, mm0fmf <none@invalid.com> wrote:

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.

That is for IP routing, using seperate IP networks on the ethernet and wifi side. You can do that, but it may make the setup more complicated and cause problems with prototols that rely on broadcast/multicast packets, as these
are not routed. Also, if your WIFI clients require internet access, you need
to setup routes on your internet router so it can forward packages back to
the WIFI gateway. You need to decide if routing or bridging best suits your needs.

"normal" WIFI access points usually operate in bridging mode.



For bridging, you need to set up a bridge device, with both the ethernet and wifi devices slaved to the bridge. In that scenario, the slave devices do
not get IP addresses assigned - the bridge device is the one with the IP address.

Looking at a running example (on custom hardware, not a raspberry),
with a single of the 3 wifi modules active, it looks like this (eth1 is the ethernet interface, phy0-ap0 is wifi):

root@lx6500-dev:~# brctl show
bridge name bridge id STP enabled interfaces
br-lan 7fff.00a057802bee no eth1
phy0-ap0

root@lx6500-dev:~# ip l
4: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master br-lan state UP mode DEFAULT group default qlen 1000
link/ether 00:a0:57:80:2b:ee brd ff:ff:ff:ff:ff:ff
5: br-lan: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000
link/ether 00:a0:57:80:2b:ee brd ff:ff:ff:ff:ff:ff
6: phy0-ap0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue master br-lan state DOWN mode DEFAULT group def0
link/ether 04:f0:21:bf:45:cc brd ff:ff:ff:ff:ff:ff

root@lx6500-dev:~# ip a
4: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master br-lan state UP group default qlen 1000
link/ether 00:a0:57:80:2b:ee brd ff:ff:ff:ff:ff:ff
5: br-lan: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether 00:a0:57:80:2b:ee brd ff:ff:ff:ff:ff:ff
inet 192.168.1.1/24 brd 192.168.1.255 scope global br-lan
valid_lft forever preferred_lft forever
inet6 fe80::2a0:57ff:fe80:2bee/64 scope link proto kernel_ll
valid_lft forever preferred_lft forever
6: phy0-ap0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue master br-lan state DOWN group default qlen 1000
link/ether 04:f0:21:bf:45:cc brd ff:ff:ff:ff:ff:ff

Using that configuration, WIFI clients get addresses from the existing DHCP server on the LAN, and are in the same IP network as the LAN devices.

cu
Michael
--
Some people have no respect of age unless it is bottled.

--- PyGate Linux v1.5.2
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)

On 2026-01-13, The Natural Philosopher <tnp@invalid.invalid> wrote:

Sorry, I should have been clearer. It only does one band at once.
There is only one radio.

David

Does that preclude 2 band operation?

It precludes what vendors call concurrent dual-band operation. You can
operate on both bands, but only one at a time.

For an accesspoint, that basically means single-band, but you get to pick
which band is used.

cu
Michael
--
Some people have no respect of age unless it is bottled.

--- PyGate Linux v1.5.2
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)

On 18/01/2026 10:54, Michael Schwingen wrote:

On 2026-01-13, mm0fmf <none@invalid.com> wrote:

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.

That is for IP routing, using seperate IP networks on the ethernet and wifi side. You can do that, but it may make the setup more complicated and cause problems with prototols that rely on broadcast/multicast packets, as these are not routed. Also, if your WIFI clients require internet access, you need to setup routes on your internet router so it can forward packages back to the WIFI gateway. You need to decide if routing or bridging best suits your needs.

"normal" WIFI access points usually operate in bridging mode.

For bridging, you need to set up a bridge device, with both the ethernet and wifi devices slaved to the bridge. In that scenario, the slave devices do
not get IP addresses assigned - the bridge device is the one with the IP address.

Looking at a running example (on custom hardware, not a raspberry),
with a single of the 3 wifi modules active, it looks like this (eth1 is the ethernet interface, phy0-ap0 is wifi):

root@lx6500-dev:~# brctl show
bridge name bridge id STP enabled interfaces
br-lan 7fff.00a057802bee no eth1
phy0-ap0

root@lx6500-dev:~# ip l
4: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master br-lan state UP mode DEFAULT group default qlen 1000
link/ether 00:a0:57:80:2b:ee brd ff:ff:ff:ff:ff:ff
5: br-lan: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000
link/ether 00:a0:57:80:2b:ee brd ff:ff:ff:ff:ff:ff
6: phy0-ap0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue master br-lan state DOWN mode DEFAULT group def0
link/ether 04:f0:21:bf:45:cc brd ff:ff:ff:ff:ff:ff

root@lx6500-dev:~# ip a
4: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master br-lan state UP group default qlen 1000
link/ether 00:a0:57:80:2b:ee brd ff:ff:ff:ff:ff:ff
5: br-lan: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether 00:a0:57:80:2b:ee brd ff:ff:ff:ff:ff:ff
inet 192.168.1.1/24 brd 192.168.1.255 scope global br-lan
valid_lft forever preferred_lft forever
inet6 fe80::2a0:57ff:fe80:2bee/64 scope link proto kernel_ll
valid_lft forever preferred_lft forever
6: phy0-ap0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue master br-lan state DOWN group default qlen 1000
link/ether 04:f0:21:bf:45:cc brd ff:ff:ff:ff:ff:ff

Using that configuration, WIFI clients get addresses from the existing DHCP server on the LAN, and are in the same IP network as the LAN devices.

cu
Michael

Yes. a bridge is - a bridge! and that is how normal wifi access points work

My issue is not with the basic config. It is with the performance - and
in fact a subset of the performance - access to my LAN is FINE access
the internet beyond is dire, but not impossible

For reference this is what IP link shows:

# ip l
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master
nm-bridge state UP mode DEFAULT group default qlen 1000
link/ether d8:3a:dd:85:22:b1 brd ff:ff:ff:ff:ff:ff
3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast
master nm-bridge state UP mode DORMANT group default qlen 1000
link/ether d8:3a:dd:85:22:b2 brd ff:ff:ff:ff:ff:ff
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


Everything seems as it should be. No interface reports packet loss, yet
still it is massive but *only when going to/from wifi client to.from the Internet*.

I do not understand what is so different about a packet going to or from
the internet that causes the problem.

--
?But what a weak barrier is truth when it stands in the way of an
hypothesis!?

Mary Wollstonecraft


--- PyGate Linux v1.5.2
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)

The Natural Philosopher <tnp@invalid.invalid> 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.

--- PyGate Linux v1.5.2
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)

On 19/01/2026 10:08, Anssi Saari wrote:

The Natural Philosopher <tnp@invalid.invalid> 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.

It made no difference. I added that in case it helped. It didnt.

--
Civilization exists by geological consent, subject to change without notice.
? Will Durant


--- PyGate Linux v1.5.2
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)