Lost. Very new to Raspberry pi.. need help for a project.

[dwendooley]

Good day kind folk,

I need suggestions on what and where to fix things.
Very long story as short as I can make it. (I've been through at least 4 iterations of starting from scratch and fixing things)
I'm building Wall-E for my daughter. She's been asking for years. (She's in college).
https://wired.chillibasket.com/3d-printed-wall-e/

So.. Raspberry Pi 4 B, new, the official installer, 64 bit, etc.
SSH in and lots of locale problems that I think I largely solved. Even reviewed the jounralctl and found one place where country was being assumed to be GB. (Definitely in US, Eastern time, US keyboard).

I think this might relate to how the AP is configured for country, but.. you tell me.
It thinks it's up. I've tried numerous settings in the web gui and once or twice I was able to see the network from my windows machine and iphone, but I have yet to connect. Typically it does not show up at all and can't be connected with the QR code.

OK so.. I'll share and attach the debug log.

I am on windows using putty wireless and do believe this AP is supposed to allow for both Pi to my router on my lan, as well as being an AP itself. I'm not worried about throughput at all.. I want to control a robot with a web interface without wifi, later.

Routing:

default via 10.3.141.1 dev wlan0 src 10.3.141.1 metric 3003
10.3.141.0/24 dev wlan0 proto dhcp scope link src 10.3.141.1 metric 3003
192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.156 metric 600

eth:
2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether 2c:cf:67:a2:3d:0f brd ff:ff:ff:ff:ff:ff

(No, no wired connection, no bluetooth in use)

wlan0:

3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq state UP group default qlen 1000
    link/ether 2c:cf:67:a2:3d:10 brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.156/24 brd 192.168.1.255 scope global dynamic noprefixroute wlan0
       valid_lft 85291sec preferred_lft 85291sec
    inet 10.3.141.1/24 brd 10.3.141.255 scope global noprefixroute wlan0
       valid_lft forever preferred_lft forever
    inet6 2600:4040:ae50:8600:460f:5ec5:6839:ee9/64 scope global dynamic noprefixroute
       valid_lft 861sec preferred_lft 861sec
    inet6 2600:4040:ae50:8600:d7e5:3453:3805:3fbf/64 scope global dynamic mngtmpaddr noprefixroute
       valid_lft 860sec preferred_lft 860sec
    inet6 fe80::a344:6304:cf4d:9b25/64 scope link noprefixroute
       valid_lft forever preferred_lft forever

raspap_debug.log

I've seen this, which may be related:
raspberrypi/linux#6049

I added these to .bashrc before I started the install of raspap, and found a conf file that still had country=GB in it, fixed that, relogged, rebooted, did everything in order.

Any ideas on what the issue is? I cannot see the AP despite the gui saying it's up.

Thank you in advance!

Side note... I can work vi, I know a thing or two in a *nix environment, but assume I don't. It's been a couple of decades since I worked in there.

bz edit: formatting

[billz]

Your eth0 interface is down, and wlan0 is configured in client (STA) mode. With a single WLAN adapter, you can reliably configure it as either an access point (AP) or as a wireless client/station (STA), not both. If your intention is to operate this as a wireless repeater (assumed if this project won't have a persistent ethernet connection), you'll need a second WLAN adapter. See the docs for a detailed walkthrough on creating a repeater. The FAQ has a link to recommended hardware. Good luck.

[dwendooley]

Good to know, thanks. I'm going to stick with just an AP and wire in when I need to. Thanks!

[dwendooley]

Worked perfectly. You are a gentleman and a scholar, sir. Thank you!

…

On Sat, Apr 26, 2025 at 2:29 AM Bill Zimmerman ***@***.***> wrote: Start with a custom RaspAP OS image <https://github.com/RaspAP/raspap-webgui/releases/latest>. This will give you a functional AP on first boot. Modify settings as needed from there. If something doesn't work, perform a system reset (option below 'Generate debug log'). This simple approach eliminates 99% of the guesswork for the vast majority of users. — Reply to this email directly, view it on GitHub <#1836 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AKR6I5GU42Z6C6GWOR4W6XT23MRTJAVCNFSM6AAAAAB34UGX5OVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTEOJVGM2DCNI> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[billz]

Glad to hear it! Please do share progress on your project and perhaps a photo in show and tell. It sounds fun.