Syncthing through the ethernet to other device

User Support
,
5

Sorry for that, I’m reall new to network things, and the setups are really complicated, I missed what should I explain.

In fact, I resolved the question already.
I didn’t fully complete firewall settings, but it seems work.
The problem was that I didn’t insert the device addresses after registering device IDs. After I write like tcp:// 192.168.0.3:22000 in device addresses entries, they successfully shares the folder.

But honestly, I also don’t fully understand what I should set up.

Here are what I’ve done.

  1. (Physical setup) I connect my phone and laptop by LAN card. Laptop – (LAN cable) – (LAN card with USB-C) – Android phone
  2. (Qubes setup) Disposable netvm for ethernet sys-eth, firewall for ethernet sys-eth-firewall and destination qube ss
    2-1. sys-eth, sys-eth-firewall, and ss are all dispVM.
    2-2. I set up already on the templateVM of ss by following instructions : [[Split-syncthing]], and [[Use qubes-sync with multiple clients and one server]]
    2-3. sys-eth, sys-eth-firewall are constructed by following the instructions in Disposable customization | Qubes OS named disposables for service qubes
  3. (IP setup) Use static ips. On the network option of sys-eth, I use 192.168.0.2 with gateway 192.168.0.1 and subnet mask 255.255.255.0. On my phone, I set up 192.168.0.3 with same gateway and subnet mask.
  4. I try to build the firewall by following the above instruction, but here are the problems:
    4-1. ping 192.168.0.3 443 doesn’t work but ping 192.168.0.3 works.
    4-2. When I run the command nft list table ip qubes,
chain custom-forward {
  iif "ens6" ip saddr 192.168.0.0/24 ip daddr <sys-eth-firewall ip address> tcp dport 443 ct state new,established,related counter packets 7 bytes 448 accept
}

is shown. (Why 192.168.0.0? Not 192.168.0.3)
The same problem occurs for each qubes;sys-eth-firewall and ss

  1. Despite of these problems, ping 192.168.0.3 works in sys-eth-firewall and ss
  2. Despite of these problems, syncthing works. I guess it’s because direct connection is established, but no firewall filtered.

I’m not sure this is helpful to understand my setup.