Hacking How to use drc-sim?

  • Thread starter Thread starter AboodXD
  • Start date Start date
  • Views Views 50,049
  • Replies Replies 98
  • Likes Likes 4
You mean something like this: https://bitbucket.org/memahaxx/drc-cap
That is still very different from having drc-sim (which is a Gamepad simulator) and a real Gamepad connected at the same time and somehow shareing all of the traffic between them.

No I don't mean a sniffer.

You put one or more devices (pc, raspberry pi ...) between console and gamepad.

The console and the gamepad are not talking directly to each other.
The device in the middle is controling the dataflow.

You basically send every ethernet package witch is send to port 50120,50121 and 50123 directly to the gamepad or the console.

Packages on Port 50122 (input data) have to be recreated by the Linux or Windows system.

The pros of this approach is that you do not need a kernel patch, because the timestamps for the video signal are created on the gamepad or console (I don't know where exactly).
So you may implement this on a windows PC (EAPHost can do this maybe).

Another pro is that you can use the gamepad with this method in vWii mode.
Basically the device in the middle takes the input data and emulates a vWii compatible controler,
video and audio streaming already works in vWii mode thanks to Nintendo.

The cons of this approach is that the latency increases.
 
Actually, somebody did write a patcher that hacks support into windows (and probably breaks all other wifi, much like the wpa_supplicant patch does). See here: https://bitbucket.org/memahaxx/wudrnet. Note that I haven't tried this, there is almost no documentation, and the odds of FUBARing your windows install are pretty high. Somebody could also create a new wireless device driver from scratch, but that project would be VERY difficult and time consuming. I'm currently working on a version of wpa_supplicant that works with both normal and drc wifi (ideally without the user having to distinguish the two), which would be awesome as it would actually allow any device using wpa_supplicant (including any android device) to connect to the Wii U without ruining its normal wifi capabilities. Right now I'm using a raspberry pi as my testing platform. If I make any progress, I'll let everybody here know.
 
Yes I did, did you test it?
Try things before you open your mouth dude. >_>
I don't need to test it. I'm just looking at the sequence of events:
  1. your drm-sim fork was updated to indicate that it has been modified to work with 3.4 on June 5: https://github.com/aboood40091/drc-sim/commit/74fc471e5c5b4205a8141f3d150128d1e402ada2
  2. you create this thread not knowing how to use the application, later on June 5.
  3. you start adding support for python 3.4 on June 9: https://github.com/aboood40091/drc-sim/commit/9100bb3bd925379f68964b38d22baf47609b9b5a
So, I found it to be amusing that you claimed to make it work with python 3.4 before creating this thread, but you actually hadn't yet made it work with python 3.4. I then said, which I still find to be an accurate summary:
The best part of this thread is how he made it "work with python 3.4" before creating this thread, but didn't.

I am glad that you did eventually add support for python 3.4, though.
 
I don't need to test it. I'm just looking at the sequence of events:
  1. your drm-sim fork was updated to indicate that it has been modified to work with 3.4 on June 5: https://github.com/aboood40091/drc-sim/commit/74fc471e5c5b4205a8141f3d150128d1e402ada2
  2. you create this thread not knowing how to use the application, later on June 5.
  3. you start adding support for python 3.4 on June 9: https://github.com/aboood40091/drc-sim/commit/9100bb3bd925379f68964b38d22baf47609b9b5a
So, I found it to be amusing that you claimed to make it work with python 3.4 before creating this thread
Wait, what?! I didn't claim that I added Python3 support before making this thread!
 
Wait, what?! I didn't claim that I added Python3 support before making this thread!
Actually, you did by saying
It was modified by AboodXD to work with Python 3.4
in this commit, while the actual python support was added in this commit which was well after you created this thread. Look at the time stamps if you don't believe.
 
So is there any progress so far? And even if not may I ask if someone could make a page for this in the tutorials section so this doesn't fall into obscurity again. (also a slight bump so people who got a WiiU for Christmas w/o a gamepad can have some help with the setup)
 
Sorry for the bump, but I am trying to build this in a Kali Linux VM, and I keep getting this error:
Code:
root@kali:~/drc/drc-mac80211# make -C /usr/src/linux-headers-4.3.0-kali1-amd64 M=/home/drc/drc-mac80211/
make: Entering directory '/usr/src/linux-headers-4.3.0-kali1-amd64'
/usr/src/linux-headers-4.3.0-kali1-common/scripts/Makefile.build:44: /home/drc/drc-mac80211//Makefile: No such file or directory
make[3]: *** No rule to make target '/home/drc/drc-mac80211//Makefile'.  Stop.
/usr/src/linux-headers-4.3.0-kali1-common/Makefile:1395: recipe for target '_module_/home/drc/drc-mac80211/' failed
make[2]: *** [_module_/home/drc/drc-mac80211/] Error 2
Makefile:146: recipe for target 'sub-make' failed
make[1]: *** [sub-make] Error 2
Makefile:8: recipe for target 'all' failed
make: *** [all] Error 2
make: Leaving directory '/usr/src/linux-headers-4.3.0-kali1-amd64'
I hope that I can get this working. I bought the exact TP-LINK model from this tutorial just because I want to use drc-sim.
 
Last edited by I pwned U!,
  • Like
Reactions: The Cringe
Sorry for the bump, but I am trying to build this in a Kali Linux VM, and I keep getting this error:
Code:
root@kali:~/drc/drc-mac80211# make -C /usr/src/linux-headers-4.3.0-kali1-amd64 M=/home/drc/drc-mac80211/
make: Entering directory '/usr/src/linux-headers-4.3.0-kali1-amd64'
/usr/src/linux-headers-4.3.0-kali1-common/scripts/Makefile.build:44: /home/drc/drc-mac80211//Makefile: No such file or directory
make[3]: *** No rule to make target '/home/drc/drc-mac80211//Makefile'.  Stop.
/usr/src/linux-headers-4.3.0-kali1-common/Makefile:1395: recipe for target '_module_/home/drc/drc-mac80211/' failed
make[2]: *** [_module_/home/drc/drc-mac80211/] Error 2
Makefile:146: recipe for target 'sub-make' failed
make[1]: *** [sub-make] Error 2
Makefile:8: recipe for target 'all' failed
make: *** [all] Error 2
make: Leaving directory '/usr/src/linux-headers-4.3.0-kali1-amd64'
I hope that I can get this working. I bought the exact TP-LINK model from this tutorial just because I want to use drc-sim.
Obviously, the problem is that the folder/file you want doesn't exist, aka wrong directory, change:
Code:
make -C /usr/src/linux-headers-4.3.0-kali1-amd64 M=/home/drc/drc-mac80211/
to:
Code:
make -C /usr/src/linux-headers-4.3.0-kali1-amd64 M=/home/YourUsernameHere!!/drc/drc-mac80211/
 
Last edited by AboodXD,
Obviously, the problem is that the folder/file you want doesn't exist, aka wrong directory, change:
Code:
make -C /usr/src/linux-headers-4.3.0-kali1-amd64 M=/home/drc/drc-mac80211/
to:
Code:
make -C /usr/src/linux-headers-4.3.0-kali1-amd64 M=/home/YourUsernameHere!!/drc/drc-mac80211/
After adding the username folder for the VM, I now get this error:
Code:
make -C /usr/src/linux-headers-4.3.0-kali1-amd64 M=/home/root/drc/drc-mac80211/
make: Entering directory '/usr/src/linux-headers-4.3.0-kali1-amd64'
arch/x86/Makefile:148: CONFIG_X86_X32 enabled but no binutils support
/usr/src/linux-headers-4.3.0-kali1-common/Makefile:663: Cannot use CONFIG_CC_STACKPROTECTOR_STRONG: -fstack-protector-strong not supported by compiler
/usr/src/linux-headers-4.3.0-kali1-common/scripts/Makefile.build:44: /home/root/drc/drc-mac80211//Makefile: No such file or directory
make[3]: *** No rule to make target '/home/root/drc/drc-mac80211//Makefile'.  Stop.
/usr/src/linux-headers-4.3.0-kali1-common/Makefile:1395: recipe for target '_module_/home/root/drc/drc-mac80211/' failed
make[2]: *** [_module_/home/root/drc/drc-mac80211/] Error 2
Makefile:146: recipe for target 'sub-make' failed
make[1]: *** [sub-make] Error 2
Makefile:8: recipe for target 'all' failed
make: *** [all] Error 2
make: Leaving directory '/usr/src/linux-headers-4.3.0-kali1-amd64'

I also tried it with network manager turned off, and got this error:
Code:
make -C /usr/src/linux-headers-4.3.0-kali1-amd64 M=/home/root/drc/drc-mac80211/
make: Entering directory '/usr/src/linux-headers-4.3.0-kali1-amd64'
/usr/src/linux-headers-4.3.0-kali1-common/scripts/Makefile.build:44: /home/root/drc/drc-mac80211//Makefile: No such file or directory
make[3]: *** No rule to make target '/home/root/drc/drc-mac80211//Makefile'.  Stop.
/usr/src/linux-headers-4.3.0-kali1-common/Makefile:1395: recipe for target '_module_/home/root/drc/drc-mac80211/' failed
make[2]: *** [_module_/home/root/drc/drc-mac80211/] Error 2
Makefile:146: recipe for target 'sub-make' failed
make[1]: *** [sub-make] Error 2
Makefile:8: recipe for target 'all' failed
make: *** [all] Error 2
make: Leaving directory '/usr/src/linux-headers-4.3.0-kali1-amd64'
 
  • Like
Reactions: The Cringe
A USB Wi-Fi adapter passed through to a VM would probably work just fine, from what I see.

Just tossing that out there.
 
After adding the username folder for the VM, I now get this error:
Code:
make -C /usr/src/linux-headers-4.3.0-kali1-amd64 M=/home/root/drc/drc-mac80211/
make: Entering directory '/usr/src/linux-headers-4.3.0-kali1-amd64'
arch/x86/Makefile:148: CONFIG_X86_X32 enabled but no binutils support
/usr/src/linux-headers-4.3.0-kali1-common/Makefile:663: Cannot use CONFIG_CC_STACKPROTECTOR_STRONG: -fstack-protector-strong not supported by compiler
/usr/src/linux-headers-4.3.0-kali1-common/scripts/Makefile.build:44: /home/root/drc/drc-mac80211//Makefile: No such file or directory
make[3]: *** No rule to make target '/home/root/drc/drc-mac80211//Makefile'.  Stop.
/usr/src/linux-headers-4.3.0-kali1-common/Makefile:1395: recipe for target '_module_/home/root/drc/drc-mac80211/' failed
make[2]: *** [_module_/home/root/drc/drc-mac80211/] Error 2
Makefile:146: recipe for target 'sub-make' failed
make[1]: *** [sub-make] Error 2
Makefile:8: recipe for target 'all' failed
make: *** [all] Error 2
make: Leaving directory '/usr/src/linux-headers-4.3.0-kali1-amd64'

I also tried it with network manager turned off, and got this error:
Code:
make -C /usr/src/linux-headers-4.3.0-kali1-amd64 M=/home/root/drc/drc-mac80211/
make: Entering directory '/usr/src/linux-headers-4.3.0-kali1-amd64'
/usr/src/linux-headers-4.3.0-kali1-common/scripts/Makefile.build:44: /home/root/drc/drc-mac80211//Makefile: No such file or directory
make[3]: *** No rule to make target '/home/root/drc/drc-mac80211//Makefile'.  Stop.
/usr/src/linux-headers-4.3.0-kali1-common/Makefile:1395: recipe for target '_module_/home/root/drc/drc-mac80211/' failed
make[2]: *** [_module_/home/root/drc/drc-mac80211/] Error 2
Makefile:146: recipe for target 'sub-make' failed
make[1]: *** [sub-make] Error 2
Makefile:8: recipe for target 'all' failed
make: *** [all] Error 2
make: Leaving directory '/usr/src/linux-headers-4.3.0-kali1-amd64'
So... I gues you would go to the drc-mac80211/ folder and manually put the Makefile and the other files there.

Also, a screenshot of your drc/ folder and what is inside of it would be fine. :)
 
Last edited by AboodXD,
So... I gues you would go to the drc-mac80211/ folder and manually put the Makefile and the other files there.

Also, a screenshot of your drc/ folder and what is inside of it would be fine. :)
Except that they are already there:
drcsim.PNG
 
  • Like
Reactions: The Cringe
Does anyone have any suggestions on how to fix this? I really want to make good use of the adapter that I bought just for this...
After adding the username folder for the VM, I now get this error:
Code:
make -C /usr/src/linux-headers-4.3.0-kali1-amd64 M=/home/root/drc/drc-mac80211/
make: Entering directory '/usr/src/linux-headers-4.3.0-kali1-amd64'
arch/x86/Makefile:148: CONFIG_X86_X32 enabled but no binutils support
/usr/src/linux-headers-4.3.0-kali1-common/Makefile:663: Cannot use CONFIG_CC_STACKPROTECTOR_STRONG: -fstack-protector-strong not supported by compiler
/usr/src/linux-headers-4.3.0-kali1-common/scripts/Makefile.build:44: /home/root/drc/drc-mac80211//Makefile: No such file or directory
make[3]: *** No rule to make target '/home/root/drc/drc-mac80211//Makefile'.  Stop.
/usr/src/linux-headers-4.3.0-kali1-common/Makefile:1395: recipe for target '_module_/home/root/drc/drc-mac80211/' failed
make[2]: *** [_module_/home/root/drc/drc-mac80211/] Error 2
Makefile:146: recipe for target 'sub-make' failed
make[1]: *** [sub-make] Error 2
Makefile:8: recipe for target 'all' failed
make: *** [all] Error 2
make: Leaving directory '/usr/src/linux-headers-4.3.0-kali1-amd64'

I also tried it with network manager turned off, and got this error:
Code:
make -C /usr/src/linux-headers-4.3.0-kali1-amd64 M=/home/root/drc/drc-mac80211/
make: Entering directory '/usr/src/linux-headers-4.3.0-kali1-amd64'
/usr/src/linux-headers-4.3.0-kali1-common/scripts/Makefile.build:44: /home/root/drc/drc-mac80211//Makefile: No such file or directory
make[3]: *** No rule to make target '/home/root/drc/drc-mac80211//Makefile'.  Stop.
/usr/src/linux-headers-4.3.0-kali1-common/Makefile:1395: recipe for target '_module_/home/root/drc/drc-mac80211/' failed
make[2]: *** [_module_/home/root/drc/drc-mac80211/] Error 2
Makefile:146: recipe for target 'sub-make' failed
make[1]: *** [sub-make] Error 2
Makefile:8: recipe for target 'all' failed
make: *** [all] Error 2
make: Leaving directory '/usr/src/linux-headers-4.3.0-kali1-amd64'
Except that they are already there:
 
  • Like
Reactions: The Cringe

Site & Scene News

Popular threads in this forum