Home of the Squeezebox™ & Transporter® network music players.
Page 1 of 3 123 LastLast
Results 1 to 10 of 28
  1. #1
    Member
    Join Date
    Apr 2019
    Location
    Wunstorf, Germany
    Posts
    30

    piCorePlayer 4 sometimes is not starting WIFI connection?

    Hello!

    I have a Raspberry Pi 3B+ with piCorePlayer and I enabled the WIFI connection (LAN is not connected and not available at the place).
    Most of the time the connection is working without any problems but sometimes I am getting this:

    Name:  IMG_9616.jpg
Views: 306
Size:  218.2 KB

    What can I do to let the connection always be working?

    Thank you!

  2. #2
    Senior Member paul-'s Avatar
    Join Date
    Jan 2013
    Posts
    1,850
    You are not getting a DHCP address from your home router/server. Does your router have any indications as to why? Try rebooting your router.
    piCorePlayer a small player for the Raspberry Pi in RAM.
    Homepage: https://www.picoreplayer.org

    Please donate if you like the piCorePlayer

  3. #3
    Senior Member Greg Erskine's Avatar
    Join Date
    Sep 2006
    Location
    Sydney, Australia
    Posts
    1,668
    hi carsten_h,

    When you do connect, you need to run [Diagnostics] on the [Wifi Settings] page.

    Check signal quality and level. Also look at the ping tests, they should be a few ms and reasonably consistent and 0% packet loss.

    Have you noticed when it does connect how long it takes. Does it approach 52 (26 seconds) like when it fails?

    regards
    Greg

  4. #4
    Member
    Join Date
    Apr 2019
    Location
    Wunstorf, Germany
    Posts
    30
    Quote Originally Posted by paul- View Post
    You are not getting a DHCP address from your home router/server.
    Every other device is getting an IP address via DHCP. And normally it is working for this Raspberry also without any problem. I have also a Pi zero W with Raspbian and this is getting an IP Address every time.
    There is no message in the error log of the router.
    Last edited by carsten_h; 2019-05-20 at 21:14.

  5. #5
    Member
    Join Date
    Apr 2019
    Location
    Wunstorf, Germany
    Posts
    30
    Quote Originally Posted by Greg Erskine View Post
    When you do connect, you need to run [Diagnostics] on the [Wifi Settings] page.
    Ok, I will do! Yesterday it didn't connect a single time.

    Quote Originally Posted by Greg Erskine View Post
    Check signal quality and level. Also look at the ping tests, they should be a few ms and reasonably consistent and 0% packet loss.
    Ok!

    Quote Originally Posted by Greg Erskine View Post
    Have you noticed when it does connect how long it takes. Does it approach 52 (26 seconds) like when it fails?
    Normally I see the connect at the third message of "udhcpc: sending discover". I don't know how long this takes.

    Today in the morning it had worked, but I don't had the time to take a look at the Diagnostics. I will do it this evening.
    Here is the output from today:

    Name:  IMG_9617.jpg
Views: 133
Size:  226.2 KB
    Last edited by carsten_h; 2019-05-20 at 21:16.

  6. #6
    Member
    Join Date
    Apr 2019
    Location
    Wunstorf, Germany
    Posts
    30
    Here are the diagnose outputs (I deleted the networks that are not belonging to me, I am using the first one):

    Code:
    wlan0     Scan completed :
              Cell 02 - Address: 5C:49:79:4F:A8:D8
                        Channel:11
                        Frequency:2.462 GHz (Channel 11)
                        Quality=59/70  Signal level=-51 dBm  
                        Encryption key:on
                        ESSID:"BleibWeg!"
                        Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
                                  9 Mb/s; 12 Mb/s; 18 Mb/s
                        Bit Rates:24 Mb/s; 36 Mb/s; 48 Mb/s; 54 Mb/s
                        Mode:Master
                        Extra:tsf=0000000000000000
                        Extra: Last beacon: 70ms ago
                        IE: Unknown: 0009426C65696257656721
                        IE: Unknown: 010882848B968C129824
                        IE: Unknown: 03010B
                        IE: Unknown: 050400010080
                        IE: Unknown: 0706444520010D14
                        IE: Unknown: 2A0100
                        IE: Unknown: 3204B048606C
                        IE: Unknown: 460573D000000C
                        IE: Unknown: 2D1AAD011BFFFFFF00000000000000000001000000000406E6470D00
                        IE: Unknown: 3D160B080400000000000000000000000000000000000000
                        IE: Unknown: 4A0E14000A002C01C800140005001900
                        IE: Unknown: 7F0805000F0000000040
                        IE: Unknown: DD180050F2020101000003A4000027A4000042435E0062322F00
                        IE: Unknown: DD0900037F01010000FF7F
                        IE: Unknown: DD088CFDF00101020100
                        IE: Unknown: DD168CFDF004000049000003020972010000000039000000
                        IE: Unknown: DD0C00040E010102010000000000
                        IE: Unknown: DD1D0050F204104A0001101044000102103C0001031049000600372A000120
                        IE: IEEE 802.11i/WPA2 Version 1
                            Group Cipher : CCMP
                            Pairwise Ciphers (1) : CCMP
                            Authentication Suites (1) : PSK
              Cell 07 - Address: 5C:49:79:4F:A8:D9
                        Channel:60
                        Frequency:5.3 GHz (Channel 60)
                        Quality=34/70  Signal level=-76 dBm  
                        Encryption key:on
                        ESSID:"Marvin"
                        Bit Rates:6 Mb/s; 9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s
                                  36 Mb/s; 48 Mb/s; 54 Mb/s
                        Mode:Master
                        Extra:tsf=0000000000000000
                        Extra: Last beacon: 70ms ago
                        IE: Unknown: 00064D617276696E
                        IE: Unknown: 01088C129824B048606C
                        IE: Unknown: 03013C
                        IE: Unknown: 050400010000
                        IE: Unknown: 073C4445202401172801172C01173001173401173801173C011740011764011E68011E6C011E70011E74011E78011E7C011E80011E84011E88011E8C011E
                        IE: Unknown: 200103
                        IE: Unknown: 460573D000000C
                        IE: Unknown: 2D1AEF091BFFFFFF0000000000000000000100000000000000000000
                        IE: Unknown: 3D163C050400000000000000000000000000000000000000
                        IE: Unknown: 7F0804000F0000000040
                        IE: Unknown: BF0CB2018033EAFF0000EAFF0000
                        IE: Unknown: C005013A00FCFF
                        IE: Unknown: C304022E2E2E
                        IE: Unknown: DD180050F2020101000003A4000027A4000042435E0062322F00
                        IE: Unknown: DD0900037F01010000FF7F
                        IE: Unknown: DD088CFDF00101020100
                        IE: Unknown: DD168CFDF004000049000003020972018C1600003C000000
                        IE: Unknown: DD0C00040E010102010000000000
                        IE: Unknown: DD1D0050F204104A0001101044000102103C0001031049000600372A000120
                        IE: IEEE 802.11i/WPA2 Version 1
                            Group Cipher : CCMP
                            Pairwise Ciphers (1) : CCMP
                            Authentication Suites (1) : PSK
    Code:
    PING 192.168.178.107 (192.168.178.107): 56 data bytes
    64 bytes from 192.168.178.107: seq=0 ttl=64 time=0.134 ms
    64 bytes from 192.168.178.107: seq=1 ttl=64 time=0.124 ms
    64 bytes from 192.168.178.107: seq=2 ttl=64 time=0.113 ms
    64 bytes from 192.168.178.107: seq=3 ttl=64 time=0.109 ms
    64 bytes from 192.168.178.107: seq=4 ttl=64 time=0.107 ms
    64 bytes from 192.168.178.107: seq=5 ttl=64 time=0.111 ms
    64 bytes from 192.168.178.107: seq=6 ttl=64 time=0.112 ms
    64 bytes from 192.168.178.107: seq=7 ttl=64 time=0.112 ms
    64 bytes from 192.168.178.107: seq=8 ttl=64 time=0.103 ms
    64 bytes from 192.168.178.107: seq=9 ttl=64 time=0.115 ms
    64 bytes from 192.168.178.107: seq=10 ttl=64 time=0.105 ms
    64 bytes from 192.168.178.107: seq=11 ttl=64 time=0.109 ms
    64 bytes from 192.168.178.107: seq=12 ttl=64 time=0.110 ms
    64 bytes from 192.168.178.107: seq=13 ttl=64 time=0.113 ms
    64 bytes from 192.168.178.107: seq=14 ttl=64 time=0.107 ms
    64 bytes from 192.168.178.107: seq=15 ttl=64 time=0.104 ms
    64 bytes from 192.168.178.107: seq=16 ttl=64 time=0.113 ms
    64 bytes from 192.168.178.107: seq=17 ttl=64 time=0.117 ms
    64 bytes from 192.168.178.107: seq=18 ttl=64 time=0.122 ms
    64 bytes from 192.168.178.107: seq=19 ttl=64 time=0.129 ms
    
    --- 192.168.178.107 ping statistics ---
    20 packets transmitted, 20 packets received, 0% packet loss
    round-trip min/avg/max = 0.103/0.113/0.134 ms
    Isn't it possible to use a fixed IP with WIFI?

  7. #7
    Senior Member Greg Erskine's Avatar
    Join Date
    Sep 2006
    Location
    Sydney, Australia
    Posts
    1,668
    Looks OK to me.

    How far away is pCP from the router?

    I'd be inclined to try a USB wifi adaptor to see if its more reliable.

  8. #8
    Member
    Join Date
    Apr 2019
    Location
    Wunstorf, Germany
    Posts
    30
    It is 5m away from a Mesh-repeater, so I switched first yesterday to 5GHz to see if it makes any difference. The connection is good, I hope that DHCP is working there.

    Thank you for the help so far!

  9. #9
    Senior Member paul-'s Avatar
    Join Date
    Jan 2013
    Posts
    1,850
    I've heard of problems with Mesh systems. Most residential routers have very poor logging, but it would be nice to know if it is even trying to setup a WPA handshake.
    piCorePlayer a small player for the Raspberry Pi in RAM.
    Homepage: https://www.picoreplayer.org

    Please donate if you like the piCorePlayer

  10. #10
    Member
    Join Date
    Apr 2019
    Location
    Wunstorf, Germany
    Posts
    30
    Quote Originally Posted by paul- View Post
    if it is even trying to setup a WPA handshake.
    I will look into the log of the main router (AVM) and the repeater (also AVM) the next time the problem appears and will post it here.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •