SSBU peer detection not working on OpenWRT-18.06

[Driphter]

I'm not having any luck getting the script to work. Half the time I run it, I get disconnected from my SSH/SCP sessions. The other half the time when the status screen show up, it never detects any peers when I play people online.

Is there any sort of debug/error log file or mode that I can use to help diagnose the problem? It's hard to figure out what's going on when the source is obfuscated.

[42Kmi]

Hello,

First and foremost, thank you for showing interest in using LagDrop. I've been working on this for so long and it's nice to see people curious about it. From my testing on OpenWRT and DD-WRT, I've seen that it does work. I know the instructions included are brief, but I am working on making a more detailed document. Could you share some detail about your set up? -Did you set your Switch to a Static IP? If using a wired connection, use should use the Ethernet adapter's IP and MAC address when setting the Static IP.

-Did you check the 42Kmi directory for your options.txt file? You can add your console's [Ethernet adapter] IP address there manually. It autofills if there is already a Static IP set.

-When running, if you have set your static IP, for example, if you named your Switch "Driphter_Switch" and run "./lagdrop.sh switch" LagDrop will find the first instance of Switch among the names in the Static IP list and grab that IP as the one to use when initiating the options_Driphter_Switch.txt file.

After reading your message I push an updated LagDrop and included a non-obfuscated lagdrop.sh to the repository. Hope that helps.

Also, could you link me to any screenshots of your terminal as you run lagdrop?

Again, thanks for checking out LagDrop.

On Thu, May 9, 2019 at 11:50 PM Driphter notifications@github.com wrote:

I'm not having any luck getting the script to work. Half the time I run it, I get disconnected from my SSH/SCP sessions. The other half the time when the status screen show up, it never detects any peers when I play people online.

Is there any sort of debug/error log file or mode that I can use to help diagnose the problem? It's hard to figure out what's going on when the source is obfuscated.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/42Kmi/LagDrop/issues/5, or mute the thread https://github.com/notifications/unsubscribe-auth/AEYWUGMUE6B4M5JNMF2U6UDPUTWJDANCNFSM4HL7UO3A .

[42Kmi]

I found those bugs and corrected them. Hopefully it should run without closing your terminal. Please update and check

On Fri, May 10, 2019, 12:59 AM Torengo torengo@42kmi.com wrote:

Hello,

First and foremost, thank you for showing interest in using LagDrop. I've been working on this for so long and it's nice to see people curious about it. From my testing on OpenWRT and DD-WRT, I've seen that it does work. I know the instructions included are brief, but I am working on making a more detailed document. Could you share some detail about your set up? -Did you set your Switch to a Static IP? If using a wired connection, use should use the Ethernet adapter's IP and MAC address when setting the Static IP.

-Did you check the 42Kmi directory for your options.txt file? You can add your console's [Ethernet adapter] IP address there manually. It autofills if there is already a Static IP set.

-When running, if you have set your static IP, for example, if you named your Switch "Driphter_Switch" and run "./lagdrop.sh switch" LagDrop will find the first instance of Switch among the names in the Static IP list and grab that IP as the one to use when initiating the options_Driphter_Switch.txt file.

After reading your message I push an updated LagDrop and included a non-obfuscated lagdrop.sh to the repository. Hope that helps.

Also, could you link me to any screenshots of your terminal as you run lagdrop?

Again, thanks for checking out LagDrop.

On Thu, May 9, 2019 at 11:50 PM Driphter notifications@github.com wrote:

I'm not having any luck getting the script to work. Half the time I run it, I get disconnected from my SSH/SCP sessions. The other half the time when the status screen show up, it never detects any peers when I play people online.

Is there any sort of debug/error log file or mode that I can use to help diagnose the problem? It's hard to figure out what's going on when the source is obfuscated.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/42Kmi/LagDrop/issues/5, or mute the thread https://github.com/notifications/unsubscribe-auth/AEYWUGMUE6B4M5JNMF2U6UDPUTWJDANCNFSM4HL7UO3A .

[Driphter]

I'm already using a static IP, but I'll test out the update and report back, thanks!

[Driphter]

The disconnection is definitely gone, but it's still not picking up peers. The only thing it's doing differently is detecting 192.xx.xx.1 which I assume is my gateway of 192.168.1.1.

[42Kmi]

So I JUST pushed another update to the repository. It corrects one of the bugs you encountered (initially meant to prevent multiple instances of lagdrop.sh from running, fixed so it won't terminate the terminal), then I fixed some more I encountered. Also, make sure you have openssl-util installed for OpenWRT. I hardreset my OpenWRT router to run through the LagDrop setup again. Not having openssl-util installed will cause LagDrop to misbehave (no reading peers). Make a huge difference.

On Fri, May 10, 2019 at 7:18 PM Driphter notifications@github.com wrote:

The disconnection is definitely gone, but it's still not picking up peers. The only thing it's doing differently is detecting 192.xx.xx.1 which I assume is my gateway of 192.168.1.1.

[image: Screenshot] https://user-images.githubusercontent.com/196429/57561185-4c8aec80-7358-11e9-91cd-8daaf6259c7e.PNG

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/42Kmi/LagDrop/issues/5#issuecomment-491455331, or mute the thread https://github.com/notifications/unsubscribe-auth/AEYWUGOO4NZMR2AA3RVWQY3PUX7D5ANCNFSM4HL7UO3A .

[Driphter]

Yep, openssl-util is installed. I tried updating the script again, but I'm still only seeing 192.xx.xx.1 like in the screenshot above.

[42Kmi]

Could you share a pic of your options.txt, the static IP assigned to your Switch on the router's web interface, and the Switch's IP address on the Internet setting page on the Switch?

Is there a 42Kmi/cache folder with files in it? Do you see the filterignore, pingmem and geomem files?

On Sat, May 11, 2019 at 1:13 AM Driphter notifications@github.com wrote:

Yep, openssl-util is installed. I tried updating the script again, but I'm still only seeing 192.xx.xx.1 like in the screenshot above.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/42Kmi/LagDrop/issues/5#issuecomment-491480400, or mute the thread https://github.com/notifications/unsubscribe-auth/AEYWUGMTOHZG63SSNPUMYQLPUZIWLANCNFSM4HL7UO3A .

[42Kmi]

Make sure you have curl installed. If that doesn't solve it, try installing libcurl.

On Sat, May 11, 2019 at 3:02 AM Torengo torengo@42kmi.com wrote:

Could you share a pic of your options.txt, the static IP assigned to your Switch on the router's web interface, and the Switch's IP address on the Internet setting page on the Switch?

Is there a 42Kmi/cache folder with files in it? Do you see the filterignore, pingmem and geomem files?

On Sat, May 11, 2019 at 1:13 AM Driphter notifications@github.com wrote:

Yep, openssl-util is installed. I tried updating the script again, but I'm still only seeing 192.xx.xx.1 like in the screenshot above.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/42Kmi/LagDrop/issues/5#issuecomment-491480400, or mute the thread https://github.com/notifications/unsubscribe-auth/AEYWUGMTOHZG63SSNPUMYQLPUZIWLANCNFSM4HL7UO3A .

[Driphter]

No luck after installing curl.

[42Kmi]

Go get the latest lagdrop update. Delete the cache folder. Install curl and libcurl. Then try again. I also added a stay awake for OpenWRT, which basically pings and curls example.com every 5 seconds.

After installing curl and libcurl on my OpenWRT router I stopped seeing the Taipei results for all IPs. Maybe that had to do with curl not being on the system, so it just defaulted to Taipei? Weird.

Walk me through what you have set up. What kind of router? Is lagdrop.sh installed on the router? Is the Switch directly connected to the same router?

Another option to try is to make a "debug" options.txt. Run "lagdrop.sh debug -s -l" It's just like running lagdrop the same as any other time, but the will load the non-filter that's used for PC, etc, which doesn't omit console-specific servers from being tested against LagDrop. Go to the options_debug.txt and add your Switch's IP address. Hopefully you'll see something.

You can also do the debug thing with your phone or PC or whatever. Browser the internet a bit. Hopefully you will see the montior populate.

Also, could you send a pic of all available commands in your terminal? Press tab twice.

As far as I can tell, I'm not seeing anything on my end, but if I can compare your available commands against my own I may be able to see what may be missing.

In the meantime, you can try running without location. That may still work, but it will remove the location-enabled features.

Thanks again. I hope to get this working for you because it's really impressive when it works.

On Sat, May 11, 2019 at 2:53 PM Driphter notifications@github.com wrote:

No luck after installing curl.

[image: options txt] https://user-images.githubusercontent.com/196429/57573713-24ec6080-73fa-11e9-9783-6c7c8c1a54aa.png

[image: dhcp-lease] https://user-images.githubusercontent.com/196429/57573773-7812e300-73fb-11e9-870b-b31a04e95098.PNG

[image: dhcp-static] https://user-images.githubusercontent.com/196429/57573774-7a753d00-73fb-11e9-9b6a-713d764e4f3a.PNG

[image: switch-settings] https://user-images.githubusercontent.com/196429/57573791-b8726100-73fb-11e9-833f-c83bf3bddd3b.jpg

[image: switch-status] https://user-images.githubusercontent.com/196429/57573792-bc9e7e80-73fb-11e9-96a8-e6f8b46ce93e.jpg

[image: root-42kmi] https://user-images.githubusercontent.com/196429/57573828-7eee2580-73fc-11e9-9256-f458715bcb96.PNG

[image: root-42kmi-cache] https://user-images.githubusercontent.com/196429/57573829-81e91600-73fc-11e9-8f64-6b07ecbc26aa.PNG

[image: cahe-files] https://user-images.githubusercontent.com/196429/57573830-86adca00-73fc-11e9-9a50-ec22a5e09235.PNG

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/42Kmi/LagDrop/issues/5#issuecomment-491535557, or mute the thread https://github.com/notifications/unsubscribe-auth/AEYWUGKWX3GYCX6EQDZU2C3PU4I3JANCNFSM4HL7UO3A .

[42Kmi]

You can try flushing your iptables with "iptables -F"

On Sat, May 11, 2019 at 3:36 PM Torengo torengo@42kmi.com wrote:

Go get the latest lagdrop update. Delete the cache folder. Install curl and libcurl. Then try again. I also added a stay awake for OpenWRT, which basically pings and curls example.com every 5 seconds.

After installing curl and libcurl on my OpenWRT router I stopped seeing the Taipei results for all IPs. Maybe that had to do with curl not being on the system, so it just defaulted to Taipei? Weird.

Walk me through what you have set up. What kind of router? Is lagdrop.sh installed on the router? Is the Switch directly connected to the same router?

Another option to try is to make a "debug" options.txt. Run "lagdrop.sh debug -s -l" It's just like running lagdrop the same as any other time, but the will load the non-filter that's used for PC, etc, which doesn't omit console-specific servers from being tested against LagDrop. Go to the options_debug.txt and add your Switch's IP address. Hopefully you'll see something.

You can also do the debug thing with your phone or PC or whatever. Browser the internet a bit. Hopefully you will see the montior populate.

Also, could you send a pic of all available commands in your terminal? Press tab twice.

As far as I can tell, I'm not seeing anything on my end, but if I can compare your available commands against my own I may be able to see what may be missing.

In the meantime, you can try running without location. That may still work, but it will remove the location-enabled features.

Thanks again. I hope to get this working for you because it's really impressive when it works.

On Sat, May 11, 2019 at 2:53 PM Driphter notifications@github.com wrote:

No luck after installing curl.

[image: options txt] https://user-images.githubusercontent.com/196429/57573713-24ec6080-73fa-11e9-9783-6c7c8c1a54aa.png

[image: dhcp-lease] https://user-images.githubusercontent.com/196429/57573773-7812e300-73fb-11e9-870b-b31a04e95098.PNG

[image: dhcp-static] https://user-images.githubusercontent.com/196429/57573774-7a753d00-73fb-11e9-9b6a-713d764e4f3a.PNG

[image: switch-settings] https://user-images.githubusercontent.com/196429/57573791-b8726100-73fb-11e9-833f-c83bf3bddd3b.jpg

[image: switch-status] https://user-images.githubusercontent.com/196429/57573792-bc9e7e80-73fb-11e9-96a8-e6f8b46ce93e.jpg

[image: root-42kmi] https://user-images.githubusercontent.com/196429/57573828-7eee2580-73fc-11e9-9256-f458715bcb96.PNG

[image: root-42kmi-cache] https://user-images.githubusercontent.com/196429/57573829-81e91600-73fc-11e9-8f64-6b07ecbc26aa.PNG

[image: cahe-files] https://user-images.githubusercontent.com/196429/57573830-86adca00-73fc-11e9-9a50-ec22a5e09235.PNG

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/42Kmi/LagDrop/issues/5#issuecomment-491535557, or mute the thread https://github.com/notifications/unsubscribe-auth/AEYWUGKWX3GYCX6EQDZU2C3PU4I3JANCNFSM4HL7UO3A .

[Driphter]

I have a Linksys WRT1900AC v1 with a fresh install of OpenWRT 18.06. I've updated all of the packages. lagdrop.sh is installed in /root/. My Switch is connected directly to the router via an Ethernet adapter.

I just tried setting it up with the "debug" options and didn't have any luck. Every now and then a random IP will show up, but nothing that was unique per game. Tried it with my computer's IP and my phone's IP and nothing came up. Maybe the IP filter is too strict? No luck removing the -l flag.

Here's the commands we're working with:

Thanks for the help, I really appreciate it!

[42Kmi]

Please check the /proc/net/ directory. Do you see nf_conntrack or ip_conntrack?

On Sat, May 11, 2019 at 7:20 PM Driphter notifications@github.com wrote:

I have a Linksys WRT1900AC v1 with a fresh install of OpenWRT 18.06. I've updated all of the packages. lagdrop.sh is installed in /root/. My Switch is connected directly to the router via an Ethernet adapter.

I just tried setting it up with the "debug" options and didn't have any luck. Every now and then a random IP will show up, but nothing that was unique per game. Tried it with my computer's IP and my phone's IP and nothing came up. Maybe the IP filter is too strict? No luck removing the -l flag.

Here's the commands we're working with: [image: commands] https://user-images.githubusercontent.com/196429/57575775-2e3bf400-741f-11e9-96c7-40d0901b632a.PNG

Thanks for the help, I really appreciate it!

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/42Kmi/LagDrop/issues/5#issuecomment-491551117, or mute the thread https://github.com/notifications/unsubscribe-auth/AEYWUGPGHH5OZDHQ22DSOALPU5IB7ANCNFSM4HL7UO3A .

[42Kmi]

I pushed another update. Hopefully it fixes LagDrop for you. If that doesn't work, do you want to try it on DD-WRT? I'm running OpenWrt 18.06.2 r7676-cddd7b4c77 on a NETGEAR R6100 and am not having any issues. IP's are logging and disappearing on my OpenWRT. Some stay for a bit then disappear, which is normal since LagDrop does clear IPs that are no longer connected to the router. I have my OpenWRT LagDrop listening to the router.

On Sat, May 11, 2019 at 8:53 PM Torengo torengo@42kmi.com wrote:

Please check the /proc/net/ directory. Do you see nf_conntrack or ip_conntrack?

On Sat, May 11, 2019 at 7:20 PM Driphter notifications@github.com wrote:

I have a Linksys WRT1900AC v1 with a fresh install of OpenWRT 18.06. I've updated all of the packages. lagdrop.sh is installed in /root/. My Switch is connected directly to the router via an Ethernet adapter.

I just tried setting it up with the "debug" options and didn't have any luck. Every now and then a random IP will show up, but nothing that was unique per game. Tried it with my computer's IP and my phone's IP and nothing came up. Maybe the IP filter is too strict? No luck removing the -l flag.

Here's the commands we're working with: [image: commands] https://user-images.githubusercontent.com/196429/57575775-2e3bf400-741f-11e9-96c7-40d0901b632a.PNG

Thanks for the help, I really appreciate it!

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/42Kmi/LagDrop/issues/5#issuecomment-491551117, or mute the thread https://github.com/notifications/unsubscribe-auth/AEYWUGPGHH5OZDHQ22DSOALPU5IB7ANCNFSM4HL7UO3A .

[42Kmi]

It may be fixed now. Please check.

On Sat, May 11, 2019 at 10:55 PM Torengo torengo@42kmi.com wrote:

I pushed another update. Hopefully it fixes LagDrop for you. If that doesn't work, do you want to try it on DD-WRT? I'm running OpenWrt 18.06.2 r7676-cddd7b4c77 on a NETGEAR R6100 and am not having any issues. IP's are logging and disappearing on my OpenWRT. Some stay for a bit then disappear, which is normal since LagDrop does clear IPs that are no longer connected to the router. I have my OpenWRT LagDrop listening to the router.

On Sat, May 11, 2019 at 8:53 PM Torengo torengo@42kmi.com wrote:

Please check the /proc/net/ directory. Do you see nf_conntrack or ip_conntrack?

On Sat, May 11, 2019 at 7:20 PM Driphter notifications@github.com wrote:

I have a Linksys WRT1900AC v1 with a fresh install of OpenWRT 18.06. I've updated all of the packages. lagdrop.sh is installed in /root/. My Switch is connected directly to the router via an Ethernet adapter.

I just tried setting it up with the "debug" options and didn't have any luck. Every now and then a random IP will show up, but nothing that was unique per game. Tried it with my computer's IP and my phone's IP and nothing came up. Maybe the IP filter is too strict? No luck removing the -l flag.

Here's the commands we're working with: [image: commands] https://user-images.githubusercontent.com/196429/57575775-2e3bf400-741f-11e9-96c7-40d0901b632a.PNG

Thanks for the help, I really appreciate it!

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/42Kmi/LagDrop/issues/5#issuecomment-491551117, or mute the thread https://github.com/notifications/unsubscribe-auth/AEYWUGPGHH5OZDHQ22DSOALPU5IB7ANCNFSM4HL7UO3A .

[Driphter]

I just played against a few people on the latest update and no peer showed up. :( Maybe it's a location thing? I'm in MI, USA if that helps. I might try DD-WRT at some point, it's just a matter of finding a good day to do it, since I'm going to have to kick everyone and everything off of the internet to do it lol.

[42Kmi]

I don't have anything specifically blocking Michigan. That would be weird if I did. If you updated within about 1 hour of when I wrote this reply, I did push another update.

On Sun, May 12, 2019 at 3:56 PM Driphter notifications@github.com wrote:

I just played against a few people on the latest update and no peer showed up. :( Maybe it's a location thing? I'm in MI, USA if that helps. I might try DD-WRT at some point, it's just a matter of finding a good day to do it, since I'm going to have to kick everyone and everything off of the internet to do it lol.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/42Kmi/LagDrop/issues/5#issuecomment-491624418, or mute the thread https://github.com/notifications/unsubscribe-auth/AEYWUGIKD2RULGD3DLICWSLPVBZALANCNFSM4HL7UO3A .

[42Kmi]

Hold off on installing DD-WRT. I might be onto something now. I think I finally solved. Thanks for bearing with me. I'll let you know when to update again.

On Sun, May 12, 2019 at 4:01 PM Torengo torengo@42kmi.com wrote:

I don't have anything specifically blocking Michigan. That would be weird if I did. If you updated within about 1 hour of when I wrote this reply, I did push another update.

On Sun, May 12, 2019 at 3:56 PM Driphter notifications@github.com wrote:

I just played against a few people on the latest update and no peer showed up. :( Maybe it's a location thing? I'm in MI, USA if that helps. I might try DD-WRT at some point, it's just a matter of finding a good day to do it, since I'm going to have to kick everyone and everything off of the internet to do it lol.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/42Kmi/LagDrop/issues/5#issuecomment-491624418, or mute the thread https://github.com/notifications/unsubscribe-auth/AEYWUGIKD2RULGD3DLICWSLPVBZALANCNFSM4HL7UO3A .

[42Kmi]

Could you run this in your terminal and send a screenshot of the result?

tail +1 "/proc/net/nf_conntrack"|grep -Ev "^192.168.1.13"|grep -Eo "(([0-9]{1,3}.?){3}).([0-9]{1,3})"|sort -u|grep -Ev "^192.168.1.1"|grep -Ev "^192.168"

On Sun, May 12, 2019 at 4:42 PM Torengo torengo@42kmi.com wrote:

Hold off on installing DD-WRT. I might be onto something now. I think I finally solved. Thanks for bearing with me. I'll let you know when to update again.

On Sun, May 12, 2019 at 4:01 PM Torengo torengo@42kmi.com wrote:

I don't have anything specifically blocking Michigan. That would be weird if I did. If you updated within about 1 hour of when I wrote this reply, I did push another update.

On Sun, May 12, 2019 at 3:56 PM Driphter notifications@github.com wrote:

I just played against a few people on the latest update and no peer showed up. :( Maybe it's a location thing? I'm in MI, USA if that helps. I might try DD-WRT at some point, it's just a matter of finding a good day to do it, since I'm going to have to kick everyone and everything off of the internet to do it lol.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/42Kmi/LagDrop/issues/5#issuecomment-491624418, or mute the thread https://github.com/notifications/unsubscribe-auth/AEYWUGIKD2RULGD3DLICWSLPVBZALANCNFSM4HL7UO3A .

[Driphter]

To answer an earlier question, I have nf_conntrack, but no ip_conntrack.

Here's the result of that command:

I didn't have the Switch on when I did it though. Did you mean for me to do it while in a game with a peer?