Vadim Smirnov

Forum Replies Created

Viewing 15 posts - 316 through 330 (of 1,507 total)
  • Author
    Posts
  • in reply to: ALLOWED DOMAIN #12807
    Vadim Smirnov
    Keymaster

      You can configure access to a desired domain over VPN if it consistently resolves to the same IP addresses. For instance, ntkernel.com resolves to 95.179.146.125. In this case, you can add this IP address to the AllowedIPs to access it via VPN. However, if the domain name resolves to varying IP addresses, such as with dynamic DNS or a CDN hosted site, this method is not supported.

      in reply to: Trying to understand the Bridge example #12792
      Vadim Smirnov
      Keymaster

        There are two possible approaches to Ethernet bridge implementation:

        1. Turn on promiscuous mode on both bridged interfaces and relay packets between these.
        2. Do MAC address translation. This approach is similar to how IP address NAT implemented.

        EBRIDGE sample implements the first, it is a bit slower (due to using promiscuous mode) but easier to understand. The only complex part is bridging Wi-Fi to wired LAN, where you still need the MAC address translation.

        I would also recommend unchecking the IPv4/IPv6 protocols on the NIC’s you are bridging, especially if you are using MAC address translation because it tends to confuse some routers (two IPs on the same MAC).

        Since both your network adapters are wired, the simple approach should work. Just forward packets received from one to another and vice versa without changing them.

        in reply to: How can I exclude domains in WireSock? #12789
        Vadim Smirnov
        Keymaster

          You are right, only IP addresses are currently supported.

          It is possible to monitor DNS queries and maintain a dynamic database of IP addresses translated to specified FQDNs. But this will only work for traditional DNS, if you are using DNS over HTTPS then these DNS requests cannot be intercepted and traffic routed correctly. I’m not sure if such a feature is in high demand, but I’ll consider adding it when I have some free time.

          in reply to: error when using ipv6 address as endpoint #12784
          Vadim Smirnov
          Keymaster

            Thanks for reporting this. Hopefully I have fixed this in v1.2.16. Please give it a try.

            in reply to: Suddenly stopped working #12780
            Vadim Smirnov
            Keymaster

              Glad you finally solved it! ☺️

              in reply to: Suddenly stopped working #12778
              Vadim Smirnov
              Keymaster

                If this does not work only on a particular Wi-Fi, then the first thing I would do is check the MTU. Try to put 1380 or even 1280.

                in reply to: Suddenly stopped working #12776
                Vadim Smirnov
                Keymaster

                  Thanks, I checked the log and it looks strange. The tunnel appears to be broken at the very beginning, immediately after receiving the response to the handshake. I also noticed that you are running a SOCKS proxy on the same host as the WireGuard Server. I’ve never tested this setup and can’t exclude some sort of network collision going on. Have you tried disabling the SOCKS5 proxy feature? Also could you update to the latest WireSock client 1.2.15? It will be easier if we use the same build.

                  in reply to: Suddenly stopped working #12774
                  Vadim Smirnov
                  Keymaster

                    Are you by any chance running two wireguard clients with the same configuration (keys, etc.)? In such a case, two (or even more) clients will compete for the same slot, causing tunnel errors from time to time.

                    If not then some logs could help to understand the problem.

                    in reply to: нет доступа в интернет. #12772
                    Vadim Smirnov
                    Keymaster

                      В режиме прокси тоже не работает?

                      Можно запустить как приложение и посмотреть/записать логи. Должно стать понятнее.

                      in reply to: Inspecting packet flows modified by WinpkFilter #12769
                      Vadim Smirnov
                      Keymaster

                        Yes, you are right about ExitLag, it does indeed use WinpkFilter to intercept and process network traffic. However, I’m afraid the only way I can suggest for researching how it affects traffic flow is to create two winpkfilter-derived drivers and set one above and one below ExitLag in the stack. Thus, you can capture and record the traffic from these two drivers, save to a PCAP file, and analyze the difference in Wireshark.

                        in reply to: WireSock – SOCKS5 over Trojan #12763
                        Vadim Smirnov
                        Keymaster

                          Hmm, looks like the problem is in v2rayN. Perhaps his SOCKS5 implementation has issues with UDP support.

                          in reply to: WireSock – SOCKS5 over Trojan #12761
                          Vadim Smirnov
                          Keymaster

                            It would be helpful to look at the log/PCAP files, however, I would check to see if the handshake packet is being blocked by Windows Firewall on another machine.

                            Off topic:
                            Your website blocked in my country, so I need VPN to access it.
                            Your web server also disallows to accept a post or comment from any kind of non-personal IP address.
                            I had a really hard time to overcome this issue!

                            SPAM is a real problem, but I’ve just adjusted the spam protection settings a little, I hope this improves your situation.

                            in reply to: WireSock – SOCKS5 over Trojan #12758
                            Vadim Smirnov
                            Keymaster

                              The problem is using a locally running SOCKS5 proxy (127.0.0.1:1080). WireSock does not currently support this option, it is assumed that the SOCKS5 proxy is running on another machine.

                              in reply to: Smb over wiresock as allowed app #12757
                              Vadim Smirnov
                              Keymaster

                                I wouldn’t say it’s anything complicated, just another filter similar to the existing DNS redirect implementation. But at the same time, it requires adding new configuration options and some tests. All in all, it will probably take me a day. So I guess if I won’t have anything urgent, I can dedicate a day to it next weekend.

                                in reply to: Smb over wiresock as allowed app #12753
                                Vadim Smirnov
                                Keymaster

                                  I think the SMB redirector runs in the context of a system process, so adding something like this to AllowedApps will tunnel more than you really need. However, I think I can add a new setting called AllowedPorts to have AllowedPorts = tcp:139, tcp:445 force SMB traffic into the tunnel.

                                Viewing 15 posts - 316 through 330 (of 1,507 total)