No SSH connection via WiFi

@Sandbird, it is all getting a little confusing, isn’t it? :slightly_smiling: As I understand it (@apsikus, please correct me if I’m wrong):

His PC is on 104.

His OSMC box was on 105, and is now on 110.

The default router (his DSL router) is on 1.

What concerns me is the “Host docelowy jest nieosiągalny” (destination host unreachable). That suggests there may be a problem with the PC IP configuration (not the OSMC box).

@apsikus (and sorry here if I’m treading on any OSMC support toes by chipping in here), I would suggest you try the following:

Your DSL router will almost certainly have some diagnostics, at the very least the ability to “ping”. Try that - see whether your router can ping your OSMC box.
Then, on the PC, open a command window ([Start], [Run], “cmd.exe” or [Windows]R “cmd.exe”) and type:
ipconfig -all
then
route print
and paste the results in here please.

@apsikus after you do the ipconfig /all thingy…download this: Download Advanced_IP_Scanner_2.5.3850.exe Free - Advanced IP Scanner 2.5.3850 install file

and run it in portable version…then do a full scan and post a screeshot of the results.
I bet that pi is under 192.168.0.110 waiting be connected.

And
.1.2 is your PC or your router, or?

My PC. My router is under .1.1 and i got a static ip on all computers (including the pi) in the house.
I’ve set up my DHCP on the router to start from 192.168.1.10 and all my devices are under that range…so if a friend comes to house and joins the wifi he’ll get an ip above 192.168.1.10 and it wont affect my other devices.
For example my pc is 192.168.1.2 the pi is 192.168.1.3 and so on.

Hi,

I will try my best to answer all you requests and sugestions.
ipconfig /all from laptop

[code]Microsoft Windows [Wersja 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. Wszelkie prawa zastrzeżone.

C:\Windows\system32>ipconfig /all

Windows IP Configuration

Host name . . . . . . . . . . . : G500
Primary Dns Sufix. . . . . . . :
Node type . . . . . . . . . . . : Hybrid
IP routing enabled. . . . . . . : No
WINS Proxy enabled . . … . . . : No

Ethernet adapter Wireless Network Conection:

Connection-specific DNS suffix :
Description. . . . . . . . . . . . . . . : Karta sieciowa Broadcom 802.11n
Physical address. . . . . . . . . . : B8-76-3F-A3-38-59
DHCP enabled . . . . . . . . . . : Yes
Autoconfiguration enabled . . . . : Yes
Link-local IPv6 address . : fe80::392b:1382:943e:7520%14(Preferred)

IPv4 address. . . . . . . . . . . . . : 192.168.0.104(Preferred)
Subnet mask. . . . . . . . . . : 255.255.255.0
Lease obtained. . . . . . . . : 6 marca 2016 09:25:41
Lease expires. . . . . . . . . : 19 stycznia 2038 04:14:07
Default gateway. . . . . . . . . . : 192.168.0.1
DHCP servers . . . . . . . . . . . : 192.168.0.1
DHCPv6 IAID . . . . : 364410431
DHCPv6 Client DUID : 00-01-00-01-1E-59-CA-59-20-89-84-DF-73-00

DNS servers . . . . . . . . . . . : 8.8.8.8
8.8.4.4
NetBIOS over Tcpip . . . . . . . : Enabled
[/code]
Route print

[code]C:\Users\Kris_2>route print

Interface list
14…b8 76 3f a3 38 59 …Karta sieciowa Broadcom 802.11n
12…b8 76 3f a3 38 5a …Urządzenie Bluetooth (sieć osobista)
11…20 89 84 df 73 00 …Qualcomm Atheros AR8172/8176/8178 PCI-E Fast Ether
net Controller (NDIS 6.20)
1…Software Loopback Interface 1
15…00 00 00 00 00 00 00 e0 Karta Microsoft ISATAP

IPv4 route table

active routes:
Network destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.0.1 192.168.0.104 25
127.0.0.0 255.0.0.0 On-link 127.0.0.1 306
127.0.0.1 255.255.255.255 On-link 127.0.0.1 306
127.255.255.255 255.255.255.255 On-link 127.0.0.1 306
192.168.0.0 255.255.255.0 On-link 192.168.0.104 281
192.168.0.104 255.255.255.255 On-link 192.168.0.104 281
192.168.0.255 255.255.255.255 On-link 192.168.0.104 281
224.0.0.0 240.0.0.0 On-link 127.0.0.1 306
224.0.0.0 240.0.0.0 On-link 192.168.0.104 281
255.255.255.255 255.255.255.255 On-link 127.0.0.1 306
255.255.255.255 255.255.255.255 On-link 192.168.0.104 281

Persisten routes:
None

IPv6 route table

Active routes:
If Metric Network destination gateway
1 306 ::1/128 On-link
14 281 fe80::/64 On-link
14 281 fe80::392b:1382:943e:7520/128
On-link
1 306 ff00::/8 On-link
14 281 ff00::/8 On-link

Persisten routes:
None
[/code]

grab-logs -A
Logs successfully uploaded
Logs available at http://paste.osmc.io/qicobitoka

ifconfig

[code]lo link encap: local loopback
inet addr 127.0.0.1 mask 255.0.0.0
inet6 addr ::1/128 scope host
up loopback running mtu 65536 metric 1
rx packets 54991 errors 0 dropped 0 overrruns 0 frame 0
tx packets 54991 errors 0 dropped 0 overruns 0 carriers 0
collisions 0 txqueuelen 0
rx bytes 5329211 (5.0 mib) tx bytes 5329211 (5.0 mib)

wlan0 link encap Ethernet hwaddr f4:f2:6d:0f:43:d3
inet addr 192.168.0.110 bcast 192.168.0.255 mask 255.255.255.0
up braodcast running multicats dynamic mtu 1500 metric 1
rx packets 1253 errors 0 dropped 18347 overruns 0 frame 0
tx packets 2879 errors 0 dropped 1840 overruns 0 carrier 0
collisions 0 txqueuelen 1000
rx bytes 18931239 (18.0 mib) tx bytes 15787004 (15.0 mib)[/code]

Why commans lsusb is not working in OSMC?
How to list USB devices?

sudo apt-get install usbutils

@apsikus ok try these things:

  1. It might be your power supply…How much power does it give ? 1Amp ? 2 Amps? Are you using a wall socket or a powered USB to power up the pi ? You might not have enough ‘juice’ to power up the wifi stick.

  2. Choose a different password on your wifi router…Something simple for starters without weird symbols.

  3. Try a different encryption (wep, wpa2…) and see if it connects then. Try WPA-Personal (PSK) instead. WPA2 isnt so compatible with every device.

  4. Skip the wifi and try with cable. Disable the wifi on osmc settings and put a static ip on the wired

    IP address: 192.168.0.111
    Subnet mask: 255.255.255.0
    Default gateway: 192.168.0.1

Then run the ipscan program again from your pc, and see if it can find it…or just try to putty to 192.168.0.111

IF it connects with the wired then definitely its either your pi doesnt have enough power to power up the wifi properly, or the wifi stick/router cant communicate properly with the encryption/passwords/TKIP/AES protocols you have set…try simpler and go up from there.

Well I don’t thin that his wifi has any problem to communicate

rx bytes 18931239 (18.0 mib) tx bytes 15787004 (15.0 mib)

I really would like to see some communication (ping) being tried from OSMC to the router .1 and PC .104

I just read thru the logfile and there are a couple of undefined disconnects. So maybe as @Sandbird said it could be a power issue.
Suggest to add max_usb_current=1 to /boot/config.txt and ensure that your powersupply is strong enough

Hi,

But, don’t you think that problem can be rather with driver for dongle instead of power adapter?

Maybe I’m stupid, but according to your suggestion there can be not enough power for WiFi dongle. In that case how it will get enough power for wired connection?

Well I have not said that it couldn’t be a driver problem. But the question is if it is easier for you to troubleshoot a power supply or a Linux Kernel Driver?
And the power usage of the Ethernet adapter is different from an wifi adapter :wink:

OK. Understood.

Regarding RPi forum, if there is under-voltage issue, color (rainbow) square is displayed on the screen in right up corner.

Is this feature available in OSMC? If yes, when and how should I check for this square?
Edit: According to this topic it should be above clock on main screen of KODI - [solved] Flashing squares on the screen
I will check in details by changing screen resolution to make sure that it’s not there.

I heave read how to create own driver. Looks easier then investigate if power supply is powerful enough for RPi and WiFi adapter :stuck_out_tongue:

Well despite having or not having the rainbow square you still should add max_usb_current=1 to /boot/config.txt to ensure the device get proper power

Will do then :slightly_smiling:
Can you provide command to edit file config.txt?

You can do this easily from the MyOSMC pi config module in the GUI.

max_usb_current=1 is the command. But either do it from the osmc config panel or power down your pi and edit the config.txt via a card reader. Yesterday i edited my config.txt via winscp while the pi was running and i bricked my sd card…

There is no relation with your card dying and access the /boot partition during operation of OSCM.

2 Likes

The same thing happened on the p1, running openelec, long time ago. Maybe its the winscp program i dont know…but from now on i will not be doing this :slight_smile:

We’ve never seen a report of such an issue. Of you can consistently repeat the issue, then it might be worth investigating.

2 Likes

I have executed command max_usb_current=1 and nothing has happend on the screen.
As I understand it should be added to config.txt file, but how to edit file in Linux?

RPi rebooted. Still not available via SSH or via ping.

I am not able to ping from one laptop to another, so it must be some kind network issue.