search

rolandoislas / drc-sim

Wii U Gamepad Simulator Backend
Other
165 stars 31 forks source link

Drc Sim Server - Cannot connect error after sync with Wii U #37

Open geopapai opened 7 years ago

geopapai commented 7 years ago

Hi, great work, you got me to set up a linux system once again... ;-) My steps: Setup a Virtualbox Ubuntu 14.04, with a Ralink 801.11n 5ghz usb I installed via the Easy Install script (got an error for puthon3-pip, installed it manually first, then script went through ). Managed to connect to the Wii U (get key) after 1-2 tries/restarts BUT When trying to start the server I get the following error:

virtualbox_ubu14_05_07_2017_18_01_15

Tried reinstalling wpa_supplicant_src etc, checked log - see pic, seems ok?

What am I missing?

Rgds, George

rolandoislas commented 7 years ago

The issue appears to be the Ralink driver. See rolandoislas/drc-hostap#1.

Unfortunately, the last status on that front was pairing attempts completing, but the normal connection failing. I am interested in seeing what driver the adapter is using.

geopapai commented 7 years ago

Thanks for the quick reply. Linux newbie here, so bear with me. I am trying to see what driver I'm using. In the meantime this is the cards capabilities

osboxes@osboxes:~$ iwlist frequency wlan0 29 channels in total; available frequencies : Channel 01 : 2.412 GHz Channel 02 : 2.417 GHz Channel 03 : 2.422 GHz Channel 04 : 2.427 GHz Channel 05 : 2.432 GHz Channel 06 : 2.437 GHz Channel 07 : 2.442 GHz Channel 08 : 2.447 GHz Channel 09 : 2.452 GHz Channel 10 : 2.457 GHz Channel 11 : 2.462 GHz Channel 12 : 2.467 GHz Channel 13 : 2.472 GHz Channel 14 : 2.484 GHz Channel 36 : 5.18 GHz Channel 38 : 5.19 GHz Channel 40 : 5.2 GHz Channel 42 : 5.21 GHz Channel 44 : 5.22 GHz Channel 46 : 5.23 GHz Channel 48 : 5.24 GHz Channel 149 : 5.745 GHz Channel 151 : 5.755 GHz Channel 153 : 5.765 GHz Channel 155 : 5.775 GHz Channel 157 : 5.785 GHz Channel 159 : 5.795 GHz Channel 161 : 5.805 GHz Channel 165 : 5.825 GHz lo no frequency information.

eth0 no frequency information.

osboxes@osboxes:~$ iw list Wiphy phy1 Band 1: Capabilities: 0x2f2 HT20/HT40 Static SM Power Save RX Greenfield RX HT20 SGI RX HT40 SGI TX STBC RX STBC 2-streams Max AMSDU length: 3839 bytes No DSSS/CCK HT40 Maximum RX AMPDU length 65535 bytes (exponent: 0x003) Minimum RX AMPDU time spacing: 2 usec (0x04) HT RX MCS rate indexes supported: 0-15, 32 TX unequal modulation not supported HT TX Max spatial streams: 2 HT TX MCS rate indexes supported may differ Frequencies:

geopapai commented 7 years ago

my connect_to_wii_u.conf

ctrl_interface=/var/run/wpa_supplicant_drc update_config=1 ap_scan=1

network={ scan_ssid=1 bssid=18:2a:7b:7f:e2:43 ssid="WiiU182a7b7fe243" psk=6ad35978f57770ca6feb13b424c1e800d93b5f7233b241ac1e1d82641d9fe09d proto=RSN key_mgmt=WPA-PSK pairwise=CCMP GCMP group=CCMP GCMP TKIP auth_alg=OPEN pbss=2 }

geopapai commented 7 years ago

Think I got it ...

root@osboxes:~/.drc-sim# sudo lshw -C network -network
description: Ethernet interface product: 82540EM Gigabit Ethernet Controller vendor: Intel Corporation physical id: 3 bus info: pci@0000:00:03.0 logical name: eth0 version: 02 serial: 08:00:27:71:d8:ff size: 1Gbit/s capacity: 1Gbit/s width: 32 bits clock: 66MHz capabilities: pm pcix bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=e1000 driverversion=7.3.21-k8-NAPI duplex=full ip=10.0.2.15 latency=64 link=yes mingnt=255 multicast=yes port=twisted pair speed=1Gbit/s resources: irq:10 memory:f0000000-f001ffff ioport:d010(size=8) -network DISABLED description: Wireless interface physical id: 1 bus info: usb@1:1 logical name: wlan0 serial: bc:30:7d:d5:2f:83 capabilities: ethernet physical wireless configuration: broadcast=yes drive**r=rt2800usb driverversion=4.4.0-31**-generic firmware=N/A link=no multicast=yes wireless=IEEE 802.11abg

geopapai commented 7 years ago

OK last post. So my usb card chipset is Ralink RT3592. This is supported by driver rt2800usb. Probably my driver version is OK. (more info here http://rt2x00.serialmonkey.com/pipermail/users_rt2x00.serialmonkey.com/2011-April/003562.html)

Rolando, your time is precious so, is there a point trying to config this Ralink usb wifi, or should I just find another stick to try connecting to my WiiU?

Do you believe my installation apart from this is OK?

10000000 thanks!

rolandoislas commented 7 years ago

I misread and linked to a Realtek driver thread earlier. It is unrelated.

The results from iwlist do indicate that the card will not be able to perform an active scan, and will not be able to scan and connect to the Wii U's normal access point. If possible, attempt to view the wpa_supplicant log when DRC Sim Server is running in verbose mode.

Also, try a manual scan and check to see if the Wii U's BSSID appears.

sudo ifconfig <interface> up
sudo iw <interface> scan
sudi ifconfig <interface> down
geopapai commented 7 years ago

What do you mean by "Wii U's normal access point"?

If you look at my connect_to_wii_u.conf above isn't this ssid="WiiU182a7b7fe243" the "correct" WiiU?

I think that when I initially setup my Ralink usb, I scanned and verified that I saw the wiiU. But I can try it again and post back.

I remind you that I did get the key and got connected to my WiiU. The program hang when I tried to start the server.

Now that I think of it, was I supposed to get a Region to input at the server settings? Cause I only had NA and None - I think I tried both during my efforts to connect

rolandoislas commented 7 years ago

The Wii U has two access point states. The pairing mode, which allows authentication via WPS (wifi protected setup) and the normal mode that functions as a regular access point (AP). This issue that some adapters have is going into AP mode for the connection attempt from WPA Supplicant (the wifi connection backend). Given the driver in use, it is either a lack of hardware capabilities (the likely scenario) or a restriction placed by the regulatory domain.

geopapai commented 7 years ago

Thanks. I am currently at work and cannot give you accurate feedback on the system, but as I understand - given the fact that I get the wii keys - there is something wrong with the hardware compatibility from that point and on...

If you have no other suggestions / ideas, my best choice is try another usb wifi stick..., right?

rolandoislas commented 7 years ago

Unfortunately, another USB adapter seems to be needed. See the wiki for a small list of tested devices.

geopapai commented 7 years ago

Thanks, I will try with another adapter.

In the meantime, could you please tell me -in detail, me being a newbie- how to manually reinstall wpa_supplicant, or test that it's correctly installed, just to be on the safe side... Much obliged!

rolandoislas commented 7 years ago

The libdrc documentation gives some overview to the connection process. Wpa_supplicant(_drc) is compiled at installation time if the install script is used. Compile instructions are available, however.

The following commands will assume wpa_supplicant_drc is in your path (e.g. /usr/local/bin/).

Another option before ruling out the adapter entirely is to change the ap_scan=1 mode to 2 in connect_to_wii_u.conf and attempting another connection.

rolandoislas commented 7 years ago

A log in verbose mode might better explain the reason wpa_supplicant is failing to start.

DrHacknik commented 6 years ago

Using this inside of VirtualBox would cause issues; because Virtual Drivers. On the other hand, I purchased the Panda N600 that is recommended in the Wiki. It works perfectly, both with DRC and Normal use. It's a great investment; and is only $15 or so.

Using a built in Wireless Card is like playing a game of chance. It may or may not work, and might not be worth the time to get it working.