Trouble with Raspberry Pi connection and initial setup

No, you’re past that. The Bridge is already on your network.

Click next on this screen:

Your Bridge should then appear on the next screen.

I got this instead…

If you login into your router can you see that the Bridge is connected? What does your TV look like now?

I’ve been locked out for too many replies on my first day. :-0

Here’s what it looks like now. Still not showing up in my WiFi list and the TV connection appears unchanged…

Not sure how to log into my router. As for the Terminal output:

Last login: Tue Dec 21 12:52:35 on console

The default interactive shell is now zsh.
To update your account to use zsh, please run chsh -s /bin/zsh.
For more details, please visit Use zsh as the default shell on your Mac - Apple Support.
Arthurs-MBP:~ ifconfig
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
options=1203<RXCSUM,TXCSUM,TXSTATUS,SW_TIMESTAMP>
inet 127.0.0.1 netmask 0xff000000
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1
nd6 options=201<PERFORMNUD,DAD>
gif0: flags=8010<POINTOPOINT,MULTICAST> mtu 1280
stf0: flags=0<> mtu 1280
en0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
options=400<CHANNEL_IO>
ether 78:9f:70:7a:35:9a
inet6 fe80::146a:a72e:a713:60bf%en0 prefixlen 64 secured scopeid 0x4
inet 192.168.1.xxx netmask 0xffffff00 broadcast 192.168.1.xxx
nd6 options=201<PERFORMNUD,DAD>
media: autoselect
status: active
en1: flags=8963<UP,BROADCAST,SMART,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
options=460<TSO4,TSO6,CHANNEL_IO>
ether 82:0f:1a:7c:a4:40
media: autoselect
status: inactive
en2: flags=8963<UP,BROADCAST,SMART,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
options=460<TSO4,TSO6,CHANNEL_IO>
ether 82:0f:1a:7c:a4:41
media: autoselect
status: inactive
bridge0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
options=63<RXCSUM,TXCSUM,TSO4,TSO6>
ether 82:0f:1a:7c:a4:40
Configuration:
id 0:0:0:0:0:0 priority 0 hellotime 0 fwddelay 0
maxage 0 holdcnt 0 proto stp maxaddr 100 timeout 1200
root id 0:0:0:0:0:0 priority 0 ifcost 0 port 0
ipfilter disabled flags 0x0
member: en1 flags=3<LEARNING,DISCOVER>
ifmaxaddr 0 port 5 priority 0 path cost 0
member: en2 flags=3<LEARNING,DISCOVER>
ifmaxaddr 0 port 6 priority 0 path cost 0
nd6 options=201<PERFORMNUD,DAD>
media:
status: inactive
p2p0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 2304
options=400<CHANNEL_IO>
ether 0a:9f:70:7a:35:9a
media: autoselect
status: inactive
awdl0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1484
options=400<CHANNEL_IO>
ether 7a:12:5e:d7:af:e3
inet6 fe80::7812:5eff:fed7:afe3%awdl0 prefixlen 64 scopeid 0x9
nd6 options=201<PERFORMNUD,DAD>
media: autoselect
status: active
llw0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
options=400<CHANNEL_IO>
ether 7a:12:5e:d7:af:e3
inet6 fe80::7812:5eff:fed7:afe3%llw0 prefixlen 64 scopeid 0xa
nd6 options=201<PERFORMNUD,DAD>
media: autoselect
status: active
utun0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1380
inet6 fe80::a4c8:9a3f:ea0f:383c%utun0 prefixlen 64 scopeid 0xb
nd6 options=201<PERFORMNUD,DAD>
utun1: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 2000
inet6 fe80::68a8:53a4:7d17:1b85%utun1 prefixlen 64 scopeid 0xc
nd6 options=201<PERFORMNUD,DAD>
utun2: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1380
inet6 fe80::738b:3697:65bb:ec15%utun2 prefixlen 64 scopeid 0xd
nd6 options=201<PERFORMNUD,DAD>
utun3: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1380
inet6 fe80::5ebd:82ff:7dca:2fdc%utun3 prefixlen 64 scopeid 0xe
nd6 options=201<PERFORMNUD,DAD>
en4: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
options=400<CHANNEL_IO>
ether 32:57:14:51:9e:be
inet6 fe80::1c2e:e79b:4088:8c2a%en4 prefixlen 64 secured scopeid 0xf
inet 169.254.247.13 netmask 0xffff0000 broadcast 169.254.255.xxx
nd6 options=201<PERFORMNUD,DAD>
media: autoselect (100baseTX )
status: active

Last login: Fri Jan 14 22:18:33 on console

Restored session: Fri Jan 14 22:16:35 EST 2022

The default interactive shell is now zsh.

To update your account to use zsh, please run chsh -s /bin/zsh.

For more details, please visit Use zsh as the default shell on your Mac - Apple Support.

ping 192.168.1.36

PING 192.168.1.36 (192.168.1.36): 56 data bytes

64 bytes from 192.168.1.36: icmp_seq=0 ttl=64 time=52.016 ms

64 bytes from 192.168.1.36: icmp_seq=1 ttl=64 time=3.101 ms

64 bytes from 192.168.1.36: icmp_seq=2 ttl=64 time=4.172 ms

64 bytes from 192.168.1.36: icmp_seq=3 ttl=64 time=4.482 ms

64 bytes from 192.168.1.36: icmp_seq=4 ttl=64 time=4.310 ms

64 bytes from 192.168.1.36: icmp_seq=5 ttl=64 time=5.795 ms

64 bytes from 192.168.1.36: icmp_seq=6 ttl=64 time=5.193 ms

64 bytes from 192.168.1.36: icmp_seq=7 ttl=64 time=3.571 ms

64 bytes from 192.168.1.36: icmp_seq=8 ttl=64 time=3.133 ms

64 bytes from 192.168.1.36: icmp_seq=9 ttl=64 time=3.566 ms

64 bytes from 192.168.1.36: icmp_seq=10 ttl=64 time=4.184 ms

64 bytes from 192.168.1.36: icmp_seq=11 ttl=64 time=3.107 ms

64 bytes from 192.168.1.36: icmp_seq=12 ttl=64 time=6.590 ms

64 bytes from 192.168.1.36: icmp_seq=13 ttl=64 time=4.761 ms

64 bytes from 192.168.1.36: icmp_seq=14 ttl=64 time=301.163 ms

64 bytes from 192.168.1.36: icmp_seq=15 ttl=64 time=3.530 ms

64 bytes from 192.168.1.36: icmp_seq=16 ttl=64 time=5.254 ms

64 bytes from 192.168.1.36: icmp_seq=17 ttl=64 time=4.201 ms

64 bytes from 192.168.1.36: icmp_seq=18 ttl=64 time=3.988 ms

64 bytes from 192.168.1.36: icmp_seq=19 ttl=64 time=4.592 ms

64 bytes from 192.168.1.36: icmp_seq=20 ttl=64 time=3.341 ms

64 bytes from 192.168.1.36: icmp_seq=21 ttl=64 time=4.667 ms

64 bytes from 192.168.1.36: icmp_seq=22 ttl=64 time=3.197 ms

64 bytes from 192.168.1.36: icmp_seq=23 ttl=64 time=3.247 ms

64 bytes from 192.168.1.36: icmp_seq=24 ttl=64 time=3.258 ms

64 bytes from 192.168.1.36: icmp_seq=25 ttl=64 time=4.631 ms

64 bytes from 192.168.1.36: icmp_seq=26 ttl=64 time=3.343 ms

64 bytes from 192.168.1.36: icmp_seq=27 ttl=64 time=4.755 ms

64 bytes from 192.168.1.36: icmp_seq=28 ttl=64 time=4.922 ms

64 bytes from 192.168.1.36: icmp_seq=29 ttl=64 time=2.894 ms

64 bytes from 192.168.1.36: icmp_seq=30 ttl=64 time=4.103 ms

64 bytes from 192.168.1.36: icmp_seq=31 ttl=64 time=3.856 ms

64 bytes from 192.168.1.36: icmp_seq=32 ttl=64 time=4.149 ms

64 bytes from 192.168.1.36: icmp_seq=33 ttl=64 time=4.216 ms

64 bytes from 192.168.1.36: icmp_seq=34 ttl=64 time=4.221 ms

64 bytes from 192.168.1.36: icmp_seq=35 ttl=64 time=3.233 ms

64 bytes from 192.168.1.36: icmp_seq=36 ttl=64 time=3.915 ms

64 bytes from 192.168.1.36: icmp_seq=37 ttl=64 time=3.521 ms

64 bytes from 192.168.1.36: icmp_seq=38 ttl=64 time=4.362 ms

64 bytes from 192.168.1.36: icmp_seq=39 ttl=64 time=4.396 ms

64 bytes from 192.168.1.36: icmp_seq=40 ttl=64 time=2.310 ms

64 bytes from 192.168.1.36: icmp_seq=41 ttl=64 time=3.870 ms

64 bytes from 192.168.1.36: icmp_seq=42 ttl=64 time=2.665 ms

64 bytes from 192.168.1.36: icmp_seq=43 ttl=64 time=6.351 ms

64 bytes from 192.168.1.36: icmp_seq=44 ttl=64 time=51.567 ms

64 bytes from 192.168.1.36: icmp_seq=45 ttl=64 time=5.221 ms

64 bytes from 192.168.1.36: icmp_seq=46 ttl=64 time=6.247 ms

64 bytes from 192.168.1.36: icmp_seq=47 ttl=64 time=4.535 ms

64 bytes from 192.168.1.36: icmp_seq=48 ttl=64 time=3.219 ms

64 bytes from 192.168.1.36: icmp_seq=49 ttl=64 time=3.147 ms

64 bytes from 192.168.1.36: icmp_seq=50 ttl=64 time=3.761 ms

64 bytes from 192.168.1.36: icmp_seq=51 ttl=64 time=3.090 ms

64 bytes from 192.168.1.36: icmp_seq=52 ttl=64 time=3.777 ms

64 bytes from 192.168.1.36: icmp_seq=53 ttl=64 time=3.256 ms

64 bytes from 192.168.1.36: icmp_seq=54 ttl=64 time=19.910 ms

64 bytes from 192.168.1.36: icmp_seq=55 ttl=64 time=6.968 ms

64 bytes from 192.168.1.36: icmp_seq=56 ttl=64 time=6.018 ms

64 bytes from 192.168.1.36: icmp_seq=57 ttl=64 time=4.731 ms

64 bytes from 192.168.1.36: icmp_seq=58 ttl=64 time=3.363 ms

64 bytes from 192.168.1.36: icmp_seq=59 ttl=64 time=4.945 ms

64 bytes from 192.168.1.36: icmp_seq=60 ttl=64 time=3.345 ms

64 bytes from 192.168.1.36: icmp_seq=61 ttl=64 time=3.777 ms

64 bytes from 192.168.1.36: icmp_seq=62 ttl=64 time=8.390 ms

64 bytes from 192.168.1.36: icmp_seq=63 ttl=64 time=3.103 ms

64 bytes from 192.168.1.36: icmp_seq=64 ttl=64 time=3.858 ms

64 bytes from 192.168.1.36: icmp_seq=65 ttl=64 time=4.689 ms

64 bytes from 192.168.1.36: icmp_seq=66 ttl=64 time=3.063 ms

64 bytes from 192.168.1.36: icmp_seq=67 ttl=64 time=6.625 ms

64 bytes from 192.168.1.36: icmp_seq=68 ttl=64 time=3.789 ms

64 bytes from 192.168.1.36: icmp_seq=69 ttl=64 time=3.445 ms

64 bytes from 192.168.1.36: icmp_seq=70 ttl=64 time=3.502 ms

64 bytes from 192.168.1.36: icmp_seq=71 ttl=64 time=3.726 ms

64 bytes from 192.168.1.36: icmp_seq=72 ttl=64 time=7.365 ms

64 bytes from 192.168.1.36: icmp_seq=73 ttl=64 time=3.346 ms

64 bytes from 192.168.1.36: icmp_seq=74 ttl=64 time=4.403 ms

64 bytes from 192.168.1.36: icmp_seq=75 ttl=64 time=3.635 ms

64 bytes from 192.168.1.36: icmp_seq=76 ttl=64 time=3.161 ms

64 bytes from 192.168.1.36: icmp_seq=77 ttl=64 time=8.185 ms

64 bytes from 192.168.1.36: icmp_seq=78 ttl=64 time=3.749 ms

64 bytes from 192.168.1.36: icmp_seq=79 ttl=64 time=3.838 ms

64 bytes from 192.168.1.36: icmp_seq=80 ttl=64 time=3.230 ms

64 bytes from 192.168.1.36: icmp_seq=81 ttl=64 time=4.209 ms

64 bytes from 192.168.1.36: icmp_seq=82 ttl=64 time=10.165 ms

@adammhaile Any insight on this? Can’t see why the Bridge wouldn’t show up in the device scan.

Could be a local network config thing… but honestly unsure. My advice would be to skip the scan, manually create a Ruida device and just choose Bridge as the connection option and manually input the IP address. And see if it still won’t connect.
The scan usually works, but it’s not infallible.

That did the trick. I deleted the existing device and started from scratch using the manual option. Looks like we’re in business. Thanks for the assist, gents.

2 Likes