epoch1970,
I reflashed the SD card to pCP 7, 32 bit, installed in a rP1 4b and went
through the updates and setup and it works as you said.
Once more the 64 bit pCP 7 is not quite up to speed (my Allo Boss2
initially needed pCP 7 32 bit to work) no big deal.
>From a former life in IT project
Wirrunna wrote:
> Well, I can't get AP to work.
> My understanding of Bridge Mode is that it will take the network range
> via the ethernet cable, so shouldn't the AP IP Address be greyed out if
> Bridge Mode is Yes ?
You're correct.
There is a glitch in the matrix, you should just disregard the
I tried a rPi 3b and was able to get that to work, sort of. My laptop
could see the test network but not connect. WiFi Analyzer showed the
SSID but the signal level seemed to drop after a few minutes. Had
another go with the rPi 4b, still no luck.
Googled Raspberry Pi wifi Access Point and
paul- wrote:
> Make sure to update the APmode extension itself. Or did you just
> download the add on?
I clicked the update box. There is a 7" Official Touch screen attached
but Jivelite is not installed so I can see the screen output and saw the
line about Readline.tcz .
A camel is a
Make sure to update the APmode extension itself. Or did you just
download the add on?
piCorePlayer a small player for the Raspberry Pi in RAM.
Homepage: https://www.picoreplayer.org
Please 'donate'
Paul Webster wrote:
> Did you connect to the new pCP WAP via WiFi at that point?
No, it was connected with ethernet, WiFi Analyzer on my phone did not
show any new network SSIDs and having an ip address of 10.10.10.1 I
could not connect from my PC on 192.168.2.20 without stuffing about
with
Wirrunna wrote:
>
>
> Message on the screen "To setup piCorePlayer, use ..
> - http://10.10.10.1
>
> That stuffs me
Did you connect to the new pCP WAP via WiFi at that point?
Paul Webster
http://dabdig.blogspot.com
author of \"now playing\" plugins covering radio france (fip etc),
Well, I can't get AP to work.
New RPi 4b, new SD card with new download of pCP 7, 64 bit.
After booting,
1. Patch update and reboot
2. Minor update, now 7.0.1 - pCP4b-113-HFD | piCorePlayer v7.0.1 | www
v00015 | linux 5.4.83-pcpCore-v8 | piCore v12.0pCP | Squeezelite
v1.9.8-1287-pCP
click
It works too on my configuration.
I had to start with a new fresh install of pcp and after configuration
it will work... I have now wifi and music in one device in my garden.
Thanks for this really good job ! ;-)
As far as this issue is resolve ap-mode should be a stable feature...
Well thank you for the update, indeed it works for me now. That's
great.
There is at least one advantage to bridging in the script, the AP could
be run by wpa-supplicant and not hostapd. Wpa-supplicant doesn't bridge
the interface for you, AFAIK.
Code:
network={
I love the use of the word "wrong". I know you to tinker around with
enough stuff to know that there are more than one way to tackle a task.
The hostapd documentation clearly states that it "can" be used. That
does not mean it has to be used, and it for sure does not mean that
hostapd has
paul- wrote:
> Brctl is creating the bridge. Hostapd does care or need to know itÂs
> in a bridge, the kernel handles it.
>
> The cgi doesnÂt do the work, itÂs done in shell scripts.
> >
Code:
> >
> brctl addbr br0
> brctl addif br0 eth0 wlan0
>
Brctl is creating the bridge. Hostapd does care or need to know its in
a bridge, the kernel handles it.
The cgi doesnt do the work, its done in shell scripts.
Code:
brctl addbr br0
brctl addif br0 eth0 wlan0
So for some reason your
paul- wrote:
> I just tested, and it's working as designed (obviously with the updated
> kernel modules) It was intended to bridge eth0 to wlan0, where the eth0
> is the upstream connection to your main network. I'm browsing the
> internet from my cell phone connected to the wifi AP created by
I just tested, and it's working as designed (obviously with the updated
kernel modules) It was intended to bridge eth0 to wlan0, where the eth0
is the upstream connection to your main network. I'm browsing the
internet from my cell phone connected to the wifi AP created by pCP, and
my phone
Crap. vi says 'wifi_apmode.cgi' is read only and I don't know how to set
/tmp/tcloop/pcp-7.0.0-www in RW mode. A remount doesn't do it.
Anyways.
/usr/local/etc/pcp/hostapd.conf
Needs to be modified with
Code:
#bridge=
(for sed to succeed in the
Its been forever since I did a full test on that feature. I'll have to
check it out.
piCorePlayer a small player for the Raspberry Pi in RAM.
Homepage: https://www.picoreplayer.org
Please 'donate'
paul- wrote:
> net-bridge kernel module extensions have been updated with missing
> dependencies.
Thanks for that!
Should be working (I'm not in front of the machine) but looks like it
went away again from my network when I applied settings.
I am puzzled by the fact the bridge uses the static
net-bridge kernel module extensions have been updated with missing
dependencies.
piCorePlayer a small player for the Raspberry Pi in RAM.
Homepage: https://www.picoreplayer.org
Please 'donate'
Ill check out the module packaging.
piCorePlayer a small player for the Raspberry Pi in RAM.
Homepage: https://www.picoreplayer.org
Please 'donate'
(https://www.paypal.com/cgi-bin/webscr?cmd=_donations=U7JHY5WYHCNRU=GB_code=USD=PP%2dDonationsBF%3abtn_donateCC_LG%2egif%3aNonHosted)
if you
Thats a packaging issue I think. When the kernel was compiled a
bunch of modules were compiled, including those we miss.
The question would be in which .tcz extension file modules stp.ko and
llc.ko have landed, and I dont know how to answer that.
2 SB 3 1 PCP 6 Libratone Loop, Zipp, Zipp
Hello Epoch and thank you for your research. As you say we are in the
same boat..
For me the problem is on the side of the kernel compiling. One option
for it is "CONFIG_BRIDGE". We can see it in the sumary of the compile
options used to compile the kernel. File is 5.4.83-pcpCore-v7_.config.
A
Some more info after reinstalling a clean copy of pCP 7 on the machine.
Still no HDMI output so I'm unwilling to commit settings again.
>From the web GUI I installed AP mode.
Then I tried the commands the OP posted and I am in the same boat.
Code:
tc@carmel:~$ brctl
Well, well.
I wasn't aware bridged AP mode was a thing in piCore. I have one player
running pCP v7 that I installed recently. So I went about and clicked my
way through setting up AP mode (downloads went well apparently), bridged
mode (doesn't seem to get concerned with the IP address field just
Hello Epoch and Paul,
Thanks for tour answers.
I use the last version of piCore player or not far... (piCorePlayer
v7.0.1 | www v00016 | linux 5.4.83-pcpCore-v7 | piCore v12.0pCP |
Squeezelite v1.9.9-1364-pCP)
WAP mode has an option to use bridge mode, and when i check sh, i can
see it calls
The bridging kernel modules should have been installed when you
installed WAP mode. What version are you using?
piCorePlayer a small player for the Raspberry Pi in RAM.
Homepage: https://www.picoreplayer.org
Please 'donate'
brctl is certainly not a requirement otherwise it would be part of the
kernel.
Perhaps you can try using "ip":
https://baturin.org/docs/iproute2/#ip-link-add-bridge
This being said I guess you'll have to bridge ethernet early enough so
that it'll get IP configured at boot, and not eth0. Hope
Hello all!
Nobody has an idea?
oliverbg1's Profile: http://forums.slimdevices.com/member.php?userid=71652
View this thread: http://forums.slimdevices.com/showthread.php?t=114369
Hello all!
I use with success pcp for my audio multiroom since 4 years now. All
works fine.
One of my player is hoste on a Rpi3 (with embedded wifi chip), so I want
this player do more things like sharing LAN access.
I activate WAP mode, go to wap mode page and fill in fields. After
reboot
29 matches
Mail list logo
