Jump to content

ljm42

Community Developer
  • Content Count

    1572
  • Joined

  • Last visited

  • Days Won

    8

ljm42 last won the day on September 2

ljm42 had the most liked content!

Community Reputation

158 Very Good

2 Followers

About ljm42

  • Rank
    Advanced Member

Converted

  • Gender
    Undisclosed
  • Personal Text
    the answer to life, the universe, and everything

Recent Profile Visitors

2292 profile views
  1. Try the timeout command: timeout 10 wget --user=user--password='pw' ftp://adr:port/file -O /root/keyfile That will start wget and then kill it if it is still running after 10 seconds. More details here: https://www.howtoforge.com/linux-timeout-command/
  2. Wireguard is very difficult to troubleshoot because it fails silently - there are no error messages or logs. But based on what you've said, it sounds like your port forward isn't working correctly. By default the guide gets you setup with one of the "split tunneling" options, where only traffic destined for your server (or LAN) goes through the tunnel. If you want all your traffic to go through the tunnel you need to choose the "Remote tunneled access" option instead. I'd suggest getting "Remote access to LAN" working first though.
  3. Try getting a free config from TunSafe and comparing them to see what is different? Also note the comment about DNS in the OP
  4. Am I wrong or does their implementation require you to use their NordLynx client? If so that won't work with the standard WireGuard client that we use. If you can provide a link that shows how to download a standard WireGuard config file, I'll link to that.
  5. The problem seems to be unique to your installation of Firefox. Try a new Private Window in Firefox. If that doesn't work, create a new blank profile: https://support.mozilla.org/en-US/kb/profile-manager-create-remove-switch-firefox-profiles
  6. That is a good data point, thanks! Oh and for the record, I am using UPnP. With bridging (not bonding) on br0.
  7. It isn't just you. I complicated my network a bit to try and reproduce this, and I'm seeing it too. I amended the guide to acknowledge this. Still looking for a solution. I'm glad everything is working for you @nuhll, but your network is rather unique I'm not sure how we can leverage that into a solution that will work for everybody.
  8. I have amended the guide, there is now a section for "Complex Networks" that talks about setting "Use NAT" to "No" and adding a static route in your router. This is needed if you have Dockers with custom IPs or certain VM setups. These changes should allow everything on the network to work normally. However, as several people have seen, your WireGuard clients may not be able to access those Dockers or VMs. This still needs to be figured out. If you find a solution, please comment
  9. Not sure what happened, but hopefully you saw this in the Troubleshooting section of the guide:
  10. Activity with no handshake is odd, I don't think I have seen that before. Not sure what you mean by "static route"? Are you trying to get around issues with VMs or dockers? I'd remove that until you get the basics down first. i'd recommend you start with the scenario in the guide, "remote access to LAN". If you can get that working that will prove all the basics are good. If you have issues with that, go through the troubleshooting section with a fine tooth comb. Once you have the basics working you can move on to the other options.
  11. No, as mentioned in the first post, you really need to trust the people that you give this VPN access to. Regardless of which access type you choose, assume the user could get full access to your LAN. If you really want to do it, you could potentially put WireGuard on a raspberry pi on its own VLAN. But that is well beyond the scope of what we are trying to do with this plugin.
  12. Depends on what you are trying to do. See the description and diagram in the first post of this thread.
  13. OK, so 192.168.20.1 is the direct IP of your router, without using VPN. And 10.8.0.1 is some sort of VPN running on your router? I see no evidence of Unraid being used as a gateway or anything super strange like that. I would look closer at how your router determines whether to send traffic through 10.8.0.1 or 192.168.20.1. Is it based on IP address or MAC address maybe? If so, you'll have to figure out why the router thinks the IP or MAC has changed.
  14. On the VM, try running "tracert www.google.com" in various configurations and see what changes. That will show you the path that the system is taking to get out to Google.
  15. I don't use dockers with custom IPs. The best information is in this thread, I'd suggest following the discussion over there rather than starting a new one Not that I can see. As mentioned in the OP, I'd suggest using a hosts file if you must have name resolution. You could possibly use the LAN's DNS server, but that doesn't make sense for split tunneling.