I do not have SSH access via network.GTR2Fan wrote:kbordzan wrote:Is it possible to restart SSH somehow?... I think.Code: Select all
sudo service ssh restart
I guess I need to connect by cable.
But any idea why via WiFi SSH is not working?
I do not have SSH access via network.GTR2Fan wrote:kbordzan wrote:Is it possible to restart SSH somehow?... I think.Code: Select all
sudo service ssh restart
Code: Select all
source-directory /etc/network/interfaces.d
auto lo
iface lo inet loopback
iface eth0 inet manual
allow-hotplug wlan0
auto wlan0
iface wlan0 inet manual
wpa-roam /etc/wpa_supplicant/wpa_supplicant.conf
iface default inet manual
Code: Select all
ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev
update_config=1
network={
ssid="xxxxx"
psk="xxxxx"
proto=RSN
key_mgmt=WPA-PSK
pairwise=TKIP
auth_alg=OPEN
group=TKIP WEP104 WEP40
}
network={
ssid="xxxxx"
psk="xxxxx"
proto=RSN
key_mgmt=WPA-PSK
pairwise=CCMP
auth_alg=OPEN
}
network={
ssid="xxxxx"
psk="xxxxx"
proto=RSN
key_mgmt=WPA-PSK
pairwise=TKIP
auth_alg=OPEN
}
BRANCH=next should get you to 4.4.xaloodb wrote:sudo branch=next rpi-update ( this did nothing other than say I'm already on the latest version 4.1.8)
Check /etc/wpa_supplicant/wpa_supplicant.conf for 'country=GB'anyone got any more suggestions of what I can try ?
Code: Select all
country=GB
ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev
update_config=1
Code: Select all
iwconfig
Code: Select all
sudo iwconfig wlan0 power off
Code: Select all
sudo nano /etc/modprobe.d/8192cu.conf
Code: Select all
options 8192cu rtw_power_mgnt=0 rtw_enusbss=0 rtw_ips_mode=1
Code: Select all
sudo nano /etc/rc.local
Code: Select all
sleep 10
iwconfig wlan0 power off
Code: Select all
sudo nano /etc/systemd/system/root-resume.service
Code: Select all
[Unit]
Description=Turn of wlan power management
After=suspend.target
[Service]
Type=simple
ExecStartPre= /bin/sleep 10
ExecStart= /sbin/iwconfig wlan0 power off
[Install]
WantedBy=suspend.target
Code: Select all
sudo systemctl enable root-resume
Code: Select all
iwconfig
Just to reiterate what was said above, in case you missed the import:aloodb wrote:sudo branch=next rpi-update
Code: Select all
sudo BRANCH=next rpi-update
Code: Select all
[ 5056.502602] brcmfmac: brcmf_sdio_hdparse: seq 74: sequence number error, expect 70
[ 5056.502705] brcmfmac: brcmf_sdio_hdparse: seq 70: sequence number error, expect 75
[ 5056.504321] brcmfmac: brcmf_sdio_hdparse: seq 79: sequence number error, expect 75
Code: Select all
sudo iwconfig wlan0 power off
Thanks Rurwinrurwin wrote:Switch off power management. No it doesn't make sense, but it will probably work even so.
It's easy enough to try, just:If it does then there's instructions for making it permanent a few posts above.Code: Select all
sudo iwconfig wlan0 power off
Joshimuz wrote:I've have similar issues with the Pi3 wifi as manawyrm.
But I also have a problem whereby if the wireless connection is not being used for ~1 minute, it drops completely and I can no longer connect/ping the Pi at all, yet it still shows on my router's connection list.
I found that opening a SSH connection and using the top command is a good way to keep it connected, but obviously this isn't an ideal solution. There might be a better way but I'm not very familiar with Linux.
I'm a bit surprised. As a test I left an SSH session over wlan open all night and this morning it was still alive.mkarliner wrote:Yep, same here. Pi drops an ssh that doesn't have activity after a minute or so
Are you saying that problem can be used channel for WiFi, that SSH is not working?rurwin wrote:I was using SSH over WiFi last night, having finally got channel 13 working.
Although now you mention it, I did have to reboot it an extra time before it worked. I put that down to the protocols getting in a mess.
One thing I might have done between failing and succeeding is to unplug the Ethernet cable.
Code: Select all
wlan0 Link encap:Ethernet HWaddr b8:27:eb:70:84:01
inet addr:169.254.92.44 Bcast:169.254.255.255 Mask:255.255.0.0
inet6 addr: fe80::ba27:ebff:fe70:8401/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:11 errors:0 dropped:11 overruns:0 frame:0
TX packets:5800 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:4548 (4.4 KiB) TX bytes:1603408 (1.5 MiB)
Code: Select all
> wps_pbc
OK
<3>CTRL-EVENT-SCAN-RESULTS
<3>WPS-AP-AVAILABLE-PBC
<3>Trying to associate with xx:xx:xx:xx:xx:xx (SSID='Max2Play' freq=2412 MHz)
<3>Association request to the driver failed
<3>Authentication with xx:xx:xx:xx:xx:xx timed out.
<3>CTRL-EVENT-DISCONNECTED bssid=xx:xx:xx:xx:xx:xx reason=3 locally_generated=1
<3>CTRL-EVENT-SCAN-RESULTS
<3>WPS-AP-AVAILABLE-PBC
<3>CTRL-EVENT-SCAN-RESULTS
<3>WPS-AP-AVAILABLE-PBC
<3>Trying to associate with xx:xx:xx:xx:xx:xx (SSID='Max2play' freq=2412 MHz)
<3>Association request to the driver failed
<3>Authentication with xx:xx:xx:xx:xx:xx timed out.
<3>CTRL-EVENT-DISCONNECTED bssid=xx:xx:xx:xx:xx:xx reason=3 locally_generated=1
Code: Select all
> wps_pbc
OK
<3>CTRL-EVENT-DISCONNECTED bssid=xx:xx:xx:xx:xx:xx reason=3 locally_generated=1
<3>CTRL-EVENT-SCAN-RESULTS
<3>WPS-AP-AVAILABLE-PBC
<3>Trying to associate with xx:xx:xx:xx:xx:xx (SSID='Max2Play' freq=2412 MHz)
<3>Association request to the driver failed
<3>Associated with xx:xx:xx:xx:xx:xx
<3>CTRL-EVENT-EAP-STARTED EAP authentication started
<3>CTRL-EVENT-EAP-STATUS status='started' parameter=''
<3>CTRL-EVENT-EAP-PROPOSED-METHOD vendor=14122 method=1
<3>CTRL-EVENT-EAP-STATUS status='accept proposed method' parameter='WSC'
<3>CTRL-EVENT-EAP-METHOD EAP vendor 14122 method 1 (WSC) selected
<3>WPS-CRED-RECEIVED
<3>WPS-SUCCESS
Code: Select all
/etc/network/interfaces
Code: Select all
allow-hotplug wlan0
iface wlan0 inet manual
wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf
# deaktiviere power save modus fuer Raspberry Pi 3 on board wifi
post-up iwconfig wlan0 power off
Code: Select all
atom:~# traceroute -I 192.168.1.220
traceroute to 192.168.1.220 (192.168.1.220), 30 hops max, 60 byte packets
1 raspberry.local (192.168.1.220) 8.431 ms 8.717 ms 9.044 ms
atom:~# traceroute -T 192.168.1.220
traceroute to 192.168.1.220 (192.168.1.220), 30 hops max, 60 byte packets
1 raspberry.local (192.168.1.220) 7.371 ms 7.769 ms 7.756 ms
atom:~# traceroute -U 192.168.1.220
traceroute to 192.168.1.220 (192.168.1.220), 30 hops max, 60 byte packets
1 * * *
2 * * *
3 * * *
4 * * *
5 * * *
6 * * *
7 * * *