›

Rasp pi 3B successfull install, cant connect to wifi

mundimundi
in Repetier-Server
Hi!

Yesterday I got my repetier host (latest release) installed on SD card and fired it on rasp pi 3 B. On ehernet I see it on my lan all the-time and I can go to Wifi settings. In wifi setting I can see many wlans broadcasting in the are.
-I click on my wlan,
-type the password
-click connect
-tab changes back to Available wlan Router tab and blue message appears: "Unconnected"

I tried multiple working wifis, including my phone hotspot but problem is the same: "unconnected"
-I've tried saving wifi settings

It's a bit frustrating when I will not get a proper error message. Just Unconnected.

I got the system working yesterday for a while but had to shut it down for night. Today I canät get it working at all.

Comments

  • mundimundi
    Got it working again. Tried solutions from https://forum.repetier.com/discussion/comment/27417/#Comment_27417
    I unplugged ethernet and power. Plugged power and there it was on lan and working.
    Unplugged the power again to move it 2meters to printers and now I cannot get it working again (disconnected printers, cam and all other devices).
  • mundimundi
    So I went very wild and commented all the "nmcli connection delete" lines. I'm ecpecting that now I can never change the wifi while it will not delete old connection. It reallt doesnt bother me but will there be other problems?

    I will report later how stable it is.
  • mundimundi
    Disconnected today after day of printing and connected rasp server again and it will not get back to wifi. So problem presists.
  • RepetierRepetier
    Which image/version are you using?

    Also read our faq especially how to set up a file with fixed data, then that is always used to define wifi connection.

    eventually also read /var/log/syslog to see what linux tries when connecting and why it undoes the connection.
  • mundimundi
    Repetier said:
    Which image/version are you using?

    Also read our faq especially how to set up a file with fixed data, then that is always used to define wifi connection.

    eventually also read /var/log/syslog to see what linux tries when connecting and why it undoes the connection.
    Repetier-Server-Image_0_92_0_v15.img

    I did not find your FAQ about setting up files for wifi connection. https://www.repetier-server.com/knowledgebase/
    I tought I can set up wifi on the panel, which I succeeded of doing. I think I'm not getting something here?

    I started to look at the log files and in the first start of today wifi did not work, moved it closer to the router and it started working with wifi. So I tried to replicate the problem and succeeded. Now in the panel (with eth0) is says "No WLAN adapter installed".

    Could you tell me what am I looking for in logs. Somehow the logfiles are not in order. Timestamps. Some in the beginning of syslog are from today and some in the end are today. Inbetween there are logs from yesterday.

    Aug  1 17:17:06 Repetier-Server NetworkManager[314]: <info>  [1564669026.1721] device (wlan0): driver supports Access Point (AP) mode
Aug  1 17:17:06 Repetier-Server NetworkManager[314]: <info>  [1564669026.1749] manager: (wlan0): new 802.11 WiFi device (/org/freedesktop/NetworkManager/Devices/3)
Aug  1 17:17:06 Repetier-Server NetworkManager[314]: <info>  [1564669026.1797] device (wlan0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Aug  1 17:17:06 Repetier-Server kernel: [    9.215329] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Aug  1 17:17:06 Repetier-Server kernel: [    9.740463] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Aug  1 17:17:06 Repetier-Server kernel: [    9.740495] brcmfmac: power management disabled
Aug  1 17:17:06 Repetier-Server NetworkManager[314]: <info>  [1564669026.7048] device (wlan0): set-hw-addr: set MAC address to FA:02:30:91:95:69 (scanning)
Aug  1 17:17:06 Repetier-Server NetworkManager[314]: <info>  [1564669026.7762] modem-manager: ModemManager available
Aug  1 17:17:06 Repetier-Server NetworkManager[314]: <info>  [1564669026.8079] supplicant: wpa_supplicant running
Aug  1 17:17:06 Repetier-Server NetworkManager[314]: <info>  [1564669026.8084] device (wlan0): supplicant interface state: init -> starting
Aug  1 17:17:06 Repetier-Server kernel: [    9.858721] random: crng init done
Aug  1 17:17:06 Repetier-Server kernel: [    9.858729] random: 7 urandom warning(s) missed due to ratelimiting
Aug  1 17:17:06 Repetier-Server dhcpcd[275]: eth0: waiting for carrier
Aug  1 17:17:06 Repetier-Server dhcpcd[275]: wlan0: waiting for carrier
Aug  1 17:17:06 Repetier-Server dhcpcd[275]: wlan0: carrier acquired
Aug  1 17:17:06 Repetier-Server dhcpcd[275]: DUID 00:01:00:01:24:cb:24:e3:b8:27:eb:67:14:80
Aug  1 17:17:06 Repetier-Server dhcpcd[275]: wlan0: IAID eb:34:78:ca
Aug  1 17:17:06 Repetier-Server dhcpcd[275]: wlan0: adding address fe80::b839:e6ba:ea8a:5460
Aug  1 17:17:06 Repetier-Server avahi-daemon[321]: Joining mDNS multicast group on interface wlan0.IPv6 with address fe80::b839:e6ba:ea8a:5460.
Aug  1 17:17:06 Repetier-Server avahi-daemon[321]: New relevant interface wlan0.IPv6 for mDNS.
Aug  1 17:17:06 Repetier-Server avahi-daemon[321]: Registering new address record for fe80::b839:e6ba:ea8a:5460 on wlan0.*.
Aug  1 17:17:06 Repetier-Server dhcpcd[275]: wlan0: carrier lost
Aug  1 17:17:07 Repetier-Server wpa_supplicant[312]: ctrl_iface exists and seems to be in use - cannot override it
Aug  1 17:17:07 Repetier-Server wpa_supplicant[312]: Delete '/run/wpa_supplicant/wlan0' manually if it is not used anymore
Aug  1 17:17:07 Repetier-Server wpa_supplicant[312]: Failed to initialize control interface '/run/wpa_supplicant'.#012You may have another wpa_supplicant process already running or the file was#012left by an unclean termination of wpa_supplicant in which case you will need#012to manually remove this file before starting wpa_supplicant again.
Aug  1 17:17:07 Repetier-Server dhcpcd[275]: wlan0: deleting address fe80::b839:e6ba:ea8a:5460
Aug  1 17:17:07 Repetier-Server avahi-daemon[321]: Withdrawing address record for fe80::b839:e6ba:ea8a:5460 on wlan0.
Aug  1 17:17:07 Repetier-Server avahi-daemon[321]: Leaving mDNS multicast group on interface wlan0.IPv6 with address fe80::b839:e6ba:ea8a:5460.
Aug  1 17:17:07 Repetier-Server avahi-daemon[321]: Interface wlan0.IPv6 no longer relevant for mDNS.
Aug  1 17:17:07 Repetier-Server dhcpcd[275]: wlan0: new hardware address: fa:02:30:91:95:69
Aug  1 17:17:07 Repetier-Server wpa_supplicant[312]: nl80211: deinit ifname=wlan0 disabled_11b_rates=0
Aug  1 17:17:07 Repetier-Server NetworkManager[314]: <error> [1564669027.1893] sup-iface[0x103cdd8,wlan0]: error adding interface: wpa_supplicant couldn't grab this interface.
Aug  1 17:17:07 Repetier-Server NetworkManager[314]: <info>  [1564669027.1894] device (wlan0): supplicant interface state: starting -> down
Aug  1 17:17:08 Repetier-Server ModemManager[271]: <info>  Couldn't check support for device '/sys/devices/platform/soc/3f300000.mmcnr/mmc_host/mmc1/mmc1:0001/mmc1:0001:1': not supported by any plugin
Aug  1 17:17:08 Repetier-Server ModemManager[271]: <info>  Couldn't check support for device '/sys/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.1': not supported by any plugin
Aug  1 17:17:08 Repetier-Server systemd[1]: systemd-rfkill.service: Succeeded.
Aug  1 17:17:12 Repetier-Server NetworkManager[314]: <info>  [1564669032.1559] manager: startup complete
Aug  1 17:17:12 Repetier-Server systemd[1]: Started Network Manager Wait Online.
Aug  1 17:17:15 Repetier-Server systemd[1]: NetworkManager-dispatcher.service: Succeeded.
Aug  1 17:17:16 Repetier-Server NetworkManager[314]: <warn>  [1564669036.9690] device (wlan0): re-acquiring supplicant interface (#1).
Aug  1 17:17:17 Repetier-Server wpa_supplicant[312]: ctrl_iface exists and seems to be in use - cannot override it
Aug  1 17:17:17 Repetier-Server wpa_supplicant[312]: Delete '/run/wpa_supplicant/wlan0' manually if it is not used anymore
Aug  1 17:17:17 Repetier-Server wpa_supplicant[312]: Failed to initialize control interface '/run/wpa_supplicant'.#012You may have another wpa_supplicant process already running or the file was#012left by an unclean termination of wpa_supplicant in which case you will need#012to manually remove this file before starting wpa_supplicant again.
Aug  1 17:17:17 Repetier-Server wpa_supplicant[312]: nl80211: deinit ifname=wlan0 disabled_11b_rates=0
Aug  1 17:17:17 Repetier-Server NetworkManager[314]: <error> [1564669037.2299] sup-iface[0x103ca40,wlan0]: error adding interface: wpa_supplicant couldn't grab this interface.
Aug  1 17:17:17 Repetier-Server NetworkManager[314]: <info>  [1564669037.2301] device (wlan0): supplicant interface state: starting -> down
Aug  1 17:17:27 Repetier-Server NetworkManager[314]: <warn>  [1564669047.9794] device (wlan0): re-acquiring supplicant interface (#2).
Aug  1 17:17:28 Repetier-Server wpa_supplicant[312]: ctrl_iface exists and seems to be in use - cannot override it
Aug  1 17:17:28 Repetier-Server wpa_supplicant[312]: Delete '/run/wpa_supplicant/wlan0' manually if it is not used anymore
Aug  1 17:17:28 Repetier-Server wpa_supplicant[312]: Failed to initialize control interface '/run/wpa_supplicant'.#012You may have another wpa_supplicant process already running or the file was#012left by an unclean termination of wpa_supplicant in which case you will need#012to manually remove this file before starting wpa_supplicant again.
Aug  1 17:17:28 Repetier-Server wpa_supplicant[312]: nl80211: deinit ifname=wlan0 disabled_11b_rates=0
Aug  1 17:17:28 Repetier-Server NetworkManager[314]: <error> [1564669048.2399] sup-iface[0x103cb20,wlan0]: error adding interface: wpa_supplicant couldn't grab this interface.
Aug  1 17:17:28 Repetier-Server NetworkManager[314]: <info>  [1564669048.2401] device (wlan0): supplicant interface state: starting -> down
Aug  1 17:17:33 Repetier-Server systemd[1]: systemd-fsckd.service: Succeeded.
Aug  1 17:17:33 Repetier-Server btuart[280]: Initialization timed out.

    Thanks for your help.
  • ch_vladimirch_vladimir
    Hi
    same problem after update. had to install the old version
  • sindrejlsindrejl
    yep, the 0.92 has a fault with wlan, I tried it now. The wlan adapter is gone from the first menu and it wont connect to anything.
    Innstaller 0.91.2 and all is ok again
  • RepetierRepetier
    @sindrejl did you switch images or just server version? Reason I ask is that new image is based on Raspbian buster while older are not. So maybe something in handling has changed or if you just changed server and not os it must be inside server also it only calls a script to connect.
  • mwkmwk
    I need to downgrade to 91.2. How can I get that image for the raspberry pi? I deleted the file and can’t find it
  • RepetierRepetier
    Either just install 0.91.2 server on the new image or change image download link to version 14 with server version 91 2. it is still on the download server just not linked,
  • cosmith71cosmith71
    Repetier said:
    Which image/version are you using?

    Also read our faq especially how to set up a file with fixed data, then that is always used to define wifi connection.

    eventually also read /var/log/syslog to see what linux tries when connecting and why it undoes the connection.

  • cosmith71cosmith71
    I'm having similar issues.  And the MAC address seems to change?
  • doclabandoclaban
    edited August 2019
    I got the same problem. Running 0.92 on a fresh installation.
    The mac address for wlan changes on every reboot.
  • roseybrownroseybrown
    The installation process has been discussed here very nicely. After reading your information I get proper guidance. I am an Epson user and I get useful ideas from Fix Epson Printer Error 0xf1 page. You may get the most useful ideas here.
  • amigolokoamigoloko
    Same here, not yet able to connect to WiFi, I cannot get to ssh since no ip/connection is established. 
    tried V15, V16, (if manually update from server (web interface v.91 to v.92 there seems to be no issues with WiFi) but fresh burned image to sd of v15 or v16 to a RPi B3+ not working :(
  • SvenSven
    Same Problem. 
  • RepetierRepetier
    Seems like wifi is blocked by default. While testing the issue it started working after I send
    sudo rfkill unblock wifi

    Please if you test first run
    sudo rfkill list
    and post it here to confirm that it was blocked before so we know that this is what is causing the wifi to not work as expected. Also
    sudo nmcli dev
    listed wlan0 as unavailable before I unblocked wifi. Hope that also works you.
  • SvenSven
    send:  sudo rfkill

    0 wlan phy0  unblocked  unblocked

    send: sudo nmcli dev

    eth0   connected
    wlan0  unavailable

    No WLan

  • RepetierRepetier
    Did you also test if 
    sudo rfkill unblock wifi
    changed anything especially sudo nmcli dev should go to disconnected or connected afterwards.
  • RAyWBRAyWB
    Repetier said:
    Did you also test if 
    sudo rfkill unblock wifi
    changed anything especially sudo nmcli dev should go to disconnected or connected afterwards.
    same problem here, sudo rfkill unblock wifi didn´t change anything wlan0 still unanvailable (i use V16 on Pi 3B)
  • mwkmwk
    Didn’t work for me. Still no WiFi
  • RepetierRepetier
    Yep. But I think I have found the reason. Looks like dhcpcd is starting and blocking usage of it. Modifying /etc/hdcpcd.conf to ignore wlan0 interface and rebooting made it work in my tests. Will do some more tests and publish it soon. The line is
    denyinterfaces wlan0
    you need to add. Also have set NetworkManager.conf property managed to true but not sure if that is necessary. Anyhow in my tests so far it seems to work now.
  • chofmannchofmann
    edited August 2019
    The changing MAC address seems to be caused by the "network-manager".
    I have removed the "network-manager" and now the MAC address is the real one and is fixed
    sudo apt-get remove network-manager
    sudo reboot
    I have also found a way how the WLAN connection works in the newest (buster) distribution (Repeter-Server V16 Image):
    Use 'raspi-config' to set the WLAN network SSID and password.
    (This information is written into the file /etc/wpa_suppicant/wpa_supplicant.conf) 
    At next boot the WLAN connection is established automatically and I can access Repeter-Server without any problems.

    Note: This is a workaround that works for me, no final solution ;-)
    Setting WLAN parameters (e.g. password) via Repeter-Server GUI still does not work, so don't try with Image V16.
  • RepetierRepetier
    @chofmann
    Thanks for the NetworkManager hint. Was already wondering who is responsible for changes. After some research it seems that the default behaviour changed with newer NetworkManager version. /etc/NetworkManager.conf with

    [main]

    plugins=ifupdown,keyfile


    [ifupdown]

    managed=true


    [device]

    wifi.scan-rand-mac-address=no


    [connection]

    wifi.cloned-mac-address=permanent

    ethernet.cloned-mac-address=permanent


    Seems to solve the problem giving a stable mac address back. AT least it survived reboot and several restarts of NetworkManager without changing the mac after it changed to the permanent mac.


    So I hope I'm now close to get wifi back stable in buster.

  • RAyWBRAyWB
    may be this also helps

    scroll to (3)

  • amigolokoamigoloko
    edited August 2019
    V.17 working WiFi, thanks Repetier Team (also usb is working :D)

    as soon as first time on, the AP menu for region will not load, just switch languages, and it loads correctly, then you can choose the Region, for it to let you to accept clients, or connect to a WiFi network
Sign In or Register to comment.