From Newsgroup: comp.sys.raspberry-pi

I have a RPi 3B wirelessly in a LAN, currently located with access to
gigabit ethernet. I want to repurpose it to an access point, at first w/ conventional peripherals, then 'shift' it to headless operation
connecting only to power and ethernet.

So far I have installed the RealVNC server from the RPi repo/s and have
tested the VNC access using a live LM testing first the realvnc viewer
and then the Tigervnc, and I prefer the Tiger.

If it isn't 'impossible', in the beginning I would like to be able to
operate the RPi in one of two different modes, either conventionally w/
wifi connectivity or as an access point not headless.

One of my guides so far has been this article: https://learn.sparkfun.com/tutorials/setting-up-a-raspberry-pi-3-as-an-access-point/all

However, that method will 'corrupt'/destroy the conventional function of
wifi connectivity. Is it possible to somehow configure to be able to use
that configuration alternatively w/ the conventional? If not, I would
delay my conversion to access point until I decide on a USB wifi dongle
to add. I don't think much of the RPi's native antenna situation, and I
would prefer a rubber ducky which I could have on a USB dongle. I do
not want to do a board mod to enable an antenna which I have viewed.

This is my first experience heading toward doing anything headless. In
the past I have had an OEM AP in the location I would put the headless
RPi, but it died.
--
Mike Easter

--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: comp.sys.raspberry-pi

On 15/08/2025 19:53, Mike Easter wrote:

I have a RPi 3B wirelessly in a LAN, currently located with access to gigabit ethernet. I want to repurpose it to an access point, at first w/ conventional peripherals, then 'shift' it to headless operation
connecting only to power and ethernet.

So far I have installed the RealVNC server from the RPi repo/s and have tested the VNC access using a live LM testing first the realvnc viewer
and then the Tigervnc, and I prefer the Tiger.

If it isn't 'impossible', in the beginning I would like to be able to operate the RPi in one of two different modes, either conventionally w/
wifi connectivity or as an access point not headless.

One of my guides so far has been this article: https://learn.sparkfun.com/tutorials/setting-up-a-raspberry-pi-3-as-an- access-point/all

However, that method will 'corrupt'/destroy the conventional function of wifi connectivity. Is it possible to somehow configure to be able to use that configuration alternatively w/ the conventional?  If not, I would delay my conversion to access point until I decide on a USB wifi dongle
to add. I don't think much of the RPi's native antenna situation, and I would prefer a rubber ducky which I could have on a USB dongle.  I do
not want to do a board mod to enable an antenna which I have viewed.

This is my first experience heading toward doing anything headless. In
the past I have had an OEM AP in the location I would put the headless
RPi, but it died.

The 3B doesn't have any way near Gigabyte Ethernet
--
Chris
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: comp.sys.raspberry-pi

On 15/08/2025 19:53, Mike Easter wrote:

I have a RPi 3B wirelessly in a LAN, currently located with access to gigabit ethernet. I want to repurpose it to an access point, at first w/ conventional peripherals, then 'shift' it to headless operation
connecting only to power and ethernet.

So far I have installed the RealVNC server from the RPi repo/s and have tested the VNC access using a live LM testing first the realvnc viewer
and then the Tigervnc, and I prefer the Tiger.

If it isn't 'impossible', in the beginning I would like to be able to operate the RPi in one of two different modes, either conventionally w/
wifi connectivity or as an access point not headless.

One of my guides so far has been this article: https://learn.sparkfun.com/tutorials/setting-up-a-raspberry-pi-3-as-an-access-point/all

However, that method will 'corrupt'/destroy the conventional function of wifi connectivity. Is it possible to somehow configure to be able to use that configuration alternatively w/ the conventional?  If not, I would delay my conversion to access point until I decide on a USB wifi dongle
to add. I don't think much of the RPi's native antenna situation, and I would prefer a rubber ducky which I could have on a USB dongle.  I do
not want to do a board mod to enable an antenna which I have viewed.

This is my first experience heading toward doing anything headless. In
the past I have had an OEM AP in the location I would put the headless
RPi, but it died.

This may be of some help, if you want to bridge Wifi to Ethernet

https://www.baeldung.com/linux/bridging-network-interfaces
I was looking at doing something similar, but life was too short and I
got a dedicated box that works OK

I am not sure that it is easy to run wifi in client and 'server' mode
together at all. For sure you can do either separately.
--
When plunder becomes a way of life for a group of men in a society, over
the course of time they create for themselves a legal system that
authorizes it and a moral code that glorifies it.

Frédéric Bastiat

--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: comp.sys.raspberry-pi

On 15/08/2025 20:03, Chris Townley wrote:

On 15/08/2025 19:53, Mike Easter wrote:

I have a RPi 3B wirelessly in a LAN, currently located with access to
gigabit ethernet. I want to repurpose it to an access point, at first
w/ conventional peripherals, then 'shift' it to headless operation
connecting only to power and ethernet.

So far I have installed the RealVNC server from the RPi repo/s and
have tested the VNC access using a live LM testing first the realvnc
viewer and then the Tigervnc, and I prefer the Tiger.

If it isn't 'impossible', in the beginning I would like to be able to
operate the RPi in one of two different modes, either conventionally
w/ wifi connectivity or as an access point not headless.

One of my guides so far has been this article:
https://learn.sparkfun.com/tutorials/setting-up-a-raspberry-pi-3-as-an- access-point/all

However, that method will 'corrupt'/destroy the conventional function
of wifi connectivity. Is it possible to somehow configure to be able
to use that configuration alternatively w/ the conventional?  If not,
I would delay my conversion to access point until I decide on a USB
wifi dongle to add. I don't think much of the RPi's native antenna
situation, and I would prefer a rubber ducky which I could have on a
USB dongle.  I do not want to do a board mod to enable an antenna
which I have viewed.

This is my first experience heading toward doing anything headless. In
the past I have had an OEM AP in the location I would put the headless
RPi, but it died.

The 3B doesn't have any way near Gigabyte Ethernet

It doesn't matter really does it? neither will the wifi. It will
allegedly do 300Mbps, which is better than 100Mbps ethernet...
--
"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

--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: comp.sys.raspberry-pi

On 15/08/2025 20:09, The Natural Philosopher wrote:

On 15/08/2025 20:03, Chris Townley wrote:

On 15/08/2025 19:53, Mike Easter wrote:

I have a RPi 3B wirelessly in a LAN, currently located with access to
gigabit ethernet. I want to repurpose it to an access point, at first
w/ conventional peripherals, then 'shift' it to headless operation
connecting only to power and ethernet.

So far I have installed the RealVNC server from the RPi repo/s and
have tested the VNC access using a live LM testing first the realvnc
viewer and then the Tigervnc, and I prefer the Tiger.

If it isn't 'impossible', in the beginning I would like to be able to
operate the RPi in one of two different modes, either conventionally
w/ wifi connectivity or as an access point not headless.

One of my guides so far has been this article:
https://learn.sparkfun.com/tutorials/setting-up-a-raspberry-pi-3-as-
an- access-point/all

However, that method will 'corrupt'/destroy the conventional function
of wifi connectivity. Is it possible to somehow configure to be able
to use that configuration alternatively w/ the conventional?  If not,
I would delay my conversion to access point until I decide on a USB
wifi dongle to add. I don't think much of the RPi's native antenna
situation, and I would prefer a rubber ducky which I could have on a
USB dongle.  I do not want to do a board mod to enable an antenna
which I have viewed.

This is my first experience heading toward doing anything headless.
In the past I have had an OEM AP in the location I would put the
headless RPi, but it died.

The 3B doesn't have any way near Gigabyte Ethernet

It doesn't matter really does it? neither will the wifi. It will
allegedly do 300Mbps, which is better than 100Mbps ethernet...

It would depend on how many client devices connect, and what they want
to use...
--
Chris
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: comp.sys.raspberry-pi

Chris Townley wrote:

The 3B doesn't have any way near Gigabyte Ethernet

The LAN is; giga router, giga switch and other ethernet devices on the LAN.
--
Mike Easter
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: comp.sys.raspberry-pi

On 15/08/2025 19:53, Mike Easter wrote:

I have a RPi 3B wirelessly in a LAN, currently located with access to gigabit ethernet. I want to repurpose it to an access point, at first w/ conventional peripherals, then 'shift' it to headless operation
connecting only to power and ethernet.

The Pi 3B would not make a good access point, it only has 100Mbit
Ethernet at 2.4GHz WiFi. The 3B+ can do 300Mbit/s with Gigabit Ethernet,
and has 2.4 and 5 GHz Wifi, but is still not as good as a dedicated
access point.

[Snip]

However, that method will 'corrupt'/destroy the conventional function of wifi connectivity. Is it possible to somehow configure to be able to use that configuration alternatively w/ the conventional?  If not, I would delay my conversion to access point until I decide on a USB wifi dongle
to add. I don't think much of the RPi's native antenna situation, and I would prefer a rubber ducky which I could have on a USB dongle.  I do
not want to do a board mod to enable an antenna which I have viewed.

This is my first experience heading toward doing anything headless. In
the past I have had an OEM AP in the location I would put the headless
RPi, but it died.

If you also have to get a USB dongle for the Pi, then you might as well
just get another proper access point which will have better WiFi range
and performance, and doesn't require a whole lot of configuration.

---druck

--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: comp.sys.raspberry-pi

Chris Townley wrote:

It would depend on how many client devices connect, and what they want
to use...

Normally, there is very little wifi 'load'. The desirability of an AP is because of logistics. The wifi/ethernet router is buried in a location disadvantageous to wifi, but extremely advantageous and *necessary* for
the ethernet distribution. The house is big. 'Moving' the AP from its
buried router location to a more open position would improve the signal thru'out the house.

Under 'normal' operation, the wifi device in the kitchen in off, the
wifi device in the LR is off, and the wifi device in a bedroom is only streaming audio while I'm in bed.

Normally the location of the RPi is at a seat about 10' from the wifi
router, and normally the one ethernet connxn 'nearby' the RPi is being
used by another device, a VoIP, so the RPi just uses its wifi for
connectivity out of convenience.

During this 'research' I've brought another ethernet connection from a
switch 'across the floor' over to the RPi. Whenever I'm willing to
sacrifice the most convenient connectivity of the Pi, I can give it AP functionality not headless for testing, but I've been putting that off
until I'm almost ready to move it to the AP position for headless operation.
--
Mike Easter
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: comp.sys.raspberry-pi

druck wrote:

The Pi 3B would not make a good access point, it only has 100Mbit
Ethernet at 2.4GHz WiFi. The 3B+ can do 300Mbit/s with Gigabit Ethernet,
and has 2.4 and 5 GHz Wifi, but is still not as good as a dedicated
access point.

I see.
--
Mike Easter
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: comp.sys.raspberry-pi

druck wrote:

you might as well just get another proper access point which will have better WiFi range and performance, and doesn't require a whole lot of configuration.

Shopping around, it looks like I can get a pretty good AP for about $40.

Gigabit on the ethernet side and 802.11ac on the wifi, and one I see has
4 antennas :-) (I'm a fan of at least 1)

Lots of the low end are 10/100 on the ethernet and not 'ac' on the wifi.
--
Mike Easter
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: comp.sys.raspberry-pi

Mike Easter wrote:

If it isn't 'impossible', in the beginning I would like to be able to operate the RPi in one of two different modes, either conventionally w/
wifi connectivity or as an access point not headless.

I'm modifying my original idea of deploying the RPi as a 'real' AP; but
I'm going to continue my 'quest' in the 'direction' of doing that,
because I've figured a strategy to allow me to go in the direction I
started toward the Pi as an AP first w/ conventional peripherals, then headless.

I can do it using a spare SD.

I'll start w/ my current RPi Raspbian install, then I'll modify it as
the tutorial instructed to make it a conventionally configured
peripherally access point by using the combination of temporary ethernet
and the native Pi wifi w/ RealVNC server on the Pi and Tiger viewer on
another LAN device LM live.

Then I'll see if I can use the conventional peripheral Pi as an AP for a
wifi device, probably a chromebook (past EOL). Then I'll 'bypass' the
Pi's connected peripherals and do it headlessly, for the 'conclusion' of
the project. I can use a different SD to bring the Pi back to the
normal peripherals and wifi connectivity.

That is, I've decided the original idea isn't so good, but I want to see
it work.
--
Mike Easter
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: comp.sys.raspberry-pi

On 15/08/2025 20:11, Chris Townley wrote:

On 15/08/2025 20:09, The Natural Philosopher wrote:

On 15/08/2025 20:03, Chris Townley wrote:

On 15/08/2025 19:53, Mike Easter wrote:

I have a RPi 3B wirelessly in a LAN, currently located with access
to gigabit ethernet. I want to repurpose it to an access point, at
first w/ conventional peripherals, then 'shift' it to headless
operation connecting only to power and ethernet.

So far I have installed the RealVNC server from the RPi repo/s and
have tested the VNC access using a live LM testing first the realvnc
viewer and then the Tigervnc, and I prefer the Tiger.

If it isn't 'impossible', in the beginning I would like to be able
to operate the RPi in one of two different modes, either
conventionally w/ wifi connectivity or as an access point not headless. >>>>
One of my guides so far has been this article:
https://learn.sparkfun.com/tutorials/setting-up-a-raspberry-pi-3-as-
an- access-point/all

However, that method will 'corrupt'/destroy the conventional
function of wifi connectivity. Is it possible to somehow configure
to be able to use that configuration alternatively w/ the
conventional?  If not, I would delay my conversion to access point
until I decide on a USB wifi dongle to add. I don't think much of
the RPi's native antenna situation, and I would prefer a rubber
ducky which I could have on a USB dongle.  I do not want to do a
board mod to enable an antenna which I have viewed.

This is my first experience heading toward doing anything headless.
In the past I have had an OEM AP in the location I would put the
headless RPi, but it died.

The 3B doesn't have any way near Gigabyte Ethernet

It doesn't matter really does it? neither will the wifi. It will
allegedly do 300Mbps, which is better than 100Mbps ethernet...

It would depend on how many client devices connect, and what they want
to use...

So does gigabit Ethernet
--
In theory, there is no difference between theory and practice.
In practice, there is.
-- Yogi Berra

--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: comp.sys.raspberry-pi

On 15/08/2025 21:30, Mike Easter wrote:

Chris Townley wrote:

It would depend on how many client devices connect, and what they want
to use...

Normally, there is very little wifi 'load'. The desirability of an AP is because of logistics. The wifi/ethernet router is buried in a location disadvantageous to wifi, but extremely advantageous and *necessary* for
the ethernet distribution.  The house is big.  'Moving' the AP from its buried router location to a more open position would improve the signal thru'out the house.

Under 'normal' operation, the wifi device in the kitchen in off, the
wifi device in the LR is off, and the wifi device in a bedroom is only streaming audio while I'm in bed.

Normally the location of the RPi is at a seat about 10' from the wifi router, and normally the one ethernet connxn 'nearby' the RPi is being
used by another device, a VoIP, so the RPi just uses its wifi for connectivity out of convenience.

During this 'research' I've brought another ethernet connection from a switch 'across the floor' over to the RPi. Whenever I'm willing to
sacrifice the most convenient connectivity of the Pi, I can give it AP functionality not headless for testing, but I've been putting that off
until I'm almost ready to move it to the AP position for headless
operation.

I just bought one of these.

https://www.4gon.co.uk/mikrotik-hap-ax-lite-p-10452.html

user interface is a disgrace, but I stumbled through it and got it working
--
In theory, there is no difference between theory and practice.
In practice, there is.
-- Yogi Berra

--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: comp.sys.raspberry-pi

On 15/08/2025 19:53, Mike Easter wrote:

If it isn't 'impossible', in the beginning I would like to be able to operate the RPi in one of two different modes, either conventionally w/
wifi connectivity or as an access point not headless.

It's possible for it to operate as an AP and as a Station at the same
time but I think both funtions have to operate on the same channel. i.e.
both are on channel 1 not AP on channel1 and station on channel9
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: comp.sys.raspberry-pi

On Fri, 15 Aug 2025 13:30:30 -0700, Mike Easter wrote:

Under 'normal' operation, the wifi device in the kitchen in off, the
wifi device in the LR is off, and the wifi device in a bedroom is only streaming audio while I'm in bed.

A got a guy in to run Ethernet cabling between my office as a central
point (where the switch and main computer gear are located) and various strategic points around the house, including the living room and master bedroom.
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: comp.sys.raspberry-pi

On Fri, 15 Aug 2025 20:04:15 +0100, The Natural Philosopher wrote:

This may be of some help, if you want to bridge Wifi to Ethernet

https://www.baeldung.com/linux/bridging-network-interfaces

That references old commands like “brctl” and “ifconfig”. One of those I don’t even have installed on the system which provides my wi-fi
access point.

Here’s the relevant part of /etc/network/interfaces on that machine (“enp3s0” and “wlp5s0” are the wired and wireless interfaces being bridged):

auto br0
iface br0 inet static
pre-up ip link add name br0 type bridge
pre-up ip link set dev br0 up
post-up ip link set dev enp3s0 master br0
post-up iw dev wlp5s0 set 4addr on
post-up ip link set dev wlp5s0 master br0
post-up ip link set dev enp3s0 up
post-up ip link set dev wlp5s0 up
address ...
netmask ...
network ...
broadcast ...
gateway ...
bridge_ports wlp5s0 enp3s0
bridge_fd 0

The additional bridge-specific options are documented here <https://manpages.debian.org/bridge-utils-interfaces(5)>.
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: comp.sys.raspberry-pi

Mike Easter wrote:

Then I'll see if I can use the conventional peripheral Pi as an AP for
a wifi device, probably a chromebook (past EOL).

The scheme didn't work for me. My guess is because part of the
configuration instructions didn't have the right entry for the wifi
driver, but I didn't figure that out until later.

The proper driver is mmc_bcm2835, but the instructions I followed said;

driver=nl80211

If I ever choose to go back to test if the other driver would work, I
still have that SD; it was an earlier Raspbian, so I just replaced the
SD w/ a newer.
--
Mike Easter

--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: comp.sys.raspberry-pi

On 15/08/2025 22:09, Mike Easter wrote:

druck wrote:

you might as well just get another proper access point which will have
better WiFi range and performance, and doesn't require a whole lot of
configuration.

Shopping around, it looks like I can get a pretty good AP for about $40.

Gigabit on the ethernet side and 802.11ac on the wifi, and one I see has
4 antennas :-) (I'm a fan of at least 1)

The Raspberry Pi is great general purpose machine, and if you were to be stranded on a desert island (i.e. somewhere without Amazon delivery),
and a container load of the Pi's and peripherals washed up, you could
make them do just about anything.

However, if you are somewhere where a delivery driver can chuck stuff
over your back gate, and are after a specific single function bit of
tech such as an access point (or security camera came up recently),
dedicated hardware has both cost and performance advantages.

Although I do like see if the Pi will do things just in case of desert islands!

---druck

--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: comp.sys.raspberry-pi

On Mon, 18 Aug 2025 16:22:26 +0100, druck wrote:

However, if you are somewhere where a delivery driver can chuck stuff
over your back gate, and are after a specific single function bit of
tech such as an access point (or security camera came up recently),
dedicated hardware has both cost and performance advantages.

Sure, an off-the-shelf product may do 90% of what you want. But it will
never quite be 100% of what you want.

That’s where roll-your-own comes in. Think of a Raspberry Pi with Linux as being like modelling clay, both hardware and software, that you can mould
to whatever shape you want.
--- Synchronet 3.21a-Linux NewsLink 1.2