View captureInterface Timestamp SRC DST outputIGC2_Cisco6co_ETH3_CAT7blueigc2 2024-10-0918:45:13.458246 Tablet MAC LAN2 MAC IPv4, length 688: 192.168.102.103.48346 > Public IP : tcp 622IGC2_Cisco6co_ETH3_CAT7blueigc2 2024-10-0918:45:13.570098 LAN2 MAC Tablet MAC IPv4, length Public IP > 192.168.102.103.48346: tcp 0IGC2_Cisco6co_ETH3_CAT7blueigc2 2024-10-0918:45:13.580465 LAN2 MAC Tablet IP IPv4, length 480: Public IP > 192.168.102.103.48346: tcp 414IGC2_Cisco6co_ETH3_CAT7blueigc2 2024-10-0918:45:13.584274 Tablet MAC 192.168.102.103 LAN2 MAC IPv4, length 66: 192.168.102.103.48346 > Public IP.443: tcp 0IGC2_Cisco6co_ETH3_CAT7blueigc2 2024-10-0918:45:17.972276 Tablet MAC 192.168.102.103 LAN2 MAC IPv4, length 74: 192.168.102.103.33891 > Public IP.443: tcp 0IGC2_Cisco6co_ETH3_CAT7blueigc2 2024-10-0918:45:18.875502 Tablet MAC Unknown MAC or IPv6 ? IPv4, length 133: 192.168.102.103.5353 > Public IP.5353: UDP, length 91IGC2_Cisco6co_ETH3_CAT7blueigc2 2024-10-0918:45:19.089311 Tablet MAC LAN2 MAC IPv4, length 66: 192.168.102.103.38107 > Public IP.443: tcp 0IGC2_Cisco6co_ETH3_CAT7blueigc2 2024-10-0918:45:21.742308 Tablet MAC LAN2 MAC IPv4, length 66: 192.168.102.103.60959 > Public IP.443: tcp 0IGC2_Cisco6co_ETH3_CAT7blueigc2 2024-10-0918:45:21.863101 LAN2 MAC Tablet MAC IPv4, length 66: Public IP.443 > 192.168.102.103.60959: tcp 0IGC2_Cisco6co_ETH3_CAT7blueigc2 2024-10-0918:45:21.866320 Tablet MAC LAN2 MAC IPv4, length 66: 192.168.102.103.60959 > Public IP.443: tcp 0IGC2_Cisco6co_ETH3_CAT7blueigc2 2024-10-0918:45:24.643595 Tablet MAC LAN2 MAC IPv4, length 74: 192.168.102.103.46383 > Public IP.443: tcp 0IGC2_Cisco6co_ETH3_CAT7blueigc2 2024-10-0918:45:24.665528 LAN2 MAC Tablet MAC IPv4, length 74: Public IP.443 > 192.168.102.103.46383: tcp 0IGC2_Cisco6co_ETH3_CAT7blueigc2 2024-10-0918:45:24.669333 Tablet MAC LAN2 MAC IPv4, length 66: 192.168.102.103.46383 > Public IP.443: tcp 0
Quote from: cookiemonster on October 10, 2024, 10:04:00 pmAh!. Unlikely unless you hare doing something wacky with certificates and breaking TLS.Some of those use certificate pinning.If it is so, then it's completely out of my wish/controle, I just use the tablet the same way I did while connected to my previous router, which was much of a strainer, letting most going through, hence me on OPNsense nowQuote from: cookiemonster on October 10, 2024, 10:04:00 pmTo me the next step in diagnostic is to do a packet capture and analysis.I would be happy to oblige, using the search I found "packet capture" and set it up to interface LAN2, IP 192.168.102.103 (Tablet)And will post it belowQuote from: cookiemonster on October 10, 2024, 10:04:00 pmYou are using Unbound, right ?And do they (the apps) give some error or some indication of the problem?Unbound, yeswith or without blocklist (AdWare, ...) doesn't change anythingThe app asks for passphrase, then spin for about a minute and then drop saying: -"Sorry, there was an issue processing your request, please try again later" kinda standard msg
Ah!. Unlikely unless you hare doing something wacky with certificates and breaking TLS.Some of those use certificate pinning.
To me the next step in diagnostic is to do a packet capture and analysis.
You are using Unbound, right ?And do they (the apps) give some error or some indication of the problem?
Great. That diagram works.So where is the VPN, an app installed on a device, which one?I thought you meant the VPN was set as a VPN client on OPN to a provider like say Surfshark or even a rented vps. Can you elaborate?p.s. you seem to have two ips on the same network for the same device (NAS). That can cause problems, unrelated to these apps though.
Quote from: MarieSophieSG on October 10, 2024, 11:43:12 pmThe NASes have two network interfaces,NAS1 has 2x 2,5 GbE and NAS2 has 2x 1GbE, with a failover (if one is down, or one is overloaded, traffic goes to the other)Each independant from the other, so I can, if I want, connect 1 laptop to 192.168.101.111 as root, and 1 laptop to 192.168.101.112 as userThis is fundamentally impossible in networking. A system cannot have two interfaces in a single network. Period.One possible cause of your problems.
The NASes have two network interfaces,NAS1 has 2x 2,5 GbE and NAS2 has 2x 1GbE, with a failover (if one is down, or one is overloaded, traffic goes to the other)Each independant from the other, so I can, if I want, connect 1 laptop to 192.168.101.111 as root, and 1 laptop to 192.168.101.112 as user
But *I am* connected to both interface ...
Then everything works as you intend it to do and we can close all the threads. Right?